I am hoping to get some assistance in determining why a vb.net web site I have written on my workstation will not work on an IIS 7.5 server. Background: I have Visual Web Developer 2010 Express installed on my system (Windows 7 Professional 64 bit). I also have the client for our accounting package (Sage Timberline \ CRE 300) installed. The installation of the Sage client also includes the installation of a Pervasive Workgroup Engine component in 32 bit. My understanding from searching for support on this is that Sage has modified \ cutsomized the driver for the Pervasive engine for its use with the Sage client software. The Sage client includes an ODBC connection driver, that we have licenses for. Through this driver you can connect to the Timberline database through other applications (Excel, for example).
I am attempting to complete a web based application that will allow me to briefly connect to one of the Timberline tables to read the existing data from that table, and then copy two fields from that table to a local Access database, and then use the Access database for further querying and processing. Please understand, I am not a developer by trade, and therefore may not be using what most would consider to be correct terminology and methods, apologies in advance.
I have been able to successfully complete the application on my workstation, and it is working exactly how I would like. The problem is when I attempt to migrate it to a dedicated web server. The server in question is Windows 2008 Standard 64 bit, with IIS 7.5 installed. I have installed the Timberline client on the server, including the 32 bit Pervasive Workgroup engine, and have verified that the ODBC driver works when run locally on the server (ie: I created a DSN on the server to one of the test companies in the Timberline data folder and was able to successfully make a connection to the proper tables and fields using that DSN). After creating the web site on the server, I also went into the Application Pool settings for that web site and set Enable 32-bit Applications to True. I have tried setting Managed Pipeline Mode to both Integrated and Classic, but neither of those seem to make any difference.
What is happening is when I attempt to make the ODBC connection from the web site, the connection fails, and often when I go back into the IIS management console, the Application Pool for the web site is stopped. I have tried to turn on ODBC tracing to see if that yields any informaiton, but nothing is logged. At face value, this may be a permissions \ security problem, but I have not been able to make any headway.
Can anyone give me an idea of what the difference would be between the development environment on my system and the IIS 7.5 environment on the server with regard to running odbc connections?
Thanks very much,