Error establishing communication with OpExec service on OPALIS: - The network location cannot be reached. (code 1231)

Ok, I figured out the solution...

Apparently you must have a network adapter enabled to make this work.  I'm running a local VM and had my NAT NIC to the outside world disabled.  I created a separate internal network adapter, gave it an IP address, and the policy worked.

December 19th, 2012 5:58pm

Ok, I figured out the solution...

Apparently you must have a network adapter enabled to make this work.  I'm running a local VM and had my NAT NIC to the outside world disabled.  I created a separate internal network adapter, gave it an IP address, and the policy worked.

Free Windows Admin Tool Kit Click here and download it now
December 19th, 2012 5:58pm

Ok, I figured out the solution...

Apparently you must have a network adapter enabled to make this work.  I'm running a local VM and had my NAT NIC to the outside world disabled.  I created a separate internal network adapter, gave it an IP address, and the policy worked.

December 19th, 2012 5:58pm

Ok, I figured out the solution...

Apparently you must have a network adapter enabled to make this work.  I'm running a local VM and had my NAT NIC to the outside world disabled.  I created a separate internal network adapter, gave it an IP address, and the policy worked.

Free Windows Admin Tool Kit Click here and download it now
December 19th, 2012 5:58pm

Ok, I figured out the solution...

Apparently you must have a network adapter enabled to make this work.  I'm running a local VM and had my NAT NIC to the outside world disabled.  I created a separate internal network adapter, gave it an IP address, and the policy worked.

December 19th, 2012 5:58pm

Ok, I figured out the solution...

Apparently you must have a network adapter enabled to make this work.  I'm running a local VM and had my NAT NIC to the outside world disabled.  I created a separate internal network adapter, gave it an IP address, and the policy worked.

Free Windows Admin Tool Kit Click here and download it now
December 19th, 2012 5:58pm

Ok, I figured out the solution...

Apparently you must have a network adapter enabled to make this work.  I'm running a local VM and had my NAT NIC to the outside world disabled.  I created a separate internal network adapter, gave it an IP address, and the policy worked.

December 19th, 2012 5:58pm

Ok, I figured out the solution...

Apparently you must have a network adapter enabled to make this work.  I'm running a local VM and had my NAT NIC to the outside world disabled.  I created a separate internal network adapter, gave it an IP address, and the policy worked.

Free Windows Admin Tool Kit Click here and download it now
December 19th, 2012 5:58pm

Ok, I figured out the solution...

Apparently you must have a network adapter enabled to make this work.  I'm running a local VM and had my NAT NIC to the outside world disabled.  I created a separate internal network adapter, gave it an IP address, and the policy worked.

December 19th, 2012 5:58pm

Ok, I figured out the solution...

Apparently you must have a network adapter enabled to make this work.  I'm running a local VM and had my NAT NIC to the outside world disabled.  I created a separate internal network adapter, gave it an IP address, and the policy worked.

Free Windows Admin Tool Kit Click here and download it now
December 19th, 2012 5:58pm

Ok, I figured out the solution...

Apparently you must have a network adapter enabled to make this work.  I'm running a local VM and had my NAT NIC to the outside world disabled.  I created a separate internal network adapter, gave it an IP address, and the policy worked.

December 19th, 2012 5:58pm

Ok, I figured out the solution...

Apparently you must have a network adapter enabled to make this work.  I'm running a local VM and had my NAT NIC to the outside world disabled.  I created a separate internal network adapter, gave it an IP address, and the policy worked.

Free Windows Admin Tool Kit Click here and download it now
December 19th, 2012 5:58pm

Ok, I figured out the solution...

Apparently you must have a network adapter enabled to make this work.  I'm running a local VM and had my NAT NIC to the outside world disabled.  I created a separate internal network adapter, gave it an IP address, and the policy worked.

December 19th, 2012 5:58pm

Ok, I figured out the solution...

Apparently you must have a network adapter enabled to make this work.  I'm running a local VM and had my NAT NIC to the outside world disabled.  I created a separate internal network adapter, gave it an IP address, and the policy worked.

Free Windows Admin Tool Kit Click here and download it now
December 19th, 2012 5:58pm

Ok, I figured out the solution...

Apparently you must have a network adapter enabled to make this work.  I'm running a local VM and had my NAT NIC to the outside world disabled.  I created a separate internal network adapter, gave it an IP address, and the policy worked.

December 19th, 2012 5:58pm

Ok, I figured out the solution...

Apparently you must have a network adapter enabled to make this work.  I'm running a local VM and had my NAT NIC to the outside world disabled.  I created a separate internal network adapter, gave it an IP address, and the policy worked.

Free Windows Admin Tool Kit Click here and download it now
December 19th, 2012 5:58pm

Ok, I figured out the solution...

Apparently you must have a network adapter enabled to make this work.  I'm running a local VM and had my NAT NIC to the outside world disabled.  I created a separate internal network adapter, gave it an IP address, and the policy worked.

December 19th, 2012 5:58pm

I have a simple policy with a Custom Start object linked to a Run Program object.  This Run Program object is supposed to run a batch file which echo's a word into a log file.  For some reason, when I attempt to test or run the policy, I get the following error:

Error establishing communication with OpExec service on OPALIS: - The network location cannot be reached. For information about network troubleshooting, see Windows Help.   (code 1231)

I deleted the OpExec service and had it recreated as suggested in this post: http://social.technet.microsoft.com/Forums/sk/opalisv5v6/thread/378f9f5d-a31d-4b69-8e6c-c597fde0e928.  However, it didn't help.

Does anyone have any idea of what may be causing this or how to fix it?

Thank you!

Free Windows Admin Tool Kit Click here and download it now
December 19th, 2012 7:58pm

I turned on registry debugging to level 7 for the Action Server and found this if it may be of any help:

2012-12-19 12:11:11 [3904] 4 [RPT] Thread 3904, RPT 2820.1, RunProgramRemoteCmd::OPEXESVC File versions are the same. No need to copy

2012-12-19 12:11:11 [3904] 4 AutoTrace : << OpalisUtilityFromWorkflowContext::LogTraceMessage (0 ms)

2012-12-19 12:11:11 [3860] 4 ThreadQueueMonitor is running

2012-12-19 12:11:11 [3904] 4 AutoTrace : >> OpalisUtilityFromWorkflowContext::LogTraceMessage

2012-12-19 12:11:11 [3904] 4 [RPT] Thread 3904, RPT 2820.1, RunProgramRemoteCmd::Leaving RemoteServiceInstall with SUCCESS

2012-12-19 12:11:11 [3904] 4 AutoTrace : << OpalisUtilityFromWorkflowContext::LogTraceMessage (1 ms)

2012-12-19 12:11:11 [3904] 4 AutoTrace : >> OpalisUtilityFromWorkflowContext::LogTraceMessage

2012-12-19 12:11:11 [3904] 4 [RPT] Thread 3904, RPT 2820.1, RunProgramRemoteCmd::connectToRemoteService - error creating pipe

2012-12-19 12:11:11 [3904] 4 AutoTrace : << OpalisUtilityFromWorkflowContext::LogTraceMessage (1 ms)

2012-12-19 12:11:11 [3904] 4 AutoTrace : >> OpalisUtilityFromWorkflowContext::LogTraceMessage

2012-12-19 12:11:11 [3904] 4 [RPT] Thread 3904, RPT 2820.1, RunProgramRemoteCmd::Exception Error establishing communication with OpExec service on OPALIS: - The network location cannot be reached. For information about network troubleshooting, see Windows Help.   (code 1231)

2012-12-19 12:11:11 [3904] 4 AutoTrace : << OpalisUtilityFromWorkflowContext::LogTraceMessage (1 ms)

2012-12-19 12:11:11 [3904] 4 AutoTrace : >> OpalisUtilityFromWorkflowContext::LogTraceMessage

2012-12-19 12:11:11 [3904] 4 [RPT] Thread 3904, RPT 2820.1, RunProgramRemoteCmd::Disconnecting from OPALIS...

December 19th, 2012 8:14pm

Ok, I figured out the solution...

Apparently you must have a network adapter enabled to make this work.  I'm running a local VM and had my NAT NIC to the outside world disabled.  I created a separate internal network adapter, gave it an IP address, and the policy worked.

Free Windows Admin Tool Kit Click here and download it now
December 19th, 2012 8:58pm

Ok, I figured out the solution...

Apparently you must have a network adapter enabled to make this work.  I'm running a local VM and had my NAT NIC to the outside world disabled.  I created a separate internal network adapter, gave it an IP address, and the policy worked.

December 19th, 2012 8:58pm

Ok, I figured out the solution...

Apparently you must have a network adapter enabled to make this work.  I'm running a local VM and had my NAT NIC to the outside world disabled.  I created a separate internal network adapter, gave it an IP address, and the policy worked.

Free Windows Admin Tool Kit Click here and download it now
December 19th, 2012 8:58pm

Ok, I figured out the solution...

Apparently you must have a network adapter enabled to make this work.  I'm running a local VM and had my NAT NIC to the outside world disabled.  I created a separate internal network adapter, gave it an IP address, and the policy worked.

December 19th, 2012 8:58pm

Ok, I figured out the solution...

Apparently you must have a network adapter enabled to make this work.  I'm running a local VM and had my NAT NIC to the outside world disabled.  I created a separate internal network adapter, gave it an IP address, and the policy worked.

Free Windows Admin Tool Kit Click here and download it now
December 19th, 2012 8:58pm

Ok, I figured out the solution...

Apparently you must have a network adapter enabled to make this work.  I'm running a local VM and had my NAT NIC to the outside world disabled.  I created a separate internal network adapter, gave it an IP address, and the policy worked.

December 19th, 2012 8:58pm

Ok, I figured out the solution...

Apparently you must have a network adapter enabled to make this work.  I'm running a local VM and had my NAT NIC to the outside world disabled.  I created a separate internal network adapter, gave it an IP address, and the policy worked.

Free Windows Admin Tool Kit Click here and download it now
December 19th, 2012 8:58pm

Ok, I figured out the solution...

Apparently you must have a network adapter enabled to make this work.  I'm running a local VM and had my NAT NIC to the outside world disabled.  I created a separate internal network adapter, gave it an IP address, and the policy worked.

December 19th, 2012 8:58pm

Ok, I figured out the solution...

Apparently you must have a network adapter enabled to make this work.  I'm running a local VM and had my NAT NIC to the outside world disabled.  I created a separate internal network adapter, gave it an IP address, and the policy worked.

Free Windows Admin Tool Kit Click here and download it now
December 19th, 2012 8:58pm

Ok, I figured out the solution...

Apparently you must have a network adapter enabled to make this work.  I'm running a local VM and had my NAT NIC to the outside world disabled.  I created a separate internal network adapter, gave it an IP address, and the policy worked.

December 19th, 2012 8:58pm

Ok, I figured out the solution...

Apparently you must have a network adapter enabled to make this work.  I'm running a local VM and had my NAT NIC to the outside world disabled.  I created a separate internal network adapter, gave it an IP address, and the policy worked.

Free Windows Admin Tool Kit Click here and download it now
December 19th, 2012 8:58pm

Ok, I figured out the solution...

Apparently you must have a network adapter enabled to make this work.  I'm running a local VM and had my NAT NIC to the outside world disabled.  I created a separate internal network adapter, gave it an IP address, and the policy worked.

December 19th, 2012 8:58pm

Ok, I figured out the solution...

Apparently you must have a network adapter enabled to make this work.  I'm running a local VM and had my NAT NIC to the outside world disabled.  I created a separate internal network adapter, gave it an IP address, and the policy worked.

Free Windows Admin Tool Kit Click here and download it now
December 19th, 2012 8:58pm

Ok, I figured out the solution...

Apparently you must have a network adapter enabled to make this work.  I'm running a local VM and had my NAT NIC to the outside world disabled.  I created a separate internal network adapter, gave it an IP address, and the policy worked.

December 19th, 2012 8:58pm

Ok, I figured out the solution...

Apparently you must have a network adapter enabled to make this work.  I'm running a local VM and had my NAT NIC to the outside world disabled.  I created a separate internal network adapter, gave it an IP address, and the policy worked.

Free Windows Admin Tool Kit Click here and download it now
December 19th, 2012 8:58pm

Ok, I figured out the solution...

Apparently you must have a network adapter enabled to make this work.  I'm running a local VM and had my NAT NIC to the outside world disabled.  I created a separate internal network adapter, gave it an IP address, and the policy worked.

December 19th, 2012 8:58pm

Ok, I figured out the solution...

Apparently you must have a network adapter enabled to make this work.  I'm running a local VM and had my NAT NIC to the outside world disabled.  I created a separate internal network adapter, gave it an IP address, and the policy worked.

Free Windows Admin Tool Kit Click here and download it now
December 19th, 2012 8:58pm

Ok, I figured out the solution...

Apparently you must have a network adapter enabled to make this work.  I'm running a local VM and had my NAT NIC to the outside world disabled.  I created a separate internal network adapter, gave it an IP address, and the policy worked.

December 19th, 2012 8:58pm

Ok, I figured out the solution...

Apparently you must have a network adapter enabled to make this work.  I'm running a local VM and had my NAT NIC to the outside world disabled.  I created a separate internal network adapter, gave it an IP address, and the policy worked.

Free Windows Admin Tool Kit Click here and download it now
December 19th, 2012 8:58pm

Ok, I figured out the solution...

Apparently you must have a network adapter enabled to make this work.  I'm running a local VM and had my NAT NIC to the outside world disabled.  I created a separate internal network adapter, gave it an IP address, and the policy worked.

December 19th, 2012 8:58pm

Ok, I figured out the solution...

Apparently you must have a network adapter enabled to make this work.  I'm running a local VM and had my NAT NIC to the outside world disabled.  I created a separate internal network adapter, gave it an IP address, and the policy worked.

Free Windows Admin Tool Kit Click here and download it now
December 19th, 2012 8:58pm

Ok, I figured out the solution...

Apparently you must have a network adapter enabled to make this work.  I'm running a local VM and had my NAT NIC to the outside world disabled.  I created a separate internal network adapter, gave it an IP address, and the policy worked.

December 19th, 2012 8:58pm

Ok, I figured out the solution...

Apparently you must have a network adapter enabled to make this work.  I'm running a local VM and had my NAT NIC to the outside world disabled.  I created a separate internal network adapter, gave it an IP address, and the policy worked.

Free Windows Admin Tool Kit Click here and download it now
December 19th, 2012 8:58pm

Ok, I figured out the solution...

Apparently you must have a network adapter enabled to make this work.  I'm running a local VM and had my NAT NIC to the outside world disabled.  I created a separate internal network adapter, gave it an IP address, and the policy worked.

December 19th, 2012 8:58pm

Ok, I figured out the solution...

Apparently you must have a network adapter enabled to make this work.  I'm running a local VM and had my NAT NIC to the outside world disabled.  I created a separate internal network adapter, gave it an IP address, and the policy worked.

Free Windows Admin Tool Kit Click here and download it now
December 19th, 2012 8:58pm

Ok, I figured out the solution...

Apparently you must have a network adapter enabled to make this work.  I'm running a local VM and had my NAT NIC to the outside world disabled.  I created a separate internal network adapter, gave it an IP address, and the policy worked.

December 19th, 2012 8:58pm

Ok, I figured out the solution...

Apparently you must have a network adapter enabled to make this work.  I'm running a local VM and had my NAT NIC to the outside world disabled.  I created a separate internal network adapter, gave it an IP address, and the policy worked.

Free Windows Admin Tool Kit Click here and download it now
December 19th, 2012 8:58pm

Ok, I figured out the solution...

Apparently you must have a network adapter enabled to make this work.  I'm running a local VM and had my NAT NIC to the outside world disabled.  I created a separate internal network adapter, gave it an IP address, and the policy worked.

December 19th, 2012 8:58pm

Ok, I figured out the solution...

Apparently you must have a network adapter enabled to make this work.  I'm running a local VM and had my NAT NIC to the outside world disabled.  I created a separate internal network adapter, gave it an IP address, and the policy worked.

Free Windows Admin Tool Kit Click here and download it now
December 19th, 2012 8:58pm

Ok, I figured out the solution...

Apparently you must have a network adapter enabled to make this work.  I'm running a local VM and had my NAT NIC to the outside world disabled.  I created a separate internal network adapter, gave it an IP address, and the policy worked.

December 19th, 2012 8:58pm

Ok, I figured out the solution...

Apparently you must have a network adapter enabled to make this work.  I'm running a local VM and had my NAT NIC to the outside world disabled.  I created a separate internal network adapter, gave it an IP address, and the policy worked.

Free Windows Admin Tool Kit Click here and download it now
December 19th, 2012 8:58pm

Ok, I figured out the solution...

Apparently you must have a network adapter enabled to make this work.  I'm running a local VM and had my NAT NIC to the outside world disabled.  I created a separate internal network adapter, gave it an IP address, and the policy worked.

December 19th, 2012 8:58pm

Ok, I figured out the solution...

Apparently you must have a network adapter enabled to make this work.  I'm running a local VM and had my NAT NIC to the outside world disabled.  I created a separate internal network adapter, gave it an IP address, and the policy worked.

Free Windows Admin Tool Kit Click here and download it now
December 19th, 2012 8:58pm

Ok, I figured out the solution...

Apparently you must have a network adapter enabled to make this work.  I'm running a local VM and had my NAT NIC to the outside world disabled.  I created a separate internal network adapter, gave it an IP address, and the policy worked.

December 19th, 2012 8:58pm

Ok, I figured out the solution...

Apparently you must have a network adapter enabled to make this work.  I'm running a local VM and had my NAT NIC to the outside world disabled.  I created a separate internal network adapter, gave it an IP address, and the policy worked.

Free Windows Admin Tool Kit Click here and download it now
December 19th, 2012 8:58pm

Ok, I figured out the solution...

Apparently you must have a network adapter enabled to make this work.  I'm running a local VM and had my NAT NIC to the outside world disabled.  I created a separate internal network adapter, gave it an IP address, and the policy worked.

December 19th, 2012 8:58pm

Ok, I figured out the solution...

Apparently you must have a network adapter enabled to make this work.  I'm running a local VM and had my NAT NIC to the outside world disabled.  I created a separate internal network adapter, gave it an IP address, and the policy worked.

Free Windows Admin Tool Kit Click here and download it now
December 19th, 2012 8:58pm

Ok, I figured out the solution...

Apparently you must have a network adapter enabled to make this work.  I'm running a local VM and had my NAT NIC to the outside world disabled.  I created a separate internal network adapter, gave it an IP address, and the policy worked.

December 19th, 2012 8:58pm

Ok, I figured out the solution...

Apparently you must have a network adapter enabled to make this work.  I'm running a local VM and had my NAT NIC to the outside world disabled.  I created a separate internal network adapter, gave it an IP address, and the policy worked.

Free Windows Admin Tool Kit Click here and download it now
December 19th, 2012 8:58pm

Ok, I figured out the solution...

Apparently you must have a network adapter enabled to make this work.  I'm running a local VM and had my NAT NIC to the outside world disabled.  I created a separate internal network adapter, gave it an IP address, and the policy worked.

December 19th, 2012 8:58pm

Ok, I figured out the solution...

Apparently you must have a network adapter enabled to make this work.  I'm running a local VM and had my NAT NIC to the outside world disabled.  I created a separate internal network adapter, gave it an IP address, and the policy worked.

Free Windows Admin Tool Kit Click here and download it now
December 19th, 2012 8:58pm

Ok, I figured out the solution...

Apparently you must have a network adapter enabled to make this work.  I'm running a local VM and had my NAT NIC to the outside world disabled.  I created a separate internal network adapter, gave it an IP address, and the policy worked.

December 19th, 2012 8:58pm

Ok, I figured out the solution...

Apparently you must have a network adapter enabled to make this work.  I'm running a local VM and had my NAT NIC to the outside world disabled.  I created a separate internal network adapter, gave it an IP address, and the policy worked.

Free Windows Admin Tool Kit Click here and download it now
December 19th, 2012 8:58pm

Ok, I figured out the solution...

Apparently you must have a network adapter enabled to make this work.  I'm running a local VM and had my NAT NIC to the outside world disabled.  I created a separate internal network adapter, gave it an IP address, and the policy worked.

December 19th, 2012 8:58pm

Ok, I figured out the solution...

Apparently you must have a network adapter enabled to make this work.  I'm running a local VM and had my NAT NIC to the outside world disabled.  I created a separate internal network adapter, gave it an IP address, and the policy worked.

Free Windows Admin Tool Kit Click here and download it now
December 19th, 2012 8:58pm

Ok, I figured out the solution...

Apparently you must have a network adapter enabled to make this work.  I'm running a local VM and had my NAT NIC to the outside world disabled.  I created a separate internal network adapter, gave it an IP address, and the policy worked.

December 19th, 2012 8:58pm

Ok, I figured out the solution...

Apparently you must have a network adapter enabled to make this work.  I'm running a local VM and had my NAT NIC to the outside world disabled.  I created a separate internal network adapter, gave it an IP address, and the policy worked.

Free Windows Admin Tool Kit Click here and download it now
December 19th, 2012 8:58pm

Ok, I figured out the solution...

Apparently you must have a network adapter enabled to make this work.  I'm running a local VM and had my NAT NIC to the outside world disabled.  I created a separate internal network adapter, gave it an IP address, and the policy worked.

December 19th, 2012 8:58pm

Ok, I figured out the solution...

Apparently you must have a network adapter enabled to make this work.  I'm running a local VM and had my NAT NIC to the outside world disabled.  I created a separate internal network adapter, gave it an IP address, and the policy worked.

Free Windows Admin Tool Kit Click here and download it now
December 19th, 2012 8:58pm

Ok, I figured out the solution...

Apparently you must have a network adapter enabled to make this work.  I'm running a local VM and had my NAT NIC to the outside world disabled.  I created a separate internal network adapter, gave it an IP address, and the policy worked.

December 19th, 2012 8:58pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics