We are moving the vault database from a Server 2003 (32 Bit) to a 64 bit Server 2008 R2 (among other things).
We installed the new server on new hardware, gave it a name 'NewX', copied the files and stuff from 'X' to 'NewX', then renamed 'X'->'OldX' and 'NewX' -> 'X' (just so the internal network will appear to run the same to everyone else). Now in the process of installing the web services (like Vault) on 'X' (the new one).
The Server 2003 was running SQL server 2005 Standard. The Server 2008 R2 is running SQL Server 2008 Enterprise.
Server 2003 was running IIS6; Server 2008 R2 is running IIS7
Server 2003 Vault was installed as own 'site' on port 8000; on Server 2008, I created a separate site as well on port 8000 (this keeps the vault service separate from other web services like CRM running on the same machine)
Copy and restore of the database worked fine to Server 2008
I created a new directory and 'site' on Server 2008 stored in C:\Inetpub\VaultServer (on Server 2003 it had been stored at C:\InetPub\wwwroot)
I installed the 64 bit 5.0.4 release (just downloaded today); Server 2003 was running 5.0.3 32 bit version.
During installation that appeared to work just fine (it found the database, asked if we wanted to keep it, etc.) is when the strange behavior occurs;
[The web browser is IE8 and the URL is in the 'Trusted' sites zone which does have scripting turned on (I think)]
Immediately after installation, you are placed in a web browser for Admin functions. The url is http://xyz.domain.com:8000/vaultservice ... Login.aspx?........
but the web display has NO images, only simple text and hyperlinks; it is as if the javascript code that is in the page isn't being executed [this is my conjecture]. You can do some of the Admin stuff by clicking on the links that appear, but the background images etc.
Furthermore, a client computer accessing http://xyz.domain.com:800/vaultservice (to get the new client installed), is presented with a completely blank screen whose page contents contain only
This was using Firefox 3.6.6<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=windows-1252" http-equiv=Content-Type></HEAD>
<BODY></BODY></HTML>
If I use my existing 5.0.3 client to access the new server, the respository shows up just fine, and we can do normal vault things.
It appears that something in the 'web' delivery of pages is mucked up on this installation? or we have IIS7 configured in some bizarre fashion?
Have anyone else observed this behavior? Suggestions?
I have added a snippet of the sgvault log:
Code: Select all
----16/07/2010 9:29:00 AM admin--fe80::e4be:e719:5335:ba6f%11(fe80::e4be:e719:5335:ba6f%11)--SSL Disabled Login
----16/07/2010 9:31:57 AM kadorken--puma.thoughts.thinkage.ca(192.102.11.45)--SSL Disabled Login
----16/07/2010 9:44:07 AM sgvaultsystem--()--
System Started
Version 5.0.4.18845
Cache Level = 1
DataBase Buffer Size (KB) = 256
LogFile Path = C:\Windows\Temp\sgvault
Log Level = Quiet
Archive Log = Weekly
ReverseDNS Lookup = True
Maximum HTTP Request Length = 102400
Overwrite Log on Startup = False
Session Timeout = 10080
SGVault Working Directory = C:\Windows\Temp
SGVault Server URL =
Identity = IIS APPPOOL\VaultAppPool
----16/07/2010 10:41:27 AM admin--fe80::e4be:e719:5335:ba6f%11(fe80::e4be:e719:5335:ba6f%11)--SSL Disabled Login
----16/07/2010 10:46:55 AM sgvaultsystem--()--
System Started
Version 5.0.4.18845
Cache Level = 1
DataBase Buffer Size (KB) = 256
LogFile Path = C:\Windows\Temp\sgvault
Log Level = Quiet
Archive Log = Weekly
ReverseDNS Lookup = True
Maximum HTTP Request Length = 102400
Overwrite Log on Startup = False
Session Timeout = 10080
SGVault Working Directory = C:\Windows\Temp
SGVault Server URL =
Identity = IIS APPPOOL\VaultAppPool
----16/07/2010 10:47:02 AM admin--fe80::e4be:e719:5335:ba6f%11(fe80::e4be:e719:5335:ba6f%11)--SSL Disabled Login
) information. I run the VaultService on port 8000; I'm wondering if there is something else besides TCP port 8000 incoming&outgoing I need to open on the firewall?