Trouble changing user rights after upgrade to 3.1
Moderator: SourceGear
Trouble changing user rights after upgrade to 3.1
Hello.
I am having problems with folder security after the upgrade to Vault 3.1. I am trying to give a single user check out/check in and add/rename/delete rights in a folder in which he only has read rights (inherited from the group). Yesterday, the admin tool hung when I tried to apply the change. Today, nothing happens after applying the change. Different behaviour, but the effect is the same: I can't change the user rights.
Both the Vault server and the Admin Tool are version 3.1. I don't see any error messages in the Vault log file.
Any help will be appreciated.
Regards,
Frans
I am having problems with folder security after the upgrade to Vault 3.1. I am trying to give a single user check out/check in and add/rename/delete rights in a folder in which he only has read rights (inherited from the group). Yesterday, the admin tool hung when I tried to apply the change. Today, nothing happens after applying the change. Different behaviour, but the effect is the same: I can't change the user rights.
Both the Vault server and the Admin Tool are version 3.1. I don't see any error messages in the Vault log file.
Any help will be appreciated.
Regards,
Frans
Hello Linda,
I have tried to answer you question but the admin tool seems to have switched its behaviour back to hanging in response to trying to adjust the user rights. This time, it got so bad I had to reboot the Vault machine. Or maybe there is something else going on?
Before I try to change the user rights again I'd like to mention the error messages from the last incident:
In the application event log, the following is written:
Event ID: 1000
Event Source: perflib
Message: Access to performance data was denied to ASPNET as attempted from C:\WINNT\System32\WBEM\WinMgmt.exe
This event repeats five times every now and then. The event started occurring after the upgrade to 3.1. It is not associated with messages in the Vault log.
After the admin tool hung, the following messages were written to the Vault log:
“System.Data.SqlClient.SqlException: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream)
at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior)
at VaultServiceSQL.VaultSqlSCC.GetUserSecurityRights(VaultSqlConn conn, VaultUserSecurityRights vusr, Int32 nRepID, Int64 nTxID) at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream)
at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior)
at VaultServiceSQL.VaultSqlSCC.GetUserSecurityRights(VaultSqlConn conn, VaultUserSecurityRights vusr, Int32 nRepID, Int64 nTxID)”
I will now try changing the user rights for a (small) folder again…
Frans
I have tried to answer you question but the admin tool seems to have switched its behaviour back to hanging in response to trying to adjust the user rights. This time, it got so bad I had to reboot the Vault machine. Or maybe there is something else going on?
Before I try to change the user rights again I'd like to mention the error messages from the last incident:
In the application event log, the following is written:
Event ID: 1000
Event Source: perflib
Message: Access to performance data was denied to ASPNET as attempted from C:\WINNT\System32\WBEM\WinMgmt.exe
This event repeats five times every now and then. The event started occurring after the upgrade to 3.1. It is not associated with messages in the Vault log.
After the admin tool hung, the following messages were written to the Vault log:
“System.Data.SqlClient.SqlException: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream)
at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior)
at VaultServiceSQL.VaultSqlSCC.GetUserSecurityRights(VaultSqlConn conn, VaultUserSecurityRights vusr, Int32 nRepID, Int64 nTxID) at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream)
at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior)
at VaultServiceSQL.VaultSqlSCC.GetUserSecurityRights(VaultSqlConn conn, VaultUserSecurityRights vusr, Int32 nRepID, Int64 nTxID)”
I will now try changing the user rights for a (small) folder again…
Frans
All right, I will send you a copy of the log. Please note that when I try to change the user rights and the admin tool hangs, no error messages are written to the log. The earlier timeout errors may have been caused by not killing the admin tool when it hangs (like I did yesterday, I left it on when I went home to see if it was just a matter of waiting long enough), or may be caused by something unrelated to the problem I am having with editing the user rights.
Regards,
Frans
Regards,
Frans
There was a database error at 7/27/2005 6:59:34 PM that could be causing a problem. We'd suggest running DBCC CHECKDB on the database.
The DBCC CHECKDB command will run through a thorough set of checks to make sure the database is in operating condition. This can be done within any SQL Server Query tool by running the Check DB command ( DBCC CHECKDB ( 'sgvault' ) ). See SQL Server's help system for more information for DBCC CHECKDB - http://msdn.microsoft.com/library/defau ... c_00gy.asp
The DBCC CHECKDB command will run through a thorough set of checks to make sure the database is in operating condition. This can be done within any SQL Server Query tool by running the Check DB command ( DBCC CHECKDB ( 'sgvault' ) ). See SQL Server's help system for more information for DBCC CHECKDB - http://msdn.microsoft.com/library/defau ... c_00gy.asp
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager
Hello Linda,
The problem seems to have changed somewhat. Maybe the CHECKDB has done some good? This morning, after having rebooted our Vault machine, I could see all the user rights I had try to apply earlier had been applied. This could be confirmed by using the query you posted. I could also change some user rights using the Vault admin tool. The tool reacted almost instantaneously. But after the third or fourth change, the admin tool hung again.
I have tested some more afterwards. What goes well now is that every time after I select the repository in the ‘Folder Security’ section, the entire tree is displayed and I can see all user rights. I can make a few changes which are applied very quickly. Then, after a couple of changes, the admin tool hangs again.
In the log file, two “timeout expired” errors were written, but the admin tool has crashed more times so those errors are not likely to be a direct effect of my tests.
Also, the perflib error in the application event log keeps occurring. I think it must have something to do with Vault. The machine Vault and SQL Server are running on is dedicated to Vault.
Regards,
Frans
The problem seems to have changed somewhat. Maybe the CHECKDB has done some good? This morning, after having rebooted our Vault machine, I could see all the user rights I had try to apply earlier had been applied. This could be confirmed by using the query you posted. I could also change some user rights using the Vault admin tool. The tool reacted almost instantaneously. But after the third or fourth change, the admin tool hung again.
I have tested some more afterwards. What goes well now is that every time after I select the repository in the ‘Folder Security’ section, the entire tree is displayed and I can see all user rights. I can make a few changes which are applied very quickly. Then, after a couple of changes, the admin tool hangs again.
In the log file, two “timeout expired” errors were written, but the admin tool has crashed more times so those errors are not likely to be a direct effect of my tests.
Also, the perflib error in the application event log keeps occurring. I think it must have something to do with Vault. The machine Vault and SQL Server are running on is dedicated to Vault.
Regards,
Frans
We'll look into this and try to reproduce it here. Is there a specific set of steps that reproduces it, or is does it happen after X number of changes in the Admin Tool? Or does it happen after a period of time?
Regarding the perflib error, I found this posting on the web:
http://www.dotnet247.com/247reference/m ... 56881.aspx
But we're not sure how this might be related to Vault. We'll investigate further.
Regarding the perflib error, I found this posting on the web:
http://www.dotnet247.com/247reference/m ... 56881.aspx
But we're not sure how this might be related to Vault. We'll investigate further.
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager
Indeed, we use Windows 2000 Server. With service pack 4. The OS is current on its updates.
I just had to reboot the machine again because Vault had become unresponsive, SQL Server was pushing the CPU to 100% usage. Things are now back to normal. I will wait a while before trying to adjust the user rights because I have a feeling that the perflib error may be caused by either the admin tool or trying to adjust the user rights with the admin tool. Up till now, the perflib error has not occured yet after the restart.
When I test with the admin tool again, I will log my actions to see if there is a particular way of causing the tool to hang.
Greetings,
Frans
I just had to reboot the machine again because Vault had become unresponsive, SQL Server was pushing the CPU to 100% usage. Things are now back to normal. I will wait a while before trying to adjust the user rights because I have a feeling that the perflib error may be caused by either the admin tool or trying to adjust the user rights with the admin tool. Up till now, the perflib error has not occured yet after the restart.
When I test with the admin tool again, I will log my actions to see if there is a particular way of causing the tool to hang.
Greetings,
Frans
I should have noticed this earlier, but now I see that the occurrence of a set of 5 perflib errors coincides with a user login. I can see this by comparing the times in the event log with the times in the vault log. It’s just the login, not the logout.
Does the Vault client request performance data?
And to answer the question: for the .net process model the machine account is used.
Regards,
Frans
Does the Vault client request performance data?
And to answer the question: for the .net process model the machine account is used.
Regards,
Frans