Select to view content in your preferred language

Runtime error R3064 when creating a job

9757
12
06-10-2014 12:45 AM
LeonardLuz3
Occasional Contributor
Hi all,

I've been encountering this issue for a while now and I can't seem to resolve it. Every time I create a new job for the first time, a runtime error R3064 wizard pops out. The job is still created and there seems to be no wrong in the workflow as I have closed it without encountering any problem. It seems that this error message only pops out when you create the first job after opening the client application since I do not encounter it when I created the succeeding jobs.

[ATTACH=CONFIG]34464[/ATTACH]

Hope you can help me with this.
12 Replies
BrianDemers
Esri Contributor
Hi Leonard,

Could you please clarify how you're creating the job -- using the "Create Job" button in Workflow Manager, using one of the custom steps ("JTXSteps.CreateJob" or "JTXDesktopSteps.CreateJobAdvanced"), or some other method -- and which version of ArcGIS you're using?

In case it triggers any ideas: I haven't experienced this personally, but I found a case where someone had run into what sounds like a similar issue.  In that instance, I believe they were creating a job via a custom step and somehow referencing a resource (script? .mxd?) on a file share or network drive.  It looks like they were able to resolve the issue by copying the resource locally before running the step.  ...anyway, I'm not sure if this is relevant to your case, but if so, it may be a place to start looking.

Brian D.
0 Kudos
MLMRMLMR
New Contributor

Hi, I am having the same problem. After configuring the job in Workflow Administrator and then open Workflow Manager, when I select the job and try to add I get the run time error.

Runtime Error

Program:C:ProgramFiles

(x86)\ArcGUS\WMX\Desktop10.2\Bin\WMX.exe

R6034

An application has made an attempt to load the C runtime library incorrectly. Please contact the application's support team for more information

0 Kudos
LeonardLuz3
Occasional Contributor
I am creating it from the WMX client application. Just a little background. I imported a configuration file during the post-installation process and looks like one of its components is the culprit. I managed to find a workaround by doing a 'no config' post-installation, then sending the job components, notifications, users/groups configurations from the original geodatabase to the new one. I'm still reviewing my custom steps to see if one of those are referencing a resource (script? .mxd?) on a file share or network drive just like what you've mentioned.

Thanks for the info. 🙂
0 Kudos
NiteshJauhari
New Contributor II

Hi Leonard,

I understand that you are encountering error “Microsoft Visual C++ runtime Library

Runtime Error! 

Program: C\ESRI\WMX\Desktop 10.2\Bin\WMX.exe

R6034

An application has made an attempt to load the C runtime library incorrectly.

Please contact the application's support team for more information” when  you are trying to create a new job in workflow manager.

You could follow the following steps to get rid of runtime error before uninstalling workflow manager and making changes to this software. Make sure that you have the most recent backup of your SDE geodatabase before using  following steps : 

1) Download Process Explorer.

2) Start your application and reproduce runtime error R6034

3) Start Process Explorer. In the "View" menu go to "Lower Pane View" and choose "DLLs".

4) In the top pane, locate your application and click on it. The bottom pane should show a list of DLLS loaded for your application.

5) Locate "msvcr??.dll" in the list. There should be several. Look for the one that is not in the "winsxs" folder, and make a note of it.

6) Now, check the path just before your application runs. If it includes the folder you noted in step 5, you've probably found the problem. You'll have to remove the offending entry from the path before running your program to resolve this problem.

7) The batch file simply clears the path before my program runs, so that the conflicting runtime DLL is not found.

You can also refer a third party link mentioned below which are not promoted by ESRI but may be worth reading it.

http://stackoverflow.com/questions/14552348/runtime-error-r6034-in-embedded-python-application/14680...

Let me know if this does not helps.

Regards,

Nitesh Jauhari

0 Kudos
LeonardLuz2
New Contributor

Hi Nitesh,

It seems that the path below is the one which is present just before I run the application and during the error. My question is how do I actually "remove" this offending entry? I'm not a programmer so I don't want to risk touching anything from my OS especially that the path is located under Windows folder. Please see screenshot for your reference.

dll.PNG

Thanks,

Leonard

0 Kudos
NiteshJauhari
New Contributor II

Hi Leonard,

Thanks for the screenshot.

First, make a copy of the "path" variable somewhere on a drive. Then edit the "path" variable from 'Environment  Variables' and remove the path of this dll from its current location and place somewhere in the end. Close the WMX application and relaunch it and try to repro the behavior.

Hope this is going to work. If not, let me know.

Thanks & Regards,

Nitesh Jauhari

ArcSDE Enterprise Geodatabase Analyst || ESRI

0 Kudos
LeonardLuz2
New Contributor

Hi Nitesh,

I tried what you've said but the problem still persists. Sorry about my previous post but I believe that the Intel iCLS Client is the one conflicting with the program. I also move its path at the end but I still get the Runtime Error.

Capture.PNG

Any thoughts?

-Leonard

0 Kudos
NiteshJauhari
New Contributor II

No problem Leonard.

Can you remove the 'Intel iCLS Client' path from the "path" system variable, reboot your machine once and then try to repro the behaviour. Make sure that you have a copy of the "Path" system variable before you modify any path.

The path should look like this :

C:\Oracle\product\11.2.0\client_1\bin;C:\Program Files (x86)\Intel\iCLS Client\;C:\Program Files\Intel\iCLS Client\;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;C:\Program
Files\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files\Intel\Intel(R) Management Engine Components\IPT;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\IPT;C:\Program
Files (x86)\Intel\OpenCL SDK\3.0\bin\x86;C:\Program Files (x86)\Intel\OpenCL SDK\3.0\bin\x64;C:\Program Files (x86)\QuickTime\QTSystem\;C:\Program Files (x86)\ArcGIS\Bin;C:\Program Files (x86)\ArcGIS\EsriProductionMapping\Desktop10.2\Bin

For more information on Intel ICLS Client, please review :

https://communities.intel.com/thread/46711

Hope this helps.

Regards,

Nitesh Jauhari

ArcSDE Enterprise Geodatabase Analyst || ESRI

0 Kudos
LeonardLuz2
New Contributor

Hi Nitesh,

Thank you for your patience.

I read the external link you've attached above and I learned that it's not safe for customers to remove or modify a path like that in the variable. May I ask if you personally have done this before?

Thanks,

Leonard

0 Kudos