Hi Scott,
I don´t have seen your error message, but your description sounds familiar. Especially when considering that you know Innovator I expect that the basic configuration was done correct.
I remember following error message when updating from I11 to I12 -> Multiple Errors: DoPhysicalFiles - Access to the path is denied. -
It´s not the same text, but somehow similar.
Do you use Active Directory? Is your Innovator installed at a server that contains another Innovator? Does this other Innovator use Active Directory?
If yes, go to IIS and check if "Vault" has Windows Authentication enabled. If yes, deactivate it. It can happen that previous installations mess up your latest installation regarding IIS settings. Especially when your new Innovator uses the same IIS paths then the old one.
In my case I had to restart the Vault App Pool each single hour otherwise people weren´t able to open files. So file download worked for a certain amount of time. It was fun to restart the app pool 8 times a day for several days. Aras support team really fought hard to find the root cause.
Angela
Hi Angela, Thanks for taking the time to look at this.
This is a new server with just the one Innovator installed on it, no Active Directory either. I checked the website, the InnovatorServer, and the 5 subfolders including the Vault in IIS and they are all just Anonymous Authentication.
I have uninstalled and re-installed a couple time to try and figure this out, but the issue has been there since the initial one. We've also reproduced the error on a few different servers now.
Even more confusing, we installed a new instance of Innovator 2023 on a server that had an existing, and properly working, Innovator 2023 install. The old one was the typical InnovatorServer, and the new one we just called InnovatorServer2. It's under the same Default Web site in IIS and yet the old install works and the new install has the vault issue.
Thanks,
-Scott
Have you updated all the config files in the code tree? Especially vault.config and the ones in the OAuthServer folder?
We've done it a few different ways trying to narrow down the cause of our issue.
The current server I'm looking at we have all the config files in their out of the box state. We figured it would be easier to find the issue without any changes or customizations involved. So all URLs are left as localhost, the vault path is just E:\Aras\Vault\, etc.
Our dev server, which we didn't notice the instance in until recently though it may have been there the whole time and we just missed it, is set up differently. In that case, IIS is setup with an SSL certificate and the website is running HTTPS, so the the Vault.config's InnovatorServerUrl key was changed to use that https URL rather than localhost. The OAuth.config also has the https URL in the various places it should be, <redirectUris>, <postLogoutRedirectUris>, <allowedCorsOrigins>. The main InnovatorServerConfig.xml uses the https URL for the OAuthServerDiscovery url as well.
To Scott or anyone else facing this issue, this is how I have solved the same error:
Adding the yellow highlighted section below to your "Innovator/Server/appsettings.json" file, save and restart IIS
"SessionOptions": {
"IdleTimeout": "08:00:00",
"Cookie": {
"Path": "/"
}
},
