Object reference not set to an instance of an object on Init

BillKalicious · Post by **BillKalicious** » Fri Mar 18, 2005 3:02 pm

My company is using Vault 2.0.6. When using the GUI, this problem does not occur. I'm using the API and standard vault.exe that comes with it. I have recompiled only to troubleshoot this problem, that was with VS 2003. Somewhere around line 303 (I've added a bunch of debug messages) is the Login method. When calling this method, it calls

_ci.Init(altCommand) - altCommand = Client when called.

I'm 95% sure this is a permissions issue. When I set IIS to run as NETWORK SERVICE, this error does not occur. It only occurs when using the domain account. This domain account has the same policys setup as NETWORK SERVICE. It is in the Debug User and IIS_WPG groups (debug for killing a process).

I have verified that this domain user has read access to the CONFIG folder in the framework. I have searched both the 'Net as well as this forum and haven't found any answers yet. From the Object Browser, I can see that Init sets up the initial IO operations, plus creates the connection class.

As a guess, it seems like the Vault Server is using impersonation and running it's worker process as the Domain User running the client (which is on the same machine). I'm guessing that partially because it works for the NETWORK SERVICE account. Does anyone know what permissions/policys a user needs for its process to access the Vault server locally?

Thanks for any help!
Bill

S Malloy · Post by **S Malloy** » Fri Mar 18, 2005 7:04 pm

I ha the same problem... issue was the vault loogging directory wasn't created at installation:

c:\windows\temp\sgvault

with appropriate ntfs permissions

BillKalicious · Post by **BillKalicious** » Mon Mar 21, 2005 2:36 pm

Thanks a ton, this worked!

Sean Malloy · Post by **Sean Malloy** » Mon Mar 21, 2005 7:22 pm

Bill,

you're going to have even more problems!

Make sure you set NTFS permissions on the TEMP folder itself, otherwise file uploads into vault will fail with a 500, and it'll seem like the server broke (yay for generic error message in log file)

Anyways, I just spent the last day tearing hair out over this problem.

Once again: Make sure you get your permissions set on the temp folder as well as the sgvault folder!

Post by **jclausius** » Tue Mar 22, 2005 1:15 pm

Which account did you guys use to grant access?