I keep getting these error messages on my SBS 2003 server. Anybody know what they mean?
EventType : clr20r3 P1 : w3wp.exe P2 : 6.0.3790.1830 P3 : 42435be1
P4 : vaultserviceapilib P5 : 3.5.1.4786 P6 : 45085b44 P7 : d6
P8 : 6b P9 : system.nullreferenceexception
system.nullreferenceexception
Moderator: SourceGear
Are there any .NET errors going on as well?
Can you go to a Vault GUI and open Help - Technical Support and provide me the environment information from there?
Are you seeing any errors in the Vault Server Log that coincide with the error you posted? (You may need to put the server into debug mode for more detailed logging.)
Can you go to a Vault GUI and open Help - Technical Support and provide me the environment information from there?
Are you seeing any errors in the Vault Server Log that coincide with the error you posted? (You may need to put the server into debug mode for more detailed logging.)
Configuration information
We are still getting these errors occasionally. I have put the Vault Server into debug logging mode. What should I be looking for in the log?
Client Information
Vault Client Version: 3.5.1.4786
.Net Framework Version: 1.1.4322.2300
Operating System: Microsoft(R) Windows(R) Server 2003 for Small Business Server
Service Pack: 1.0
OS Version: 5.2.3790
Total Physical Memory: 1023.18 MB
Time Zone: (GMT-05:00) Eastern Time (US & Canada)
Server Information
Vault Server Version: 3.5.1.4786
.Net Framework Version: 2.0.50727.42
Operating System: Microsoft(R) Windows(R) Server 2003 for Small Business Server
Service Pack: 1.0
OS Version: 5.2.3790
Timezone: (GMT-05:00) Eastern Time (US & Canada)
SQL Version: Microsoft SQL Server 2005 - 9.00.3042.00 (Intel X86)
Feb 9 2007 22:47:07
Copyright (c) 1988-2005 Microsoft Corporation
Express Edition with Advanced Services on Windows NT 5.2 (Build 3790: Service Pack 1)
License Information
1 serial number(s):
1 of 1: 10 users, expiring 9/10/2007
Client Information
Vault Client Version: 3.5.1.4786
.Net Framework Version: 1.1.4322.2300
Operating System: Microsoft(R) Windows(R) Server 2003 for Small Business Server
Service Pack: 1.0
OS Version: 5.2.3790
Total Physical Memory: 1023.18 MB
Time Zone: (GMT-05:00) Eastern Time (US & Canada)
Server Information
Vault Server Version: 3.5.1.4786
.Net Framework Version: 2.0.50727.42
Operating System: Microsoft(R) Windows(R) Server 2003 for Small Business Server
Service Pack: 1.0
OS Version: 5.2.3790
Timezone: (GMT-05:00) Eastern Time (US & Canada)
SQL Version: Microsoft SQL Server 2005 - 9.00.3042.00 (Intel X86)
Feb 9 2007 22:47:07
Copyright (c) 1988-2005 Microsoft Corporation
Express Edition with Advanced Services on Windows NT 5.2 (Build 3790: Service Pack 1)
License Information
1 serial number(s):
1 of 1: 10 users, expiring 9/10/2007
The first thing I'm noticing is that your client and your server are using different .NET frameworks. Try setting your Vault Client to use the 2.0 .NET framework.
1. Go to the vaultguiclient.exe.config file in the Vault directory on your client.
2. Look at the top between <configuration> and <system.net>.
a. Add in the lines I show in between those below, but substitute the x's with the numbers for the .NET framework your server uses. For example, 2.0.50727.
<configuration>
<startup>
<requiredRuntime version="vx.x.xxxxx" safemode="true"/>
</startup>
<system.net>
3. Restart your system afterwards and then try using Vault.
If the .NET framework you chose is not working:
1. Go to the vaultguiclient.exe.config file in the Vault directory on your client.
2. Look at the top between <configuration> and <system.net>.
a. Add in the lines I show in between those below, but substitute the x's with the numbers for the .NET framework your server uses. For example, 2.0.50727.
<configuration>
<startup>
<requiredRuntime version="vx.x.xxxxx" safemode="true"/>
</startup>
<system.net>
3. Restart your system afterwards and then try using Vault.
If the .NET framework you chose is not working:
- Uninstall the version of the .NET framework involved. You can do this by going into the directory of that framework and running aspnet_regiis –u.
Then reinstall that same version of the .NET framework by running aspnet_regiis –i.