Just uploaded my ASP 3.5 application and 'installed' application on the folder using the Web Application tool. All the files are there when I look via FTP but cannot seem to launch the login.aspx page (Getting file cannot be found error) Am I missing a step? Regards, Jim
We are using .vb code behind files if that's what you're referring to. Do we need to compile to .dll? We used the VS 2008 Copy Website function as outlined in the Knowledge base article. The site is: http://ccomsolutio.web155.discountasp.net/PresentationMGR/login.aspx
We've reloaded all files and double checked and all the files are there. I've uploaded a simple html page and that seems to be working but when we attempt to access our login page: http://ccomsolutio.web155.discountasp.net/presentationmgr/login.aspx we're getting redirected as follows: http://ccomsolutio.web155.discountasp.net/presentationmgr/GenericErrorPage.htm?aspxerrorpath=/presentationmgr/login.aspx Are there any logs we can look at to determine why IIS is not able to serve up the application login page? Regards, James
Not at all. It's a fairly basic ASP.net application. With a few pages. One thing which might be little different than regular sites is that we're creating an application log file in a sibling folder to the application file. Not sure if this exceeds permissions for the ASP.net application process. Regards,
Don't think the error had anything to do with permissions.It seems that the page is working fine now.Were you able to trace the cause? Vikram DiscountASP.NET www.DiscountASP.NET
Yes that is what I was referring to, they are often missed in file uploads. With the Copy Web site feature select and synchronize your /bin/ folder. You can also right click on the left area and have the tool sync your entire site. http://asp.net/learn/videos/video-281.aspx Salute, Mark
Yes we were able to find the problem thanks. We were missing some of the .dlls which are normally found in the GAC. We usually use .msi deploymentswhere if the .dlls are missing from the GAC they're automatically installed to the BIN, but since we weren't deploying in the usual mannor we missed this. Thanks for all your help. James