Last post Aug 28, 2017 01:21 PM by navneetmitawa
Aug 28, 2017 06:45 AM|Manoj_|LINK
I had developed a mvc web application in VS 2017 community. I had deployed the same creating a virtual directory, creating a folder in inetpub/wwwroot/MyApp. Then in IIS, right clicked on the MyApp folder and converted to application, set the application
pool to .net 4.0 and application was working fine in IIS, localhost.
have set, <customErrors="Off"> and <modules runAllManagedModules="true">
For the same application when I published in release mode, adding the required .dlls in bin(set - copy to local true) from VS 2017 to folder, then uploading the published folder using filezilla to domain
www.mydomain.biz/mydom, I was unable to access the app in that domain, getting
- Do I need to add the references of the dll in web.config separately ?
- Do I need to add any file to server ( www.mydomain.biz/mydom) to run the application dll
- Is there any steps I missed when publishing or need to add anything in web.config for deployment.
Please correct me I might be wrong somewhere. Thanks in Advance.
Aug 28, 2017 10:40 AM|Kelmen|LINK
500 doesn't tell much
u need to look at the additional info to pinpoint the cause, there should be another error code/number, or just dig through the event log
then ask mr goggle
Aug 28, 2017 12:25 PM|Manoj_|LINK
Searched google but did not got any answers. Its says the use of IIS.
Is it possible to deploy MVC 5 web application, using release configuration, publish to file system and upload that published folder to domain
www.mydomain.biz/domain root through filezilla to ftp server?
- required that added dll (copy local to true) is added.
- How can we run or upload a web deploy package directly to remote? Without the use of windows server and web management service.
Aug 28, 2017 01:21 PM|navneetmitawa|LINK
500 - Internal server error.
Many possible cases for this...
First, you need to enable and see detailed errors of your web messages, because this is a general message without giving information on what's really happening for security reasons.
With the detailed error, you can locate the real issue here.
Also, if you can run the browser on the server, you get details on the error, because the server recognizes that you are local and shows it to you. Or if you can read the log of the server using the Event Viewer, you also
see the details of your error.
<httpErrors errorMode="Detailed" />
Note: You can avoid the Debug=true. You only need to close the custom errors for a while and get the detailed error page.