The specified workspace does not exist

[jason_hance]

"The specified workspace does not exist". I continue to encounter this error message when I try to save to a network drive location in Inventor 2017. I have opened support cases with our reseller and AutoDesk and cannot seem to find a cause. I do know that it is not an issue with my project file as we have gone through this exhaustively. I have a feeling that the issue is a conflict with the license server since the issue will go away temporarily after the license server is reset. This will resolve the issue for a short period of time but will come back at random intervals. I am not having any issues with opening Inventor, creating files or saving to a local directory. We have 6 licenses in our office and only myself and one other user are having this issue.

Any advice would be greatly appreciated.

Thank you,

kelly.young has embedded your image for clarity.

[Anonymous]

I have seen issues with network shares mapped to drive letters, especially since moving to Windows 10. Try using the full UNC path to the files and see if that resolves the problem.

[johnsonshiue]

Hi Jason,

I assume z: drive does exist. Do you have write privilege to the drive? Also, if you simply copy an paste to the drive, does it work?

Many thanks!

[jason_hance]

John,

Thanks for the reply. Yes we tried that first at the suggestion of our reseller support. This was unfortunately not able to resolve my issue. All of our installations are mapped drive letters and only 2 of us are having this issue. Can you think of any other settings that are unique to each workstation that my conflict with the license server. Also, could resetting the license server clear any issues that may not normally be associated wit the license server? Thank you so much for your suggestion.

[jason_hance]

Johnson,

Yes, the drive exists and is on a dedicated server. I have write privileges to this drive and can read and write to and from all of my applications including all AutoDesk products with the exception of Inventor. We have been using Inventor for several years and versions and I have never had this issue before. If I request our IT person to reset the license server I can use Inventor to save out files for a short period of time until the problem comes back. When I have this issue I can use Inventor and save to local drives only. To get by, I have had to save everything locally and then move it to the shared drive. I am concerned that this extra step could lead issues with unresolved links if something is not done correctly.

Thank you for your response!

[johnsonshiue]

Hi! The behavior still does not make sense to me. Inventor does not dictate how a drive saves or opens a file. Is it possible Z:\ is designated as a Library folder? Do you have Add-Ins relying on Z:\?

Many thanks!

[DannyHubbard]

Are the license server and the server your Z drive is mapped to the same server? And by resetting the license server, I am guessing this is just a reboot of the server.

What it the operating system on the server where the Z drive is mapped to, what are the client operating systems? Also on the clients what is the User Account Control setting and how is the Z drive mapped (through a login script or through Windows Explorer).

Thanks,

Danny

[jason_hance]

Danny,

Thanks for your response. Please see the responses I received from my IT person.

-The license server and the Z: drive are on the same server.

-When I reset the Autodesk license server, I open the LMTools GUI on the file server, and click the Start/Stop/Reread tab. Then, I click Stop Server, wait, then Start Server. This restarts the FlexLM license service only.

-The file server is running Windows Server 2008 R2 Standard.

-The clients are running Windows 10 Pro 1709.

-UAC is unchanged from default.

-The drives are mapped using Windows Explorer.

Thanks,

Jason Hance

[DannyHubbard]

Jason,

Its really strange that resetting the license server would allow you to save again to the network drive, make no sense to me.

If you borrow a network license do you still have the problem saving to the drive?

Do all the Inventor users there have the same problem?

If a different user logs onto your machine do they have the same problem?

Thanks,

Danny

[jason_hance]

Danny,

I agree about the license server. I am no IT guy or software engineer but you would think that that could narrow things down a bit. Do you know what would get refreshed when the license server is reset? I never have a problem with being able to use the software. It just can't see the network folders.

I will try to borrow a license and see what happens. Everything is working at the moment because we restarted the license this morning.

I would say that about half of us are having some sort of an issue. Two of us have this problem where we can't save at all, another person has a more intermittent issue where he will have a problem saving and just save to another folder and come back and it works. Several of us have newer HP P910 workstations with Windows 10. Half of these work properly and two of us have the issue. There are two people on older HP workstations with Windows 7. One works and one doesn't.

I had another user who is not having the issue on his machine log in to mine and it didn't work for him either. Does not seem to be linked to specific user accounts or permissions but to something in hardware or network settings.

I should mention that when I am having the problem I can see the drives in the save as dialogue box. The only thing that seems different is that it defaults to my documents folder on my hard drive instead of to the last directory I saved to as it would normally do. I can navigate to the folder I want but it gives me the "Specified Workspace does not Exist" message.

Thanks,

Jason Hance

[DannyHubbard]

Jason,

The next time this error occurs can you check the Windows Event Viewer - Windows Logs and Applications to see is there are any messages around the failed save or open attempt, I would check this on both the client and the server.

One thing that maybe the issue (though I have never seen it before) is if you have too many interaction or session between the client and the server it maybe maxing things out, which would explain why resetting the license manager fixes it for a while. Resting the license manager would reduce some of the session counts between the client and the server until they rebuild over time.

Thanks,

Danny