2023 Network Deployment - Installation quits with error 1327

[patrick.phillipsT8ATG]

Okay, so I am creating a network deployment of AutoCAD Electrical so we're all working with the same libraries and support files. I have the network deployment all set up and good to go in terms of running the shared content batch file and copying everything over to where I want it.

The problem is that when I go to install AutoCAD Electrical itself using the Install batch file, It will run, and then it will quit with an error. Checking the log file, I see this:

2022-09-02T00:56:16.266 [Deployment: 5072, single] [RMT0004 INFO] Deployment started...
2022-09-02T00:57:30.495 [Deployment: 5072, single] [RMT0004 INFO] Deployment started...
2022-09-02T00:57:39.834 [Deployment: 5072, single] [RMT0004 INFO] Installing: ODIS Installer
2022-09-02T00:57:39.837 [Deployment: 5072, single] [RMT0004 INFO] Installing: Microsoft .NET Core Runtime 3.1.10
2022-09-02T00:57:39.839 [Deployment: 5072, single] [RMT0004 INFO] Installing: Microsoft ASP.NET Core 3.1.10 Shared Framework
2022-09-02T00:57:39.841 [Deployment: 5072, single] [RMT0004 INFO] Installing: AutoCAD 2023 Shared Language Pack - English
2022-09-02T00:57:39.845 [Deployment: 5072, single] [RMT0004 INFO] Installing: ACA & MEP 2023 Object Enabler
2022-09-02T00:57:39.846 [Deployment: 5072, single] [RMT0004 INFO] Installing: AutoCAD 2023 Shared
2022-09-02T00:57:39.848 [Deployment: 5072, single] [RMT0004 INFO] Installing: Autodesk AutoCAD 2023 - English
2022-09-02T00:57:39.849 [Deployment: 5072, single] [RMT0004 INFO] Installing: AutoCAD 2023
2022-09-02T00:57:39.851 [Deployment: 5072, single] [RMT0004 INFO] Installing: Autodesk Licensing Installer 1.0
2022-09-02T00:58:27.554 [Deployment: 5072, single] [RMT0004 INFO] Installing: AutoCAD Electrical 2023
2022-09-02T00:59:14.321 [Deployment: 5072, single] [RMT0004 INFO] Installing: AutoCAD Electrical 2023 Language Pack - English
2022-09-02T00:59:14.324 [Deployment: 5072, single] [RMT0004 INFO] Installing: ACADE Private
2022-09-02T00:59:14.327 [Deployment: 5072, single] [RMT0004 INFO] Installing: AutoCAD Electrical 2023 Content Pack
2022-09-02T00:59:34.883 [Deployment: 5072, single] [RMT0004 INFO] Installing: AutoCAD Electrical 2023 Content Language Pack - English
2022-09-02T00:59:36.475 [Deployment: 5072, single] [RMT0004 ERROR] 1603: Fatal error during installation.
2022-09-02T00:59:57.277 [Deployment: 5072, single] [RMT0004 ERROR] {B80FBC28-6676-358B-AB4B-89FA3AA4F868} : 1603
2022-09-02T00:59:57.277 [Deployment: 5072, single] [RMT0004 ERROR] Deployment failed!
2022-09-02T00:59:57.277 [Deployment: 5072, single] [RMT0004 INFO] Error context: MSI (s) (E4:80) [00:59:36:351]: Product: AutoCAD Electrical 2023 Content Language Pack - English -- Error 1327. Invalid Drive: W:\ Action ended 0:59:36: CostFinalize. Return value 3. Action ended 0:59:36: INSTALL. Return value 3. Property(S): ROAMABLEROOTFOLDER = %HOME%\AppData\Roaming\Autodesk\AutoCAD Electrical 2023 Content Language Pack - English\R24.2\enu\ Property(S): ROAMING = 1 Property(S): ACAD_NOTEPAD_PATH = C:\WINDOWS\system32\notepad.exe Property(S): DOTNET_INSTALLED = #1 Property(S): DOTNET4_VERSION = 4.8.04084
2022-09-02T00:59:57.277 [Deployment: 5072, single] [RMT0004 INFO] Please explore possible solution from: https://knowledge.autodesk.com/search-result/caas/downloads/content/autodesk-licensing-service-relea...EML
2022-09-02T01:01:31.230 [Deployment: 5072, single] [RMT0004 INFO] Deployment exits

I have gone through and checked everything I can think of, and nothing seems to work to alleviate the issue. I double and triple checked all the file paths, I made sure that every last bit of Autodesk product was completely removed from the machine. I even went as far as to create an all new deployment, but still I get this error, and I cannot figure it out.

Can anyone help?

@patrick.phillipsT8ATG 

Topic title has been edited to improve findability by @alina.balkanskaia. Original: 2023 Network Deployment - AutoCAD Electrical will not install.

[TravisNave]

This is the error I see:

Electrical 2023 Content Language Pack - English -- Error 1327. Invalid Drive: W:\

What is this W:\ drive that it seems to be looking for???

Did you create your network deployment using the preferred UNC path like \\Servername\Share or a instead a mapped drive to W:\ when creating?  This might be your culprit.  

[patrick.phillipsT8ATG]

Nope. That wasn't it. Still getting the same error with the UNC path.

I did some further digging and apparently the issue is in the registry where the solution is to make sure all the registry paths for the following registries are pointing to the C: drive.

• HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders
• HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders
• HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders
• HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders

And they appear to all be pointing where they are supposed to, except the User Shell Folders are set up with alias paths instead of direct paths. By alias paths, I mean that instead of the AppData key pointing to "C:\Users\patrick.phillips\AppData\Roaming" it's instead pointing to "%USERPROFILE%\AppData\Roaming".

I think this might be the culprit, but our IT team is looking into potential alternatives that does not include editing the registry, because they don't feel comfortable doing it.

[TravisNave]

I'd look for new IT staff then. Registry changes should not bother them.
But yes, typically Autodesk installations look for profiles on the C:\
drive. Are you using roaming profiles on a network drive? Is that what's
on W:\ drive?

[mdavis22569]

@patrick.phillipsT8ATG   was @TravisNave  able to help get you all set?

[patrick.phillipsT8ATG]

Unfortunately no, as the IT department was not budging on the idea of changes to the registry, but I was able to get a workaround going.

I had to install as regular, copy the appropriate folders to the network, then manually change the support file paths. After that, I sent my team a comprehensive tutorial on what to do to connect to the correct folders on the server.

We're all set here.