Microsoft Knowledge Base Email Alertz

(939325) - Describes a problem in which a Microsoft SoftGrid-enabled application does not start. Describes how to resolve this problem.

Search KbAlertz

Advanced Search

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]











Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

Article ID: 939325 - Last Review: August 6, 2007 - Revision: 1.0

You receive an error message when you try to start a SoftGrid-enabled application in the SoftGrid client

SYMPTOMS

When you try to start a Microsoft SoftGrid-enabled application in the SoftGrid client, the application does not start. Additionally, you may receive one of the following error messages.
Error message 1
No connection could be made because the target machine actively refused it.
Error message 2
Error: User was forcibly disconnected.
Error message 3
The SoftGrid Client could not launch application_name. An unexpected error occurred. Please report the following error code to your System Administrator.
Error code: xxxxxx-xxxxxx0A-00000120

CAUSE

This problem may occur if Microsoft SQL Server is unavailable or is unresponsive. For example, this problem may occur if SQL Server is taken offline or if SQL Server job reports stop responding.

RESOLUTION

To resolve this problem, follow these steps:
  1. Make sure that the connection to the computer that is running SQL Server is working as designed.
  2. Review the Application log to determine whether SQL Server is experiencing an issue. We recommend that you contact the SQL Server database administrator (DBA) for more information.

MORE INFORMATION

The following messages may be logged in the SoftGrid client log file (Sftlog.txt).
Message 1
[05/30/2007 22:23:50.530 INOT VRB] {tid=AC4:usr=SEQ1} IN: SWFsdIoManager::Connect
Message 2
[05/30/2007 22:24:50.887 AMGR WRN] {hap=28:app=Default SoftGrid Application 1.0:tid=97C} The SoftGrid Client lost contact with a server and entered disconnected mode.
Message 3
[05/30/2007 22:24:50.897 INOT VRB] {tid=AC4:usr=SEQ1} OUT: SWFsdIoManager::Connect
Message 4
[05/30/2007 22:24:50.897 JGSW VRB] {hap=28:app=Default SoftGrid Application 1.0:tid=AC4:usr=SEQ1} Elapsed time for SWFsdIoManager::Connect(): 60.217 seconds
Message 5
[05/30/2007 22:24:50.897 JGSW ERR] {hap=28:app=Default SoftGrid Application 1.0:tid=AC4:usr=SEQ1} The SoftGrid client could not connect to stream URL 'rtsp://LAB-T2Q6T8LW4OY:554/DefaultApp.sft' (FS status: 1600190A-00000120).
Message 6
[05/30/2007 22:24:50.897 SWAP ERR] {hap=28:app=Default SoftGrid Application 1.0:tid=AC4:usr=SEQ1} The client was unable to connect to a SoftGrid server (rc 1600190A-00000120)

APPLIES TO
  • Microsoft SoftGrid for Terminal Services
  • Microsoft SoftGrid for Windows Desktops
Keywords: 
kbexpertiseadvanced kbtshoot KB939325
       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate