Revit 2017 will not create LOCAL after Win 10 upgrade

[Anonymous]

There are some PCs that have been affected by this issue. Revit 2017 cannot created a new LOCAL of a central model on Revit Server 2017. Some PCs are capable. so are not.  Everything was fine before the Win10 upgrade.

Revit 2015 on the problem PC is OK.

I will post the resolution if I find one.

Terry

[lars-ake.johansson]

Hi,

Can you post a journal-file from when you get the error?

[Anonymous]

Files attached.

[Anonymous]

And I just saw the attached dump file was created immediately after i clicked OPEN on the dialog box.

To re-iterate, this is only happening on 2-3 PCs from what I am gathering right now....  And on those PCs, it is happening in multiple windows profiles.

[lars-ake.johansson]

Hi,

I need the file that's named "journal.#####.txt" from the session where you had the error.

[Anonymous]

The previous three files are all the journal files from the error session.

Are there any files on the Revit Server side?

Thanks, Terry

[lars-ake.johansson]

sorry i missed the previous post.

[lars-ake.johansson]

Hi,

From the journal it looks like the server throws an error:

0:< Message inside RevitServerClientSideException: 
   An exception caught in RSEnterpriseClientInterop during operation handleServerException: 
   Type=UnauthorizedAccessException, Message : Access to the path is denied.

 The server logs will probably have some more info. Please refer to the following article to locate them:

https://knowledge.autodesk.com/support/revit-products/learn-explore/caas/CloudHelp/cloudhelp/2015/EN...

If you could post the following logs, I will have a look.

• AdminService.log
• AutoSyncLog.log
• LocalService.log
• ModelService.log

Strange though that a client update would cause an error on the server......

Have did you change the default location on the server? Please make sure that directories have the appropriate access (step 6-7 in the following):

https://knowledge.autodesk.com/support/revit-products/troubleshooting/caas/CloudHelp/cloudhelp/2017/...

[Anonymous]

Something to keep in mind, other PCs have no issues.  It is also not related to the user credentials.

The following two files are the only ones located in the folder that are timestamped for the occurrence of the error.

I will upload the other files shortly, just in case....

https://jptarchs.sharefile.com/d-s8eac63ff68946ce9

https://jptarchs.sharefile.com/d-s0eaded35e7446598

[Anonymous]

Sumething I just realized, the ones I uploaded were SSVCLOG files.  LOGs coming shortly.

[Anonymous]

LOGs are in the link below.  The attached screenshot shows the timestamps.  Therror was around 4:57pm.

https://jptarchs.sharefile.com/d-s3500383007e4a3da

[Anonymous]

Thank you for your help Lars-Ake.

Let me know if you need anything else from me.  The issue is currently affecting two PCs.

Terry

[lars-ake.johansson]

Hi,

I have been looking trough the logs and talked to some of my colleagues and they are as stumped as I am.....

The error message indicates some kind of server error/exception but here is nothing in the logs that would indicate what that might be..... You might want to check the Windows logs on the server, if there is any errors there that might indicate if something went wrong on the system....

We need to do some detective work to figure out where or what is causing this and where the "UnauthorizedAccessException" is coming from.

1. On the system "WS12" (where the journal came from) - could you check if the directory "C:\Users\terry\AppData\Local\Temp\Revit_ModelDataFileDownload_febbaeba8b3f427bbbf4c5e2402cfb83" still exist?
   This might indicate that it for some reason was unable do delete the temp files (access rights, files locked by virus scanners......)
2. On WS12 - Try saving a new file to the server and see if that cause problems as well.
3. Problems with the model?
   1. Have you tried other models on the same system?
   2. Have you tried the same model on other systems (from scratch without having the local file)?
4. User profile/access.
   1. What is another user logs in on this system and tries to open the same model (and/or other models)?
   2. What if "terry" logs in to a system where it's working and opens this model (and/or other models)?
5. Systems - Is there anything 'special' about the two systems that are not working? Brand, Virus scanner, configuration ......
6. There is a slight possibility that it might be cause by an invalid/corrupt "Revit.exe.config" - some 3rd party addons could cause this if they are not installing correctly. Could you post a copy here of this file from WS12 (it's in the Revit program directory)

[Anonymous]

Those are great things to check.  I will remote into there systems tonight and report my findings.

On a side note, they are able to SYNC using existing local models, just cannot create new local models.

And for the one user, I created a local for her using a system that works.  She moved it to her PC and was able to successfully SYNC to the Revit Server, I checked the RevitServerAdmin interface.

[Anonymous]

1. Cleaned out TEMP folder.  still getting error.

2. Created new worksharing model, saved it to Revit Server. Closed model. Tried to create new LOCAL of new model, failed, see attached error which i have been getting this entire time.

3.   1. Yes, same error.

      2. Yes, that model opens on known good system.

4.   1. Still errors

       2. any user can create LOCAL on a known good system

5.  Systems are Dell, one is quite old, the other is two years old.  Save Antivirus.  Disabled Antivrus, still errors.  

6.  config file attached.

[Anonymous · Accepted solution]

I previously tried the Repair and Reinstall option through Control panel, it did not fix it.

Last night I completely uninstalled Revit 2017, rebooted, then Reinstalled.

It is working correctly now for both of the affected PCs.

Thanks for your help.

[lars-ake.johansson]

Glad that worked.

I looked trough the .config and that was OK so something else in Revit obviously got corrupt...

This one is defiantly on the top-list of weird errors... 😉

Regards