Active upgrade fails with a combination of 3.x clients and 4.x serversEven after the restart of a domain controller, an active upgrade may fail for 3.x clients and 4.x servers
|Active upgrade works with SoftGrid Sequencer 4.x, 4.x server and 4.x clients. An active upgrade may work in various mixed environments.|
An MSDE upgrade on a SoftGrid version 3.2 server prompts for a restartIf the database is on the same computer as the server, it may prompt for a restart during an MSDE upgrade. If you restart, you must restart the whole upgrade.
|Do not restart. When you are prompted, click Cancel, and then continue with the upgrade.|
Application fails when it starts after you cancel an application importYou receive unexpected error code 00000125 when you try to start an application after you cancel an application import through the SoftGrid Client Management Console Snap-in.
|Unload the application in the SoftGrid Client Management Console Snap-in before you try to restart the application.|
Application server uninstall fails with unavailable content directoryIf the content directory points to a shared network location that is not available, the uninstall fails with error message 1606.
|If the content directory is a local directory, re-create the directory with the same name before you uninstall. If content is in a shared location, make sure that this location is available to the server before you uninstall.|
Applications that have background processes may prevent the SoftGrid client from uninstalling correctlyA dialog box appears that prompts you to close all the virtual applications before you continue, even though all virtual applications appear to be closed.
|Manually exit from the SoftGrid client notification area before you uninstall the SoftGrid client.|
Client installer does not appear to save new global data folderDuring client installation, the display is not updated when you browse for and select a folder.
|This is a display issue. You can see the change by using either the Back button or the Next button.|
Client UPN logon requires full domain nameFor remote connections, the client logon needs the full UPN name. This includes the suffix. For example, firstname.lastname@example.org.
|When you log on with a UPN domain user, use the full credentials.|
Conflict about how to import applications used by multiple packagesIn rare cases, when you import an application that is used by more than one package, you may receive error messages and reports that the package GUID is already being used. The Management Console Snap-in may freeze.
|These error messages are a known limitation of this release. However, when you restart the Management Console Snap-in, the package is successfully imported.|
Corrupted VFS files on FAT32 driveOn a computer that is running SoftGrid Sequencer using a FAT32 drive, the VFS files can become corrupted.
|Use only NTFS drives for sequencing. Do not sequence to a FAT32 drive.|
Default application does not appear in a split-server SoftGrid installationIn a SoftGrid installation that uses the Web service and database on one computer and the Virtual Application Server on another, the default application may not appear in the database or on the published shortcut locations.
|This is a known limitation.|
You cannot change the default port during client installThe default port 554 remains after you enter a different port during installation.
|After installation, use the Client Management Console Snap-in to select the SoftGrid server and enter the desired port in the server properties.|
Multi-Stage upgrade failureThe second update on 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 Q:\MyApp\New instead of Q:\MyApp.|
Sequencer command line: SystemGuard failure messageDuring 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 provided as parameters are less than 255 characters and that they do not include special characters such as /\ : | ? * s< or >.|
Sequencer may produce extra .osd filesSoftGrid Sequencer version 4.x can generate more .osd files than necessary for an application.
|Before you copy sequenced files to the Virtual Application Server, verify that the .osd files relate to the application. For example, if SoftGrid Sequencer created .osd files for Notepad and Explorer, and you know that these are not part of the application, delete these .osd files before you copy the SoftGrid Sequencer output.|
Server does not start after 3.1 to 4.x server upgradeIf a port number value is in the SQL server DATA_SOURCES table, the SoftGrid server may not start.
|Edit the SQL Server’s DATA_SOURCES table to remove the port number.|
Server Service: Fail on Name ChangeThe SoftGrid Virtual Application Server service does not start when the server name is changed to DNS format.
|Leave the server name in the same format as it is in after installation.|
Server Upgrade Error MessagesIf you modified your SoftGrid server content path during the original install, you may receive two error messages when the upgrade tries to replace DefaultApp.osd. It cannot find that file if it is not in Drive_Letter:\Program Files\Softricity\SoftGrid Server\content.
|Click OK at each error message. This error does not affect the upgrade. You can still locate that file in its previous location.|
Silent upgrade of the server may fail under certain scenariosSilent upgrade of the server may fail when the REINSTALL=ALL and REINSTALLMODE=vomus properties are specified on the misexec command line and you are doing a major upgrade.
|If you run the setup.exe program for the SoftGrid server installer, you will avoid this situation if you determine whether you are doing a major or minor upgrade.Specify the REINSTALL=ALL and REINSTALLMODE=vomus properties on the misexec command line only if you are doing an upgrade from SoftGrid version 4.1.|
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 provide a dialog to the user that explains that the platform is not supported.
|SoftGrid currently does not support 64-bit editions of Windows.|
SoftGrid Server Management Console Snap-in reports an earlier version after you upgradeAfter you upgrade the SoftGrid Server Management Console Snap-in, the earlier version of SoftGrid Server Management Console Snap-in is displayed in the About SoftGrid Console window.
|The SoftGrid Server Management Console Snap-in was upgraded correctly but the version number is incorrectly cached by MMC 3.0.|
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 application migration.|
Stopped listener may not recoverUsing the command line to stop the listener when a virtualized application is running can freeze the listener.
|The listener freezes if shutdown by a command line happens when the end-user has virtualized applications that are running. Restart the client computer if this happens.|
Two reports are missing in version 4.1 SP1The license compliance and Use/Group Application Configuration reports do not appear in version 4.1 SP1.
|This is a known limitation.|
Unable to import upgraded sequencings as new applications in the Server Management Console Snap-inIf you try to import a sequencing that has been upgraded through a package upgrade that did not previously exist on the SoftGrid Server Management Console Snap-in, you may receive error code 0000C81E.
|To work around this issue, remove the trailing version number in the .sft file name, for example, rename MyApp_3.sft to MyApp.sft.|
Upgrading SoftGrid server from 126.96.36.199 to 4.x cannot create snap-inIf you try to upgrade the SoftGrid server from 188.8.131.52 to 4.x, it cannot create the SoftGrid Server Management Console Snap-in.
|This issue is resolved if you perform a repair.|
Upgrading SoftGrid server to MMC 3.0 produces error in SoftGrid client Management Console Snap-inIf you have the SoftGrid Client Management Console Snap-in installed on a computer where the SoftGrid Server Management Console Snap-in is also installed and you upgrade to MMC 3.0, when you click any of the nodes under SoftGrid in the SoftGrid Client Management Console Snap-in, you receive an error message.
|If you ignore this error message, the SoftGrid Client Management Console Snap-in works correctly.|
Upgrading the SoftGrid server from version 4.x resets the server log location back to the default locationIf you previously deleted the default log directory and specified a custom log directory, the SoftGrid server does not start with error 41539.
|To resolve this issue, reset the log location manually.|
Usage data lost with server connectionApplication usage information can be discarded when the SoftGrid client reconnects after it loses the 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 fileOn 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 Management Console Snap-in.
|After you import the file, remove the file type associations through the Management Console Snap-in File Associations node.|
<configuration><system.web><!-- Time out (in seconds) when servicing request --><httpRuntime executionTimeout="900" /></system.web></configuration>
Article ID: 938497 - Last Review: 02/19/2008 20:57:28 - Revision: 5.0