Our company runs a variety of applications based on the ASP.NET 2.0 Framework. Our standard environment is to run these apps on Windows Server 2003 machines with IIS 6.0, but I'm a bit more bleeding edge and chose to install Vista, and thus IIS 7.0, the last time I rebuilt my machine. I have encountered a few issues here and there, but perhaps the most frustrating was the HTTP 500 Internal Server Error I would get every time I hit the site on my Vista machine.
It turns out that my problem was in the Managed Pipeline Mode. We are using a variety of Handlers and Listeners to support logging and error tracing and they were not working in Integrated mode. Switching to Classic fixed it right up, though.
Sweet! Now on to the next challenge.
Monday, August 27, 2007
Friday, August 17, 2007
How to Set Network Access for DTC in Windows Vista
Finally, a developer related post by the Cranky Developer. I am using Transaction Scope in ADO.NET 2.0 to maintain cross database transactions. It's a great technology, but as anyone who has used it knows it takes some fiddling with the configuration of the participating machines in order to work correctly. In my case I was getting the "Network access for Distributed Transaction Manager (MSDTC) has been disabled. Please enable DTC for network access in the security configuration for MSDTC using the Component Services Administrative tool." error.
No sweat, the solution is pretty simple--in versions of Windows previous to Vista you would just go to Administrative Tools and open Component Services and change the settings in the MSDTC tab of the properties of My Computer. It's changed significantly in Vista, however. For starters, the Component Services console isn't linked from the Administrative Tools any more. To start it you have to open %windir%\System32\compexp.msc.
The difference is that the properties you're looking for are no long on My Computer, but "Local DTC". To get to it go to Component Services\Computers\My Computer\Distributed Transaction Coordinator\Local DTC and use the Security Tab.
Check Network DTC Access, Allow Remote Clients, Allow Inbound and Allow Outbound and you're set.
No sweat, the solution is pretty simple--in versions of Windows previous to Vista you would just go to Administrative Tools and open Component Services and change the settings in the MSDTC tab of the properties of My Computer. It's changed significantly in Vista, however. For starters, the Component Services console isn't linked from the Administrative Tools any more. To start it you have to open %windir%\System32\compexp.msc.
The difference is that the properties you're looking for are no long on My Computer, but "Local DTC". To get to it go to Component Services\Computers\My Computer\Distributed Transaction Coordinator\Local DTC and use the Security Tab.
Check Network DTC Access, Allow Remote Clients, Allow Inbound and Allow Outbound and you're set.
Subscribe to:
Posts (Atom)