nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Enterprise Server Upgrade: Error 1310

dsinha

Hello everyone,

We are upgrading our Enterprise installation from 11.2 to 11.4. It is a single-machine install and we are upgrading each component individually.

The portal upgrade completes without any problem. But when we run the server executable, it keeps getting stuck and up pops an error message saying that it cannot write to a file in the Config.Msi folder (see screenshot below).

configmsi error.jpg

Needless to say, we are doing this upgrade with full admin privileges on the server machine. We cannot see/find the Config.Msi folder and thus cannot change any read/write permissions for it. We have talked with Esri tech support, but they say that it is a Windows issue.

We are really stuck, having tried to run the upgrade three times in three days, only to get stuck at the same step every time.

I am hoping someone here has run into a similar issue and would have some suggestions for us.

Thanks in advance for your help!

Deb

Find more posts tagged with

Accepted answers

All comments

ryanuthoff

Open command prompt as an administrator and type in: icacls "C:\Config.Msi" /T /C /grant administrators:F

Once you do that, you should be able to access the C:\Config.Msi directory in file explorer (note you will still need to type the file path into file explorer and navigate to it that way). I had the same issue, where I couldn't navigate to the folder in File Explorer. It existed, but it said access was denied, even though I have admin privileges. Running that command fixed it for me. My Source.

From there, you can set privileges appropriately. And if you see the .rbf file that Esri is having issues with, you can probably delete it and try installing server again.

George Thompson

I just want to ask, do you have both install files (<filename>.exe & <filename>.exe.001) in the same location?

Have you done a checksum on the files you downloaded matches what is in My Esri?

As far as I know, there is NOT a way to download "114_192937". That is not a released version.

dsinha

Hello, our IT team is understandably hesitant to give full control permissions to the entire C: drive.

We tried to create a Config.Msi folder but we receive a message saying that the folder already exists (though still not visible). And we cannot change permissions of a folder that is not visible.

I am starting to believe that the problem is with the Server executable file given that we didn't run into the issue with the Portal or Portal Web Adaptor installation files. Those executables must have used the Config.Msi folder during the installation process too, yet they didn't have any problems writing to the folder.

We have already spent 4 days trying to complete the upgrade, have broken connections to our organization's network drives and our reverse proxy server due to rollbacks every time the process got stuck at the Server installation stage.

Are there any Esri representatives reading these questions and can they confirm if our hunch about the Server executable file is correct? Is there any way I can escalate my case to a level where they can confirm or deny the possibility?
The Server installation file that is currently available for download on the website is ArcGIS_Server_Windows_114_192938. Is it possible to download a older version (for example, 114_192937) and see if it produces the same error message?

Thanks for your help!

Deb.

dsinha

Thanks @RyanUthoff, would try the two suggestions and post the results.

ryanuthoff

That folder is used by Windows Installer during installation processes of software. I believe that that folder is automatically created during the installation process, and then automatically deleted after the installation process. So it makes sense that you are not able to see it.

There are a couple things that I would try next.

Referencing this post the Windows Installer performs the installation in the system context, even if you're logged in as an admin. So you'll need to make sure the directory has full control permissions for either everyone or the system group. Of course, since you can't see that folder, that's going to be difficult to do. So, you'd need to move one step higher, which in your case, is going to be the entire C: drive. So, you might want to check that both the admin account and either everyone or the system group has full control permissions for the C: drive.
Alternatively, (and I'm not sure if this will work), you could manually create the Config.Msi folder and ensure that everyone has full control permissions. That way when Esri starts the installation process, the folder will already exist and already have full permissions. So if it is in fact a permissions issue, that should take care of it, theoretically of course.

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.