Critical Patch Error copying ORACORE10.DLL on a Win2K SP4 Server

In running the opatch apply for the CPUApr2007 critical patch on a 10.2.0.3 database, it fails to copy file oracore10.dll. I'm assuming that some process is using the DLL, but it's not Oracle. All Services relating to Oracle have been stopped. I then set them to manual start and rebooted the server, but the patch still balks that it can't copy the file. I remember back with Oracle 6i Developer Installs that you have to rename the bin directory, reboot, and then revert it to bin again, and that would resolve the problems with copy-type errors. I'll try that when I get back into the office. I do have a full backup, of course, and the services start normally after an opatch rollback, but I'm wondering whether anyone else has run into this, and what they might have done to resolve it.
Thanks for your time.
Phil

Thanks Chris. That's a must get download. But what I did to get around it was to stop the Oracle Services, set them to manual, rename the %ORACLE_HOME%\bin to %ORACLE_HOME%\TempBin, and then reboot the server. With the server up, Oracle down, and Microsoft not doing me any favors by preloading any Oracle DLLs, the patch installed without incident...(Note to Bill Gates...Stop messin with my DLLs!!!)

Similar Messages

Error with oracore10.dll !!!!

Hello all,
We are implementing a home grown application.
The APP server is MS 2003 and uses IIS 6.0 and contains Oracle Runtime Client 10.2.0.4
The database is 10.2.0.4 on 2 node RAC on Solaris 10.
When we started the UAT, the APP server(IIS) gets hanged at times for around 2-3 mins and would return back as if nothing has happened. This occurs very often. We used the DebugDiag from MS to trace the IIS and took the dump and in it, it seems like a request goes to the DB server and it gets timed out. There are no "timeout" things mentioned at the database side (profile as well as sqlnet.ora).
Below is the message from DebugDiag tool.
The following threads in w3wp.exe__DefaultAppPool__PID__4880__Date__04_17_2009__Time_03_18_24PM__171__IIS_COM+ Hang Dump.dmp are making a database operation using ADO.
The call to MSADO15!CCOMMAND::EXECUTE originated from vbscript!CatchIDispatchInvoke+46
( 25 28 29 )
7.50% of threads blocked
Detected possible blocking or leaked critical section at 0x02bafe28 owned by thread 37 in w3wp.exe__DefaultAppPool__PID__4880__Date__04_17_2009__Time_03_18_24PM__171__IIS_COM+ Hang Dump.dmp
Impact of this lock
5.00% of threads blocked
(Threads 32 39)
The following functions are trying to enter this critical section
oracore10!sltsmna+f
The following module(s) are involved with this critical section
D:\oracle\product\10.2.0\client_1\BIN\oracore10.dll from Oracle Corporation
Thread 32 - System ID 4208
Entry point msvcrt!_endthreadex+2f
Create time 4/17/2009 3:18:08 PM
Time spent in user mode 0 Days 00:00:00.671
Time spent in kernel mode 0 Days 00:00:00.343
This thread is waiting on critical section 0x02bafe28 which is owned by thread 37
Function Source
ntdll!KiFastSystemCallRet
ntdll!NtWaitForSingleObject+c
ntdll!RtlpWaitOnCriticalSection+1a3
ntdll!RtlEnterCriticalSection+a8
oracore10!sltsmna+f
oranl10!snltmgms+59a5
oranl10!nltrcwrite+49
orantcp10!snttclose+5619
oran10!ztvull+1e58e
oran10!nsrdr+7f
oran10!nsdo+407
oran10!nsbrecv+1a
oran10!nioqrc+14d
oracommon10!ttcdrv+2c5
oran10!nioqwa+39
ORACLIENT10!upicui2+761
ORACLIENT10!upicui2+1a2
ORACLIENT10!upiosd0+2be
ORACLIENT10!upipi0+1c2f
ORACLIENT10!upiosd+29
ORACLIENT10!ocisq7+55
msorcl32!ServiceOCIWorkRequest+be
msorcl32!OCIWorkerThreadFunc+57
msvcrt!_endthreadex+a3
kernel32!BaseThreadStart+34
Thread 39 - System ID 5960
Entry point msvcrt!_endthreadex+2f
Create time 4/17/2009 3:18:23 PM
Time spent in user mode 0 Days 00:00:00.00
Time spent in kernel mode 0 Days 00:00:00.00
This thread is waiting on critical section 0x02bafe28 which is owned by thread 37
Function Source
ntdll!KiFastSystemCallRet
ntdll!NtWaitForSingleObject+c
ntdll!RtlpWaitOnCriticalSection+1a3
ntdll!RtlEnterCriticalSection+a8
oracore10!sltsmna+f
oranl10!snltmgms+59a5
oranl10!nltrcwrite+49
oran10!ztcrprocfini+2b76f
oran10!osncon+1e7
ORACLIENT10!kpuatch+4f9
ORACLIENT10!upicui2+a7d
ORACLIENT10!upikgt+502
ORACLIENT10!upikgt+55a
ORACLIENT10!kpuleqr+a3c1
ORACLIENT10!kpuleqr+beff
ORACLIENT10!kpuleqr+be5a
ORACLIENT10!upilog+75
ORACLIENT10!ocirlo+11f
msorcl32!ServiceOCIWorkRequest+10e
msorcl32!OCIWorkerThreadFunc+57
msvcrt!_endthreadex+a3
kernel32!BaseThreadStart+34
Does anyone have any clue on what will cause these kind of problem ?
Is it that a request is made to the DB server and there comes a timeout and IIS hangs ?
TIA,
J J

Hello Greg,
I checked the Bug 7585970, and the patch you mentioned is for "Error Updating A Long Raw Column Greater Than 64 kb".
We do not have any long columns and our situation is different.
Again we ran the DebugDiag and we always get this
Thread 55 - System ID 4948
Entry point       msvcrt!_endthreadex+2f
Create time       4/22/2009 12:39:34 PM
Time spent in user mode       0 Days 00:00:00.015
Time spent in kernel mode       0 Days 00:00:00.00
This thread is waiting on data to be returned from another server via WinSock.
The call to WinSock originated from orantcp10!snttclose+227 and is destined for port 1521 at IP address 10.108.123.13
Function       Source
ntdll!KiFastSystemCallRet
ntdll!NtWaitForSingleObject+c
mswsock!SockWaitForSingleObject+3a
mswsock!WSPRecv+203
ws2_32!WSARecv+77
orantcp10!snttclose+227
orantcp10!nttini+cec
oran10!ztvull+1e58e
oran10!nsrdr+7f
oran10!nsdo+407
oran10!nsbrecv+1a
oran10!nioqrc+14d
oracommon10!ttcdrv+2c5
oran10!nioqwa+39
ORACLIENT10!upicui2+761
ORACLIENT10!upirtrc+42
ORACLIENT10!kpudbcx+c9b
ORACLIENT10!kpuleqr+3d785
ORACLIENT10!upifcn+1d
ORACLIENT10!ocifen+44
msorcl32!ServiceOCIWorkRequest+88
msorcl32!OCIWorkerThreadFunc+57
msvcrt!_endthreadex+a3
kernel32!BaseThreadStart+3410.108.123.13 is the DB server. The DB server is working good and there are no err or trace files in the DB server.
Even when IIS and IIS Server hangs, i can login to the the DB server from my PC using the same credentials used by the application.
Any clue ??
TIA,
J J

Fatal error 78: Cannot connect to User Group LDAP Server

After configuring Calendar server when trying to start:
give following error:
# ./start-cal
Restarting calendar services
Stopping all calendar services
Starting all calendar services
# enpd is started
csnotifyd is started
csadmind is started
Fatal error 78: Cannot connect to User Group LDAP Server
cshttpd is not started
Calendar service(s) not started
cshttpd is not started
Calendar service(s) not started
Following logs are from http logs of calendar server
[13/Sep/2004:22:02:47 +0100] Vigor11 cshttpd[17916]: General Information: Log created (1095109367)
[13/Sep/2004:22:02:47 +0100] Vigor11 cshttpd[17916]: General Notice: Sun Java System Calendar Server 6 2004Q2 (built Apr 28 2004) cshttpd starting up
[13/Sep/2004:22:02:47 +0100] Vigor11 cshttpd[17916]: General Notice: cshttpd attempting to open Counters Database
[13/Sep/2004:22:02:47 +0100] Vigor11 cshttpd[17916]: General Notice: cshttpd successfully opened the Counters Database
[13/Sep/2004:22:02:48 +0100] Vigor11 cshttpd[17916]: General Notice: HTTP Module is refreshing
[13/Sep/2004:22:02:48 +0100] Vigor11 cshttpd[17916]: General Notice: cshttpd is refreshing
[13/Sep/2004:22:02:48 +0100] Vigor11 cshttpd[17916]: General Notice: cshttpd is refreshed
[13/Sep/2004:22:02:48 +0100] Vigor11 cshttpd[17916]: General Notice: HTTP Module has refreshed
[13/Sep/2004:22:02:48 +0100] Vigor11 cshttpd[17916]: General Notice: cshttpd: argc=3 argv[0]=/opt/SUNWics5/cal/lib/cshttpd
[13/Sep/2004:22:02:48 +0100] Vigor11 cshttpd[17916]: General Notice: session_init: attempting to open session database for cshttpd
[13/Sep/2004:22:02:49 +0100] Vigor11 cshttpd[17916]: General Notice: session_init: session database open completed for cshttpd
[13/Sep/2004:22:02:49 +0100] Vigor11 cshttpd[17916]: Store Critical: Error checking session database: DB->set_alloc: method not permitted in shared environment
[13/Sep/2004:22:02:49 +0100] Vigor11 cshttpd[17916]: General Notice: LdapCacheInit: Ldap Cache not enabled.
[13/Sep/2004:22:02:49 +0100] Vigor11 cshttpd[17916]: General Notice: cshttpd_parse_commandline: successfully bind process 17916 to processor 0
[13/Sep/2004:22:02:49 +0100] Vigor11 cshttpd[17916]: General Critical: Fatal error 78: Cannot connect to User Group LDAP Server
Have any body seen this before.
Regards

The server was running fine for few months until i restarted the calendar server. i started to see the same error and the problem was the machine name got changed at some point.
I added the old hostname to the /etc/hosts file and restarted the calender server and it started to work fine.

Error when try to install CPU - Critical Patch Update with OPatch

Hello gurus,
I´m faccing with a problem... After I update the patch set to 10.2.0.4 and install the interim patches for Linux X86_64 now I´m trying to import/install the Oracle Critical Patch Update - Oracle CPU patch!!
I´m trying to import it with OPatch, and I already update this OPatch tool for the last version even before proceeding with installation of Oracle CPU!
I've tried to import it by two methods. The first I tried to apply as described in the relevant README file inside of CPU patch directory, and I used in this case the following command:
redhatsap:orajmd> unzip p9119226_10204_<platform>.zip
redhatsap:orajmd> cd 9119226
redhatsap:orajmd> opatch napply -skip_subset -skip_duplicate
opatch: Command not found
After that previous error, I tried again but now with other method that is described in note 839182 (Installing patches using OPatch) with the following command:
redhatsap:orajmd> cd 9119226
redhatsap:orajmd> $ORACLE_HOME/OPatch/opatch apply
========================================================
GENERIC OPATCH VERSION - FOR USE IN SAP ENVIRONMENT ONLY
========================================================
Invoking OPatch 10.2.0.4.5
Oracle Interim Patch Installer version 10.2.0.4.5
Copyright (c) 2008, Oracle Corporation. All rights reserved.
Oracle Home       : /oracle/JMD/102_64
Central Inventory : /oracle/oraInventory
   from           : /etc/oraInst.loc
OPatch version    : 10.2.0.4.5
OUI version       : 10.2.0.4.0
OUI location      : /oracle/JMD/102_64/oui
Log file location : /oracle/JMD/102_64/cfgtoollogs/opatch/opatch2010-04-19_01-49-17AM.log
Patch history file: /oracle/JMD/102_64/cfgtoollogs/opatch/opatch_history.txt
Failed to load the patch object. Possible causes are:
The specified path is not an interim Patch shiphome
Meta-data files are missing from the patch area
Patch location = /oracle/JMD/102_64/9119226
Details = PatchObject constructor: Input file "/oracle/JMD/102_64/9119226/etc/config/actions" or "/oracle/JMD/102_64/9119226/etc/config/inventory" does not exist.
ApplySession failed: PatchObject constructor: Input file "/oracle/JMD/102_64/9119226/etc/config/actions" or "/oracle/JMD/102_64/9119226/etc/config/inventory" does not exist.
System intact, OPatch will not attempt to restore the system
OPatch failed with error code 73
Can you help me please?
Best regards
João Dimas - Portugal

Hello again Joe Bo... and all of others,
I´m with a doubt after installing the CPU patch, which is related to post-installation tasks. I´m in this momment install the SAP System and it was during this installation that sapinst asked me to install the database and all other activities after this installation that are related to the database, for example, the updating of database patches.
At README file in chapter 3.3.2 Post Installation Instructions is described the following:
After installing the patch, perform the following actions:
1.Load modified .sql files into the database, as explained in Section 3.3.2.1.
2.Recompile views in the database, if necessary, as explained in Section 3.3.2.2.
In this momment, as you certainly know, I still don´t have a database because the sap system isn´t yet totally installed (I´m in phase 8 of sapinst wizard).
I only have to do this "Post Installation Tasks" when I have a database, this database will be created after that phase 8 - so now I don´t need to perform the post steps... am I right?
Thanks in advance,
João Dimas - Portugal

Critical patch update fails with error code 73

RDBMS Version: 10.2.0.3
Operating System and Version: solaris 5.9
Error Number (if applicable): error code 73
Product (i.e. SQL*Loader, Import, etc.): oracle server enterpirse edition
Product Version: 10.2.0.3
Critical patch update fails with errors(urgent)
UD00_102030>pwd
/mnt/base_install/downloads/10gR2/cpu/6394981
UD00_102030> opatch apply
Invoking OPatch 10.2.0.3.0
Oracle interim Patch Installer version 10.2.0.3.0
Copyright (c) 2005, Oracle Corporation. All rights reserved..
Oracle Home : /u01/app/oracle/product/10.2.0
Central Inventory : /u01/app/oracle/oraInventory
from : /var/opt/oracle/oraInst.loc
OPatch version : 10.2.0.3.0
OUI version : 10.2.0.3.0
OUI location : /u01/app/oracle/product/10.2.0/oui
Log file location : /u01/app/oracle/product/10.2.0/cfgtoollogs/opatch/opatch2007-10-19_19-53-31PM.log
Failed to load the patch object. Possible causes are:
The specified path is not an interim Patch shiphome
Meta-data files are missing from the patch area
Patch location = /mnt/base_install/downloads/10gR2/cpu/6394981
Details = PatchObject constructor: Input file "/mnt/base_install/downloads/10gR2/cpu/6394981/etc/config/actions" or "/mnt/base_install/downloads/10gR2/cpu/6394981/etc/config/inventory" does not exist.
ApplySession failed: PatchObject constructor: Input file "/mnt/base_install/downloads/10gR2/cpu/6394981/etc/config/actions" or "/mnt/base_install/downloads/10gR2/cpu/6394981/etc/config/inventory" does not exist.
System intact, OPatch will not attempt to restore the system
OPatch failed with error code 73
This cpu oct 2007 patch for 10.2.0.3(for solaris)

That's great :) ...
Does anybody know which is the difference between
opatch napply
and
opatch apply ?
thanks,
P.

Critical SMS_NOTIFICATION_SERVER ERROR sccm 2012 R2 WITH SQL 2012 SP1

Environement
SCCM 2012 R2
SQL 2012 SP1
On the same server
In sccm console i have in Monitoring - System Status - Component Status
critical SMS_NOTIFICATION_SERVER ERROR
Here are the two error that keep popping up
ERROR 1016
Site Component Manager failed to install this component on this site system.
Solution: Review the previous status messages to determine the exact reason for the failure. Site Component Manager will automatically retry the installation in 60 minutes. To force Site Component Manager to immediately retry the installation, stop and restart
Site Component Manager using the Configuration Manager Service Manager.
Folowing message
ERROR 4951
Site Component Manager failed to install this component, because the Microsoft Installer File for this component (bgbisapi.msi) could not install.
Refer to the BgbSetup.log, the bgbisapimsi.log, as well as the ConfigMgr Documentation and the Microsoft Knowledge Base for further information.
Here are the 2 logs
bgbsetuplog
<02/28/14 09:00:53> ====================================================================
<02/28/14 09:00:53> SMSBGB Setup Started....
<02/28/14 09:00:53> Parameters: D:\Program Files\Microsoft Configuration Manager\bin\x64\rolesetup.exe /install /siteserver:TCI-SCCMR2-LAV SMSBGB 0
<02/28/14 09:00:53> Installing Pre Reqs for SMSBGB
<02/28/14 09:00:53>         ======== Installing Pre Reqs for Role SMSBGB ========
<02/28/14 09:00:53> Found 1 Pre Reqs for Role SMSBGB
<02/28/14 09:00:53> Pre Req SqlNativeClient found.
<02/28/14 09:00:53> SqlNativeClient already installed (Product Code: {D411E9C9-CE62-4DBF-9D92-4CB22B750ED5}). Would not install again.
<02/28/14 09:00:53> Pre Req SqlNativeClient is already installed. Skipping it.
<02/28/14 09:00:53>         ======== Completed Installation of Pre Reqs for Role SMSBGB ========
<02/28/14 09:00:53> Installing the SMSBGB
<02/28/14 09:00:53> Passed OS version check.
<02/28/14 09:00:53> IIS Service is installed.
<02/28/14 09:00:53> SMSBGB already installed (Product Code: {A78E8003-2307-4B70-B7CD-1A07C0A31D21}). Upgrading/Reinstalling SMSBGB
<02/28/14 09:00:53> New SMSBGB is the same product code. This is a minor upgrade.
<02/28/14 09:00:53> Enabling MSI logging. bgbisapi.msi will log to D:\Program Files\Microsoft Configuration Manager\logs\bgbisapiMSI.log
<02/28/14 09:00:53> Installing D:\Program Files\Microsoft Configuration Manager\bin\x64\bgbisapi.msi REINSTALL=ALL REINSTALLMODE=vmaus CCMINSTALLDIR="D:\Program Files\SMS_CCM" CCMSERVERDATAROOT="D:\Program Files\Microsoft Configuration
Manager" USESMSPORTS=TRUE SMSPORTS=80 USESMSSSLPORTS=TRUE SMSSSLPORTS=443 USESMSSSL=TRUE SMSSSLSTATE=0 CCMENABLELOGGING=TRUE CCMLOGLEVEL=1 CCMLOGMAXSIZE=1000000 CCMLOGMAXHISTORY=1
<02/28/14 09:01:01> bgbisapi.msi exited with return code: 0
<02/28/14 09:01:01> Installation was successful.
<02/28/14 09:01:01> CTool::RegisterComPlusService: run command line: "C:\Windows\Microsoft.NET\Framework64\v4.0.30319\RegSvcs.exe" /u "D:\Program Files\Microsoft Configuration Manager\bin\x64\microsoft.configurationmanager.bgbserverchannel.dll"
<02/28/14 09:01:04> CTool::RegisterComPlusService: Failed to unregister D:\Program Files\Microsoft Configuration Manager\bin\x64\microsoft.configurationmanager.bgbserverchannel.dll with .Net Fx 4.0
<02/28/14 09:01:04> CTool::RegisterComPlusService: run command line: "C:\Windows\Microsoft.NET\Framework64\v4.0.30319\RegSvcs.exe" /extlb /tlb:"D:\Program Files\SMS_CCM\microsoft.configurationmanager.bgbserverchannel.tlb" "D:\Program
Files\Microsoft Configuration Manager\bin\x64\microsoft.configurationmanager.bgbserverchannel.dll"
<02/28/14 09:01:07> CTool::RegisterComPlusService: Failed to register D:\Program Files\Microsoft Configuration Manager\bin\x64\microsoft.configurationmanager.bgbserverchannel.dll with .Net Fx 4.0
<02/28/14 09:01:07> Cannot register BGB server channel DLL D:\Program Files\Microsoft Configuration Manager\bin\x64\microsoft.configurationmanager.bgbserverchannel.dll. Installation cannot continue.
<02/28/14 09:01:07> Fatal MSI Error - bgbisapi.msi could not be install
bgpisapi.log
MSI (s) (00:60) [09:01:01:660]: Product: BGB http proxy -- Configuration completed successfully.
MSI (s) (00:60) [09:01:01:661]: Windows Installer reconfigured the product. Product Name: BGB http proxy. Product Version: 5.00.7958.1000. Product Language: 1033. Manufacturer: Microsoft Corporation. Reconfiguration success or error status: 0.
MSI (s) (00:60) [09:01:01:665]: Deferring clean up of packages/files, if any exist
MSI (s) (00:60) [09:01:01:665]: MainEngineThread is returning 0
MSI (s) (00:04) [09:01:01:670]: RESTART MANAGER: Session closed.
MSI (s) (00:04) [09:01:01:670]: No System Restore sequence number for this installation.
=== Logging stopped: 2/28/2014 9:01:01 ===
MSI (s) (00:04) [09:01:01:674]: User policy value 'DisableRollback' is 0
MSI (s) (00:04) [09:01:01:674]: Machine policy value 'DisableRollback' is 0
MSI (s) (00:04) [09:01:01:674]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (00:04) [09:01:01:675]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (00:04) [09:01:01:677]: Note: 1: 2265 2: 3: -2147287035
MSI (s) (00:04) [09:01:01:678]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (00:04) [09:01:01:678]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (s) (00:04) [09:01:01:679]: Destroying RemoteAPI object.
MSI (s) (00:B8) [09:01:01:679]: Custom Action Manager thread ending.
MSI (c) (3C:B8) [09:01:01:686]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (3C:B8) [09:01:01:686]: MainEngineThread is returning 0
MSI (c) (3C:B0) [09:01:01:690]: RESTART MANAGER: Session closed.
=== Verbose logging stopped: 2/28/2014 9:01:01 ===

Problem not fixed SORRY GUY'S
Environement
1 SERVER
WINDOWS SERVER 2012 R2
SQL SERVER 2012 SP1
SCCM 2012 R2
ERROR in system center
Message ID 1016
Site Component Manager failed to install this component on this site system.
Solution: Review the previous status messages to determine the exact reason for the failure. Site Component Manager will automatically retry the installation in 60 minutes. To force Site Component Manager to immediately retry the installation, stop and restart
Site Component Manager using the Configuration Manager Service Manager.
Message ID
4951
Site Component Manager failed to install this component, because the Microsoft Installer File for this component (bgbisapi.msi) could not install.
Refer to the BgbSetup.log, the bgbisapimsi.log, as well as the ConfigMgr Documentation and the Microsoft Knowledge Base for further information.
BGPSETUP.LOG
<03/05/14 09:49:33> ====================================================================
<03/05/14 09:49:33> SMSBGB Setup Started....
<03/05/14 09:49:33> Parameters: D:\Program Files\Microsoft Configuration Manager\bin\x64\rolesetup.exe /install /siteserver:TCI-SCCMR2-LAV SMSBGB 0
<03/05/14 09:49:33> Installing Pre Reqs for SMSBGB
<03/05/14 09:49:33>         ======== Installing Pre Reqs for Role SMSBGB ========
<03/05/14 09:49:33> Found 1 Pre Reqs for Role SMSBGB
<03/05/14 09:49:33> Pre Req SqlNativeClient found.
<03/05/14 09:49:33> SqlNativeClient already installed (Product Code: {D411E9C9-CE62-4DBF-9D92-4CB22B750ED5}). Would not install again.
<03/05/14 09:49:33> Pre Req SqlNativeClient is already installed. Skipping it.
<03/05/14 09:49:33>         ======== Completed Installation of Pre Reqs for Role SMSBGB ========
<03/05/14 09:49:33> Installing the SMSBGB
<03/05/14 09:49:33> Passed OS version check.
<03/05/14 09:49:33> IIS Service is installed.
<03/05/14 09:49:33> SMSBGB already installed (Product Code: {A78E8003-2307-4B70-B7CD-1A07C0A31D21}). Upgrading/Reinstalling SMSBGB
<03/05/14 09:49:33> New SMSBGB is the same product code. This is a minor upgrade.
<03/05/14 09:49:33> Enabling MSI logging. bgbisapi.msi will log to D:\Program Files\Microsoft Configuration Manager\logs\bgbisapiMSI.log
<03/05/14 09:49:33> Installing D:\Program Files\Microsoft Configuration Manager\bin\x64\bgbisapi.msi REINSTALL=ALL REINSTALLMODE=vmaus CCMINSTALLDIR="D:\Program Files\SMS_CCM" CCMSERVERDATAROOT="D:\Program Files\Microsoft Configuration
Manager" USESMSPORTS=TRUE SMSPORTS=80 USESMSSSLPORTS=TRUE SMSSSLPORTS=443 USESMSSSL=TRUE SMSSSLSTATE=0 CCMENABLELOGGING=TRUE CCMLOGLEVEL=1 CCMLOGMAXSIZE=1000000 CCMLOGMAXHISTORY=1
<03/05/14 09:49:41> bgbisapi.msi exited with return code: 0
<03/05/14 09:49:41> Installation was successful.
<03/05/14 09:49:41> CTool::RegisterComPlusService: run command line: "C:\Windows\Microsoft.NET\Framework64\v4.0.30319\RegSvcs.exe" /u "D:\Program Files\Microsoft Configuration Manager\bin\x64\microsoft.configurationmanager.bgbserverchannel.dll"
<03/05/14 09:49:43> CTool::RegisterComPlusService: Failed to unregister D:\Program Files\Microsoft Configuration Manager\bin\x64\microsoft.configurationmanager.bgbserverchannel.dll with .Net Fx 4.0
<03/05/14 09:49:43> CTool::RegisterComPlusService: run command line: "C:\Windows\Microsoft.NET\Framework64\v4.0.30319\RegSvcs.exe" /extlb /tlb:"D:\Program Files\SMS_CCM\microsoft.configurationmanager.bgbserverchannel.tlb" "D:\Program
Files\Microsoft Configuration Manager\bin\x64\microsoft.configurationmanager.bgbserverchannel.dll"
<03/05/14 09:49:45> CTool::RegisterComPlusService: Failed to register D:\Program Files\Microsoft Configuration Manager\bin\x64\microsoft.configurationmanager.bgbserverchannel.dll with .Net Fx 4.0
<03/05/14 09:49:45> Cannot register BGB server channel DLL D:\Program Files\Microsoft Configuration Manager\bin\x64\microsoft.configurationmanager.bgbserverchannel.dll. Installation cannot continue.
<03/05/14 09:49:45> Fatal MSI Error - bgbisapi.msi could not be installed.
<03/05/14 09:49:45> ~RoleSetup().
BGBISAPI.LOG
=== Verbose logging started: 3/5/2014 9:49:33 Build type: SHIP UNICODE 5.00.9600.00 Calling process: D:\Program Files\Microsoft Configuration Manager\bin\x64\rolesetup.exe ===
MSI (c) (08:C0) [09:49:33:974]: Resetting cached policy values
MSI (c) (08:C0) [09:49:33:974]: Machine policy value 'Debug' is 0
MSI (c) (08:C0) [09:49:33:974]: ******* RunEngine:
           ******* Product: D:\Program Files\Microsoft Configuration Manager\bin\x64\bgbisapi.msi
           ******* Action:
           ******* CommandLine: **********
MSI (c) (08:C0) [09:49:33:974]: Client-side and UI is none or basic: Running entire install on the server.
MSI (c) (08:C0) [09:49:33:974]: Grabbed execution mutex.
MSI (c) (08:C0) [09:49:34:021]: Cloaking enabled.
MSI (c) (08:C0) [09:49:34:021]: Attempting to enable all disabled privileges before calling Install on Server
MSI (c) (08:C0) [09:49:34:025]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (C4:E4) [09:49:34:039]: Running installation inside multi-package transaction D:\Program Files\Microsoft Configuration Manager\bin\x64\bgbisapi.msi
MSI (s) (C4:E4) [09:49:34:039]: Grabbed execution mutex.
MSI (s) (C4:E8) [09:49:34:045]: Resetting cached policy values
MSI (s) (C4:E8) [09:49:34:045]: Machine policy value 'Debug' is 0
MSI (s) (C4:E8) [09:49:34:045]: ******* RunEngine:
           ******* Product: D:\Program Files\Microsoft Configuration Manager\bin\x64\bgbisapi.msi
           ******* Action:
           ******* CommandLine: **********
MSI (s) (C4:E8) [09:49:34:047]: Machine policy value 'DisableUserInstalls' is 0
MSI (s) (C4:E8) [09:49:34:053]: Note: 1: 2203 2: C:\Windows\Installer\inprogressinstallinfo.ipi 3: -2147287038
MSI (s) (C4:E8) [09:49:34:057]: SRSetRestorePoint skipped for this transaction.
MSI (s) (C4:E8) [09:49:34:058]: Note: 1: 1402 2: HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer 3: 2
MSI (s) (C4:E8) [09:49:34:060]: File will have security applied from OpCode.
MSI (s) (C4:E8) [09:49:34:065]: SOFTWARE RESTRICTION POLICY: Verifying package --> 'D:\Program Files\Microsoft Configuration Manager\bin\x64\bgbisapi.msi' against software restriction policy
MSI (s) (C4:E8) [09:49:34:065]: SOFTWARE RESTRICTION POLICY: D:\Program Files\Microsoft Configuration Manager\bin\x64\bgbisapi.msi has a digital signature
MSI (s) (C4:E8) [09:49:34:067]: SOFTWARE RESTRICTION POLICY: D:\Program Files\Microsoft Configuration Manager\bin\x64\bgbisapi.msi is permitted to run because the user token authorizes execution (system or service token).
MSI (s) (C4:E8) [09:49:34:067]: MSCOREE not loaded loading copy from system32
MSI (s) (C4:E8) [09:49:34:077]: End dialog not enabled
MSI (s) (C4:E8) [09:49:34:077]: Original package ==> D:\Program Files\Microsoft Configuration Manager\bin\x64\bgbisapi.msi
MSI (s) (C4:E8) [09:49:34:077]: Package we're running from ==> C:\Windows\Installer\3897f9.msi
MSI (s) (C4:E8) [09:49:34:080]: APPCOMPAT: Uninstall Flags override found.
MSI (s) (C4:E8) [09:49:34:080]: APPCOMPAT: Uninstall VersionNT override found.
MSI (s) (C4:E8) [09:49:34:080]: APPCOMPAT: Uninstall ServicePackLevel override found.
MSI (s) (C4:E8) [09:49:34:081]: APPCOMPAT: looking for appcompat database entry with ProductCode '{A78E8003-2307-4B70-B7CD-1A07C0A31D21}'.
MSI (s) (C4:E8) [09:49:34:081]: APPCOMPAT: no matching ProductCode found in database.
MSI (s) (C4:E8) [09:49:34:094]: Note: 1: 2262 2: MsiFileHash 3: -2147287038
MSI (s) (C4:E8) [09:49:34:094]: Machine policy value 'DisablePatch' is 0
MSI (s) (C4:E8) [09:49:34:094]: Machine policy value 'AllowLockdownPatch' is 0
MSI (s) (C4:E8) [09:49:34:094]: Machine policy value 'DisableLUAPatching' is 0
MSI (s) (C4:E8) [09:49:34:094]: Machine policy value 'DisableFlyWeightPatching' is 0
MSI (s) (C4:E8) [09:49:34:095]: APPCOMPAT: looking for appcompat database entry with ProductCode '{A78E8003-2307-4B70-B7CD-1A07C0A31D21}'.
MSI (s) (C4:E8) [09:49:34:095]: APPCOMPAT: no matching ProductCode found in database.
MSI (s) (C4:E8) [09:49:34:096]: Transforms are not secure.
MSI (s) (C4:E8) [09:49:34:096]: PROPERTY CHANGE: Adding MsiLogFileLocation property. Its value is 'D:\Program Files\Microsoft Configuration Manager\logs\bgbisapiMSI.log'.
MSI (s) (C4:E8) [09:49:34:096]: Command Line: REINSTALL=ALL REINSTALLMODE=vmaus CCMINSTALLDIR=D:\Program Files\SMS_CCM CCMSERVERDATAROOT=D:\Program Files\Microsoft Configuration Manager USESMSPORTS=TRUE SMSPORTS=80 USESMSSSLPORTS=TRUE SMSSSLPORTS=443 USESMSSSL=TRUE
SMSSSLSTATE=0 CCMENABLELOGGING=TRUE CCMLOGLEVEL=1 CCMLOGMAXSIZE=1000000 CCMLOGMAXHISTORY=1 CURRENTDIRECTORY=D:\Program Files\Microsoft Configuration Manager\bin\x64 CLIENTUILEVEL=3 MSICLIENTUSESEXTERNALUI=1 CLIENTPROCESSID=5384
MSI (s) (C4:E8) [09:49:34:096]: Product Code passed to Engine.Initialize:           '{A78E8003-2307-4B70-B7CD-1A07C0A31D21}'
MSI (s) (C4:E8) [09:49:34:096]: Product Code from property table before transforms: '{A78E8003-2307-4B70-B7CD-1A07C0A31D21}'
MSI (s) (C4:E8) [09:49:34:096]: Product Code from property table after transforms: '{A78E8003-2307-4B70-B7CD-1A07C0A31D21}'
MSI (s) (C4:E8) [09:49:34:096]: Product registered: entering maintenance mode
MSI (s) (C4:E8) [09:49:34:096]: Determined that existing product (either this product or the product being upgraded with a patch) is installed per-machine.
MSI (s) (C4:E8) [09:49:34:096]: Product {A78E8003-2307-4B70-B7CD-1A07C0A31D21} is admin assigned: LocalSystem owns the publish key.
MSI (s) (C4:E8) [09:49:34:096]: Product {A78E8003-2307-4B70-B7CD-1A07C0A31D21} is managed.
MSI (s) (C4:E8) [09:49:34:096]: MSI_LUA: Credential prompt not required, user is an admin
MSI (s) (C4:E8) [09:49:34:096]: PROPERTY CHANGE: Adding ProductState property. Its value is '5'.
MSI (s) (C4:E8) [09:49:34:096]: PROPERTY CHANGE: Adding ProductToBeRegistered property. Its value is '1'.
MSI (s) (C4:E8) [09:49:34:096]: Entering CMsiConfigurationManager::SetLastUsedSource.
MSI (s) (C4:E8) [09:49:34:096]: Specifed source is already in a list.
MSI (s) (C4:E8) [09:49:34:096]: User policy value 'SearchOrder' is 'nmu'
MSI (s) (C4:E8) [09:49:34:096]: Machine policy value 'DisableBrowse' is 0
MSI (s) (C4:E8) [09:49:34:096]: Machine policy value 'AllowLockdownBrowse' is 0
MSI (s) (C4:E8) [09:49:34:096]: Adding new sources is allowed.
MSI (s) (C4:E8) [09:49:34:097]: Package name retrieved from configuration data: 'bgbisapi.msi'
MSI (s) (C4:E8) [09:49:34:099]: Note: 1: 2262 2: AdminProperties 3: -2147287038
MSI (s) (C4:E8) [09:49:34:099]: Machine policy value 'DisableMsi' is 1
MSI (s) (C4:E8) [09:49:34:099]: Machine policy value 'AlwaysInstallElevated' is 0
MSI (s) (C4:E8) [09:49:34:099]: User policy value 'AlwaysInstallElevated' is 0
MSI (s) (C4:E8) [09:49:34:099]: Product {A78E8003-2307-4B70-B7CD-1A07C0A31D21} is admin assigned: LocalSystem owns the publish key.
MSI (s) (C4:E8) [09:49:34:099]: Product {A78E8003-2307-4B70-B7CD-1A07C0A31D21} is managed.
MSI (s) (C4:E8) [09:49:34:099]: Running product '{A78E8003-2307-4B70-B7CD-1A07C0A31D21}' with elevated privileges: Product is assigned.
MSI (s) (C4:E8) [09:49:34:099]: PROPERTY CHANGE: Adding REINSTALL property. Its value is 'ALL'.
MSI (s) (C4:E8) [09:49:34:099]: PROPERTY CHANGE: Adding REINSTALLMODE property. Its value is 'vmaus'.
MSI (s) (C4:E8) [09:49:34:099]: PROPERTY CHANGE: Adding CCMINSTALLDIR property. Its value is 'D:\Program Files\SMS_CCM'.
MSI (s) (C4:E8) [09:49:34:099]: PROPERTY CHANGE: Adding CCMSERVERDATAROOT property. Its value is 'D:\Program Files\Microsoft Configuration Manager'.
MSI (s) (C4:E8) [09:49:34:099]: PROPERTY CHANGE: Adding USESMSPORTS property. Its value is 'TRUE'.
MSI (s) (C4:E8) [09:49:34:099]: PROPERTY CHANGE: Adding SMSPORTS property. Its value is '80'.
MSI (s) (C4:E8) [09:49:34:099]: PROPERTY CHANGE: Adding USESMSSSLPORTS property. Its value is 'TRUE'.
MSI (s) (C4:E8) [09:49:34:099]: PROPERTY CHANGE: Adding SMSSSLPORTS property. Its value is '443'.
MSI (s) (C4:E8) [09:49:34:099]: PROPERTY CHANGE: Adding USESMSSSL property. Its value is 'TRUE'.
MSI (s) (C4:E8) [09:49:34:099]: PROPERTY CHANGE: Adding SMSSSLSTATE property. Its value is '0'.
MSI (s) (C4:E8) [09:49:34:099]: PROPERTY CHANGE: Adding CCMENABLELOGGING property. Its value is 'TRUE'.
MSI (s) (C4:E8) [09:49:34:099]: PROPERTY CHANGE: Adding CCMLOGLEVEL property. Its value is '1'.
MSI (s) (C4:E8) [09:49:34:099]: PROPERTY CHANGE: Adding CCMLOGMAXSIZE property. Its value is '1000000'.
MSI (s) (C4:E8) [09:49:34:099]: PROPERTY CHANGE: Adding CCMLOGMAXHISTORY property. Its value is '1'.
MSI (s) (C4:E8) [09:49:34:099]: PROPERTY CHANGE: Adding CURRENTDIRECTORY property. Its value is 'D:\Program Files\Microsoft Configuration Manager\bin\x64'.
MSI (s) (C4:E8) [09:49:34:099]: PROPERTY CHANGE: Adding CLIENTUILEVEL property. Its value is '3'.
MSI (s) (C4:E8) [09:49:34:099]: PROPERTY CHANGE: Adding MSICLIENTUSESEXTERNALUI property. Its value is '1'.
MSI (s) (C4:E8) [09:49:34:099]: PROPERTY CHANGE: Adding CLIENTPROCESSID property. Its value is '5384'.
MSI (s) (C4:E8) [09:49:34:100]: Machine policy value 'DisableAutomaticApplicationShutdown' is 0
MSI (s) (C4:E8) [09:49:34:104]: PROPERTY CHANGE: Adding MsiRestartManagerSessionKey property. Its value is '1ea81ab83bbb7c48a58c04b46f112051'.
MSI (s) (C4:E8) [09:49:34:104]: RESTART MANAGER: Session opened.
MSI (s) (C4:E8) [09:49:34:104]: PROPERTY CHANGE: Adding MsiSystemRebootPending property. Its value is '1'.
MSI (s) (C4:E8) [09:49:34:104]: TRANSFORMS property is now:
MSI (s) (C4:E8) [09:49:34:104]: PROPERTY CHANGE: Adding PRODUCTLANGUAGE property. Its value is '1033'.
MSI (s) (C4:E8) [09:49:34:104]: PROPERTY CHANGE: Adding VersionDatabase property. Its value is '200'.
MSI (s) (C4:E8) [09:49:34:106]: SHELL32::SHGetFolderPath returned: C:\Windows\system32\config\systemprofile\AppData\Roaming
MSI (s) (C4:E8) [09:49:34:106]: SHELL32::SHGetFolderPath returned: C:\Windows\system32\config\systemprofile\Favorites
MSI (s) (C4:E8) [09:49:34:108]: SHELL32::SHGetFolderPath returned: C:\Windows\system32\config\systemprofile\AppData\Roaming\Microsoft\Windows\Network Shortcuts
MSI (s) (C4:E8) [09:49:34:109]: SHELL32::SHGetFolderPath returned: C:\Windows\system32\config\systemprofile\Documents
MSI (s) (C4:E8) [09:49:34:109]: SHELL32::SHGetFolderPath returned: C:\Windows\system32\config\systemprofile\AppData\Roaming\Microsoft\Windows\Printer Shortcuts
MSI (s) (C4:E8) [09:49:34:110]: SHELL32::SHGetFolderPath returned: C:\Windows\system32\config\systemprofile\AppData\Roaming\Microsoft\Windows\Recent
MSI (s) (C4:E8) [09:49:34:111]: SHELL32::SHGetFolderPath returned: C:\Windows\system32\config\systemprofile\AppData\Roaming\Microsoft\Windows\SendTo
MSI (s) (C4:E8) [09:49:34:111]: SHELL32::SHGetFolderPath returned: C:\Windows\system32\config\systemprofile\AppData\Roaming\Microsoft\Windows\Templates
MSI (s) (C4:E8) [09:49:34:111]: SHELL32::SHGetFolderPath returned: C:\ProgramData
MSI (s) (C4:E8) [09:49:34:112]: SHELL32::SHGetFolderPath returned: C:\Windows\system32\config\systemprofile\AppData\Local
MSI (s) (C4:E8) [09:49:34:114]: SHELL32::SHGetFolderPath returned: C:\Windows\system32\config\systemprofile\Pictures
MSI (s) (C4:E8) [09:49:34:124]: SHELL32::SHGetFolderPath returned: C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Administrative Tools
MSI (s) (C4:E8) [09:49:34:128]: SHELL32::SHGetFolderPath returned: C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Startup
MSI (s) (C4:E8) [09:49:34:129]: SHELL32::SHGetFolderPath returned: C:\ProgramData\Microsoft\Windows\Start Menu\Programs
MSI (s) (C4:E8) [09:49:34:131]: SHELL32::SHGetFolderPath returned: C:\ProgramData\Microsoft\Windows\Start Menu
MSI (s) (C4:E8) [09:49:34:132]: SHELL32::SHGetFolderPath returned: C:\Users\Public\Desktop
MSI (s) (C4:E8) [09:49:34:135]: SHELL32::SHGetFolderPath returned: C:\Windows\system32\config\systemprofile\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Administrative Tools
MSI (s) (C4:E8) [09:49:34:137]: SHELL32::SHGetFolderPath returned: C:\Windows\system32\config\systemprofile\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup
MSI (s) (C4:E8) [09:49:34:138]: SHELL32::SHGetFolderPath returned: C:\Windows\system32\config\systemprofile\AppData\Roaming\Microsoft\Windows\Start Menu\Programs
MSI (s) (C4:E8) [09:49:34:139]: SHELL32::SHGetFolderPath returned: C:\Windows\system32\config\systemprofile\AppData\Roaming\Microsoft\Windows\Start Menu
MSI (s) (C4:E8) [09:49:34:141]: SHELL32::SHGetFolderPath returned: C:\Windows\system32\config\systemprofile\Desktop
MSI (s) (C4:E8) [09:49:34:144]: SHELL32::SHGetFolderPath returned: C:\ProgramData\Microsoft\Windows\Templates
MSI (s) (C4:E8) [09:49:34:144]: SHELL32::SHGetFolderPath returned: C:\Windows\Fonts
MSI (s) (C4:E8) [09:49:34:144]: Note: 1: 2898 2: MS Sans Serif 3: MS Sans Serif 4: 0 5: 16
MSI (s) (C4:E8) [09:49:34:156]: MSI_LUA: Setting AdminUser property to 1 because the product is already installed managed and per-machine
MSI (s) (C4:E8) [09:49:34:156]: MSI_LUA: Setting MsiRunningElevated property to 1 because the install is already running elevated.
MSI (s) (C4:E8) [09:49:34:156]: PROPERTY CHANGE: Adding MsiRunningElevated property. Its value is '1'.
MSI (s) (C4:E8) [09:49:34:156]: PROPERTY CHANGE: Adding Privileged property. Its value is '1'.
MSI (s) (C4:E8) [09:49:34:156]: Note: 1: 1402 2: HKEY_CURRENT_USER\Software\Microsoft\MS Setup (ACME)\User Info 3: 2
MSI (s) (C4:E8) [09:49:34:156]: PROPERTY CHANGE: Adding USERNAME property. Its value is 'Windows User'.
MSI (s) (C4:E8) [09:49:34:156]: Note: 1: 1402 2: HKEY_CURRENT_USER\Software\Microsoft\MS Setup (ACME)\User Info 3: 2
MSI (s) (C4:E8) [09:49:34:156]: PROPERTY CHANGE: Adding Installed property. Its value is '00:00:00'.
MSI (s) (C4:E8) [09:49:34:156]: PROPERTY CHANGE: Adding DATABASE property. Its value is 'C:\Windows\Installer\3897f9.msi'.
MSI (s) (C4:E8) [09:49:34:156]: PROPERTY CHANGE: Adding OriginalDatabase property. Its value is 'D:\Program Files\Microsoft Configuration Manager\bin\x64\bgbisapi.msi'.
MSI (s) (C4:E8) [09:49:34:156]: Machine policy value 'MsiDisableEmbeddedUI' is 0
MSI (s) (C4:E8) [09:49:34:156]: EEUI - Disabling MsiEmbeddedUI due to existing external or embedded UI
MSI (s) (C4:E8) [09:49:34:156]: EEUI - Disabling MsiEmbeddedUI for service because it's not a quiet/basic install
MSI (s) (C4:E8) [09:49:34:159]: Note: 1: 2205 2: 3: PatchPackage
MSI (s) (C4:E8) [09:49:34:159]: Machine policy value 'DisableRollback' is 0
MSI (s) (C4:E8) [09:49:34:159]: User policy value 'DisableRollback' is 0
MSI (s) (C4:E8) [09:49:34:159]: PROPERTY CHANGE: Adding UILevel property. Its value is '2'.
MSI (s) (C4:E8) [09:49:34:159]: PROPERTY CHANGE: Adding QFEUpgrade property. Its value is '1'.
=== Logging started: 3/5/2014 9:49:34 ===
MSI (s) (C4:E8) [09:49:34:161]: Note: 1: 2203 2: C:\Windows\Installer\inprogressinstallinfo.ipi 3: -2147287038
MSI (s) (C4:E8) [09:49:34:161]: PROPERTY CHANGE: Adding Preselected property. Its value is '1'.
MSI (s) (C4:E8) [09:49:34:161]: APPCOMPAT: [DetectVersionLaunchCondition] Launch condition already passes.
MSI (s) (C4:E8) [09:49:34:163]: PROPERTY CHANGE: Adding ACTION property. Its value is 'INSTALL'.
MSI (s) (C4:E8) [09:49:34:163]: Doing action: INSTALL
Action start 9:49:34: INSTALL.
MSI (s) (C4:E8) [09:49:34:165]: Running ExecuteSequence
MSI (s) (C4:E8) [09:49:34:165]: Doing action: SystemFolder.F65FD590_5BEA_48BE_8408_26F7244E8B61
MSI (s) (C4:E8) [09:49:34:166]: Note: 1: 2235 2: 3: ExtendedType 4: SELECT `Action`,`Type`,`Source`,`Target`, NULL, `ExtendedType` FROM `CustomAction` WHERE `Action` = 'SystemFolder.F65FD590_5BEA_48BE_8408_26F7244E8B61'
MSI (s) (C4:E8) [09:49:34:167]: PROPERTY CHANGE: Adding SystemFolder.F65FD590_5BEA_48BE_8408_26F7244E8B61 property. Its value is 'C:\Windows\SysWOW64\'.
Action start 9:49:34: SystemFolder.F65FD590_5BEA_48BE_8408_26F7244E8B61.
MSI (s) (C4:E8) [09:49:34:167]: Doing action: System64Folder.F65FD590_5BEA_48BE_8408_26F7244E8B61
Action ended 9:49:34: SystemFolder.F65FD590_5BEA_48BE_8408_26F7244E8B61. Return value 1.
MSI (s) (C4:E8) [09:49:34:169]: Note: 1: 2235 2: 3: ExtendedType 4: SELECT `Action`,`Type`,`Source`,`Target`, NULL, `ExtendedType` FROM `CustomAction` WHERE `Action` = 'System64Folder.F65FD590_5BEA_48BE_8408_26F7244E8B61'
MSI

Problem in applying Jul05 Critical Patch Update(4445852) for win200 server

Hi,
Anyone know the below problem, recently oracle had released the Jul05 Critical Patch Updates. I managed to download the patch (4445852) and latest Opatch version from the oracle metalink website. When i tried to run %ORACLE_HOME\OPatch\opatch apply, i encountered the below error message. Anyone encountered the below message, please let me know the resolution. Any comments and advise are welcome.
Thank You..
OPatch encounters the following issues during file patching:
The following files had problems with being patched:
1.     e:\oracle9i\9.2\bin
     [ Couldn't copy e:\oracle9i\patch_install\4445852\files\bin\oraxsd9.dll to e:\oracle9i\9.2\bin from E:/oracle9i/patch_install/4445852. ]
2.     e:\oracle9i\9.2\bin
     [ Couldn't copy e:\oracle9i\patch_install\4445852\files\bin\oraunls9.dll to e:\oracle9i\9.2\bin from E:/oracle9i/patch_install/4445852. ]
3.     e:\oracle9i\9.2\bin
     [ Couldn't copy e:\oracle9i\patch_install\4445852\files\bin\orannzsbb9.dll to e:\oracle9i\9.2\bin from E:/oracle9i/patch_install/4445852. ]
4.     e:\oracle9i\9.2\bin
     [ Couldn't copy e:\oracle9i\patch_install\4445852\files\bin\orageneric9.dll to e:\oracle9i\9.2\bin from E:/oracle9i/patch_install/4445852. ]
5.     e:\oracle9i\9.2\bin
     [ Couldn't copy e:\oracle9i\patch_install\4445852\files\bin\oraxml9.dll to e:\oracle9i\9.2\bin from E:/oracle9i/patch_install/4445852. ]
6.     e:\oracle9i\9.2\bin
     [ Couldn't copy e:\oracle9i\patch_install\4445852\files\bin\oracommon9.dll to e:\oracle9i\9.2\bin from E:/oracle9i/patch_install/4445852. ]
7.     e:\oracle9i\9.2\bin
     [ Couldn't copy e:\oracle9i\patch_install\4445852\files\bin\oracore9.dll to e:\oracle9i\9.2\bin from E:/oracle9i/patch_install/4445852. ]
8.     e:\oracle9i\9.2\bin
     [ Couldn't copy e:\oracle9i\patch_install\4445852\files\bin\orapls9.dll to e:\oracle9i\9.2\bin from E:/oracle9i/patch_install/4445852. ]
9.     e:\oracle9i\9.2\bin
     [ Couldn't copy e:\oracle9i\patch_install\4445852\files\bin\orasql9.dll to e:\oracle9i\9.2\bin from E:/oracle9i/patch_install/4445852. ]
10.     e:\oracle9i\9.2\bin
     [ Couldn't copy e:\oracle9i\patch_install\4445852\files\bin\oraclient9.dll to e:\oracle9i\9.2\bin from E:/oracle9i/patch_install/4445852. ]
11.     e:\oracle9i\9.2\bin
     [ Couldn't copy e:\oracle9i\patch_install\4445852\files\bin\orannts9.dll to e:\oracle9i\9.2\bin from E:/oracle9i/patch_install/4445852. ]
12.     e:\oracle9i\9.2\bin
     [ Couldn't copy e:\oracle9i\patch_install\4445852\files\bin\oranls9.dll to e:\oracle9i\9.2\bin from E:/oracle9i/patch_install/4445852. ]
13.     e:\oracle9i\9.2\bin
     [ Couldn't copy e:\oracle9i\patch_install\4445852\files\bin\oran9.dll to e:\oracle9i\9.2\bin from E:/oracle9i/patch_install/4445852. ]

Whenever I've encountered this problem, I've renamed the dll that had errors to dll.o. Not a good idea for rolling back, BUT for me there is no going back. :)
However, I found the following on MetaLink, you may want to give this a try.
The best way I have found to avoid these cannot write to DLL errors is:
1. Download listdlls.exe from:
http://www.sysinternals.com/ntw2k/freeware/listdlls.shtml
2. Shutdown all Oracle services in services panel
3. reboot machine
4. listdlls > todaysdll.txt
5. grep -i "ora" todaysdll.txt
(If you do not have a grep utility [i.e. GNU web site] you can search the file with a text editor)
6. If there are any hits, shutdown whatever program/service that owns it and repeat steps 4 & 5.
HTH

A critical program error has occured while opening workbook

Dear friends,
A critical error has occured while opening workbook. The issue is that the same workbook is opening in some one machine but not in others.The following Dialog box is poping out when tried to open workbook:
"A critical program error has occured.The Program will now terminate.Please refer to trace for further information."
However,i did the full updation of service pack3 of MS Excel 2003 on my machine and the same version as on that particular machine(on which workbook is opening). The problem is still there.Please provide some solution.
Thankx a lot in advance!!!
regards,
Sandeep Singla

The machine where the workbook is opening has a GUI :-
Release : "710 Final Release"
File Version : 7100.2.7.1038
Build : 967944
Patch Level : 7
and the machine where the critical program error is coming has a GUI :-
Release : "710 Final Release"
File Version : 7100.2.8.1039
Build : 983952
Patch Level : 8
The Excel 2003 are similar in both the machines as the service pack3 has been installed in the machine where workbook was not opening.
Any help will be appreciated.
Thanks and Regards,
Sandeep Singla

Critical program error while opening some workbook

Hi all,
We are in BI 7 with suppoprt package 12 and GUi version 710.
Whenever iam trying to to open some workbooks system is showing the mesaage Critical programm error. I checked the trace file also but din t get anything . Th trace file is saying:
BExConnect.Trace3: 0
BExExcelTraceListener.AddTraceListener: Added a tracelistener for Version: 7100.0.461
BExConnect.constructor2: 23.59375
BExMenu.CreateSubMenu1: 0.15625
BExMenu.CreateSubMenu2: 3.75
ListSeparator: ,
openworkbook
GetSystemInformation
SUNI Const: 0
CommunicationFactory.GetSystemInformation (Setting Conn 1)): 0.15625
CommunicationFactory.GetSystemInformation (Setting Conn 2)): 0.15625
CommunicationFactory.GetSystemInformation (Setting init Propties)): 0.15625
CommunicationFactory.GetSystemInformation (SUNI.FUNCTION_EXISTS)): 0.625
RSR_XLS_RFCtrc: 4.0625
CommunicationFactory.GetSystemInformation (RSR_XLS_NET_INTERFACE)): 7.8125
CommunicationFactory.GetSystemInformation (XML Stuff)): 10.9375
CommunicationFactory.GetSystemInformation (Prop Stuff)): 10.9375
CommunicationFactory.GetSystemInformation (Version)): 10.9375
CommunicationFactory.ObtainSystemInformationandCheckVersion (GetSysInfo)): 10.9375
CommunicationFactory.ObtainSystemInformationandCheckVersion (CheckAfterLogin)): 0
CommunicationFactory.LogOnUsingComConnection (ObtainSystemInfo)): 10.9375
CommunicationFactory.LogOnUsingComConnection (MainConnectionChangedEvent)): 2.65625
CommunicationFactory.LogOn: 13.90625
RSR_XLS_RFCtrc: 0
BExThemes.LoadFromBackend: 2.8125
BExConnect.LogOn: 70.46875
OpenWorkbookGetWorkbookId
RSR_XLS_RFCtrc: 0
<?xml version="1.0" encoding="utf-16"?>
<I_T_SEARCH_ATTR xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" />
RSR_XLS_RFCtrc: 0
RSR_XLS_RFCtrc: 0.15625
RSR_XLS_RFCtrc: 0.3125
openworkbook
BExConnect.LogOn: 633331433736.094
OpenWorkbookGetWorkbookId
RSR_XLS_RFCtrc: 0
<?xml version="1.0" encoding="utf-16"?>
<I_T_SEARCH_ATTR xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" />
<?xml version="1.0" encoding="utf-16"?>
<I_T_SEARCH_ATTR xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" />
<?xml version="1.0" encoding="utf-16"?>
<I_T_SEARCH_ATTR xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" />
RSR_XLS_RFCtrc: 0
openworkbookparam
openworkbook with param
BExConnect.LogOn: 633331433790
OpenWorkbookGetWorkbookId
OpenWorkbookGetTheMimeAndStoreItOnTemp
RSR_XLS_RFCtrc: 1.5625
13/12/2007 11:49:41 AM----
System.ArgumentException: Item has already been added. Key in dictionary: 'WORKBOOK_MODE' Key being added: 'WORKBOOK_MODE'
   at System.Collections.Hashtable.Insert(Object key, Object nvalue, Boolean add)
   at System.Collections.Hashtable.Add(Object key, Object value)
   at com.sap.bi.et.analyzer.api.BExApplicationProperties.CreateFromDeSer(BExDeSer_Properties[] iPropties)
   at com.sap.bi.et.analyzer.api.BExApplication.CreateFromDeSer(BExDeSer_Page iPage)
   at com.sap.bi.et.analyzer.addin.BExExcelApplication..ctor(String iWorkbookName)
Item has already been added. Key in dictionary: 'WORKBOOK_MODE' Key being added: 'WORKBOOK_MODE'
   at System.Collections.Hashtable.Insert(Object key, Object nvalue, Boolean add)
   at System.Collections.Hashtable.Add(Object key, Object value)
   at com.sap.bi.et.analyzer.api.BExApplicationProperties.CreateFromDeSer(BExDeSer_Properties[] iPropties)
   at com.sap.bi.et.analyzer.api.BExApplication.CreateFromDeSer(BExDeSer_Page iPage)
   at com.sap.bi.et.analyzer.addin.BExExcelApplication..ctor(String iWorkbookName)
Can naybody help me in this regard as the same workbook is opening in other system..Points will be awarded for the helpful answers..
Thanks in advance..

Niyati,
That hotfix can run only to the 640, even we have the same problem over here. Actually you should not upgarde the front end patch if you want to install. But that hot fix might run or may not run, you may get issues later with the GUI..
All these probles will cause becoz of frontend patch... If you are at patch 27 then you need to unistall and come back to the same patch level as your colleague has... actually i dont know how to unistall that patch.. Or else try out with frontend patch 28...
Hope it helps..
Assign points if it helps
Gattu

A critical program error occured when running a workbook

Some end users get a critical program error occured when running a workbook when they want to make selections.
In the trace they get the following message
System.ArgumentException: Item has already been added. Key in dictionary: "44ABATDK7TYM365CYLQ0VDKU6" Key being added: "44ABATDK7TYM365CYLQ0VDKU6"
This happens only on some PC clients !
Thanks for any help !
Ivan

Hi Vid,
Thanks for your suggestion.
I am using a different patch i.e.
BI AddOn 7.X (based on 7.10), Support Package 5, Revision 1083
and it helps to solve my problem.
Cheers.

Solved: "Error in loading DLL" adding vb Reference to Photoshop CS5.1 (CS5.5)

It took me a while to solve this so I thought I'd post the solution.
On two machines (one 32-bit the other 64-bit) running the new Phonoshop CS5.1 that ships with CS5.5, I had trouble adding a reference in vb (vba) to the Photoshop Object Library for scripting:
I would just get: Error in Loading DLL
It appears that on both machines, the CS5.5 installer incorectly referenced the dll which is called "ScriptingSupport.8li" (not exactly a .dll-looking name but anyway ;-)
The Adobe CS5.5 installer set the system registry to look for the file in:
C:\Program Files\Adobe\Adobe Photoshop CS5.1 (64 Bit)\Plug-ins\Automate
or
C:\Program Files\Adobe\Adobe Photoshop CS5.1\Plug-ins\Automate
but installed the file to:
C:\Program Files\Adobe\Adobe Photoshop CS5.1 (64 Bit)\Plug-ins\Extensions
or
C:\Program Files\Adobe\Adobe Photoshop CS5.1\Plug-ins\Extensions
I copied ScriptingSupport.8li from the Extensions folder to the Automate folder and it started working.
Hope this helps someone else. :-)
Tony

Yes, another user has the issue with windows "mandatory profiles", where rights are severely limited for users (french forum): http://forums.adobe.com/thread/948264

Error Copy Sender from Payload Sender is Missing in Payload

Hello,
we have a IDOC -> ccBPM -> IDOC scenario on PI7.0 SP12.
Since SP12, we have problems in sending the ALEAUD IDOCs from the ccBPM to the R/3 getting the LUW stucked in the queue showing the error "Copy Sender from Payload: Sender Is Missing in Payload".
In the XML for the ALEAUD the fields SNDPOR, SNDPRT and SNDPRN are filled correct and it has been working with older SP. The comm. channel is configured to take the sender from the payload and we really nead this as we send the IDOC from the ccBPM.
Does anyone has similar problems or knows about other restrictions which may cause this error?
Regards,
Dirk

Hello,
SAP solved the problem by releasing a patch.
If this problem also occurs on your machine then check the SAP note 1154710.
Regards,
Dirk

Oracle Critical Patch Update Advisory - January 2013

Hi all,
11.2.0.3
Oracle Critical Patch Update - January 2013
I am confused about CPU, PSU, SPU, USP. I am reading the docs and it seems they are same thing being rambled?
Which of them is the most important to apply?
Thanks,
PetraK

Thanks gotti and fahd
I already ask the support and he gave me docs to follow. But the more I am confused with lots of added process.
Can you validate if the process is correct? My Goal is just to comply with our IT Sec Auditor to apply the latest patch. The auditor does not even know what is the name of the patch as long as it the current updates. So I think he is referring to PSU or SPU or CPU.
This is the process I got from support:
1 Appy Oracle Database Patch Set Update (11.2.0.3.8)
    1.1 Download and install latest RDA and run and send the output.
    1.2 Download and install latest OPatch and list the current inventory.
    1.3 Check java version
    1.4 Check and Resolve PSU conflict
    1.5 Backup the current OracleHome as "root"
    1.6 Stop Listener, EM, and all DB Instances
    1.7 Apply PSU
    1.8 Resolve errors if any.
End.
So It seems I only need to apply PSU? which is 11.2.0.3.8?

WUC-20 stated size error of jacob.dll

When running our web application we are receiving the following error messages :-
WUC-20 The stated size of the source file
http://appstest1.rcn.org.uk/forms90/forms90/webutil/jacob.dll does not match
that of the downloaded file C:\PROGRA~1\Oracle\JINITI~1.9\bin\jacob.dll
We have the same problem with JNIsharedstubs.dll and d2kwut60.dll
We copied across the files from the Application Server directory /u01/ora9ias/forms90/webutil directory directly to the client but when running the application these dll's are overwritten to 1k from the following sizes :-
d2kwut60.dll 192512
jacob.dll 94208
JNIsharedstubs.dll 65582
The client is a Windows2000 server running IE5. We have downloaded JInitiator 1.3.1.9 successfully.
What are we doing wrong?

Have a look at this: Webutil error WUC-20 when running
Cheers, APC

BEx Analyzer error in loading DLL

Hello I have problem with BEx Analyzer. Each time I try to open it, there is an error message:
Microsoft Visual Basic
Error in loading DLL .
Last weak it was working! Do I need instal latest patch or what happend?
Thanks for reply.
Edited by: Marcel Horkovy on Mar 29, 2008 4:17 PM

Problem solved. I instaled MS Visio (MS Office) but last weak I uninstaled it. BEx Analyzer wasn´t working. So I tried to instal MS Visio again. And here we are. BEx Analyzer is working. I uninstaled Visio again and BEx Analyzer is still working.
Edited by: Marcel Horkovy on Mar 29, 2008 5:38 PM

Critical Patch Error copying ORACORE10.DLL on a Win2K SP4 Server

Similar Messages

Maybe you are looking for