Error granting permissions. The path is not of a legal form.

[rdcllc]

Receiving the error below in the install log when installing Vault Server 4.1.3 on Windows Vista Ultimate. Install process hangs until process is killed and install is rolled back.

Log started at 16 Nov 2008 - 16.13.41

Custom action assembly location: D:\inetpub\wwwroot\VaultService\bin\CustomActionExe.exe
Custom Action version: 4.1.3

FileVersionInfo: File: D:\inetpub\wwwroot\VaultService\bin\CustomActionExe.exe
InternalName: CustomActionExe.exe
OriginalFilename: CustomActionExe.exe
FileVersion: 4.1.3.18336
FileDescription:
Product:
ProductVersion: 4.1.3.18336
Debug: False
Patched: False
PreRelease: False
PrivateBuild: False
SpecialBuild: False
Language: Language Neutral


The commandline args as passed in to us:

/TARGETDIR=D:\inetpub\wwwroot\VaultService\
/TARGETDIR2=D:\inetpub\wwwroot\Fortress\
/PARAMS=
/DROPDB=
/UPGRADE=
/ADMINPW=
/SQLSERVER=
/WINAUTH=1
End commandline args.

Found local name of NT AUTHORITY\NETWORK SERVICE for Network Service account.
See if we need to do an upgrade or an install...Configuring your new Vault Installation
Entered CreateCryptoRegistryValues.
CreateCryptoRegistryValues completed successfully.
Requesting the IIS Process User...Found local name of NT AUTHORITY\NETWORK SERVICE for Network Service account.
Requesting Vault Admin user password... Hashing the admin pw
OK
Connecting to the SQL Server...ConnectToDatabase() completed successfully.
Warning...Custom User Issue - Using windows auth to another machine. Ensure a user account with proper permissions is used.
dialog result for uninstall is: OK
OK
Verifying the SQL Server requirements... User is trying to install to Microsoft SQL version 9.00.3042.00
OK
Checking for an existing databases...Found.
Asking for database's fate...Keep existing.
Upgrading the existing source control database...
This may take a long time. Do NOT stop this process!
Checking the installed database version... 4.1.3.0
OK
Putting sgvault database in single-user mode.
getting the collation of the current source control database
the Vault database has the collation SQL_Latin1_General_CP1_CI_AS
Upgrading existing database user information with a new install.
Login begin used is: NT AUTHORITY\NETWORK SERVICE
NT AUTHORITY\NETWORK SERVICE exists. Nothing to do.
GrantLogin completed successfully.
Granting login to 'RDCSERVER01\ASPNET'
The user, RDCSERVER01\ASPNET, could not be added as a SQL Server login. If you are running IIS6 in IIS5 isolation mode you must manually grant the RDCSERVER01\ASPNET user access to sgvault database as _dbOwner.

Note, on some database collations check the case of the user's name.
Grant database access to NT AUTHORITY\NETWORK SERVICE...Checking for database access on NT AUTHORITY\NETWORK SERVICE within the sgvault database.
Checking for database access on NT AUTHORITY\NETWORK SERVICE within the sgmaster database.
Adding role for ASPNET in addition to NET AUTHORITY user
Checking for database access on RDCSERVER01\ASPNET within the sgvault database.
An exception was encountered granting DB Access on sgvault to the SQL Login, RDCSERVER01\ASPNET. Windows NT user or group 'RDCSERVER01\ASPNET' not found. Check the name again.
User or role 'RDCSERVER01\ASPNET' does not exist in this database.
Unable to add extrea role for ASPNET
OK
Executing commands in master_upgrade.sql
Read master_upgrade.sql from our resources.
Upgrading SourceGear master database schema...OK
DoSqlCommandsFromFile completed successfully.
Executing commands in vault_upgrade.sql
Read vault_upgrade.sql from our resources.
Upgrading SourceGear source control database schema...OK
DoSqlCommandsFromFile completed successfully.
Waiting for upgrade connection to sgvault database to be released...OK
Executing commands in master_sp.sql
Read master_sp.sql from our resources.
Upgrading SourceGear master stored procedures...OK
DoSqlCommandsFromFile completed successfully.
Executing commands in vault_sp.sql
Read vault_sp.sql from our resources.
Upgrading SourceGear source control stored procedures...OK
DoSqlCommandsFromFile completed successfully.
Updating upgrade history table...
Putting sgvault database in back in multi-user mode.
Database upgrade succeeded!
Checking permissions on local folders... Shadowdir as retrieved from context params : D:\inetpub\wwwroot\VaultService\VaultShadowFolder
Adding permissions per user's request.
Adding permission to 'D:\\inetpub\\wwwroot\\VaultService' for user NT AUTHORITY\NETWORK SERVICE
Using NT AUTHORITY\NETWORK SERVICE as the user.
GrantPermissions completed successfully.
Adding permission to '' for user NT AUTHORITY\NETWORK SERVICE
Error granting permissions. The path is not of a legal form.

[rdcllc]

Anyone seen this before or have any ideas?

[DoggettCK]

I'm getting the same error, though I'm running it as MACHINENAME\ASPNET. It doesn't stop the installation, though, and everything works great, except connecting via the client and IDE. I can connect easily through IE or Firefox, even using the ASMX test page, but the client and IDE both give me 401: Access Denied errors.

It's a bit of a pain, since I've been using Vault on my workstation for nearly five months with no problems, but the second I try to put it on a production box, it's giving me grief.

I've gone through and made sure anonymous access is enabled, the anonymous user password never expires, and Sharepoint isn't installed, and no matter what, I get the error. Even running the client GUI on the server itself can't connect. I'm sure it's some sort of permissions/authentication error, but I have no idea where. Hopefully the support line will find a solution.

[lbauer]

Are you both logged in as Domain or machine Admin when you do the installation?

[DoggettCK]

I was logged in as a user with Admin rights, but not the Administrator account.

[DoggettCK]

You may have a hosed IIS install. Wiping out IIS (uninstalling from Add/Remove Programs), then reinstalling it completely solved my problems.

[Beth]

The .NET framework needs to be installed after IIS usually for proper functioning. There is a chance it could be IIS, but I do see it complaining about giving permissions to SQL in the first post.

What IIS process model is being selected during install?
How are you connecting to the SQL server?
Is the SQL server on the same machine or a different machine?
Are you installing on a Domain Controller?