Article ID: 930711
Article Last Modified on 3/23/2007
APPLIES TO
- Microsoft SoftGrid for Terminal Services
- Microsoft SoftGrid for Windows Desktops
SYMPTOMS
When you update a Desktop Configuration Server in SoftGrid Client Management 4.x, the operation is not successful. Additionally, you receive the following error message:
Additionally, the following error message is logged in the SoftGrid Client log file (Sftlog.txt):
CAUSE
This issue may occur when one or more of the following conditions are true:
- An application version does not contain an alphanumeric character.
- The application list that is returned by the Desktop Configuration Server contains invalid XML.
- The server's Type field is configured for Standard HTTP Server, and the .xml file that is specified is invalid.
RESOLUTION
To resolve this issue, use one or more of the following methods, as appropriate for your situation.
Method 1: Make sure that the application version contains an alphanumeric character
If you add an application to the SoftGrid Management Console without typing an alphanumeric character for the version, the application causes the update operation to be unsuccessful. For example, this issue occurs if you add an application only by pressing SPACEBAR one time.
Application versions must contain an alphanumeric character. To verify that the application version contains an alphanumeric character, follow these steps:
- Click Start, point to All Programs, click Administrative Tools, and then click SoftGrid Management Console.
- Expand SoftGrid Systems, expand
Server_Name, and then expand Applications. - Examine the Version column for an application version that appears to be blank.
- If you locate an application version that appears to be blank, right-click the application, and then click Properties.
- For Version, type a version that contains an alphanumeric character. For example, type 1.0.
- Locate the .osd file that is specified in the OSD Path field.
- Open the .osd file by using a text editor such as Notepad.
- In the VERSION="" attribute of the <SOFTPKG> element, type the same application version that you typed in step 5, as follows:
<SOFTPKG NAME="Default SoftGrid Application" VERSION="1.0">
- Save the .osd file, and then exit the text editor.
- Exit the SoftGrid Management Console.
Method 2: Correct the XML in the application list that is returned by the Desktop Configuration Server
When the client updates against the server, the server returns a list of applications in XML. If the list contains invalid XML, the update operation is not successful.
Frequently, this issue occurs because the ampersand character (&) is used in environments that include a 3.x version of the SoftGrid Virtual Application Server and a 4.x version of SoftGrid Client Management. To verify this, follow these steps:
- Click Start, point to All Programs, click Administrative Tools, and then click SoftGrid Client Management.
- Right-click SoftGrid on localhost, and then click Properties.
- Click the General tab.
- In the Log Level list, select Verbose, and then click OK.
- Click Desktop Configuration Servers, right-click the server that you want, and then click Refresh.
- Locate the following folder:
%ProgramFiles%\Softricity\SoftGrid for Windows Desktops or Terminal Servers
- Open the Sftlog.txt file by using a text editor such as Notepad.
- Search for the <APPLIST> element.
Copy the text from <APPLIST> to </APPLIST>, and then save the text to an .xml file.
For example, copy and then save the following text.<APPLIST> <APP NAME="Default SoftGrid Application" VERSION="1.0 & 2.0" OSD="DefaultApp.osd" ICON="DefaultApp.ico"> <SHORTCUTLIST MANAGEMENT="ServerOnly"> <SHORTCUT LOCATION="%CSIDL_DESKTOPDIRECTORY%" /> </SHORTCUTLIST> </APP> </APPLIST>
Open the .xml file by using a Web browser. The Web browser may report the line number and the column where the error occurred, as follows.
Whitespace is not allowed at this location. Error processing resource 'file://filename.xml' <APP NAME="Default SoftGrid Application" VERSION="1.0 & 2.0" OSD="DefaultApp.osd" ICON="DefaultApp.ico"> -------------------------------------------------------------------------^
In this example, the ampersand character in the "Default SoftGrid Application" application version is causing the issue.
- Click Start, point to All Programs, click Administrative Tools, and then click SoftGrid Management Console.
- Expand SoftGrid Systems, expand
Server_Name, and then expand Applications. - Right-click the application that you located in step 10, and then click Properties. For example, right-click the "Default SoftGrid Application" application.
- Correct the invalid XML. For example, remove the ampersand character from the VERSION field.
- Locate the .osd file that is specified in the OSD Path field.
- Open the .osd file by using a text editor such as Notepad.
- Correct the invalid XML. For example, remove the ampersand character from the VERSION="" attribute of the <SOFTPKG> element.
- Save the .osd file, and then exit the text editor.
- Exit the SoftGrid Management Console.
Method 3: Make sure that the .xml file that is specified is valid if the server's Type field is configured for "Standard HTTP Server"
You receive the error message that is mentioned in the "Symptoms" section if the Desktop Configuration Server Type field is configured for Standard HTTP Server and if the path of the .xml file or the .xml file name do not exist or are typed incorrectly, or if the .xml file contains invalid XML. To verify this, follow these steps:
- Click Start, point to All Programs, click Administrative Tools, and then click SoftGrid Client Management.
- Click Desktop Configuration Servers, right-click the server that you want, and then click Properties.
- If the Type field is not set to Standard HTTP Server, this condition is not causing the error code.
If the Type field is set to Standard HTTP Server, go to step 4.
- Examine the Path setting to verify that the path of the .xml file and the .xml file name exist and are typed correctly.
- Examine the .xml file for invalid XML. To do this, open the .xml file by using a Web browser. The Web browser may report the line number and the column where the error occurred.
Keywords: kbexpertiseinter kbtshoot KB930711
