Delete of ApplicationNode Failed

 BizTalk deploys and undeploys have, in recent times, become much easier than they were back in the “bad old days.”  Especially with tools like the Deployment Framework to help us out, we can usually get through the process with only a little discomfort.

Once in a while, though, you run into something that makes things more difficult than they ought to be.  During a recent application removal on one of our development servers, this lovely message appeared as I attempted to remove the application from BizTalk:

Most of the help out there for the “Delete of  ApplicationNode Failed” message relates to competing resources, etc.  Since, those are pretty well documented, I won’t go into it here.  Here our solution is much simpler than those dealing with other flavors of the exception. 

For whatever reason… someway, somehow… the event log became corrupted and our message is pretty clear on that.

As expected there are a lot of ways to get around this, but FIRST, BEFORE YOU DO ANYTHING ELSE, just try a simple clearing of the Windows Application Log.  In our case, this is what fixed the problem.

About Ed Jones

Ed is a .NET and Integration architect for Avanade in the Twin Cities. Contact Ed

What do you think?

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: