Vault Client 2017 hangs on start-up

[karthur1]

I am preparing to move our workstations and Vault to 2018. I have already updated our vault server to 2018 ADMS.  Now when I start Vault Pro 2017 it will hang on the "Authenticating with server" most of the time.  Occasionally, it will stop at "Testing server compatibility".  The only thing I can do is end the task with windows task manager. 

What is odd about this, is that I can start Inventor 2017, use a vault enabled project and login into Vault this way. I am just not able to use the Vault Professional 2017.

I have tried the three things below, which did not resolve the issue:

Repair install of Vault Pro 2017 and reboot of client.

Uninstall-Reinstall-Reboot of client.

Reboot of Vault server.

Any ideas as to why this hangs, or better yet how can I resolve it so I can use Vault Pro 2017?

Thanks,

Kirk

[Senthil_Kumar]

@karthur1 A wild guess. Have you ever used dual monitor and one of the dialog is still in the other monitor and looking for some action to perform? Also check if there is any other dialog hidden behind.

[karthur1]

Senthil,

I am using dual monitors, but there is no other dialog shown.  I have both Vault Pro 2017 and 2018 client installed on the workstation.  If I try to start the Vault Pro 2017 (and it hangs), then I end task, and next try to start Vault Pro 2018, it too will hang.  I have to reboot the computer before I can get VP 2018 to start.

Can you tell me what services have to be running on the client for Vault Pro to "Authenticate with Server"? I want to make sure they are running.  There is no Antivirus software running and the firewall is disabled on the workstation.

It seems like that after I installed VP 2018, that this became broken.  Could it have anything to do with version of Microsoft.NET or MS Visual C++ that is installed?

Kirk

[rachel_li]

Hello Krik,

Could you check if the A360 Desktop is running on your machine? There was a case that Vault client cannot start if the A360 Desktop is running. Try to exit A360 Desktop and Desktop App as well and try again. Restart Vault or restart machine may be not needed but could have a try if still not working.

Thanks,

Rachel

[karthur1]

A360 Desktop (adsync.exe) was running on the machine.  I ended this task (with Windows Task Manager).  Now when I start Vault Professional 2017, it is now able to login.  So that does seem to be the issue.

I checked the version of A360 Desktop and it is V8.2.3.1800.  This is the same version as other workstations that does not show the same issue with VP 2017.

How do I resolve the issue?  Repair install on A360 Desktop, uninstall A360.... other????

Thanks,

Kirk

[karthur1]

Just for clarification, I did not "End Task" on the "Autodesk Desktop App" (AutodeskDesktopApp.exe *32).  It is still running.

Thanks

[DarrenP]

if the a360 desktop is not being used on that machine i would just uninstall it

[karthur1]

That would be easy, but I am afraid that's not the case.

[rachel_li]

I guess there probably have some conflict when log in Vault server with the A360 Destop connection, but not figure it out yet. If you do not use A360 Desktop as your local driver, you can uninstall it or just exit it before log in Vault. 

Regards,

Rachel

[jbohn217]

We have the same issue with vault. We have also had an issue with inventor hanging when opening a file.

We found a process on our machines that if we end , vault or inventor open or continue immediatly

We have installed TCP view on all the machines now so we can see all the processes that are open.

(Note that this requies admin rights)

When Vault (or sometimes Inventor) open, there is a process called AC webbrowser. 

With inventor, it is an Inventor process.Whenever the remote address is   deploy.static.akamaitechnologies.com Vault hangs.

If you right click and end the process, The startup completes immediatly.

On a couple of machines we have deleted A360 and they still hang. 

If either vault or inventor hang, we just look for the longest remote address, It is usually deploy.static.akamaitechnologies.com.

We havent found an actual fix, but ending the process only takes a few seconds.