Win2k3 - Shadow Folder Problem - Object reference not set...

[ProbsWithWin2k3andVault]

We have installed Vault 2.0.5 on 2 different machines with clean builds of SQL Server 2000 and Win2k3, but cannot get it to work. I have reviewed as many posts/stickies as I could find regarding this, but still have not been able to diagnose the problem.

In order to eliminate as many variables as possible, we are using a user account which is in the LOCAL ADMINISTRATORS group in both web.config files (using Identity Impersonation). When I check the VaultShadowFolderService.txt logfile, the error that I keep seeing is "Object reference not set to an instance of an object." I have included a complete line from the log below:

9/2/2004 11:13:51 PM <generic>: [<null>:1516] Vault Shadow Folder encountered a problem: Object reference not set to an instance of an object.

We've been struggling with this problem for 4 days now, and would welcome any tips that could be offered =)))

[ProbsWithWin2k3andVault]

In addition, I should say that I've tried both the standard c:\inetpub\wwwroot and a custom location for the shadow folder... the projects are ASP and ASP.NET.

To set up the shadowing, we launch the Admin client, select the source node and destination folder, then click Add. The Admin client appears to do something for a moment, then adds the item, but no files show up in the target shadow folder, and the VaultShadowFolderService.txt file just indicates the extremely generic message already reported.

[jclausius]

In order to eliminate as many variables as possible, we are using a user account which is in the LOCAL ADMINISTRATORS group in both web.config files (using Identity Impersonation).

Is it safe to assume you added the permissions / local policy rights to that account? This was outlined in FAQ: Configuring Shadow Folders for UNC Paths and
Shadow Folders on Windows 2003 Server

Assuming the account is configured correctly to run as an Asp.Net process, have you tried to create a Custom Application Pool running under that identity, which is specifically assigned to the Shadow Folder Web Service, rather than use identity impersonation in Shadow Folder's web.config?

[ProbsWithWin2k3andVault]

Thanks for the quick reply!

Do you have to use a DOMAIN logon? Since both the Vault DB and webserver are the same machine, I thought that running both under a local administrator logon should work.

When I tried switching to the application pooling approach, I got an error message:

The request failed with HTTP Status 503: Server Unavailable

Again, I am running the application pool under the a local user that is a member of the local admin and users groups...

[ProbsWithWin2k3andVault]

Aha...

It looks like I shouldn't have assumed that a local admin automatically has the following rights:

- Access this computer from the network
- Log on as a batch job
- Log on as a service

I didn't find the newly created account under any of them. I added it to the first right, but for some reason, the 2nd and 3rd option have the "Add..." button grayed out.

Ideas?

Thanks in advance for your help, and sorry for being so challenged on this ;>

[ProbsWithWin2k3andVault]

An update... I went with a domain login and was able to make all of the proper settings discussed in the documents you referenced in your previous post. The reason for some rights being grayed out was that domain policy was overriding local policy, but that is no longer an issue.

Using the NT logon set up for Vault still yields no results besides the "Object reference not set to an instance of an object." error. Additionally, the use of a custom application pool still does not work; I just get the 503: Server Unavailable error.

Is there any way to generate additional information in the log besides the "Object reference not set to an instance of an object." error, such as WHICH object could not be created? knowing this would certainly help to narrow down the source of the problem! =)

Thanks in advance for any additional help you can provide.

[jclausius]

Can I assume the Object error is generated by the Admin Tool?

If so, there are two other logs you can review - the Server's sgvault.log and the Shadow Folder's log - VaultShadowFolderService.txt.

Anything in there give an indication of the problem?