- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic to the Top
- Bookmark
- Subscribe
- Printer Friendly Page
A Launcher has already been started on this workstatio n
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
12-01-2011 04:58 PM
I am receiving the error "A Launcher has already been started on this workstation" after a workstation failure. When this has happened in the past I was able to restart the workstation and MAS90 would open. However, it will not clear this time. I am using 4.4. I followed the procedure to clear a phantom user from the server. Where so I go on the workstation to clear the flag that indicates that MAS90 is open?
Re: A Launcher has already been started on this workstatio n
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
12-01-2011 05:57 PM
Open your task manager and look for any pvxwin32.exe processes. If you see any, end the process.
But this may not the fix since you say you rebooted the WS.
Is this 90 or 200?
Re: A Launcher has already been started on this workstatio n
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
12-02-2011 08:53 AM
Thanks for the reply. I am running MAS90, and this particular unit is running 3.71 not 4.4 (my mistake). I did not see PVXWIN32.EXE in task manager. When task manager is open, and I try to open MAS90, I get the error and I see PVXWIN32.EXE appear. When I select OK on the error message to clear the error PVXWIN32.EXE disappears from task manager.
Re: A Launcher has already been started on this workstatio n
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
12-02-2011 09:14 AM
Reboot the server. If that doesn't fix it, uninstall and reinstall worksation setup.
Joe
Re: A Launcher has already been started on this workstatio n
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
12-02-2011 09:55 AM
Thanks. Rebooting the server corrected the problem.


