Windows 2000 connector Patch issue (Patch ID: 8318738)

Question

Hi,
We have applied the latest Windows 2000 connector Patch on our DEV environment.
While trying to provision the Windows resource (the user’s home network shared folder), effectively there is some permissions issue that is encountered while executing in the DLL and it effectively causes some page fault that prompts the OS to kill the process and the OC4J instance is restarted.
FYI..
10/01/11 01:26:17 Running GETUSERANDPERMISSIONS
10/01/11 01:26:17 Target Class = com.thortech.xl.util.adapters.tcUtilStringOperations
10/01/11 01:26:17 Running GETGRANTUSERPERMISSIONS
10/01/11 01:26:17 Target Class = com.thortech.xl.util.adapters.tcUtilStringOperations
10/01/11 01:26:17 Running GETPERMCOMMANDANDFOLDERPATH
10/01/11 01:26:17 Target Class = com.thortech.xl.util.adapters.tcUtilStringOperations
10/01/11 01:26:17 Running GETFULLGRANTUSERSHARECOMMAND
10/01/11 01:26:17 Target Class = com.thortech.xl.util.adapters.tcUtilStringOperations
10/01/11 01:26:17 Running EXECUTEGRANTUSERFOLDERPERMISSIONSCOMMAND
10/01/11 01:26:17 Target Class = com.thortech.xl.integration.WindowsNT40.tcUtilWindowsNT40
Entering method runRemoteCommand
szAdminName is =:OIMADMIN
szDomainName is =:dev.abc.com
szCommand is =:cmd /c cacls %home%\user70065 /E /P User70065:C 2>C:\WINDOWS\system32\windowsConnectorError.txt
temp is \\hou016.dev.abc.com\root\cimv2
connecting to server
# An unexpected error has been detected by HotSpot Virtual Machine:
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x695befe7, pid=2212, tid=4184
# Java VM: Java HotSpot(TM) Server VM (1.5.0_06-b05 mixed mode)
# Problematic frame:
# C [tcWindowsNT40.dll+0x1efe7]
# An error report file with more information is saved as hs_err_pid2212.log
# If you would like to submit a bug report, please visit:
# http://java.sun.com/webapps/bugreport/crash.jsp
10/01/11 01:26:20 Start process
WARNING: Code-source D:\product\OASDev_2\j2ee\halOIM\applications\Xellerate\soap.jar (from manifest of /D:/product/OASDev_2/j2ee/halOIM/applications/Xellerate/xlGenConnector.jar) has the same filename but is not identical to /D:/product/OASDev_2/webservices/lib/soap.jar (from <code-source> (ignore manifest Class-Path) in META-INF/boot.xml in D:\product\OASDev_2\j2ee\home\oc4j.jar). If it contains different versions of the same classes, it will be masked as the latter is already visible in the search path of loader Xellerate.root:0.0.0.
WARNING: Code-source D:\product\OASDev_2\j2ee\halOIM\applications\Xellerate\http_client.jar (from manifest of /D:/product/OASDev_2/j2ee/halOIM/applications/Xellerate/xlGenConnector.jar) has the same filename but is not identical to /D:/product/OASDev_2/j2ee/home/lib/http_client.jar (from <code-source> (ignore manifest Class-Path) in META-INF/boot.xml in D:\product\OASDev_2\j2ee\home\oc4j.jar). If it contains different versions of the same classes, it will be masked as the latter is already visible in the search path of loader Xellerate.root:0.0.0.
WARNING: Code-source D:\product\OASDev_2\j2ee\halOIM\applications\Xellerate\xlWebApp\WEB-INF\lib\share.jar (from WEB-INF/lib/ directory in D:\product\OASDev_2\j2ee\halOIM\applications\Xellerate\xlWebApp\WEB-INF\lib) has the same filename but is not identical to /D:/product/OASDev_2/jlib/share.jar (from <code-source> in /D:/product/OASDev_2/j2ee/halOIM/config/server.xml). If it contains different versions of the same classes, it will be masked as the latter is already visible in the search path of loader Xellerate.web.xlWebApp:0.0.0.
10/01/11 01:26:38
GMS: address is HOUOIM602V:4079
WARNING: Code-source D:\product\OASDev_2\j2ee\halOIM\applications\Xellerate\xlScheduler\WEB-INF\lib\xlScheduler.jar (from WEB-INF/lib/ directory in D:\product\OASDev_2\j2ee\halOIM\applications\Xellerate\xlScheduler\WEB-INF\lib) has the same filename but is not identical to /D:/product/OASDev_2/j2ee/halOIM/applications/Xellerate/xlScheduler.jar (from manifest of /D:/product/OASDev_2/j2ee/halOIM/applications/Xellerate/xlDataObjectBeans.jar). If it contains different versions of the same classes, it will be masked as the latter is already visible in the search path of loader Xellerate.web.xlScheduler:0.0.0.
10/01/11 01:26:42 Loading xalan.jar for XPathAPI.
10/01/11 01:26:43 Nexaweb Technologies Inc.(C)2000-2004. All Rights Reserved.
10/01/11 01:26:43 Nexaweb Technologies Inc.
10/01/11 01:26:43 10 Canal Park
10/01/11 01:26:43 Cambridge, MA 02141
Any one of you faced a similar issue if you also happend to apply this patch? Please suggest if you interpret any other issue from the logs.
Thanks in advance.

Answer 1

Guys,
Any Help on this Issue?