Commander Gui Startup Failing
After nearly a year of flawless usage, today commander refused to start its GUI.
It fails after bringing up a windows user control dialog asking for permission to make a change to this computer. Selecting NO does nothing, selecting YES fails the load and exits.
Error numbers include #6402, #1000 and others
After more investigation, it appears that even the commander service is refusing to run intermittently.
Commander is currently set to run using an account with full admin, r/w priviledges on this computer.
Any advice would be greatly appreciated as I would love to get this running tomorrow...
Thanks in advance
Mike
-
Hi, Mike:
Do you receive error message #6402 commander service did not appear to start. Trying starting the Commander Service using the services dialogue in commander?
Can you give it a try to verify if the problems in on service user permissions part?
Open Commander-> Service Setup-> Change run as "Service" to run as "Application" to see if it work properly.
If run as application work properly and run as service can not work as expected, the problems is most likely on user permission.
You can get it running OK by changing start-> services.msc-> commander service-> right-click properties-> Login-> This account to the account with permissions? If you do not want to use administrator, can you assign one proper user account with permission to run it. If you still have problems, you cna contact us at asiatech@seagullscientific.com. I will help you further. Thanks!0 -
Yes, I do get #6402. The problem is I can not get commander to open...
therefore I can not follow the specified procedure:
Open Commander-> Service Setup-> Change run as "Service" to run as "Application" to see if it work properly.
Is there some way of forcing it to open?
We have used Commander on a specific account for months that had all the correct permissions. So I am at a loss as to what happened.0 -
FYI: Seagull tech support helped find a solution to this problem. It was a full uninstall and reinstall of bartender. Thankfully it kept all my printer settings and label templates which saved a lot of work ... 0 -
Hi,
I have this #6402 error to. My Commander runs as an application. I have it as a start up program as it depends on the coms port being created.
It has worked like this for a year but today gave up the error. I noticed that when commander does finally open, the task list is not opened from previous use. The settings are defaulted. I opened the commander task list, set the settings back to what they were closed commander and reset the PC. On start up it opened and worked as usual. This PC has no user so it must run automate without being a service as the coms port is virtual and needs to start before commander searches for it.
When the PC is shut down, Commander is still running. Could that be the problem.
Any advise on what I can adjust to not get this error.
Thank you
0
Please sign in to leave a comment.
Comments
4 comments