I also search for some place to find archived updates, i think they had an ftp for that earlier… But at last i took a look at the link to 8504 and simply changed it to 8503 instead, naming standards are great :).
8504:
Regards,I performed the actions according to your list, but the update still fails.If I try to run the "startDB.bat" after the update failed, I get an error message reading "\PMP\scripts\\..\conf\serverstate.conf was unexpected at this time".I continued to perform some additional troubleshooting and compared the startDB.bat before and after the update. One line was changed, line 50.The original reads:FOR /f "eol=; tokens=1*" %%x IN (..\conf\serverstate.conf) DO SET SSTATE=%%xwhile the updated version reads:FOR /f "eol=; tokens=1*" %%x IN (%SERVER_HOME%\conf\serverstate.conf) DO SET SSTATE=%%xJust to test I created a backup of the startDB-file. I then started the update process and kept an eye on the time-stamp of the startDB-file in the bin-folder. As soon as the time-stamp changed, I replaced the file with my original backup. Now the update process worked just fine, everything is up and running on version 8504. I haven't performed this action in production, only in a cloned offline environment since it seems a bit risky.
Jonas