We have 2 new biztalk application servers (bts2013 r2) and are deploying our first application from dev to integration.

We have one service (schema deployed as a webservice) that is published in the IIS.Import of the msi works with no errors.

But if we try to browse to the service in iis, we get an error 'Server Application Unavailable'  and in the iislog we see code 500.

By looking back in the application log the only odd thing we see is that te first time we deployed our application we see a warning that says '

The following Web Site that was packed from a 32 Bit IIS machine is being installed on to a 64 Bit IIS machine. The web site may not function as expected.

If we browse to our the service in development from our integration-machine that works...

Hi

There are several check which need here

- Are both Dev and Integration servers running on same windows server editions and .NET frameworks?

- MSI package deployed will create DLLs in 32 and 64 bit (https://msdn.microsoft.com/en-us/library/aa560166.aspx) but with IIS setting is the app pool also set with same version as the DLLs are built (V4.0 or higher)

Regards

K

Hi Isabelledc,

This can almost be absolutely anything. From not having installed the (correct) .NET framework, having selected the wrong application pool in IIS, an invalid web.config file, whatsoever.

One thing you can try: check the Windows Eventlog. There might be a more detailed error message in there, under the Application section.

For fix try to create a new App Pool user (accepting all of the defaults), and use this new pool user instead of the default one.

Check the settings of the application deployed and compare with Development environment like if 32-bit appplication is enabled, which .Net framework version it is using. You should be able to run the web site from the IIS atleast and it has nothing to do with BizTalk.

Rahul

Hi

There are several check which need here

- Are both Dev and Integration servers running on same windows server editions and .NET frameworks?

- MSI package deployed will create DLLs in 32 and 64 bit (https://msdn.microsoft.com/en-us/library/aa560166.aspx) but with IIS setting is the app pool also set with same version as the DLLs are built (V4.0 or higher)

Regards

K

• Marked as answer by isabelledc 19 hours 18 minutes ago

Hi

There are several check which need here

- Are both Dev and Integration servers running on same windows server editions and .NET frameworks?

- MSI package deployed will create DLLs in 32 and 64 bit (https://msdn.microsoft.com/en-us/library/aa560166.aspx) but with IIS setting is the app pool also set with same version as the DLLs are built (V4.0 or higher)

Regards

K

• Marked as answer by isabelledc Wednesday, September 09, 2015 11:44 AM

Well it finally resolved by removing the whole application  and reinstalling it.

I guess it was caused by the fact that when we were importing the app-pool didn't have the correct settings yet.Thank you for your help