ESU Backup functionality not working

[Joel]

Hello,
We recently migrated our deployment server from a Windows 2000 server to Windows 2003. This was done in the month of July. We are on Tools release 8.95.F1. We have now observed that when applying an ESU with the backup checked the tables in the OWBAK_PGxxx_xx810 are completely empty. All ESU's except one have been successfully applied in DV and pristine. This problem with the backup was realised when we applied an ESU which failed in the spec merge. When trying to restore from backup it was noticed that all backup tables are without data.
The error in the JDE Log is:-
6036/368 WRK:Starting jdeCallObject Thu Dec 07 09:33:34.121001 MSDEDBAPI.cpp821
MSDE000013 - SQL grantUser failed for 'OWBAK_PG4004_PS810'

6036/368 WRK:Starting jdeCallObject Thu Dec 07 09:33:34.121003 MSDEDBAPI.cpp965
[Microsoft][Microsoft SQL Server Driver]User or role 'JDE' already exists in the current database. SQLSTATE: 42000 HRESULT:0X80040E14 Native Error:15023.

6036/368 WRK:Starting jdeCallObject Thu Dec 07 09:33:48.247011 SpecOpen.c1727
JDESPEC0000006 - Bad Pathcode or Data Source provided to open up Central Objects! Either a path code (empathd col in F00942) or a deployment data source (emdats col in F00942) must be passed in. Bad DS or Path Code = OWBAK_PG4004_PS810

6036/368 WRK:Starting jdeCallObject Thu Dec 07 09:33:48.247014 SpecOpen.c2233
jdeSpecOpenIndexed completed in error - Operation failed!.

 

[peterbruce]

Joel,

I have never known the ESU backup to work and have never used it. It still deosn't work in 8.11 sp1 and tools 8.96. You can back out an ESU by taking the "Remove Update" form exit in the "Electronic Software Updates" or "Application Software Updates" applications.

 

[Joel]

LOL, it used to work in our setup untill we migrated our deployment server to Windows 2003. After migration it worked just once.