search cancel

Unable to access Datamaker getting error PowerBuilder application execution error(R0002)


Article ID: 199912


Updated On:


CA Test Data Manager (Data Finder / Grid Tools)


Hi Team,

I am unable to access 'Data maker' in 2S machine issue. Other folks in my team are able to access it. Its the issue with my ID only.


From your updates and screenshots we can see the following when trying to access GT data maker:
Datamaker Fatal Error:2
Error message : ''Null object reference at line 14 in function uf_skytap_id of object u_nv_global.''

PowerBuilder application execution error(R0002)
Error: Null object reference at line 25 in systemerror event of object gtpolicy




GT Datamaker 4.8.x 4.9.x

Component: CA Test Data Manager


the user environment did not have the %AppData% variable setup.

Diagnostic Findings:
During WebEx, we have noticed that the client was unable to start Datamaker with the option "Run as administrator" either.
We noticed that the %Appdata% variable value was set to a path non-existent due to which when we tried to locate logs from the Appdata location for the datamaker we were unable to reach the location.

Looking under her %USERPROFILE%/appdata/roaming we did not find the Grid Tools folder which existed for other users.
The below solution to change the location of the %AppData% variable helped to resolve the issue.


In the event that the AppData environment variable has been changed, it can cause problems with some programs running or installing.
To change it to the default, follow these instructions:
Click the Start button (Windows XP Users: Then click Run).
1) Type Regedit and press Enter.
2) In the left column, navigate to:
3) Click on the “Shell Folders” folder. In the right column
4) double click on the AppData value and change it to (without quotes): “%USERPROFILE%\AppData\Roaming” (If using Windows Vista or above)
                   “%USERPROFILE%\Application Data” (If using Windows XP)
5) In the left column, click on the “User Shell Folders” folder.
6) Repeat Step 4 for this folder.
7) Close Regedit.
8) Restart the computer.

If this doesn’t resolve the problem then repeat steps 3 to 8 for the following registry keys: