The SQL Server Compact Edition (SSCE) Server Tools1 use a 32-bit ISAPI Extension DLL which cannot run directly in a IIS 64-bit worker process.
What can make this problem difficult to debug is the rather poor error message that gets returned : %1 is not a valid Win32 application.
For those running the 64-bit version of Windows Server 2003, Windows Server 2003 Service Pack 1 provides a solution through the addition of the W3SVC/AppPools/Enable32bitAppOnWin64 IIS metabase property. Setting this metabase property to a non-zero value causes IIS to start a 32-bit worker process which is then able to successfully host SSCE Server Tools.
For more information checkout this knowledge base article: Windows Server 2003 SP1 enables WOW64 compatibility for 32-bit Web applications in IIS 6.0.
Unfortunately, this solution can cause the ASP.NET 2.0 applications running on the server to fail - the problem that occurs is the same issue one encounters when attempting to run ASP.NET 1.1 (requires 32-bit) and ASP.NET 2.0 simultaneously on a 64-bit server - ASP.NET 2.0 expects a 64-bit worker process and IIS 6.0 cannot run both 32-bit & 64-bit worker processes simultaneously.
To resolve this problem, you'll need to configure ASP.NET 2.0 to use a 32-bit worker process. For details on how to configure ASP.NET 2.0 to use a 32-bit worker process, see this knowledge base article: How to switch between the 32-bit versions of ASP.NET 1.1 and the 64-bit version of ASP.NET 2.0 on a 64-bit version of Windows.
Credit for getting these issues worked out goes to Alberto Silva. If you're fortunate enough to read Portuguese, you can read his post on the topic here.
1This same problem exists for earlier Server Tools as well including SQL Server CE Server Tools & SQL Server Mobile Edition Server Tools.
Posted
Jul 06 2007, 08:56 AM
by
jim-wilson