Microsoft Knowledge Base Email Alertz

KBAlertz.com: (931254) - When launching an application, why does it fail with the following error code? The SoftGrid Client could not launch {application_name}. Either you are not authorized to use this application or the system could not obtain a license for this...

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]

Search KbAlertz

Advanced Search

Webmasters
Put kbAlertz on your website.
[ Click Here for more! ]





ASP.NET 3.5 Web Hosting with Windows 2008 and SQL 2008: Click Here!
Discount ASP.NET Hosting
ASP.NET 2.0 and 3.5
Windows2008 and SQL2008
US and UK Hosting
The ad says 3 - but KBAlertz referrals get
** SIX MONTHS FREE **


Bug Tracking Software
For bug tracking software or defect tracking software or issue tracking software, visit Axosoft.


Community Site



We Send hundreds of thousands of emails using ASP.NET Email



Expert Web Design & Graphic Design
Design44.com

ASP.NET 3.5 Web Hosting with Windows 2008 and SQL 2008: Click Here!
Discount ASP.NET Hosting
ASP.NET 2.0 and 3.5
Windows2008 and SQL2008
US and UK Hosting
The ad says 3 - but KBAlertz referrals get
** SIX MONTHS FREE **




Mentioned In








Microsoft Knowledge Base Article

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




Article ID: 931254 - Last Review: May 15, 2007 - Revision: 2.0

Error message when you try to start an application in SoftGrid Client: "Error code: xxxxxx-xxxxxx07-000DF004"

SYMPTOMS

When you start an application in Microsoft SoftGrid Client, the operation is unsuccessful. Additionally, you receive one of the following error messages:
The SoftGrid Client could not launch application_name.
Either you are not authorized to use this application or the system could not obtain a license for this application. If the problem persists, please report the following error code to your System Administrator.
Error code: xxxxxx-xxxxxx07-000DF004
The SoftGrid Client could not launch application_name.
You are not authorized to use this application, possibly because there are no more licenses available. Please report the following error code to your System Administrator
Error code: xxxxxx-xxxxxx07-000DF004
Additionally, the following error message is logged in the SoftGrid Virtual Application Server log file (Sft-server.log):
41994 "Authentication denied for address ip_address:port. User not authorized for access to provider."
41998 "The connection has not been authenticated."

CAUSE

This issue may occur if one or more of the following conditions are true:
  • The SoftGrid Virtual Application Server cannot locate the .sft file.
  • The Softricity File field contains a backslash (\) character instead of a forward slash (/) character.
  • The user who is trying to start the application does not have access to the application.
  • The user who is trying to start the application does not have access to the Provider Policy.
  • The application is disabled.
  • Licensing is enabled and is configured under Enforce License Policies in the Provider Policy Provider Pipeline, and the Application License Group for the application is set to none.
  • Licensing is enabled and is configured under Enforce License Policies in the Provider Policy Provider Pipeline, and the Application License Group for the application is set to disabled or to expired.
  • The Authentication option is disabled and the Enforce Access Permission Settings option is enabled for the Provider Policy Provider Pipeline.

RESOLUTION

To resolve this issue, use one or more of the following methods, as appropriate for your situation.
  • If the SoftGrid Virtual Application Server cannot locate the .sft file, follow these steps:
    1. In the SoftGrid Management Console, locate the properties of the application.
    2. On the General tab, review the Softricity File field. Verify that the path and the .sft file name are valid.
  • If the Softricity File field contains a backslash character instead of a forward slash character, correct this.

    An example of the correct format for the Softricity File field is as follows:
    Softricity/sft_ea70.sft
    An example of an incorrect format is as follows:
    Softricity\sft_ea70.sft
  • Verify that the user who is trying to start the application has access to the application. To do this, follow these steps:
    1. In the SoftGrid Management Console, locate the properties of the application.
    2. Click the Access Permissions tab. Verify that the user is a member of an assigned group.
  • Verify that the user who is trying to start the application has access to the Provider Policy. To do this, follow these steps:
    1. In the SoftGrid Management Console, locate the properties of the Provider Policy.
    2. Click the Group Assignment tab. Verify that the user is a member of the assigned group.
  • Determine whether the application is disabled. To do this, follow these steps:
    1. In the SoftGrid Management Console, locate the properties of the application.
    2. Verify that the Enabled check box is selected.
  • If licensing is enabled and is configured under Enforce License Policies in the Provider Policy Provider Pipeline, and if the Application License Group for the application is set to none, follow these steps:
    1. In the SoftGrid Management Console, locate the properties of the application.
    2. Verify that the Application License Group option is configured.
    Alternatively, follow these steps:
    1. In the SoftGrid Management Console, locate the properties of the Provider Policy.
    2. Click the Provider Policy tab, and then click to clear the Licensing check box or set the Licensing option to Audit License Usage Only.
    Important Make sure that you assess the current configuration of other applications before you make these changes. When you modify the Provider Policy, all applications that are associated with the provider are affected.
  • If licensing is enabled and is configured under Enforce License Policies in the Provider Policy Provider Pipeline, and if the Application License Group for the application is set to disabled or to expired, follow these steps:
    1. In the SoftGrid Management Console, locate the properties of the application license.
    2. Verify that the Enabled check box is selected.
    3. Verify that the expiration date has not expired (do this if the Expiration Date check box is selected).
    Important Make sure that you assess the current configuration of other applications before you make these changes. When you modify the Provider Policy, all applications that are associated with the provider are affected.
  • If the Authentication option is disabled and if the Enforce Access Permission Settings option is enabled for the Provider Policy Provider Pipeline, follow these steps:
    1. In the SoftGrid Management Console, locate the properties of the Provider Policy.
    2. Click the Provider Policy tab. Click to select the Authentication check box, or click to clear the Enforce Access Permission Settings check box.
    Important Make sure that you assess the current configuration of other applications before you make these changes. When you modify the Provider Policy, all applications that are associated with the provider are affected.

APPLIES TO
  • Microsoft SoftGrid for Terminal Services
  • Microsoft SoftGrid for Windows Desktops
Keywords: 
kbexpertiseinter kbtshoot KB931254
       

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

Be the first to leave feedback, to help others about this knowledge base article.

(Optional) Name

(Optional) Public URL Or Email

Comments
No HTML -- Text Only Please