View Full Version: Windows 2003 Upgrade

LawsonTalk > UPGRADE: All other upgrades > Windows 2003 Upgrade



Title: Windows 2003 Upgrade
Description: O/S Upgrade Problems


achapa1 - March 21, 2006 04:08 PM (GMT)
We are having tons of problems with this upgrade due to the Lawson change of no longer supporting Windows 2000. The upgrade to 2003 gave us so many problems that we decided to revert back to W2K. Well, that didn't go easily either, and were spending so much time on this that we decided to start from scratch with a new box. I have currently installed all the software with the W2K3 O/S and still have not cleaned up all the errors. Luckily this was our test environment, but we are going on almost two full weeks without a test environment that it has pushed many projects down by that same amount of time. Has anyone else tried this upgrade and experienced any problems? My current problem is with shmget size too large error. I know it has something to do with shared memory, but I can't seem to find anything specific to the windows environment. Does anyone have any clues that might help us resolve this error?

forestearly - March 21, 2006 11:00 PM (GMT)
What version of the environment are you on before and after upgrading the OS?
What are your laconfig settings for each?

achapa1 - March 23, 2006 05:44 PM (GMT)
I am using Env 8.0.3 (same before and after upgrade) and what specifically are you looking for in laconfig? Like I also mentioned before I even began with a brand new box so that we don't get any conflicts from a prior version, but we did. I even downloaded the latest version of the MKS Toolikt (9.0 to be exact) and even though it is just an evaluation version, I was hoping that it might be involved in configuring something with shared memory, but it didn't make a difference either. I am starting from scratch again and going with Windows 2000 because even though Lawson doesn't support it, I know it worked before our upgrade. I will setup another box with an older version of Win 2003 and test it one last time, but that's not going to happen for a few weeks because we have too many projects that are on hold with the loss of our development server. If anyone has done an O/S upgrade successfully, please let me know if you encountered any problems because I haven't heard of anyone that has been able to do this with a system like ours which is a basic configuration in my opinion.

Milo - March 23, 2006 07:01 PM (GMT)
We are doing the same thing - migrating from Win2K to Win2k3. Also on 8.0.3/8.0.3 ... I'll watch out for any trouble at our end.

My boss suggests that you check for a bad starting address in memory. A bad address seems to manifest itself in shared memory problems.

forestearly - March 24, 2006 01:57 PM (GMT)
803 is the first requirement, so you should be in good shape there.
Like the last post - I would start w/ the memory address. However, before I would suggest try this/try that I would look at all the numeric values as a whole.

e.g. What are your current laconfig settings on your working production environment?

From that you can tune up to 2003.




Hosted for free by InvisionFree