Han Brinkman
28th September 2005, 14:25
I experience problems with the latest portingsets (after 7.1d.05) on Windows. After 7.1d.05 SSA is using a new installation methode.

When we install a new server we just copy the baan directory to the new server, install the portingset (to create the registry settings), do our database things. Now I have to install first 7.1d.05 and after that I can use one of the later portingsets to upgrade it. Installing e.g. 7.1d.08 I get errors like 'Can start service' and 'Windows registration error'.

I have a workaround, created a case for it but I am wondering if more people have problems with the new installation methode.

Regards,
Han

rochus
28th September 2005, 18:31
i had similar problems on w2k and windows2003,
installation process aborts , logile contents, "could
not copy some files"
always with newer portingsets, no idea why
i tried several ps, one works at the end

Martin
29th September 2005, 10:03
Yep, the same problem here.

I do the following :

copy BSE environment from old server to new server
copy the Baan-Installation from c:\baan\winnt\baan (you must look, where it is installed) to the new server c:\windows\baan.

Now the Problem is, that you had no services for baan.

I had created the services with srvinstw.exec from MS Resource Kit on the new Server exactly as they are installed in old server.

Start services.

Update Portingset.

The next Problem is, that you had no Program Group Baan and the old copied BECS won't work. --> Install the prefered Client for the new Portingset on the new server, then it works.

hope this helps

martin

EDIT:

the registry setting i had exported from registry of old server, modified and import in registry in new server