Response for No Message Sent! - SOS 5.0.1

If you are having a problem using SourceOffSite, post a message here.

Moderator: SourceGear

BrianDrab
Posts: 98
Joined: Tue Mar 25, 2008 1:27 pm
Contact:

Response for No Message Sent! - SOS 5.0.1

Post by BrianDrab » Tue Dec 22, 2009 1:16 pm

Visual Studio 2008 Professional
Windows 7 Enterprise 64-Bit

When I open Visual Studio 2008 and select File....Source Control...Open From Source Control and select the solution that I want to retrieve, at some point I get the following message:
Capture.PNG
Capture.PNG (12.06 KiB) Viewed 22124 times
Here is a snippet of the server log. Any ideas?

2009-12-22 13:54:14,175 - Loading SourceOffSite Server configuration from E:\Program Files\SourceGear\SourceOffSite 5 Server\sossvr.prp
2009-12-22 13:54:14,190 -
2009-12-22 13:54:14,190 - ****************************************************
2009-12-22 13:54:14,190 - ****************************************************
2009-12-22 13:54:14,190 - SourceOffSite Server 5.0.1.242 Professional - With Cryptography
2009-12-22 13:54:14,190 -
2009-12-22 13:54:14,190 - CurrentCulture is en-US.
2009-12-22 13:54:14,190 -
2009-12-22 13:54:14,440 - Server Information
2009-12-22 13:54:14,440 - Operating System: Microsoft(R) Windows(R) Server 2003, Standard Edition
2009-12-22 13:54:14,440 - Service Pack: 2.0
2009-12-22 13:54:14,440 - OS Version: 5.2.3790
2009-12-22 13:54:14,440 - Locale: Ox0409
2009-12-22 13:54:14,440 - OSLanguage: 1033
2009-12-22 13:54:14,440 - Total Physical Memory: 2 GB
2009-12-22 13:54:14,440 - Time Zone: (GMT-05:00) Eastern Time (US & Canada)
2009-12-22 13:54:14,440 -
2009-12-22 13:54:14,440 - SSAPI.dll Information:
2009-12-22 13:54:14,440 - Version: E:\Program Files\Microsoft Visual SourceSafe\ssapi.dll (8.0.50727.1551 (QFE.050727-1500))
2009-12-22 13:54:14,440 - Threading Model: Apartment
2009-12-22 13:54:14,440 -
2009-12-22 13:54:14,440 - Logging at level Error
2009-12-22 13:54:14,440 -
2009-12-22 13:54:14,440 -
2009-12-22 13:54:14,456 - Number of licenses configured: 4
2009-12-22 13:54:14,456 -
2009-12-22 13:54:14,456 - SourceSafe Initialization file(s) located at:
2009-12-22 13:54:14,456 - \\kaplan-dev\VSSDatabases\VSS\srcsafe.ini
2009-12-22 13:54:14,456 - \\kaplan-dev\VSSDatabases\Documentation\srcsafe.ini
2009-12-22 13:54:14,456 - \\kaplan-dev\VSSDatabases\Legacy\srcsafe.ini
2009-12-22 13:54:14,456 - \\kaplan-dev\VSSDatabases\Personal\srcsafe.ini
2009-12-22 13:54:14,456 - SourceOffSite Server will be using the Visual SourceSafe 2005 Interface.
2009-12-22 13:54:14,456 - Started at 12/22/2009 13:54:14
2009-12-22 13:54:14,456 - ****************************************************
2009-12-22 13:54:14,456 - ****************************************************
2009-12-22 13:54:14,456 -
2009-12-22 13:54:14,487 - kaplan-web is attempting to listen for connections on unsecure port 8080
2009-12-22 13:54:14,534 - Waiting for a connection....secure = False
2009-12-22 13:55:45,737 - Connection accepted from 10.10.1.117:50736 on local address 10.10.1.7:8080, session id is 1.
2009-12-22 13:56:03,190 - 1: ProtocolMessage.ParseStream() - Socket error reading protocol message number (Read 0 of 1 bytes). Exception: Exception: CONNECTION CLOSED
2009-12-22 13:56:03,190 - 1: ProtocolMessage.ParseStream() Get ProtocolMessage ID Exception: CONNECTION CLOSED BytesRead 0 of 10 (allowed).
2009-12-22 13:56:03,190 - 1: Connection Closed: CONNECTION CLOSED
2009-12-22 13:56:03,221 - Connection accepted from 10.10.1.117:50741 on local address 10.10.1.7:8080, session id is 2.
2009-12-22 13:56:03,503 - 1: VSS database closed for the session id 1.
2009-12-22 13:56:04,550 - 2: ProtocolMessage.ParseStream() - Socket error reading protocol message number (Read 0 of 1 bytes). Exception: Exception: CONNECTION CLOSED
2009-12-22 13:56:04,550 - 2: ProtocolMessage.ParseStream() Get ProtocolMessage ID Exception: CONNECTION CLOSED BytesRead 0 of 10 (allowed).
2009-12-22 13:56:04,550 - 2: Connection Closed: CONNECTION CLOSED
2009-12-22 13:56:04,550 - 2: VSS database closed for the session id 2.
2009-12-22 13:56:04,565 - Connection accepted from 10.10.1.117:50742 on local address 10.10.1.7:8080, session id is 3.
2009-12-22 13:56:08,050 - 3: ProtocolMessage.ParseStream() - Socket error reading protocol message number (Read 0 of 1 bytes). Exception: Exception: CONNECTION CLOSED
2009-12-22 13:56:08,065 - 3: ProtocolMessage.ParseStream() Get ProtocolMessage ID Exception: CONNECTION CLOSED BytesRead 0 of 10 (allowed).
2009-12-22 13:56:08,065 - 3: Connection Closed: CONNECTION CLOSED
2009-12-22 13:56:08,065 - Connection accepted from 10.10.1.117:50743 on local address 10.10.1.7:8080, session id is 4.
2009-12-22 13:56:08,362 - 3: VSS database closed for the session id 3.
2009-12-22 13:56:09,643 - 4: ProtocolMessage.ParseStream() - Socket error reading protocol message number (Read 0 of 1 bytes). Exception: Exception: CONNECTION CLOSED
2009-12-22 13:56:09,643 - 4: ProtocolMessage.ParseStream() Get ProtocolMessage ID Exception: CONNECTION CLOSED BytesRead 0 of 10 (allowed).
2009-12-22 13:56:09,643 - 4: Connection Closed: CONNECTION CLOSED
2009-12-22 13:56:09,659 - Connection accepted from 10.10.1.117:50744 on local address 10.10.1.7:8080, session id is 5.
2009-12-22 13:56:09,940 - 4: VSS database closed for the session id 4.
Brian C Drab

Beth
Posts: 8550
Joined: Wed Jun 21, 2006 8:24 pm
Location: SourceGear
Contact:

Re: Response for No Message Sent! - SOS 5.0.1

Post by Beth » Tue Dec 22, 2009 1:36 pm

Can you tell me the full version of the automation component being used? Instructions for finding that are posted here: http://support.sourcegear.com/viewtopic.php?t=1510.

While you are in the registry, in the same place where the component is registered is an entry for the Threading Model. What is that set for?
Beth Kieler
SourceGear Technical Support

BrianDrab
Posts: 98
Joined: Tue Mar 25, 2008 1:27 pm
Contact:

Re: Response for No Message Sent! - SOS 5.0.1

Post by BrianDrab » Tue Dec 22, 2009 1:41 pm

8.0.50727.1551
Apartment (I thought it only had to be Both if we were using VSS 6.0d)
Brian C Drab

Beth
Posts: 8550
Joined: Wed Jun 21, 2006 8:24 pm
Location: SourceGear
Contact:

Re: Response for No Message Sent! - SOS 5.0.1

Post by Beth » Tue Dec 22, 2009 2:01 pm

I have seen cases where setting it to Both with VSS 2005 helped as well. Please try that and let me know your results.
Beth Kieler
SourceGear Technical Support

BrianDrab
Posts: 98
Joined: Tue Mar 25, 2008 1:27 pm
Contact:

Re: Response for No Message Sent! - SOS 5.0.1

Post by BrianDrab » Tue Dec 22, 2009 3:20 pm

Done. Same issue. I did the following:

1. Change the registry value to Both
2. Stopped and Started the SOS 5 Server service
3. Performed the open from Visual Studio as documented.

Same exact issue.
Brian C Drab

Beth
Posts: 8550
Joined: Wed Jun 21, 2006 8:24 pm
Location: SourceGear
Contact:

Re: Response for No Message Sent! - SOS 5.0.1

Post by Beth » Tue Dec 22, 2009 5:24 pm

Are the SOS GUI clients able to connect and manipulate files with no errors?
Beth Kieler
SourceGear Technical Support

BrianDrab
Posts: 98
Joined: Tue Mar 25, 2008 1:27 pm
Contact:

Re: Response for No Message Sent! - SOS 5.0.1

Post by BrianDrab » Tue Dec 22, 2009 8:44 pm

Yes, it appears so.
Brian C Drab

Beth
Posts: 8550
Joined: Wed Jun 21, 2006 8:24 pm
Location: SourceGear
Contact:

Re: Response for No Message Sent! - SOS 5.0.1

Post by Beth » Wed Dec 23, 2009 4:04 pm

Often the errors you are receiving that mention a connection being closed indicate a network problem. Can you rename your current SOS log to force SOS to create a new one? After that, connect with your GUI client and manipulate a few files. Then check the server log. Do you still get the connection errors?

It might help to take a closer look. Could you send an email to support at sourcegear.com (attn: Beth) with a link to this forum thread?
Beth Kieler
SourceGear Technical Support

BrianDrab
Posts: 98
Joined: Tue Mar 25, 2008 1:27 pm
Contact:

Re: Response for No Message Sent! - SOS 5.0.1

Post by BrianDrab » Wed Dec 23, 2009 4:25 pm

OK, I did the following:
1. Stopped the SOS Server service.
2. Renamed the log.txt to log2.txt
3. Started the service.
4. Retrieved a project using the Visual Studio 2008 GUI (you didn't specifiy so I assumed this is what you meant)
5. Looked at the log. I didn't need to manipulate anything. Following is the entire contents of the fresh log.


2009-12-23 17:20:05,261 - Loading SourceOffSite Server configuration from E:\Program Files\SourceGear\SourceOffSite 5 Server\sossvr.prp
2009-12-23 17:20:05,277 -
2009-12-23 17:20:05,277 - ****************************************************
2009-12-23 17:20:05,277 - ****************************************************
2009-12-23 17:20:05,277 - SourceOffSite Server 5.0.1.242 Professional - With Cryptography
2009-12-23 17:20:05,277 -
2009-12-23 17:20:05,277 - CurrentCulture is en-US.
2009-12-23 17:20:05,277 -
2009-12-23 17:20:05,496 - Server Information
2009-12-23 17:20:05,496 - Operating System: Microsoft(R) Windows(R) Server 2003, Standard Edition
2009-12-23 17:20:05,496 - Service Pack: 2.0
2009-12-23 17:20:05,496 - OS Version: 5.2.3790
2009-12-23 17:20:05,496 - Locale: Ox0409
2009-12-23 17:20:05,496 - OSLanguage: 1033
2009-12-23 17:20:05,496 - Total Physical Memory: 2 GB
2009-12-23 17:20:05,496 - Time Zone: (GMT-05:00) Eastern Time (US & Canada)
2009-12-23 17:20:05,496 -
2009-12-23 17:20:05,496 - SSAPI.dll Information:
2009-12-23 17:20:05,496 - Version: E:\Program Files\Microsoft Visual SourceSafe\ssapi.dll (8.0.50727.1551 (QFE.050727-1500))
2009-12-23 17:20:05,496 - Threading Model: Apartment
2009-12-23 17:20:05,496 -
2009-12-23 17:20:05,496 - Logging at level Error
2009-12-23 17:20:05,496 -
2009-12-23 17:20:05,496 -
2009-12-23 17:20:05,511 - Number of licenses configured: 4
2009-12-23 17:20:05,511 -
2009-12-23 17:20:05,527 - SourceSafe Initialization file(s) located at:
2009-12-23 17:20:05,527 - \\kaplan-dev\VSSDatabases\VSS\srcsafe.ini
2009-12-23 17:20:05,527 - \\kaplan-dev\VSSDatabases\Documentation\srcsafe.ini
2009-12-23 17:20:05,527 - \\kaplan-dev\VSSDatabases\Legacy\srcsafe.ini
2009-12-23 17:20:05,527 - \\kaplan-dev\VSSDatabases\Personal\srcsafe.ini
2009-12-23 17:20:05,527 - SourceOffSite Server will be using the Visual SourceSafe 2005 Interface.
2009-12-23 17:20:05,527 - Started at 12/23/2009 17:20:05
2009-12-23 17:20:05,527 - ****************************************************
2009-12-23 17:20:05,527 - ****************************************************
2009-12-23 17:20:05,527 -
2009-12-23 17:20:05,558 - kaplan-web is attempting to listen for connections on unsecure port 8080
2009-12-23 17:20:05,590 - Waiting for a connection....secure = False
2009-12-23 17:20:55,121 - Connection accepted from 10.10.1.117:51299 on local address 10.10.1.7:8080, session id is 1.
2009-12-23 17:21:14,871 - 1: ProtocolMessage.ParseStream() - Socket error reading protocol message number (Read 0 of 1 bytes). Exception: Exception: CONNECTION CLOSED
2009-12-23 17:21:14,871 - 1: ProtocolMessage.ParseStream() Get ProtocolMessage ID Exception: CONNECTION CLOSED BytesRead 0 of 10 (allowed).
2009-12-23 17:21:14,871 - 1: Connection Closed: CONNECTION CLOSED
2009-12-23 17:21:14,902 - Connection accepted from 10.10.1.117:51301 on local address 10.10.1.7:8080, session id is 2.
2009-12-23 17:21:15,199 - 1: VSS database closed for the session id 1.
2009-12-23 17:21:16,105 - 2: ProtocolMessage.ParseStream() - Socket error reading protocol message number (Read 0 of 1 bytes). Exception: Exception: CONNECTION CLOSED
2009-12-23 17:21:16,105 - 2: ProtocolMessage.ParseStream() Get ProtocolMessage ID Exception: CONNECTION CLOSED BytesRead 0 of 10 (allowed).
2009-12-23 17:21:16,105 - 2: Connection Closed: CONNECTION CLOSED
2009-12-23 17:21:16,105 - 2: VSS database closed for the session id 2.
2009-12-23 17:21:16,105 - Connection accepted from 10.10.1.117:51302 on local address 10.10.1.7:8080, session id is 3.
2009-12-23 17:21:20,433 - 3: ProtocolMessage.ParseStream() - Socket error reading protocol message number (Read 0 of 1 bytes). Exception: Exception: CONNECTION CLOSED
2009-12-23 17:21:20,433 - 3: ProtocolMessage.ParseStream() Get ProtocolMessage ID Exception: CONNECTION CLOSED BytesRead 0 of 10 (allowed).
2009-12-23 17:21:20,433 - 3: Connection Closed: CONNECTION CLOSED
2009-12-23 17:21:20,433 - Connection accepted from 10.10.1.117:51303 on local address 10.10.1.7:8080, session id is 4.
2009-12-23 17:21:20,730 - 3: VSS database closed for the session id 3.
2009-12-23 17:21:22,199 - 4: ProtocolMessage.ParseStream() - Socket error reading protocol message number (Read 0 of 1 bytes). Exception: Exception: CONNECTION CLOSED
2009-12-23 17:21:22,199 - 4: ProtocolMessage.ParseStream() Get ProtocolMessage ID Exception: CONNECTION CLOSED BytesRead 0 of 10 (allowed).
2009-12-23 17:21:22,199 - 4: Connection Closed: CONNECTION CLOSED
2009-12-23 17:21:22,215 - Connection accepted from 10.10.1.117:51304 on local address 10.10.1.7:8080, session id is 5.
2009-12-23 17:21:22,511 - 4: VSS database closed for the session id 4.
Brian C Drab

Beth
Posts: 8550
Joined: Wed Jun 21, 2006 8:24 pm
Location: SourceGear
Contact:

Re: Response for No Message Sent! - SOS 5.0.1

Post by Beth » Thu Dec 24, 2009 9:53 am

Sorry, I meant with the SOS GUI client separate from Visual Studio 2008. This will help narrow down the problem a little. You had the right method, just do the same thing with Visual Studio completely closed.
Beth Kieler
SourceGear Technical Support

BrianDrab
Posts: 98
Joined: Tue Mar 25, 2008 1:27 pm
Contact:

Re: Response for No Message Sent! - SOS 5.0.1

Post by BrianDrab » Sun Dec 27, 2009 11:45 pm

OK, here are the resutls. I don't get any kind of "Response for No Message Sent!" message, however here is a fresh log of using only the SOS 5 GUI to check out a project and sub-projects and then undo checkout.

Are the messages in the log expected?

2009-12-28 00:39:41,533 - Loading SourceOffSite Server configuration from E:\Program Files\SourceGear\SourceOffSite 5 Server\sossvr.prp
2009-12-28 00:39:41,549 -
2009-12-28 00:39:41,549 - ****************************************************
2009-12-28 00:39:41,549 - ****************************************************
2009-12-28 00:39:41,549 - SourceOffSite Server 5.0.1.242 Professional - With Cryptography
2009-12-28 00:39:41,549 -
2009-12-28 00:39:41,549 - CurrentCulture is en-US.
2009-12-28 00:39:41,549 -
2009-12-28 00:39:41,799 - Server Information
2009-12-28 00:39:41,799 - Operating System: Microsoft(R) Windows(R) Server 2003, Standard Edition
2009-12-28 00:39:41,799 - Service Pack: 2.0
2009-12-28 00:39:41,799 - OS Version: 5.2.3790
2009-12-28 00:39:41,799 - Locale: Ox0409
2009-12-28 00:39:41,799 - OSLanguage: 1033
2009-12-28 00:39:41,799 - Total Physical Memory: 2 GB
2009-12-28 00:39:41,799 - Time Zone: (GMT-05:00) Eastern Time (US & Canada)
2009-12-28 00:39:41,799 -
2009-12-28 00:39:41,799 - SSAPI.dll Information:
2009-12-28 00:39:41,799 - Version: E:\Program Files\Microsoft Visual SourceSafe\ssapi.dll (8.0.50727.1551 (QFE.050727-1500))
2009-12-28 00:39:41,799 - Threading Model: Apartment
2009-12-28 00:39:41,799 -
2009-12-28 00:39:41,799 - Logging at level Error
2009-12-28 00:39:41,799 -
2009-12-28 00:39:41,799 -
2009-12-28 00:39:41,814 - Number of licenses configured: 4
2009-12-28 00:39:41,814 -
2009-12-28 00:39:41,830 - SourceSafe Initialization file(s) located at:
2009-12-28 00:39:41,830 - \\kaplan-dev\VSSDatabases\VSS\srcsafe.ini
2009-12-28 00:39:41,830 - \\kaplan-dev\VSSDatabases\Documentation\srcsafe.ini
2009-12-28 00:39:41,830 - \\kaplan-dev\VSSDatabases\Legacy\srcsafe.ini
2009-12-28 00:39:41,830 - \\kaplan-dev\VSSDatabases\Personal\srcsafe.ini
2009-12-28 00:39:41,830 - SourceOffSite Server will be using the Visual SourceSafe 2005 Interface.
2009-12-28 00:39:41,830 - Started at 12/28/2009 00:39:41
2009-12-28 00:39:41,830 - ****************************************************
2009-12-28 00:39:41,830 - ****************************************************
2009-12-28 00:39:41,830 -
2009-12-28 00:39:41,861 - kaplan-web is attempting to listen for connections on unsecure port 8080
2009-12-28 00:39:41,893 - Waiting for a connection....secure = False
2009-12-28 00:39:51,846 - Connection accepted from 10.10.1.108:50910 on local address 10.10.1.7:8080, session id is 1.
2009-12-28 00:41:30,095 - 1: ProtocolMessage.ParseStream() - Socket error reading protocol message number (Read 0 of 1 bytes). Exception: Exception: CONNECTION CLOSED
2009-12-28 00:41:30,095 - 1: ProtocolMessage.ParseStream() Get ProtocolMessage ID Exception: CONNECTION CLOSED BytesRead 0 of 10 (allowed).
2009-12-28 00:41:30,095 - 1: Connection Closed: CONNECTION CLOSED
2009-12-28 00:41:30,111 - 1: VSS database closed for the session id 1.
Brian C Drab

Beth
Posts: 8550
Joined: Wed Jun 21, 2006 8:24 pm
Location: SourceGear
Contact:

Re: Response for No Message Sent! - SOS 5.0.1

Post by Beth » Mon Dec 28, 2009 8:57 am

Thank you.

Can you check the Event Viewer logs on your client computer? Are any errors being logged there that correspond with you performing an Open from Source Control inside of VS 2008?
Beth Kieler
SourceGear Technical Support

BrianDrab
Posts: 98
Joined: Tue Mar 25, 2008 1:27 pm
Contact:

Re: Response for No Message Sent! - SOS 5.0.1

Post by BrianDrab » Mon Dec 28, 2009 10:07 am

The only thing I see is one Informational Event and two Logon Failure events. The details of these are shown below.

Log Name: System
Source: Service Control Manager
Date: 12/28/2009 11:02:42 AM
Event ID: 7036
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: ITMANAGER.kaplantrucking.com
Description:
The WinHTTP Web Proxy Auto-Discovery Service service entered the stopped state.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager" />
<EventID Qualifiers="16384">7036</EventID>
<Version>0</Version>
<Level>4</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8080000000000000</Keywords>
<TimeCreated SystemTime="2009-12-28T16:02:42.544246500Z" />
<EventRecordID>19077</EventRecordID>
<Correlation />
<Execution ProcessID="576" ThreadID="5148" />
<Channel>System</Channel>
<Computer>ITMANAGER.kaplantrucking.com</Computer>
<Security />
</System>
<EventData>
<Data Name="param1">WinHTTP Web Proxy Auto-Discovery Service</Data>
<Data Name="param2">stopped</Data>
<Binary>570069006E0048007400740070004100750074006F00500072006F00780079005300760063002F0031000000</Binary>
</EventData>
</Event>



Log Name: Security
Source: Microsoft-Windows-Security-Auditing
Date: 12/28/2009 11:01:37 AM
Event ID: 4625
Task Category: Logon
Level: Information
Keywords: Audit Failure
User: N/A
Computer: ITMANAGER.kaplantrucking.com
Description:
An account failed to log on.

Subject:
Security ID: KAPLANTRUCKING\Briand
Account Name: Briand
Account Domain: KAPLANTRUCKING
Logon ID: 0x9d800

Logon Type: 4

Account For Which Logon Failed:
Security ID: NULL SID
Account Name: KaplanAASLoadMonitor
Account Domain: KAPLANTRUCKING

Failure Information:
Failure Reason: The user has not been granted the requested logon type at this machine.
Status: 0xc000015b
Sub Status: 0x0

Process Information:
Caller Process ID: 0x12f0
Caller Process Name: C:\Program Files (x86)\Microsoft Visual Studio 9.0\Common7\IDE\devenv.exe

Network Information:
Workstation Name: ITMANAGER
Source Network Address: -
Source Port: -

Detailed Authentication Information:
Logon Process: Advapi
Authentication Package: Negotiate
Transited Services: -
Package Name (NTLM only): -
Key Length: 0

This event is generated when a logon request fails. It is generated on the computer where access was attempted.

The Subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.

The Logon Type field indicates the kind of logon that was requested. The most common types are 2 (interactive) and 3 (network).

The Process Information fields indicate which account and process on the system requested the logon.

The Network Information fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.

The authentication information fields provide detailed information about this specific logon request.
- Transited services indicate which intermediate services have participated in this logon request.
- Package name indicates which sub-protocol was used among the NTLM protocols.
- Key length indicates the length of the generated session key. This will be 0 if no session key was requested.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Security-Auditing" Guid="{54849625-5478-4994-A5BA-3E3B0328C30D}" />
<EventID>4625</EventID>
<Version>0</Version>
<Level>0</Level>
<Task>12544</Task>
<Opcode>0</Opcode>
<Keywords>0x8010000000000000</Keywords>
<TimeCreated SystemTime="2009-12-28T16:01:37.723246500Z" />
<EventRecordID>3248</EventRecordID>
<Correlation />
<Execution ProcessID="592" ThreadID="3544" />
<Channel>Security</Channel>
<Computer>ITMANAGER.kaplantrucking.com</Computer>
<Security />
</System>
<EventData>
<Data Name="SubjectUserSid">S-1-5-21-286218187-511082069-1553874782-1672</Data>
<Data Name="SubjectUserName">Briand</Data>
<Data Name="SubjectDomainName">KAPLANTRUCKING</Data>
<Data Name="SubjectLogonId">0x9d800</Data>
<Data Name="TargetUserSid">S-1-0-0</Data>
<Data Name="TargetUserName">KaplanAASLoadMonitor</Data>
<Data Name="TargetDomainName">KAPLANTRUCKING</Data>
<Data Name="Status">0xc000015b</Data>
<Data Name="FailureReason">%%2308</Data>
<Data Name="SubStatus">0x0</Data>
<Data Name="LogonType">4</Data>
<Data Name="LogonProcessName">Advapi </Data>
<Data Name="AuthenticationPackageName">Negotiate</Data>
<Data Name="WorkstationName">ITMANAGER</Data>
<Data Name="TransmittedServices">-</Data>
<Data Name="LmPackageName">-</Data>
<Data Name="KeyLength">0</Data>
<Data Name="ProcessId">0x12f0</Data>
<Data Name="ProcessName">C:\Program Files (x86)\Microsoft Visual Studio 9.0\Common7\IDE\devenv.exe</Data>
<Data Name="IpAddress">-</Data>
<Data Name="IpPort">-</Data>
</EventData>
</Event>



Log Name: Security
Source: Microsoft-Windows-Security-Auditing
Date: 12/28/2009 11:01:37 AM
Event ID: 4625
Task Category: Logon
Level: Information
Keywords: Audit Failure
User: N/A
Computer: ITMANAGER.kaplantrucking.com
Description:
An account failed to log on.

Subject:
Security ID: KAPLANTRUCKING\Briand
Account Name: Briand
Account Domain: KAPLANTRUCKING
Logon ID: 0x9d800

Logon Type: 5

Account For Which Logon Failed:
Security ID: NULL SID
Account Name: KaplanAASLoadMonitor
Account Domain: KAPLANTRUCKING

Failure Information:
Failure Reason: The user has not been granted the requested logon type at this machine.
Status: 0xc000015b
Sub Status: 0x0

Process Information:
Caller Process ID: 0x12f0
Caller Process Name: C:\Program Files (x86)\Microsoft Visual Studio 9.0\Common7\IDE\devenv.exe

Network Information:
Workstation Name: ITMANAGER
Source Network Address: -
Source Port: -

Detailed Authentication Information:
Logon Process: Advapi
Authentication Package: Negotiate
Transited Services: -
Package Name (NTLM only): -
Key Length: 0

This event is generated when a logon request fails. It is generated on the computer where access was attempted.

The Subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.

The Logon Type field indicates the kind of logon that was requested. The most common types are 2 (interactive) and 3 (network).

The Process Information fields indicate which account and process on the system requested the logon.

The Network Information fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.

The authentication information fields provide detailed information about this specific logon request.
- Transited services indicate which intermediate services have participated in this logon request.
- Package name indicates which sub-protocol was used among the NTLM protocols.
- Key length indicates the length of the generated session key. This will be 0 if no session key was requested.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Security-Auditing" Guid="{54849625-5478-4994-A5BA-3E3B0328C30D}" />
<EventID>4625</EventID>
<Version>0</Version>
<Level>0</Level>
<Task>12544</Task>
<Opcode>0</Opcode>
<Keywords>0x8010000000000000</Keywords>
<TimeCreated SystemTime="2009-12-28T16:01:37.760246500Z" />
<EventRecordID>3249</EventRecordID>
<Correlation />
<Execution ProcessID="592" ThreadID="3544" />
<Channel>Security</Channel>
<Computer>ITMANAGER.kaplantrucking.com</Computer>
<Security />
</System>
<EventData>
<Data Name="SubjectUserSid">S-1-5-21-286218187-511082069-1553874782-1672</Data>
<Data Name="SubjectUserName">Briand</Data>
<Data Name="SubjectDomainName">KAPLANTRUCKING</Data>
<Data Name="SubjectLogonId">0x9d800</Data>
<Data Name="TargetUserSid">S-1-0-0</Data>
<Data Name="TargetUserName">KaplanAASLoadMonitor</Data>
<Data Name="TargetDomainName">KAPLANTRUCKING</Data>
<Data Name="Status">0xc000015b</Data>
<Data Name="FailureReason">%%2308</Data>
<Data Name="SubStatus">0x0</Data>
<Data Name="LogonType">5</Data>
<Data Name="LogonProcessName">Advapi </Data>
<Data Name="AuthenticationPackageName">Negotiate</Data>
<Data Name="WorkstationName">ITMANAGER</Data>
<Data Name="TransmittedServices">-</Data>
<Data Name="LmPackageName">-</Data>
<Data Name="KeyLength">0</Data>
<Data Name="ProcessId">0x12f0</Data>
<Data Name="ProcessName">C:\Program Files (x86)\Microsoft Visual Studio 9.0\Common7\IDE\devenv.exe</Data>
<Data Name="IpAddress">-</Data>
<Data Name="IpPort">-</Data>
</EventData>
</Event>
Brian C Drab

Beth
Posts: 8550
Joined: Wed Jun 21, 2006 8:24 pm
Location: SourceGear
Contact:

Re: Response for No Message Sent! - SOS 5.0.1

Post by Beth » Mon Dec 28, 2009 1:25 pm

I have received your email that was sent to support and will be replying offline. Thanks.

F: 218654
Beth Kieler
SourceGear Technical Support

BrianDrab
Posts: 98
Joined: Tue Mar 25, 2008 1:27 pm
Contact:

Re: Response for No Message Sent! - SOS 5.0.1

Post by BrianDrab » Fri Jan 29, 2010 9:56 am

I'm posting the "offline" troubleshooting emails for completeness.

OK, done but same symptoms. I noticed something though. Each time the Response for no message sent notification comes up, the status bar is on the following file.
Item.jpg
Item.jpg (30.61 KiB) Viewed 22028 times
Brian C Drab

Post Reply