Archive for the 'Windows' Category

XP SP3, Remote Desktop and Console Session

The other day I was trying to help a client connect to the Console Session on a Windows 2003 Server from their XP computer.  For some reason connecting via mstsc.exe /console they were not getting connected to the console.  What was odd was that from my XP laptop I had no problems.  I was ready to pull out my hair when I found an article on the Terminal Services Blog.  If you are using a remote desktop connection from a Window XP SP3 machine the /console is silently ignored.  Now you need to supply a /admin instead of /console.

Amazon EC2 Running Windows Server: Coming Soon

Amazon has announced that later this fall that they will offer the ability to run Windows Server and SQL Server in the EC2 environment.

Crystal Reports 10 Runtime and Citrix

Earlier this week I installed the Crystal Reports 10 run time on a client’s Citrix server.  After installing I tried to run our application and the run time kept on giving me an error saying “Load report failed”.  Doing some research we found that the Crystal run time when installed assumes there is going to be a C drive.  In this case we didn’t have one.  The main system partition was W.  The below knowledge base article describes what needs to be done to get the run time to work on a server that doesn’t have a C drive.

Symptom

A Microsoft Visual Studio .NET application uses Crystal Reports 10 for Visual Studio .NET SDK as the reporting development tool.

When the application is deployed to a computer that does not have a C drive, the following error message appears:

“Load Report Failed”

Why does this error message appear and how can it be resolved?

Background Information

———————-

It is common to not have a C drive on Terminal servers and Citrix servers.
Resolution

This error message appears because the application sets registry values that point to the C drive. To resolve the error message, use the following steps to change these registry values in the Registry Editor.

====================

WARNING:

The following resolution involves editing the registry. Using the Registry Editor incorrectly can cause serious problems that may require you to reinstall the Microsoft Windows operating system. Use the Registry Editor at your own risk.

HELP:

For information on how to edit the registry key, view the ‘Changing Keys And Values’ online Help topic in the Registry Editor (Regedit.exe).

RECOMMENDATION:

It is strongly recommended that you make a backup copy of the registry files (System.dat and User.dat on Win9x computers) before you edit the registry.

====================

1. On the ‘Start’ menu, click ‘Run’.

2. In the ‘Run’ dialog box, type “Regedit” then click ‘OK’.

3. In the Registry Editor browse to the following subkey:

HKEY_LOCAL_MACHINE\SOFTWARE\Crystal Decisions\10.0\Report Application Server\InprocServer\LocalConnectionMgr

4. Right-click the ‘ConnectionDirectoryPath’ string value, then click ‘Modify’.

5. In the ‘Value data’ text box, change “c:\” to the drive letter where the following directory exists (You may need to search your computer to find where this directory exists):

\Program Files\Common Files\Crystal Decisions\2.5\bin

Click ‘OK’.

6. Right-click the ‘LocalConnectionMgr’ subkey, click ‘New’ then click ‘String Value’.

7. Name this String Value “ReportDirectoryPath”.

8. Right-click the ‘ReportDirectoryPath’ string value and click ‘Modify’.

9 In the ‘Value data’ text box, type the same drive letter as you typed in step 5.

====================

NOTE:

After making changes to the registry, restart the affected service or application as required.

====================

Now, when the application is run, the error message will not appear.