In my server I have SSRS already running.
http://localserver/ReportServer/
Is it possible to setup a virtual directory browsing using IIS running concurrently ?
http://localserver/IISFolder/
Tried login to my IIS and all the services are running. Try to browse website using port 80 but failed. Is SSRS conflicting with the existing IIS settings ?
Thanks.
Related
Hosted a .NET 6 basic Web App in IIS Web Server inside the Azure Virtual Machine (Windows 2016 Data Center)
Commands:
dotnet new webapp
dotnet run
dotnet publish -c Release
3rd command is used for placing release folder files in the Site Physical Path created in IIS Web Server:
It shown the result as welcome page. After VM Stop and Start action, it is showing the localhost as "The Site can't be reached"
If I create new site on Connections of the IIS Manager, then it is working.
Every time after restarting the VM, Creating New Site is not the solution.
Why previously created Site is showing me "The Site can't be reached" error.
What I have tried:
Tested by creating new Site in Connections of the IIS Manager, it worked for the new site but after restarting the VM, it also stopped working and showing above mentioned error.
Checked VM Status, it is Healthy
All required tools are installed in the VM (VS Code, .NET 6 SDK, Runtime, and Hosting Bundle)
Note: It is working successfully after I clear the cache in the browser after server restart (stop and start) but why I have to clear the browser cache every time after VM stop and start?
Update:
Forgot to mention this:
I have given HTTPS binding to the IIS Manager Website Hosted so if do localhost with port 80, it will shows IIS Web Served Home Page and localhost with Https (443), it will show the hosted website content.
After Server Stop and Start, localhost with port 80 gives the IIS Web Served Home Page and localhost with Https is not giving the website content, here it is giving error "The site is not reached".
Fix:
I have found the fix to this issue which is:
Hosting works with particular time period.
Every time when you launch the Website hosted in VM through IIS Web Server after Server restart (several hours), you need to re-host or create new site in IIS Manager Pool.
I tried to reproduce the same in my environment and I got the results like below:
I have created sample website and when I tried Stop and Start action, localhost reached successfully:
As suggested by samwu you can check event viewer like below:
In start -> select event viewer -> click Windows Logs node
Select application Event Log and Search for errors associated with the failing app like below
You can make use of Debug Diagnostics tool.
I am using SharePoint 2019 on premise and hosting our .net application into it.
I created a site in share point using port 80 and i can deploy my application into it with no problem.
while creating multiple site to host the same application system is not allowing to host application other than 80
Error:-
error occurred in deployment step recycle IIS application pool the local sharepoint server is not available.Check the server is running and connected to the sahre point farm
Please try to do some troubleshooting:
Clear the visual studio's cache.
Open VS as Administrator.
IIS reset executed before every deploy.
Use the account has full control and is the primary site collection administrator.
Restart the server.
Similar issue for reference: Getting Error occurred in deployment step 'Recycle IIS Application Pool': A task was canceled when deploying custom action to Sharepoint
I am trying to host a Node.JS app on a server that also has IIS running on it. I can open the site in the server browser. As you can see i have the website iisnode running in the browser and it is added in the IIS manager
However, i can not access this site from a different computer using ServerURL/siteName. I just get this error:
What could i be doing wrong? It works locally so i must be close to having it working. I can access other sites hosted on this server so i know the issue is with this app specifically.
We are facing issue while configuring IIS setup for weblogic servers.
Following are the environment details:
IIS8.5 on windows 2012 R2 standard 64x, wls_plugin_12.2.1.2.0 for weblogic server.
We have done the following steps:
Created a new web site on IIS.
Enabling the authentication settings.
Enabling the Directory browsing.
Added the script mapping in Handler mapping and set the path of iisproxy.dll as executor.
ISAPI filter setting for the iisproxy.dll
We are able to view the directory structure while accessing the IP and Port, but the request is not redirecting to the weblogic ip and port what we have configured in iisproxy.ini.
Is there any web.config or handler settings required to process the request?
The issue is that we are using wls-Plugin12.2.1.2.0 whose iisproxy.dll is not working in IIS8.5 on windows 2012 R2 server. After using the lower version of the plugin, able to access the web logic instance through proxy the IIS.
After that we are able to view the login page of web logic instance but not able to login to the application as it through s "404 Not found error". For this we have to change the handler mapping settings --> Request restrictions --> Mapping --> uncheck the invoke handle, restart the iis application and try browsing again. You will be able to login to web logic applications.
I've just installed Microsoft SQL Server Express 2008 (with Reporting Services).
My installation is side by side with SQL Server 2005.
So far creating reports and testing them in the development environment has worked fine, however I can't get the web server or report manager working.
In the Reporting Services Configuration Manager, it appears that they have been configured and have a working address (eg: http://mymachine:8080/ReportServer_EXPRESS2008/ and http://mymachine:8080/Reports_EXPRESS2008/).
The Virtual Directories don't exist in IIS, and clicking on the links in the config manager results in a "The page cannot be found".
If I create the Virtual Directories in IIS, and then use Reporting Services Configuration Manager to modify the two sites, Reporting Services Configuration Manager appears to be working correctly (all the right messages appear, indicating that it created the new site and dropped the old site successfully). However, it only drops the existing Virtual Directory and does not create a new one.
Has anyone had this problem before and/or know of a possible solution?
Basically, Reporting Services 2008 doesn't use IIS anymore.
By coincidence (or default?), I already had IIS (with Reporting Services 2005) running off port 8080. Reporting Services 2008 also wanted to run off port 8080.
It appears that the new IIS free address reservation system doesn't work in this situation. Changing the port number fixes the problem.