WebDev.WebServer.exe does not start – Configuration system failed to initialize

WebDev.WebServer.exe does not start – Configuration system failed to initialize

I have Visual Studio 2005 with Service Pack 1 installed and I cannot debug any web service or web application. This worked for a while and then it stopped working. I researched this on a couple of sites and the suggested solutions were


– Debug with F5
– Run with CTRL + F5 
– copy WebDev.WebServer.exe from another machine if not present in .Net Framework folder
– From .Net Framework folder run WebDev.WebServer.exe /PORT:8081 /PATH:”path to web app
– disable or open firewall port


I tried all of these and it still failed with several errors
Configuration system failed to initialize
Unable to launch Visual Studio’s Localhost Web Server.
 ASP.NET Development Server failed to start listening on port 8081.
 Error message:
 Configuration system failed to initialize

In my case, this error was caused by system.net\machineKey element in machine.config. Removing this element fixed the problem. Of course on a production system you don’t want to this but you would not run WebDev.WebServer.exe either so that’s not actually a problem.
I hope this helps other people facing the same problem!

WebDev.WebServer.exe does not start – Configuration system failed to initialize

WebDev.WebServer.exe does not start – Configuration system failed to initialize

I have Visual Studio 2005 with Service Pack 1 installed and I cannot debug any web service or web application. This worked for a while and then it stopped working. I researched this on a couple of sites and the suggested solutions were


– Debug with F5
– Run with CTRL + F5 
– copy WebDev.WebServer.exe from another machine if not present in .Net Framework folder
– From .Net Framework folder run WebDev.WebServer.exe /PORT:8081 /PATH:”path to web app
– disable or open firewall port


I tried all of these and it still failed with several errors
Configuration system failed to initialize
Unable to launch Visual Studio’s Localhost Web Server.
 ASP.NET Development Server failed to start listening on port 8081.
 Error message:
 Configuration system failed to initialize

In my case, this error was caused by system.net\machineKey element in machine.config. Removing this element fixed the problem. Of course on a production system you don’t want to this but you would not run WebDev.WebServer.exe either so that’s not actually a problem.
I hope this helps other people facing the same problem!

Clean up your BizTalk databases

Clean up your BizTalk databases

Here are a few scripts / stored procedures that most of the BizTalk newbies would love to know.

These scripts are very useful in a development environment to clean up your MessageBox and Tracking databases.

To clean up the MessageBox

  • First create the stored procedure bts_CleanupMsgBox by running the sql script found in <BizTalk Installation Folder>\Schema\msgbox_cleanup_logic.sql against your MessageBox database(BizTalkMsgBoxDb).
    • Note that your BizTalkMsgBoxDb database will already have a dummy stored procedure by the same name which does nothing, so it is important that you run the above script if this is your first time.
  • Stop all BizTalk services.
  • Reset IIS server (run iisreset from start/run) if you are running any webservices
  • Execute stored procedure bts_CleanupMsgbox on your message box database
  • Execute stored procedure bts_PurgeSubscriptions on your message box database
  • Restart all BizTalk services

To clean up the Tracking data

  • Stop all BizTalk services.
  • Execute stored procedure dtasp_CleanHMData on your tracking database (BizTalkDTADb)
  • Restart all BizTalk services

Regards

Benny Mathew
Seamless Integration Solutions
BizTalk Consulting, Development, Training
Bangalore, India

 

Website: http://www.seamless.in/
Blog: http://GeeksWithBlogs.net/benny
BizTalk Usergroup: http://groups.google.co.in/group/b-bug

Announcing the OBA Reference Application Pack for Loan Origination Systems (OR-LOS)

Announcing the OBA Reference Application Pack for Loan Origination Systems (OR-LOS)

The Architecture Strategy Team has just released an Office Business Applications Reference Application Pack for Loan Origination Systems (OR-LOS) that leverages SharePoint, BizTalk Orchestrations, BizTalk Business Rules Engine, WF Workflows, and Office Clients to automate a Loan Origination process spanning multiple human and system participants. Mike Walker has posted all the details including whitepapers, an introductory video, and the sample bits (including a new MISMO accelerator) on his blog. Attached is a pic from one of the whitepapers that shows the high level view of the process.


 Also, Mike and the Financial Services team have some more great content on building OBAs on top of an ESB here. Be sure to check out this paper. It has tons of BizTalk (even though it’s not in the title ;).


-Kris

Drum roll….BizTalk 2006 R2 Beta 2 – public release

Drum roll….BizTalk 2006 R2 Beta 2 – public release

Any day now…..it’ll be making it’s way to the download area and then refreshed by
the web front end servers and then…..viola!!! It will appear as a download.

Some great improvements around EDI (6000+ schemas out of the box)
– WCF + WCF adapters.
– there’s a new LOB Adapter SDK that allows us to develop Adapters WITHOUT the need
for BizTalk. So your one adapter has legs in many different apps.
– lots more…..

Stay tuned……there’s some great WCF channel examples being called by BizTalk in
the pipelines.

Should see it under http://www.microsoft.com/technet/prodtechnol/biztalk/2006/default.mspx I
guess sometime in the *very* near future.

We’re supporting some clients through the R2 TAP program which is always an adventure
🙂

Whitepaper on Migrating from CMS 2002 to MOSS 2007

Whitepaper on Migrating from CMS 2002 to MOSS 2007

Sezai has written a whitepaper detailing the process involved in migrating a Microsoft Content Management Server 2002 Website to a Microsoft Office SharePoint Server 2007 Publishing Internet Site.  Have a look at it here:


http://sharepointblogs.com/sezai/archive/2007/03/27/white-paper-released-migrating-a-microsoft-content-management-server-mcms-2002-website-to-microsoft-office-sharepoint-server-2007-moss-2007.aspx