Check Version

Brian B.
Loveland, CO

May 2, 2013
13 Posts

0 ✔  |  ✗ 0  

Re: Check Version

I am running a debug on some code and keep getting an error from TestExec:

"Check Version and Modify failed"

I try to trace through the issue, but I don't see exactly where the error thrown. I follow along until this line in the TestExec CheckVersionAndModify() procedure:

        if m_stRunTime.stPublicTag.vOptionsLast[ateOptionsLastLogFormat][ateOptionValue]=TRUE

and when I go to step into or over, I get tossed out and the error message is displayed

What is causing this issue? Or where should I be looking to fix the problem?

DrATEasy (Ron Y.)
Mission Viejo, CA

May 2, 2013
374 Posts

0 ✔  |  ✗ 0  

Re: Check Version

The problem is caused because the USR file that is used to store the options and other settings is different then the version of the USR file that is required by your version of the Test executive. Normally USR files are backward compatible and when you load a file that has an older version the test executive will update it. In that case the code you mentioned is called. Somehow in your case the file has wrong or unexpected data and that is why you get the error. If you have not customized the test executive you can replace the file with the generic one that comes with ATEasy (normally located in The Windows System32/SysWow64), or you can create a brand new one using the AUsers.Open function. If you customize you need to see place a breakpoint in that line and see what is wrong with the m_stRunTime.stPublicTag.vOptionsLast or just skip that block and make him continue with the load.

Brian B.
Loveland, CO

May 3, 2013
13 Posts

0 ✔  |  ✗ 0  

Re: Check Version

I should clarify. That is exactly where I set a breakpoint. When the program encounters this "if" statement and I go to step over or into, it does not go to either the true or false branch of this statement, it just jumps out to display the error message.

Also, the program is just using the generic straight out of the box .usr file. TestExec has not been modified.

DrATEasy (Ron Y.)
Mission Viejo, CA

May 3, 2013
374 Posts

0 ✔  |  ✗ 0  

Re: Check Version

Check your TestExec shortcut properties does it specify the path for different user file? You can try to rename it and see if you can still run the application.The default USR file works with the test executive. I attached the USR file.


File Attachment:
 ATEasy.usr

Brian B.
Loveland, CO

May 8, 2013
13 Posts

0 ✔  |  ✗ 0  

Re: Check Version

The .usr file is located in windows\syswow64. I don't see a path listed in the testexec properties. Where would that be listed? Under misc? If so, this is blank.

I replaced the .usr file with the one you suggested and had the same result.

DrATEasy (Ron Y.)
Mission Viejo, CA

May 8, 2013
374 Posts

0 ✔  |  ✗ 0  

Re: Check Version

I need to verify that the USR file that you use is from that folder, Can you rename the  USR file and see if the test executive complains when you start the an EXE that is using the test executive?  If you are rename the USR file, you will not be able to run the IDE, so that is why I need you to run EXE.

What version and exact build  are you using? Is it 148b? was the test executive modified or is it the default? Can you upload the file, so I can verify that it was not modified? I've tried to use ATEasy.usr and the Test Exec 148b and there is no issue.

Brian B.
Loveland, CO

May 13, 2013
13 Posts

0 ✔  |  ✗ 0  

Re: Check Version

I believe the issue stems from testing the 148.c version. I found out later that our customer could not use this version. So I reloaded the 148.b version.

Solution Available
DrATEasy (Ron Y.)
Mission Viejo, CA

May 14, 2013
374 Posts

1 ✔  |  ✗ 0  

Re: Check Version

The 148c is pre-release. I tried it and could not see a problem with. I uploaded the latest testexec.drv. If you have time , let me know if it shows with this driver.


File Attachment:
 TestExec.drv

Brian B.
Loveland, CO

May 15, 2013
13 Posts

0 ✔  |  ✗ 0  

Re: Check Version

The problem occurred after dropping back to 148b. Sorry for the confusion. I can't be certain if that is the problem or not.



Please Note
You need to have a M@GIC account to participate in the Forums.
Not yet registered on our website? Click here to register today!

All content, information and opinions presented on the Marvin Test Solutions User Forums are those of the authors of the posts and messages and not Marvin Test Solutions'. All attachments and files are downloaded at your own risk. [Read More]