Vault client.exe pending checkins differs to VS2008 GUI

[Jamie Clayton]

I've been getting a lot of errors trying to commit checkin via vault 5.0.2 on Window 7, mainly session timeout/re-login errors. VS 2008 Vault Dialog after Checkin screen + Ok Button: "Session is no longer valid. Either the server restarted, or your session timed out. You may need to login again to re-authenticate."

Environment
Windows x64 2008 R2 Server + SQL 2008 + IIS 7.5
Windows x32 7 (upgraded from vista)

Issues in my environment
1. The files seem to get saved into the vault repository and the edition increments. The local file version doesn't incremented. You then see a merge conflict, but the files are exactly the same.
2. There was a checkin that involved adding a directory then adding a new file. The file was loaded into the repository and pending checkin list in vault client confirms this. However the VS 2008 checkin for the solution is still trying to create the folder and add the files. This then causes a lot of checkin transaction failures. I can't work out how to remove these items from the VS 2008 IDE.
3. I can't seem to find an example of settings for the Windows 2008 (R2) IIS (7 or 7.5) web service, in particular the application pool advanced settings.

I'll be the first to admit that I think my development PC will need a rebuild with the windows 7 OS and then re-add all the development software to confirm these problems aren't Vista to Windows 7 upgrade issues. Is anyone else having issues with this environment?

[Jamie Clayton]

Checking the Server event log hightlighted two errors that have happened during the last few days testing vault 5.0.2 and VS 2008.

Error
An unhandled exception occurred and the process was terminated. Application ID: /LM/W3SVC/3/ROOT/VaultService Process ID: 1092 Exception: System.InvalidOperationException Message: Cannot open log for source 'Application'. You may not have write access. StackTrace: at System.Diagnostics.EventLog.OpenForWrite(String currentMachineName) at System.Diagnostics.EventLog.InternalWriteEvent(UInt32 eventID, UInt16 category, EventLogEntryType type, String[] strings, Byte[] rawData, String currentMachineName) at System.Diagnostics.EventLog.WriteEntry(String message, EventLogEntryType type, Int32 eventID, Int16 category, Byte[] rawData) at System.Diagnostics.EventLog.WriteEntry(String message, EventLogEntryType type) at VaultServiceBase.Emailer.Send(Item item, Boolean pleaseThrowExceptions) at VaultServiceBase.Emailer.EmailerMain() at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state) at System.Threading.ThreadHelper.ThreadStart() InnerException: System.ComponentModel.Win32Exception Message: Access is denied StackTrace:

Warning
A process serving application pool 'VaultAppPool' suffered a fatal communication error with the Windows Process Activation Service. The process id was '1092'. The data field contains the error number.

[Beth]

There is a lot going on here and your errors with the app pool could be leaving your client cache in a confused state that would affect Visual Studio. What will help is to see the Vault Server Log. You can either post it here or send an email to support at sourcegear.com (attn: Beth) with a link to this forum thread and the log.

For item 1, are they checked out? If the server is failing, then the cache might not be getting the information it needs. Close all instances of Vault and Visual Studio and then try renaming the cache. There are instructions posted here: http://support.sourcegear.com/viewtopic ... 13&t=11513. For right now, I'd prefer if you just renamed instead of deleted.

For item 2, open your Vault GUi client and see if the pending check-ins for the folder creation and file add. If they are, you can select them and just press your delete key on your keyboard. That will removing them from the pending changes. Then refresh your Visual Studio or reopen it.

Item 3: I've attached a screenshot of my settings from one of my test servers. I can't say if this will be the best settings for all users, but this is what my small test runs under.

[Jamie Clayton]

A) I've rebuilt my Windows 7 Development PC to ensure I've got a fresh start on these problems.
B) When I run VS 2008 I have to use "As Administrator" and the Vault Client wasn't. When I modify the Vault client to "Run as Administrator", the pending checkin list match. VS 2009 and Vault client now have matching checkin. Obviously there is a subtle difference in Windows 7 about UAC and run as Administrator + local data. So that resolves issue 1,2.
C) Reviewed Vault 5.x by moving the development PC to the servers location, rather than using the VPN to connect, to reduce network latency from the connection timeouts. This seemed to work as expected (+ the "run as administrator" change).

Attached is the server log. Will review Iis server settings now.

[Jamie Clayton]

Attached is the server log.

[Jamie Clayton]

Ok, can't attach files, will email your support address.

[Jamie Clayton]

Windows 2008 R2 (IIS 7.5) Advanced application pool settings

Beth, the only notable difference between our two settings are.

General. Managed Pipeline Mode :- Integrated (while your sample says "Classic")
Process Model. Idle Time-Out (minutes) :- 600 (while your sample says "0")

It looks like I've used a generic inhouse application pool rather than a vault service pool that was created to separate the various intranet IIS applications. (it must have changed when I upgraded the vault server software to v5 [:) sorry]) Both VaultService and VaultShadowService applications now use this application pool with classic pipeline mode. Hopefully that will make all the difference to the service behaviour.

[Beth]

I would agree. Try the App Pool change and then let me know your results.

If you continue to have problems with this, then I'd like you to increase the logging level on your Vault Server Log, cause the error to happen, and then send a new log.

[Jamie Clayton]

Beth,
The server change seems to make checkins more stable. I haven't done a large checkin yet, but the authentication errors are reducing.

I'm still having issues with VS 2008 and Vault Client "Run As Administrator" cache. I'm not totally convinced the local cache is working correctly. http://www.screencast.com/t/YjA5MWE0NmIt

Jamie.

[Jamie Clayton]

Beth,

Further discovery. I changed my user on the server to use "AD" authentication during the post vault server 5.x settings 'tinker'. The IIS server website -> Authentication -> Windows Authentication is disabled. I'm sure that's not helping, I've switched off integrated AD authentication for the time being to continue testing.

I've switched on Vault Client logging to see what's happening (ctl+alt+shift+F12). Not sure where the files will be saved. Is there a clue in the IDE? (I saw something in the status bar when I switched it on, but forgot about 5 seconds later).

[Beth]

Let's not add multiple issues into the same thread. I have received the cache issue information via email and have responded via email. I'll need you to reply to that with answers to the questions I had.

On the AD authentication, that shouldn't have anything to do with the Windows authentication setting in IIS.

Is it safe to say then that the original issue in this ticket is fixed and the rest of the information you are providing me pertains to the cache? If so, then let's keep pursuing the cache issue offline and just be finished with this forum thread.

[Jamie Clayton]

Beth, I don't think I have solved the issue, but happy to take it offline via email.

[Jamie Clayton]

Spent some time debugging this and it turns out to be an invalid SMTP server relay entry. I swapped ISP last year and hadn't noticed vaults email notifications of changes, because I had Outlook Rules automatically moving those emails.

I had to follow the error throught the vault, firewall, windows and Windows Server logs till I found a mention of "email" and decided recheck my settings. I've reported a series of test results directly to source gear.

[Beth]

Thank you for updating your thread. This should be helpful to other users as well.

HS: 219071