Article ID:	1
Last updated:	November 02, 2006

Would you like to...

Print this page

Post a comment

User Opinions

No users have voted.

---

How would you rate this answer?

Helpful

Not helpful

Thank you for rating this answer.

SUMMARY

When the importLogs script is run for an application, an error message is displayed and the import operation fails.

SYMPTOMS

When the importLogs.bat script is run for an application, one of the following error messages is displayed:

"The log(s) could not be imported because an error occurred: com.microsoft.jdbcx.sqlserver.SQLServerDataSource"

or

"The log(s) could not be imported because an error occurred: com.microsoft.jdbc.sqlserver.SQLServerDriver".

RESOLUTION

The first error ("...SQLServerDataSource") means that the listed class cannot be found in the class path.

The second error ("...SQLServerDriver") may mean that there is a problem with the activity_log_import.properties file.

For the first error, copy the required .jar files to a folder in the classpath, or specify them with the -classpath flag in the importLogs.bat file:

java -classpath "admin.jar;../lib/audium.jar;C:\WUTemp\mssqlserver.jar;C:\WUTemp\msutil.jar;C:\WUTemp\msbase.jar"

Note that the "C:\WUTemp" folder should be changed to match your configuration (i.e. where those three .jar files are located on your machine).

For the second error, make sure that all backslashes in the activity_log_import.properties file are escaped (i.e. "\\" rather than "\").  Note that backslashes generally only appear in the driver_path setting.  If the backslashes are not escaped, it generates this error when the script is run.