Monish Nagisetty's Space

Building connectivity on-premise, in the cloud and beyond

VMWare Server – Missing ASP.NET tab in IIS

I recently ran into this issue after I installed VMWare server on my Windows Server 2003 (32-bit) w/SP2 OS. I lost the ASP.NET tab in IIS immediately after I installed VMWare Server 1.0.2 build-39867.

Here are the steps to fix the issue:

1) Stop the IIS Admin service (and any services that depend on it)
2) Open C:\WINDOWS\system32\inetsrv\MetaBase.xml in notepad or your favorite XML Editor. _DELETE_ the line that reads ‘Enable32BitAppOnWin64=”TRUE”’
3) Start -> Run -> iisreset

Your tab should now be back and functional.

Did I mention that VMWare Server is free? Go get it now: http://www.vmware.com/products/server/

June 19, 2007 Posted by | Uncategorized | | 1 Comment

EDI Receiver stopped listening to port: 11011

Has anyone seen this error before? It is showing up in both QA and production BizTalk environments where BizTalk 2006 is installed and configured.  The solution utilizes the BizTalk Base EDI Adapter.

Event Type: Error
Event Source: EDI Receiver
Event Category: BizTalk Server 2006
Event ID: 28
Date:  6/18/2007
Time:  5:57:28 PM
User:  N/A
Computer: <COMPUTERNAME>
Description:
EDI Receiver stopped listening to port: 11011.

Only one usage of each socket address (protocol/network address/port) is normally permitted

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

June 19, 2007 Posted by | Uncategorized | | Leave a comment

Issues when reusing Virtual Server or VMWare baseline images

Read the event log entry below and you will know what types of issues you can run into if you do not use supported cloning tools such as sysprep or newsid.  I got this error in a scenario where a standalone (non-domain member) BizTalk server was using the SQL adapter to push data to another standalone (non-domain member) SQL Server machine.

Event Type: Error
Event Source: MSDTC
Event Category: CM
Event ID: 4101
Date:  6/1/2007
Time:  10:47:59 AM
User:  N/A
Computer: <COMPUTER NAME>
Description:
The local MS DTC detected that the MS DTC on <COMPUTER NAME> has the same unique identity as the local MS DTC. This means that the two MS DTC will not be able to communicate with each other. This problem typically occurs if one of the systems were cloned using unsupported cloning tools. MS DTC requires that the systems be cloned using supported cloning tools such as SYSPREP. Running 'msdtc -uninstall' and then 'msdtc -install' from the command prompt will fix the problem. Note: Running 'msdtc -uninstall' will result in the system losing all MS DTC configuration information.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

June 1, 2007 Posted by | Uncategorized | , | Leave a comment