An active upggrade to SoftGrid 4.2 fails for an environment that mixes SoftGrid Client 3.x andSoftGrid Server 4.x components.Even after you restart the domain controller, an active upgrade may fail for SoftGrid 3.x clients and for SoftGrid 4.x servers.
|An active upgrade works for an environment that is running SoftGrid Sequencer 4.x, SoftGrid 4.x servers, and SoftGrid 4.x clients. An active upgrade may work in various mixed environments.|
A Microsoft SQL Server 2000 Desktop Engine upgrade on a SoftGrid version 3.2 server prompts for a restart.If the database is on the same computer as the server, it may prompt you to restart the computer during the upgrade. If you restart the computer, you must restart the whole upgrade.
|Do not restart the computer. When you are prompted, click Cancel, and then continue to run the upgrade.|
The application fails when it starts after you cancel an application import operation.You receive an unexpected error code (00000125) when you try to start an application after you cancel an application import operation by using the SoftGrid Client Management Console.
|Unload the application in the console before you try to restart the application.|
An application server uninstall operation fails because it cannot find the files to uninstall. These files should be located in the %ProgramFiles%\Softricity\SoftGrid Server\Content directory.If the installation points to a shared network location that is not available, the uninstall operation fails with an "1606" error message.
|If the Content directory is a local directory, re-create the directory by using the same name before you uninstall files. If content is in a shared location, make sure that this location is available On the computer on which you have installed the SoftGrid server components.|
Applications that have background processes running may prevent you from uninstalling the SoftGrid Client correctly.A dialog box appears that prompts you to close all the virtual applications before you continue. This behavior occurs even though all virtual applications appear to be closed.
|Manually exit from the SoftGrid Client notification area before you uninstall the SoftGrid Client.|
The SoftGrid Client installer program does not appear to save a new global data folder.During client installation, the display is not updated when you browse for a folder, and then you select it.
|This is a display issue. You can see the change by clicking Back or Next.|
Client user principal name (UPN) logon requires a full domain name.For remote connections, the client logon needs the full UPN name. This name includes the suffix. For example, you must type firstname.lastname@example.org.
|When you log on by using a UPN domain user name, use the full credentials.|
You receive error messages when you import applications that are used by multiple packages.In rare cases, you may receive error messages and reports that the package GUID is already being used when you import an application that is used by more than one package. The SoftGrid Server Management Console may freeze.
|These error messages are a known limitation of this release. However, when you restart the console, the package is successfully imported.|
Virtual File System (VFS) files are corrupted on a FAT32 drive.On a computer that is running SoftGrid Sequencer on a FAT32 drive, the VFS files may become corrupted.
|Use only NTFS file system drives for sequencing. Do not sequence to a FAT32 drive.|
A default application does not appear in a split-server SoftGrid installation.In a SoftGrid installation that uses the Web service and the database on one computer and Virtual Application Server on another, the default application may not appear in the database or at the published shortcut locations.
|This behavior is a known limitation.|
You cannot change the default port during client installation.The default port (554) does not change after you enter a different port during installation.
|After installation, use the SoftGrid Client Management Console to select the SoftGrid server, and then enter the desired port in the server properties.|
You experience a multi-stage upgrade failure.The second update in a multi-stage upgrade to Microsoft Office XP can fail on the second consecutive update.
|Install the application to a folder at least two levels under the SoftGrid Sequencer drive root directory. For example, install the application to the Q:\MyApp\New directory instead of to the Q:\MyApp directory.|
You receive a "SystemGuard" failure message during command-line sequencing.During command line sequencing, you may receive an error message that reports a SystemGuard download failure. The error reports that the installation path parameter is not valid.
|Verify that file names that are provided as parameters are less than 255 characters and that they do not include special characters. For example, the file names must not include a slash mark (/), a backslash (\), a colon (:), a vertical bar (|), a question mark (?), an asterisk (*), or angle brackets (< >).|
The SoftGrid Sequencer produces extra .osd files.SoftGrid Sequencer version 4.x can generate more .osd files than are required for an application.
|Before you copy sequenced files to the Virtual Application Server, verify that the .osd files are related to the application. For example, assume that the SoftGrid Sequencer has created .osd files for Notepad and for Windows Explorer. If you know that these .osd files are not part of the application, delete them before you copy the output.|
The SoftGrid Sequencer .msi file does not automatically start the Sequencer installation in Windows Vista.In Windows Vista, if you run the SoftGrid Sequencer .msi file interactively, it does not start automatically.
|To work around this issue, you have to disable and then re-enable the auto-launch option.|
SoftGrid Server does not start after a SoftGrid 3.1 to 4.x server upgrade.If a port number value is in the SQL Server DATA_SOURCES table, SoftGrid Server may not start.
|Edit the DATA_SOURCES table in SQL Server to remove the port number.|
The SoftGrid Virtual Application Server service fails when you change the server name.The SoftGrid Virtual Application Server service does not start when the server name is changed to use a Domain Name System (DNS) format.
|Do not change the server name format after installation.|
You receive server upgrade error messages.If you modified the SoftGrid server content path during the original installation, you may receive two error messages when the upgrade program tries to replace the DefaultApp.osd file. The upgrade program cannot find that file if it is not in the Drive_Letter:\Program Files\Softricity\SoftGrid Server\Content directory.
|Click OK at each error message. These errors do not affect the upgrade. You can still locate that file in its previous location.|
A silent upgrade of the server may fail in certain scenarios.A silent upgrade of the server may fail when the REINSTALL=ALL and REINSTALLMODE=vomus properties are specified together with the misexec command. This behavior occurs when you are doing a major upgrade. A major upgrade occurs when you upgrade SoftGrid to a new version. For example, you upgrade from SoftGrid 3.x to SoftGrid 4.x. A minor upgrade occurs when you upgrade from from SoftGrid 4.1 to SoftGrid 4.2.
|To avoid this problem, specify the REINSTALL=ALL and REINSTALLMODE=vomus properties only if you are performing a minor upgrade.|
The SoftGrid Client installer does not prevent installation on 64-bit editions of WindowsThe SoftGrid Client installer does not detect that it is being run on a 64-bit system and does not inform you that the platform is not supported.
|SoftGrid currently does not support 64-bit editions of Windows.|
The SoftGrid Server Management Console reports an earlier version after you upgrade the snap-in.After you upgrade the SoftGrid Server Management Console, the earlier version of the snap-in is displayed in the About SoftGrid Console window.
|The SoftGrid Server Management Console is upgraded correctly but the version number is incorrectly cached by MMC 3.0.|
The stand-alone management Web service upgrade failsA SoftGrid management Web service cannot upgrade from version 3.2 to version 4.x. The SoftGrid management Web service cannot locate application packages.
|Upgrade the SoftGrid Virtual Application Server before you try to upgrade a stand-alone Management Web service. Then, the Management Web service can find the correct content path for the application migration.|
A stopped listener may not recover.If you use a command to stop the listener when a virtualized application is running, the listener may freeze.
|Restart the client computer if this behavior occurs.|
Two reports are missing in SoftGrid version 4.2.The "License Compliance" report and the "Use/Group Application Configuration" report do not appear in SoftGrid 4.2.
|This is a known limitation.|
You cannot import upgraded sequences as new applications in the SoftGrid Server Management Console.If you try to import a sequence that has been upgraded by using a package upgrade that did not previously exist in the SoftGrid Server Management Console, you may receive a "0000C81E" error message.
|To work around this issue, remove the trailing version number in the .sft file name. For example, rename MyApp_3.sft to MyApp.sft.|
When you try to upgrade SoftGrid server from version 126.96.36.199 to version 4.x, the SoftGrid Server Management Console cannot be created.
|This issue is resolved if you perform a repair.|
When you upgrade SoftGrid server to MMC 3.0, you receive an error in the SoftGrid Client Management Console.Assume that you have the SoftGrid Client Management Console installed on a computer that is also running the SoftGrid Server Management Console and that you upgrade to MMC 3.0. When you click any of the nodes under SoftGrid in the SoftGrid Client Management Console, you receive an error message.
|If you ignore this error message, the SoftGrid Client Management Console works correctly.|
When you upgrade the SoftGrid server from version 4.x, the server log location resets to the default location.If you previously deleted the default log directory and if you specified a custom log directory, SoftGrid Server does not start. Instead, it returns error code 41539.
|To resolve this issue, reset the log location manually.|
Usage data is lost when the client reconnects to server.Application usage information may be lost when the SoftGrid Client reconnects after it loses its connection to the SoftGrid Virtual Application Server.
|This remains a limitation of the client.|
You cannot delete file type associations when you import an .osd file.On the Import Wizard’s File Associations tab, existing file type associations appear to be deleted correctly. The file type associations may remain in the file type association node of the SoftGrid Server Management Console.
|After you import the file, remove the file type associations by using the SoftGrid Server Management Console File Associations node.|
<configuration><system.web><!-- Time out (in seconds) when servicing request --><httpRuntime executionTimeout="900" /></system.web></configuration>
Article ID: 941408 - Last Review: 02/18/2008 23:37:42 - Revision: 3.0