when trying to login to the vault server (after entering the credentials and the server name and pressing ok) one of my developers is seeing the following exception:
--
13.04.2008 18:48:31 <generic>: [GUIClientWorkerThread:1008]
[System.AccessViolationException: Attempted to read or write protected
memory. This is often an indication that other memory is corrupt.
at System.Net.HttpWebRequest.UpdateHeaders()
at System.Net.HttpWebRequest.SubmitRequest(ServicePoint servicePoint)
at System.Net.HttpWebRequest.GetRequestStream()
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String
methodName, Object[] parameters)
at
VaultClientNetLib.ClientService.VaultService.ValidateServiceVersions(Int32[]
clientSupportedVersions)
at VaultClientNetLib.VaultConnection.Login(String strURLBase, String
strUserLogin, String strPassword)
at VaultClientOperationsLib.ClientInstance.Login(String urlbase, String
username, String password)
at VaultClientPresentationLib.GUIClientInstance.ConnectToServer(String&
outserverPath, Boolean forceDialogShow, String& outprofileName, String&
outusername, Boolean& outbUseSSL, Boolean& outbAutoLogin)
at
VaultClientPresentationLib.GUIClientThread.ProcessCommand(GUIClientThreadCommand
command, GUIClientThreadCommandResult& outputResult)]Attempted to read or
write protected memory. This is often an indication that other memory is
corrupt.
at System.Net.HttpWebRequest.UpdateHeaders()
at System.Net.HttpWebRequest.SubmitRequest(ServicePoint servicePoint)
at System.Net.HttpWebRequest.GetRequestStream()
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String
methodName, Object[] parameters)
at
VaultClientNetLib.ClientService.VaultService.ValidateServiceVersions(Int32[]
clientSupportedVersions)
at VaultClientNetLib.VaultConnection.Login(String strURLBase, String
strUserLogin, String strPassword)
at VaultClientOperationsLib.ClientInstance.Login(String urlbase, String
username, String password)
at VaultClientPresentationLib.GUIClientInstance.ConnectToServer(String&
outserverPath, Boolean forceDialogShow, String& outprofileName, String&
outusername, Boolean& outbUseSSL, Boolean& outbAutoLogin)
at
VaultClientPresentationLib.GUIClientThread.ProcessCommand(GUIClientThreadCommand
command, GUIClientThreadCommandResult& outputResult)
Stack Trace:
at
VaultClientPresentationLib.GUIClientInstance.ShowCommandException(Exception
e, IWin32Window dialogOwner)
at
VaultClientPresentationLib.GUIClientThread.ProcessCommand(GUIClientThreadCommand
command, GUIClientThreadCommandResult& outputResult)
at VaultClientPresentationLib.GUIClientThread.Start()
at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
at System.Threading.ExecutionContext.Run(ExecutionContext
executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()
------
any ideas what would be causing this ?
WM_THX
-thomas woelfer
problem running the client
Moderator: SourceGear
-
thomas woelfer
- Posts: 50
- Joined: Fri Apr 04, 2008 4:27 am
- Contact:
-
thomas woelfer
- Posts: 50
- Joined: Fri Apr 04, 2008 4:27 am
- Contact:
Is this only on one machine?
I think there are several things that could cause this; maybe a bad spot on disk, or a .NET problem, or maybe permissions instead.
Is the error that user seeing coming from the Event Viewer on the client, or some pop-up window, or in some log?
Did this user perform the install of the client software while being logged into their Windows account that they are now logged in under?
I think there are several things that could cause this; maybe a bad spot on disk, or a .NET problem, or maybe permissions instead.
Is the error that user seeing coming from the Event Viewer on the client, or some pop-up window, or in some log?
Did this user perform the install of the client software while being logged into their Windows account that they are now logged in under?
-
thomas woelfer
- Posts: 50
- Joined: Fri Apr 04, 2008 4:27 am
- Contact:
This occurs when I log in as admin (should have all the neccessary read/write permissions) or a simple user, too.
A message window is displayed that states: "System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt."
There is the possibility to click on "details" (or s.th. like that) but it does not respond when clicked.
I found the full error message under %HOME%\Local...\Temp\*.txt (I do not remember the exact name and I'm currently not sitting at the computer in question). Interestingly this logfile is written only when I'm logged in as admin but nothing is written under the home directory when logged in with a simple user account. The software was installed as admin.
This is a Windows 2000 machine with all updates installed running .NET 2.0.
Sure there may be s.th. regarding "permission" - that what is said. But you should give me a hint where to look on my machine. This shgould be possible for you, since I provided the callstack. The machine did not create any connections on the network (either with proxy enabled or without). After providing my login credentials and clicking and after a short respose time the error box is displayed.
Other intra/internet connection attempts on this machine work perfectly OK.
A message window is displayed that states: "System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt."
There is the possibility to click on "details" (or s.th. like that) but it does not respond when clicked.
I found the full error message under %HOME%\Local...\Temp\*.txt (I do not remember the exact name and I'm currently not sitting at the computer in question). Interestingly this logfile is written only when I'm logged in as admin but nothing is written under the home directory when logged in with a simple user account. The software was installed as admin.
This is a Windows 2000 machine with all updates installed running .NET 2.0.
Sure there may be s.th. regarding "permission" - that what is said. But you should give me a hint where to look on my machine. This shgould be possible for you, since I provided the callstack. The machine did not create any connections on the network (either with proxy enabled or without). After providing my login credentials and clicking and after a short respose time the error box is displayed.
Other intra/internet connection attempts on this machine work perfectly OK.
What I am thinking here is that the read/write problem could be to the client-side cache. When installing, the cache is placed under the user who performed the install. When a person logs into the Windows machine under a different name, they often don't have permissions to access the profile area of the other user. A way to test out my theory would be to go to C:\Documents and Settings and just temporarily giving the everyone account read/write access and have it inherit down through the tree. Then try using Vault. If it works, then we have our answer.
Thanks for your help, but still it does not work here.
Guarded _all_ permissions to everyone on drive c.
Removed Vault Client with the uninstaller.
Removed remaining registry keys with regedit.
Re-installed Vault Client to its default location as admin.
Ran Vault client as admin (still the same account).
The problem remains.
Guarded _all_ permissions to everyone on drive c.
Removed Vault Client with the uninstaller.
Removed remaining registry keys with regedit.
Re-installed Vault Client to its default location as admin.
Ran Vault client as admin (still the same account).
The problem remains.
Can I have you do the following:
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 2.0.50727 .NET framework.
<configuration>
<startup>
<requiredRuntime version="vx.x.xxxxx" safemode="true"/>
</startup>
<system.net>
3. Restart your system afterwards and then try using Vault.
If it still doesn't work after that then can I have you go to Help - Technical Support in your client and post the information from there? You don't need to add an licensing infomation at the bottom of that window, just the client and server information.
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 2.0.50727 .NET framework.
<configuration>
<startup>
<requiredRuntime version="vx.x.xxxxx" safemode="true"/>
</startup>
<system.net>
3. Restart your system afterwards and then try using Vault.
If it still doesn't work after that then can I have you go to Help - Technical Support in your client and post the information from there? You don't need to add an licensing infomation at the bottom of that window, just the client and server information.
Now it works, but not that way...
After applying your suggestion VaultClient would not even start complaining .net 2.0.xxxx had to be installed. But of course it was.
So I tried to uninstall .NET 2.0 but this failed also saying the patch packet was not available. "Repair" in the .NET 2.0 installer also gave me the same error after a while. I finally removed the .NET 2.0 installation out of the registry using "Windows Installer Clean Up" (msicuu.exe) and then reinstalled .NET 2.0, .NET 2.0SP1, .NET 2.0SP1 Language Pack. After reboot VaultClient still complained .net 2.0.xxxx had to be installed. So I restored the previous *.config and with some magic VaultClient ran and I successfully could login on my VaultServer without the previous "permission" failure! Still no idea about the reason...
After applying your suggestion VaultClient would not even start complaining .net 2.0.xxxx had to be installed. But of course it was.
So I tried to uninstall .NET 2.0 but this failed also saying the patch packet was not available. "Repair" in the .NET 2.0 installer also gave me the same error after a while. I finally removed the .NET 2.0 installation out of the registry using "Windows Installer Clean Up" (msicuu.exe) and then reinstalled .NET 2.0, .NET 2.0SP1, .NET 2.0SP1 Language Pack. After reboot VaultClient still complained .net 2.0.xxxx had to be installed. So I restored the previous *.config and with some magic VaultClient ran and I successfully could login on my VaultServer without the previous "permission" failure! Still no idea about the reason...