LoadRunner JAVA VUser Protocol Manual script failed to find Classes.zip entry in Classpath problem.

JAVA VUser Protocol Manual script failed to find Classes.zip entry in Classpath Problem resolution:

Prerequisites:environment variables: correctly configured Java_home,path correctly indicates the bin path of Java_home and the bin path of LR, classpath indicates the Lib path of the JDK and the Lib path of LR. the current version of LoadRunner is release 9.0. the current JDK version is 1.7. first, the error content is as follows:Notice: Found jdk version:1.7.0. [msgid:mmsg-22986]
Warning: warning:failed to find Classes.zip entry in Classpath.
[msgid:mwar-22986]
Notice: Classpath=c:\program files\mercury\loadrunner\scripts\java_vuser\;c:\program files\mercury\loadrunner\ Classes\srv;c:\program files\mercury\loadrunner\classes;.; C:\Program files\mercury\loadrunner\classes; C:\Program files\mercury\loadrunner\lib;d:\program files\java\jdk1.7.0_22\lib;;; [msgid:mmsg-22986]
Notice: path=c:\progra~1\mercury\loadru~1\bin; C:\progra~1\mercury\loadru~1\bin\tulip\bin; C:\WINDOWS\system32; C:\WINDOWS; C:\windows\system32\wbem;d:\program Files\java\jdk1.5.0_22\bin; C:\Program Files\mercury\loadrunner\bin; [msgid:mmsg-22986]
Notification: VM Params:. [msgid:mmsg-22986]
Error: Java VM Internal error: "Error Loading javai.dll.
. [msgid:merr-22995]
Warning: Extension java_int.dll report error when calling function Extperprocessinitialize-1 [msgid:mwar-10485]
Error: Thread context: The service that invoked the driver failed. Cause – The thread context is not initialized on this thread. [msgid:merr-10176] the cause of the error is that LR9.0 may not be compatible with JDK1.7, and after switching to JDK1.5, the error disappears.   Note: After snow classmate verification, Loadrunner11 only support JDK1.6 32-bit

LoadRunner JAVA VUser Protocol Manual script failed to find Classes.zip entry in Classpath problem.