Hi folks, I created my first asp website linking to a MSSQL2005 database and all is working great on my local machine. I now want to publish the website and get it up and running on the company server. Here is what i have done so far! I copied the database to the company sever Then, I published the website and copied the files to our company server Through IIS, i created a new website and pointed it to the published files etc. I also changed the Connection string computer name to reflect the company server name I also changed the ASP Version to 2 through IIS The company server also hosts the Sharepoint Website so i Chose Port 81 for my website I also created a new application pool for this. When i try to run the website http://Server01:81/clients/clients.aspx - Nothing appears? Any Idea Folks? Thanks

Have you allowed ASP.NET scripts in IIS? 

which IIS vision u use... 

u need enable the asp/asp.net in IIS,and install framework on computer which u want run the website~~~

sullyman:

The company server also hosts the Sharepoint Website so i Chose Port 81 for my website I also created a new application pool for this. When i try to run the website http://Server01:81/clients/clients.aspx - Nothing appears?

 

Hi sullyman,

From your description, I understand that you have published your web project to the SharePoint Website. However, the deployed aspx page returns a blank page (my understanding of your “Nothing appears”). If I have misunderstood your concern, please let me know.

I know you have done many troubleshooting steps. The only thing I should mention is you put the web application in the SharePoint website which uses its own providers and settings. The virtual directory of your web application inherits these settings probably causes the unexpected behavior.

To solve this issue, please compare the web.config files between your virtual directory and the SharePoint website, and then remove/add the different settings in your web applicaiton's web.config file. For more detailed information, please check my reply in the following thread which has the similar issue.

web.config default provider
http://forums.asp.net/t/1156834.aspx