Jump to content

Unable to Start Producer


Recommended Posts

  • Member

Hello everyone,

I'm having trouble starting the Producer.exe (7.4.1 and 7.4.0) on a rather locked down laptop I have (domain secured) and I receive this error message:

image.png.2524fff63fd768d07b0266cd8d46d63c.png

Could I get some more information on what process "WATCHOUT MANAGER" is and where it is located on the file system? I have a feeling the anti-virus or a system policy is prohibiting the service or program from running. I'd like to get Watchout 7 into our labs for the students, but I need to get through this hurdle locally before I make a larger leap.

-Daniel

Link to comment
Share on other sites

  • Dataton Partner

Hi Daniel,

WATCHOUT Manager is the core software component and it sits in the WATCHOUT 7 folder (process-manager.exe).

When you open the Producer through the link on the desktop, it usually also starts the Manager. On a display server, the manager is normally the only component you need to start. You can check that is is started if you look at the icons of running services in the bottom right of the Windows task bar.

If you try to start WATCHOUT by just double-clicking onto a WATCHOUT 7 project file, this doesn't start the Manager. So you need to start that through the link on your desktop as well.

Hope this helps!

/Rainer

Link to comment
Share on other sites

  • Member

Thanks for the help, I dug into this a bit further and it looks like the producer shortcut is starting another process which is flagged by the security policy in the IT department. To get around this I need to run the program with administrative privileges, but because the application writes the AppData of the user it is running under (in this case an account called "manager" that is off the domain it is throwing an error. I can get around this by changing permissions, but I think I might want to flag that as a bug.

Could we explore the possibility of not using %USERS%/$user/AppData as a storage point for Watchout? I'd love for the settings to be stored inside the Watchout installation directory, not the user path. 

Now I'm running into an issue where I'm not seeing the ability to add a director or asset manager locally.

image.png.fd669a96c73c75368d9ede6e7e7d5eab.png

image.png.a8f076f7c7ccd3a726f34b3e499ccb73.png

I'm guessing this is a similar issue where the process isn't launching. Other than running without security (which is going to be a tough sell for a classroom lab situation), what options do I have to get this working?

(I can get it to recognize the manager, but I have to start the process-manager.exe manually, and then I end up with the dual-splash screen of a display server, but this isn't workable.) Does this need to be started with specific arguments to suppress the display-server configuration?

image.png.4d435c1cc2f6838a5109a584b18884a1.png

 

Link to comment
Share on other sites

  • Dataton Partner

Once you start Producer incl. Manager, you should see your computer in the right part of your devices list.

I assume that more ports need to be open, e.g. those for the discovery mechanism and at least all of the basic ports mentioned in the manual under

Appendices/Network

The splash screen might have come up because a production computer can today also act as a display server at the same time. In your case, no director is enabled which you would see as a small icon behind your production computer entry in the devices list.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...