Highlighted
Absent Member.
Absent Member.
9602 views

"Vuser compilation failed.Please set CCIDebug to Off in CCI section of mdrv.dat file" error message

The following error messages are displayed while replaying the script, Please help me to overcome this issue

 

"Error: Vuser compilation failed. Please set CCIDebug to Off in CCI section of mdrv.dat file.
Warning: Extension cciext.dll reports error -19797 on call to function ExtPerProcessInitialize
Error: Thread Context: Call to service of the driver failed, reason - thread context wasn't initialized on this thread."

 

Note: (i am using)

LR version 11.5

Protocol: Web-HTTP/HTML

 

0 Likes
5 Replies
Highlighted
Absent Member.
Absent Member.

Hi,

 

This issue is related to multi-byte characters in the script.

Currently CCI can only compile those scripts when the machine locale fits the script, e.g. compile a script with Spanish in a Spain locale windows/Linux.

Please check your script and system locale.

 

Thanks,

Kevin

0 Likes
Highlighted
Absent Member.
Absent Member.

Thank you for the reply.
My system locale is -> English (US)
But i don't know, how to check the script locale, please help me to check the script locale

0 Likes
Highlighted
Contributor.
Contributor.

I'm aware this is an old post but I don't see any solution.  

 

I've encountered this error before.  What caused my issue was that I had some code in my script that was causing the compiler in Performance Center to bomb when the test run. Although I was able to successfully compile & run the script from VuGen.  

 

I had attempted to include a file "#include <assert.h>" in the global.h in order to validate some information in the response from my rest call.  Once I removed that & simply used web_reg_save_param & web_reg_find, I no longer received that error.

0 Likes
Highlighted
New Member.

Hi,

 

Did you get any solution for this? I am facing similar issue and don't see much information on net. Please respond.

 

Thanks,

Prateek

0 Likes
Highlighted
Super Contributor.
Super Contributor.

I found the issue for my script. But the solution might not apply for everyone.

 

The error I was getting was : Failed to Start with the following details on the bpm_mdrv.log

02/11/2016 14:27:14 Error: CCI compilation error -d:\...\res\pre_cci.c: Action.c:8: error: undeclared identifier `LrsLastArg'. [MsgId: MERR-19799]
02/11/2016 14:27:14 Error: CCI compilation error -d:\...\res\pre_cci.c: d:\\hpbac\\bpm\\workspace\\agent1\\site2\\...res\\combined_xxx.c:4: error: 1 errors, not writing pre_cci.ci. [MsgId: MERR-19799]
02/11/2016 14:27:14 Error: Vuser compilation failed. Please set CCIDebug to Off in CCI section of mdrv.dat file. [MsgId: MERR-19797]
02/11/2016 14:27:14 Warning: Extension cciext.dll reports error -19797 on call to function ExtPerProcessInitialize [MsgId: MWAR-10485]
02/11/2016 14:27:14 Error: Thread Context: Call to service of the driver failed, reason - thread context wasn't initialized on this thread. [MsgId: MERR-10176]

 

Initially I tried going to the mdrv.dat to set CCIDebug to Off but I could not find that entry.

Then I focused on the initial part of the error: error: undeclared identifier `LrsLastArg'

It means that BPM does not recognize the function LrsLastArg, although it runs OK on VUGen SA.

I added to the script the following line to include the library that contains the function:  #include "lrs.h" ... and it works!

 

So in my case I had to look at the initial error and add the missing library.

Hope it helps anyone.

 

Cheers

Sergio

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.