Solution Explorer -Dll Error (SP23_M1)

ARJOHNSON

Active Member
Hi Everyone.
We are currently in the process of upgrading to SP23_M1. I ran a client install (SP23) on a Win 2003 Server (standard edition) machine. I have received no errors on any of our other machines (however the machine receiving the error is the only Win 2003 machine-- all others machines are Win2k and XP)

The Install finished successfully on the Win2003 server. However I'm receiving a dll error when trying to access OW via Solution Explorer:

(Taken from JDE.log)
5508/2684 Tue May 09 14:43:32 2006 jdb_ctl.c2763

Starting OneWorld

>5508/2684 Tue May 09 14:43:54 2006
>activConsole.cpp913
>
> Unable to register activReleaseDate.dll. Exiting.

I found that this was an issue with SP23_L1.. but was supposedly fixed.. Anyone else seen this? I did try and register the Dll.. by running regsvr32... but received an error that way also. Do I need to try and register the other Dlls (parent/child type situation).. there are 23 other activReleaseDate_*.dlls???
confused.gif


Any help would be appreciated. Thanks!

Angie
OneWorld Xe
Development- B7333, SP23_M1
Prototype and Prod--B7333, Service Pack 22_T1, Update 7
AS/400 DB2
 
We experienced the same error when we upgraded from SP23_H1 to SP23_M1. It is only a problem when deploying to workstations that have never had OneWorld on them before. We copied module activReleaseDate.dll from our SP23_H1 system folder(B7\system\Bin32) to our SP23_M1 system. You will need to rerun the foundation only client build to get the dll into the system.cab (SYSTEMCOMP) which is used in the client deploys. I hope this helps!
 
Thanks for the information! However this machine I'm installing SP23 on does have the Production path code installed on it (for SP22). We are using snapshot to save off SP22. We have installed SP23 on other machines (Win2k and XP) with no issues.
 
Response from Oracle in regard to ActivReleaseDate.dll issue:

"Regarding the issue you are facing with activereleasedate.dll,as per the SAR # 7925364 ,the issue was resolved in sp23_L2, sp23_M1 and forward. However during my research I found that although the issue was resolved in SP23_L2, it appears that a bad dll has again been delivered in SP23_M1."
 
Back
Top