I've just upgraded my production server to 11.5.1 from 11.5 and am getting the following in the AppServer (old style) logs.
[15/10/25@20:11:01.223+0000] P-007924 T-007928 1 AS -- The shared memory is version 6413507; expected 6413506 (1178)
[15/10/25@20:11:01.224+0000] P-007924 T-007928 1 AS -- Error initialising the application server. (5479)
I'm restarting everything but am concerned it won't work. Anyone else experienced this. Any ideas?
Ok seems i might have to reapply the service pack. Trying that now.
Reapplied the SP and still the same. This is rather worrying. Next logical step would be a full reinstall of Progress. Which want to avoid.
What platform? Try with _progres. Check the dates on _progres vs _proapsv. Check if _proapsv is in the SPBackup dir.
Win 2012 R2 64 bit.
I'm reinstalling. Hitting some really strange things. The installer keeps crapping out. Meh.
Are there still some Progress processes running while installing the SP? Can you verify is all was extracted successfully?
Run as Administrator?
Thanks Mike yes running as admin. One file in c:\progress\OpenEdge wouldn't delete - the cfg file of all things. I had to forcibly delete it and now we're up and running. I suspect that this file was the cause of the problems.
Love how a "quick" job often progresses into something long with Progress!
Tom will be along shortly to remind me this is only the case if you haven't installed the Linux patch I'm sure.
Certainly with *nix, I am always installing any point release in a new directory with the old one still there so that one can switch back and forth and they don't step on each other. SPs, though, tend to go on top.
Full reinstall has sorted it. Thanks for input guys.
Next time use process Explorer to find out which process still had the file open.
Or you can use the handle.exe command line tool, also from sysinternals.
Feeling very special this morning. I worked out what the problem was. We have copies of _proapsv.exe named after the AppServer names in OEE so we can track down the individual PIDs more easily when things go wrong. Helps if you refresh those .exe files after installing the SP doesn't it.
The blocked cfg file was a red herring.
Warning : untested
You can try to make a link instead of a copy.
On windows : mklink target source, on linux : ln -s source target
oe115 C:\Progress\oe115\bin> mklink asbroker1_proapsv.exe _proapsv.exe symbolic link created for asbroker1_proapsv.exe <<===>> _proapsv.exe