Folder Redirection,Roaming Profile Autodesk Install/Startup Error 1606 and 1317

Issue:

Unable to Install or launch Autodesk applications while using redirected use profile  folders.

Common errors include

Error 1606 "Could not access network location"

Error 1317: An error occurred while attempting to create the directory.

Error 1325 - 'Documents' is not a valid short file name"

More details/Solution:

https://knowledge.autodesk.com/community/article/83791

 

 

 


The borrowing period established for the license server is not valid.

Issue:

When you tried to borrow a license, you received the following error message:

You cannot borrow a license at this time. The borrowing period established for the license server is not valid. Contact your system administrator to have the borrowing period reset to a value of at least one day (24 hours)

 

Solution:

https://knowledge.autodesk.com/community/article/92901

 


Folder Redirection,Roaming Profile Autodesk Install/Startup Error 1606 and 1317

Issue:

Unable to Install or launch Autodesk applications while using redirected use profile  folders.

Common errors include

Error 1606 "Could not access network location"

Error 1317: An error occurred while attempting to create the directory.

Error 1325 - 'Documents' is not a valid short file name"

Cause:

If you use folder redirection instead of roaming profile setup, some of the Installer functionality would fail, mainly due to Permission issues.

Solution:

Please use the following solutions to fix the immediate issue.

https://support.microsoft.com/en-us/help/886549/you-receive-an-error-1606-error-message-when-you-try-to-install-or-remove-a-microsoft-program

Root cause and Solution:

Microsoft recommends following method to Deploy Roaming User Profiles.

https://technet.microsoft.com/en-us/library/jj649079(v=ws.11).aspx

When folder redirection is used, some of functionality within windows installer might fail due to permission issue.

for e.g.Disk cost calculation on the folder share on the network. \\server\sharename\%username%. If User wouldn't have read permission on \\server\sharename, installer could fail.

If the roaming profile is setup properly without folder redirection, user profile would be transparent to Windows applications.


SketchBook iOS: This app is not compatible with your device.

I am back, sort of.  I am currently on the SketchBook QA team and we are getting a lot of tickets on this topic so I wanted to share this with the community. 

_______________________________________________

If you get this error when trying to update SketchBook from 3.7.4 to 4.0.4 on an iOS device:  This app is not compatible with your device. 

This app is not compatible with your device 2

DO NOT DELETE IT FROM YOUR iPad OR iPhone!  If you delete it, you will not be able to re-download it from the AppStore because the version on our AppStore is 64 bit.   Believe it or not, there are iOS devices are 32 bit or 64 bit and the easiest way to tell is by processor type.  You just need to know this one rule:

Any iOS device with an A7 Processor or higher  is 64 bit.

We have a long list of compatible hardware and it is noted on the SketchBook iOS product page:

Compatibility: Requires iOS 9.1 or later. Compatible with iPad Air, iPad Air Wi-Fi + Cellular, iPad mini 2, iPad mini 2 Wi-Fi + Cellular, iPad Air 2, iPad Air 2 Wi-Fi + Cellular, iPad mini 3, iPad mini 3 Wi-Fi + Cellular, iPad mini 4, iPad mini 4 Wi-Fi + Cellular, 12.9-inch iPad Pro, 12.9-inch iPad Pro Wi-Fi + Cellular, 9.7-inch iPad Pro, 9.7-inch iPad Pro Wi-Fi + Cellular, iPad Wi-Fi (5th generation), and iPad Wi-Fi + Cellular (5th generation).

For more information on 64 bit support on iOS from Apple,  go here:

http://www.macworld.com/article/3163248/ios/the-future-of-ios-is-64-bit-only-apple-to-stop-support-of-32-bit-apps.html

If you need to backup your older version of SketchBook, you can back it up via the iCloud.

https://support.apple.com/en-ca/HT204247

If you decide to upgrade your iPad that has A7 Processor or higher,  you are still entitled to the upgrade to SketchBook 4.0 for free.  You just need to download from the AppStore and restore it.

https://help.sketchbook.com/knowledgebase/restore-sketchbook-3-x-app-purchase/

I have also talked about 32 and 64 bit computing back in 2011 from this older Up and Ready Blog post:

http://upandready.typepad.com/up_and_ready/2011/09/general-systems-what-is-the-difference-between-32-and-64-bit-computing.html

Epilogue [June 13, 2017]

We have fixed the back end systems from Apple to resolve this issue.  You can now download a 32 bit app if you are on a 32 bit device.  Thanks to Andy Chang and the Development team for resolving this issue!

 


Autodesk 2017 Software running as Restricted user Certificate revocation check fail

Some customers have reported Autodesk 2017 product crash on initial launch for certain users with restricted permissions and certain group policies applied.

After some research we found the root cause of the failure is an invalid registry value set,  with Group Policy (from old .adm file) or other scripts.

 

"This error occurs when the 'State' value of below mentioned registry key is incorrectly set. This value corresponds to the Internet Explorer security setting "Check for publisher’s certificate Revocation" and "Check for signatures on downloaded programs"

HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\WinTrust\Trust Providers\Software Publishing
You can find a key with the name ‘State’. By default the values is set to – ‘23c00’"

 

more details on this key.

https://support.microsoft.com/en-us/help/2715304/error-message-when-you-try-to-validate-a-copy-of-windows-the-cryptographic-operation-failed-due-to-a-local-security-option-setting

 

 

 


The Power of Process Monitor

Process Monitor is a handy tool that we use sometimes when we need more information about what is happening on a computer when an Autodesk product is throwing an error. It can be a bit daunting because Process Monitor captures TONS of information, so it's challenging wading through thousands of lines of information to find the one line that actually pertains to the error. But sometimes Process Monitor is a lifesaver, particularly when we encounter an error that none of us has seen before.

I encountered one such error earlier today. The error message is "The application was unable to start correctly (0xc0000022). Click OK to close the application."

Inventor Error

That error is similar to "The application was unable to start correctly (0xc0000142)" so I immediately guessed it was related to the AppInitDLLs registry key. However, in this particular case, that registry key was completely empty. Event Viewer had absolutely nothing related to the error, so I turned to Process Monitor to try to get some idea about what was going on.

One of the first things I search for in Process Monitor is "ACCESS DENIED". That's the message it will give if there are any problems accessing files/folders/registry keys. Lo and behold, there was an ACCESS DENIED message pointing to C:\Windows\System32\mfc140u.dll. Checking the Security tab for that file showed this lovely message:

ReadPermissions

Well that certainly didn't seem right, so I ended up having to take ownership of the file so I could fix the permissions. Once Full Control permissions had been granted to the current user for that file, the error went away. And now we have this lovely knowledge article in case we ever encounter this error again:

The application was unable to start correctly (0xc0000022). Click OK to close the application.

Digging through a Process Monitor capture isn't anybody's idea of a good time, but sometimes it's the only thing that will help you find that needle in the haystack.