Index was outside the bounds of the array.

clabough · Post by **clabough** » Mon Sep 19, 2005 4:37 pm

I've just upgraded a Vault server from 2.0.6 to 3.1.2 and when logging in via the Admin Tool or GUI client, I receive the following error.

Server was unable to process request. --> Index was outside the bounds of the array.

I've attached the client log file.

What should I do/try?

dan · Post by **dan** » Mon Sep 19, 2005 6:17 pm

Check the server log at %windows%/temp/sgvault for more info on the server error.

It is possible the server got upgraded, but the database did not, which can happen if an old database is restored after the installation.

clabough · Post by **clabough** » Tue Sep 20, 2005 1:11 am

The log file at %windows%/temp/sgvault has not been written to since 2/2004. I've attached the install.log and I saw the database upgrade take place during the install.

dan · Post by **dan** » Tue Sep 20, 2005 6:57 am

The server log might be somewhere else then - go to c:\inetpub\wwwroot\VaultService\Vault.config on the server machine and search for the LogFilePath element, which will tell you where the log file is.

clabough · Post by **clabough** » Tue Sep 20, 2005 9:29 am

I am able to login via the Web client as admin, but not via the GUI client or Admin Tool as any user. I ran the repair installation and still the same problem.

Here's the log entry for today:

----9/20/2005 8:22:04 AM sgvaultsystem--()--
System Started
Version 3.1.2.3511
Cache Level = 1
DataBase Buffer Size (KB) = 256
LogFile Path = D:\Temp\sgvault
Log Level = Quiet
Archive Log = Weekly
ReverseDNS Lookup = True
Maximum HTTP Request Length = 102400
Overwrite Log on Startup = False
Session Timeout = 4320
Active Directory Domain =
SGVault Working Directory = D:\Temp
SGVault Server URL = http://(my domain)/VaultService
Identity = JAVELIN\ASPNET
----9/20/2005 8:22:51 AM admin--shawn.csrv-staff.uidaho.edu(129.101.66.172)--SSL Disabled Login
----9/20/2005 8:23:24 AM admin--shawn.csrv-staff.uidaho.edu(129.101.66.172)--SSL Disabled Logout

No entries are made when I get the "Server was unable to process request. --> Index was outside the bounds of the array." error.

dan · Post by **dan** » Tue Sep 20, 2005 9:44 am

Is this error printed in the messages pane or a dialog, and exactly when is it displayed (you might provide a screen shot so we can see the exact message).

Were there other configuration changes to the machine along with the Vault upgrade?

Also, can users on other machines login?

And one more: Is the server on the same machine as the client?

clabough · Post by **clabough** » Tue Sep 20, 2005 10:08 am

The error occurs from both the server and a seperate client. It appears shortly after entering the login information. The upgrade to 3.1 was prompted because I was getting the CryptoAPI errors with my 2.0.6 installation.

I've attached screenshots from the GUI and Admin Tool.

dan · Post by **dan** » Tue Sep 20, 2005 10:23 am

Did the CryptoAPI errors suddenly start appearing, or did 2.0.6 ever work?

You might try uninstalling and re-installing - it sounds like something went wacky with the configuration...

clabough · Post by **clabough** » Tue Sep 20, 2005 10:33 am

The CyptoAPI errors just started appearing. I tried the steps for the machine keys etc. shown on the KB, but it still did not work, so I wanted to upgrade to 3.1 since it was supposed to not have that problem.

I've just uninstalled Vault and reinstalled and still have the same error as above.

dan · Post by **dan** » Tue Sep 20, 2005 10:46 am

Here's an idea: Try temporarily renaming your vault client cache folder (in %appdata%/SourceGear/Vault_1) and try it again - perhaps something didn't get converted right on the client. If you get the same results, rename it back to what it was.

clabough · Post by **clabough** » Tue Sep 20, 2005 11:19 am

I renamed the Admin and Client folders (the only ones) in that directory and had the same problem. The folder did not exist in my profile on the server.

I need to get this back up and running today. Is there an expedited method we could use?

clabough · Post by **clabough** » Tue Sep 20, 2005 3:00 pm

Granting Everyone Read & Execute/List/Read rights on the root All Users folder cleared up all issues.