Pages

Monday, August 20, 2007

Be surprised

Yup. That is all about when you get involved in my job line. I get surprised by all kind of system malfunction caused by different kind of situation like virus, network, people, hardware / software compatibility and the list never stop. Even a brand new system installation couldn't escape from this mess. This is happening on my latest assignment but eventually all we had to do is compromised a little. Anyway here are some of my dreadful experience of installing our archiving system on Windows 2003 R2 64 bit Server.

  1. I can't connect to the server via terminal service from my Windows XP. Looking at the event viewer, I noticed this error. "The RDP Protocol Component "DATA ENCRYPTION" Detected an Error..." error message - event ID 50.
    Read this work around (KB323497). Something to do with registry. Problem solved.

  2. My MSSQL 2005 Enterprise edition can't be connected remotely. So my OSQL script won't work (damn).
    Microsoft suggest to do a few things (KB914277) but the connection not stable. Strike one,two & three. I won't install this system on 64bit machine ever again.
Later on I found out the Windows 2003 R2 were meant for storing data not suitable for running application like MSSQL... bummer.
Some other error that I encountered from normal Windows 2003 Server 32bit:

  1. IISSample.RegistryAccess causing ASP pages failed to load.
    Solution: Simply register the reg.dll

  2. It is not possible to run two different versions of ASP.NET in the same IIS process. Please use the IIS Administration Tool to reconfigure your server to run the application in a separate process.
    In other word, you cannot run more than one version of the .NET framework in the same application pool in IIS6.
    Solution: Simply create a new application pool and move the site that you will be upgrading to that pool. You can even base it off of the existing one if you don't have the password memorized for the existing one. This is all done within IIS. Once you have placed the site or virtual directory in its own application pool, then you are ready to upgrade to the new framework version.
Maybe this is nothing much to brag about but hey life is always full of surprises.