on 04-30-2013 9:24 AM
Dear SAP Experts,
I am doing an export of our ABAP+JAVA NW7.0, and upon trying to export the source client, I receive the following error:
An error occurred while processing option SAP NetWeaver 7.0 Support Release 3 > Software Life-Cycle Options > System Copy > MS SQL Server > Source System Export > Central System > Based on AS ABAP and AS Java > Database and Central Instance Export( Last error reported by the step: uncaught exception: nw.usageTypes.utlConnectionError: Execution of UTL tool '"C:\Program Files\sapinst_instdir\NW700\LM\COPY\MSS\EXP\CENTRAL\AS\EXP\sapjvm_4\sapjvm_4\bin\java.exe" -classpath K:\usr\sap\DBW\SYS\global\sltools\sharedlib\launcher.jar -showversion -Xmx256m com.sap.engine.offline.OfflineToolStart com.sap.sl.ut.manager.UtlMain \\geadbw01gp/sapmnt/DBW/SYS/global/security/lib/tools/iaik_jce.jar;\\geadbw01gp/sapmnt/DBW/SYS/global/security/lib/tools/iaik_jsse.jar;\\geadbw01gp/sapmnt/DBW/SYS/global/security/lib/tools/iaik_smime.jar;\\geadbw01gp/sapmnt/DBW/SYS/global/security/lib/tools/iaik_ssl.jar;\\geadbw01gp/sapmnt/DBW/SYS/global/security/lib/tools/w3c_http.jar;K:/usr/sap/DBW/SYS/global/sltools/sharedlib/sap.com~sl.ut.infoprovider_lib.jar;K:/usr/sap/DBW/SYS/global/sltools/sharedlib/sap.com~sl.ut.manager.offline.jar;K:/usr/sap/DBW/SYS/global/sltools/sharedlib/antlr.jar;K:/usr/sap/DBW/SYS/global/sltools/sharedlib/exception.jar;K:/usr/sap/DBW/SYS/global/sltools/sharedlib/jddi.jar;K:/usr/sap/DBW/SYS/global/sltools/sharedlib/logging.jar;K:/usr/sap/DBW/SYS/global/sltools/sharedlib/offlineconfiguration.jar;K:/usr/sap/DBW/SYS/global/sltools/sharedlib/opensqlsta.jar;K:/usr/sap/DBW/SYS/global/sltools/sharedlib/tc_sec_secstorefs.jar;K:/usr/sap/DBW/SYS/global/sltools/sharedlib/sap.com~tc~sdt~cvl~impl.jar;K:/usr/sap/DBW/SYS/global/sltools/sharedlib/SDMutil.jar;K:/usr/sap/DBW/SYS/global/sltools/sharedlib/SLUtil.jar;K:/usr/sap/DBW/SYS/exe/uc/NTAMD64/mssjdbc/sqljdbc.jar -export -type=keydb "-expfile=C:/Program Files/sapinst_instdir/NW700/LM/COPY/MSS/EXP/CENTRAL/AS/EXP/usages_data.xml" -log=UTL_load_usages.log -sid=DBW -dsn=jdbc/pool/DBW -ssprops=K:/usr/sap/DBW/SYS/global/security/data/SecStore.properties -ssk=K:/usr/sap/DBW/SYS/global/security/data/SecStore.key' aborts with return code 64 due to a database connection error. DIAGNOSIS: The connection parameters are wrong or the database server has been shut down. SOLUTION: Check 'UTL_load_usages.log' and 'C:/Program Files/sapinst_instdir/NW700/LM/COPY/MSS/EXP/CENTRAL/AS/EXP/UTL.java.log' for more information. (in script unknown, line 0: ???)). You can now:
UTL_load_usages.log contains the following error:
Apr 30, 2013 9:39:29 AM Info : Successfully parsed!
Apr 30, 2013 9:39:29 AM Info : Executing command Export...
Apr 30, 2013 9:39:29 AM Info : Establishing DB connection...
Apr 30, 2013 9:39:30 AM Path : Exception : The DataBase is down or the connection parameters are wrong: -sid=DBW -dsn=jdbc/pool/DBW -ssprops=K:/usr/sap/DBW/SYS/global/security/data/SecStore.properties -ssk=K:/usr/sap/DBW/SYS/global/security/data/SecStore.key -keyphrase=null
java.lang.Exception
Could anyone give me some pointers on how to resolve this issue?
1.- ConfigTool / VisualAdministrator work fine and connect fine.
2.- SAPJSM user is not blocked.
3.- J2EE_ADMIN is not blocked
4.- SQL is up.
5.- SAP is up.
The system is Windows 2003 with Microsoft SQL2005.
Thank you,
Kind regards
Hi,
Did you restart the instance ? The securestore maybe has been changed and the instance didn't restarted.
Cheers.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
It seems that some of the parameters are wrong:
<!--LOGHEADER[START]/-->
<!--HELP[Manual modification of the header may cause parsing problem!]/-->
<!--LOGGINGVERSION[1.5.3.7185 - 630]/-->
<!--NAME[UTL_load_usages.log]/-->
<!--PATTERN[UTL_load_usages.log]/-->
<!--FORMATTER[com.sap.tc.logging.TraceFormatter(%24d %7s: %m)]/-->
<!--ENCODING[UTF8]/-->
<!--LOGHEADER[END]/-->
Apr 30, 2013 9:39:29 AM Info : Successfully parsed!
Apr 30, 2013 9:39:29 AM Info : Executing command Export...
Apr 30, 2013 9:39:29 AM Info : Establishing DB connection...
Apr 30, 2013 9:39:30 AM Path : Exception : The DataBase is down or the connection parameters are wrong: -sid=DBW -dsn=jdbc/pool/DBW -ssprops=K:/usr/sap/DBW/SYS/global/security/data/SecStore.properties -ssk=K:/usr/sap/DBW/SYS/global/security/data/SecStore.key -keyphrase=null
java.lang.Exception
at com.sap.exception.BaseExceptionInfo.traceAutomatically(BaseExceptionInfo.java:1175)
at com.sap.exception.BaseExceptionInfo.<init>(BaseExceptionInfo.java:423)
at com.sap.exception.BaseException.<init>(BaseException.java:316)
at com.sap.sl.ut.infoprovider.exceptions.UTInfoException.<init>(UTInfoException.java:99)
at com.sap.sl.ut.manager.persistence.db.DataBaseInfoFactory.connect(DataBaseInfoFactory.java:376)
at com.sap.sl.ut.manager.persistence.db.DataBaseInfoFactory.constructSystemInfo(DataBaseInfoFactory.java:773)
at com.sap.sl.ut.manager.command.Export.execute(Export.java:36)
at com.sap.sl.ut.manager.command.Command.exec(Command.java:90)
at com.sap.sl.ut.manager.UtlMain.exec(UtlMain.java:61)
at com.sap.sl.ut.manager.UtlMain.main(UtlMain.java:56)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:331)
at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)
Caused by: com.sap.sql.log.OpenSQLException: Could not load class com.sap.nwmss.jdbc.sqlserver.SQLServerDriver.
at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:106)
at com.sap.sql.jdbc.NativeConnectionFactory.createNativeConnection(NativeConnectionFactory.java:143)
at com.sap.sql.connect.OpenSQLDataSourceImpl.createConnection(OpenSQLDataSourceImpl.java:522)
at com.sap.sql.connect.OpenSQLDataSourceImpl.getConnection(OpenSQLDataSourceImpl.java:276)
at com.sap.sl.ut.manager.persistence.db.DBConnection.connectViaSecureStore(DBConnection.java:159)
at com.sap.sl.ut.manager.persistence.db.DBConnection.connect(DBConnection.java:171)
at com.sap.sl.ut.manager.persistence.db.DataBaseInfoFactory.connect(DataBaseInfoFactory.java:374)
at com.sap.sl.ut.manager.persistence.db.DataBaseInfoFactory.constructSystemInfo(DataBaseInfoFactory.java:773)
at com.sap.sl.ut.manager.command.Export.execute(Export.java:36)
at com.sap.sl.ut.manager.command.Command.exec(Command.java:90)
at com.sap.sl.ut.manager.UtlMain.exec(UtlMain.java:61)
at com.sap.sl.ut.manager.UtlMain.main(UtlMain.java:56)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:331)
at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)
Caused by: java.lang.ClassNotFoundException: com.sap.nwmss.jdbc.sqlserver.SQLServerDriver
at com.sap.engine.offline.FileClassLoader.findClass(FileClassLoader.java:691)
at com.sap.engine.offline.FileClassLoader.loadClass(FileClassLoader.java:600)
at com.sap.engine.offline.FileClassLoader.loadClass(FileClassLoader.java:578)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:143)
at com.sap.sql.jdbc.NativeConnectionFactory.createNativeConnection(NativeConnectionFactory.java:134)
... 15 more
caused by
java.lang.ClassNotFoundException: com.sap.nwmss.jdbc.sqlserver.SQLServerDriver
at com.sap.engine.offline.FileClassLoader.findClass(FileClassLoader.java:691)
at com.sap.engine.offline.FileClassLoader.loadClass(FileClassLoader.java:600)
at com.sap.engine.offline.FileClassLoader.loadClass(FileClassLoader.java:578)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:143)
at com.sap.sql.jdbc.NativeConnectionFactory.createNativeConnection(NativeConnectionFactory.java:134)
at com.sap.sql.connect.OpenSQLDataSourceImpl.createConnection(OpenSQLDataSourceImpl.java:522)
at com.sap.sql.connect.OpenSQLDataSourceImpl.getConnection(OpenSQLDataSourceImpl.java:276)
at com.sap.sl.ut.manager.persistence.db.DBConnection.connectViaSecureStore(DBConnection.java:159)
at com.sap.sl.ut.manager.persistence.db.DBConnection.connect(DBConnection.java:171)
at com.sap.sl.ut.manager.persistence.db.DataBaseInfoFactory.connect(DataBaseInfoFactory.java:374)
at com.sap.sl.ut.manager.persistence.db.DataBaseInfoFactory.constructSystemInfo(DataBaseInfoFactory.java:773)
at com.sap.sl.ut.manager.command.Export.execute(Export.java:36)
at com.sap.sl.ut.manager.command.Command.exec(Command.java:90)
at com.sap.sl.ut.manager.UtlMain.exec(UtlMain.java:61)
at com.sap.sl.ut.manager.UtlMain.main(UtlMain.java:56)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:331)
at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)
Please check the following sap note:
Note 1109274 - New JDBC driver for NetWeaver 7.0 and higher
Cheers
Hi,
Please check the below things:
1) R3trans output.
2) maintaining correct password in secstore in configtool and rebooting the instance.
Thanks,
Gaurav
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Are you doing the database export with the last version of sapints ( SWPM )
?
The sapinst error is about a security error. Maybe the password that you enter does't mach with the right password at secure store.
Check it out
Cheers
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dear Sargan,
Yes, I am currently using the last available version of SWPM & using the appropriate Java version which has worked fine in the previous installations.
I would assume that if it were a security error related to the parameters in the secstore, maybe ConfigTool wouldn't connect correctly to the DB, but it works fine.
Kind regards
SECSTORE is so green it blinds
SECSTORE values from ConfigTool look fine:
admin/host/DBW | (edited, hostname) |
admin/password/DBW | ********** |
admin/port/DBW | 50004 |
admin/user/DBW | J2EE_ADMIN |
jdbc/pool/DBW/ClassName | com.sap.nwmss.jdbc.sqlserver.SQLServerDriver |
jdbc/pool/DBW/Password | ********** |
jdbc/pool/DBW/Url | jdbc:nwmss:sqlserver://<edited,hostname>:1433;databasename=DBW |
jdbc/pool/DBW/User | SAPDBWDB |
Thank you Juan.
Kind regards
SECSTORE is so green it blinds
Can you post the full exception?... Also, theres has been problems before with JDBC drivers, it will be good to check if you are using a good one.
Read,
Note 639702 - JDBC Driver for Microsoft SQL Server
Note 1145221 - JDBC driver exchange to Microsoft JDBC Driver
Regards
Juan
Hello,
I have attached utl.java.log & utl_load_usages.log
I checked the notes you wrote down and when I check the JDBC driver I receive this:
No Microsoft JDBC Driver found. com.microsoft.sqlserver.jdbc.SQLServerDriver
------------------------------------------------------------------------
No DataDirect JDBC Driver found. com.sap.nwmss.jdbc.sqlserver.SQLServerDriver
In the UTL.JAVA.LOG there's the following warning:
Warning : K:/usr/sap/DBW/SYS/exe/uc/NTAMD64/mssjdbc/sqljdbc.jar file stated but does not exist !
Which directly relates to the JDBC driver no found. I will look into it.
thank you for your time
Kind regards
User | Count |
---|---|
87 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.