I recently migrated a Drupal web site and its sqldump into a IIS hosted version of the website. Everything looks as it should and all its contents are in place. My problem is I discovered Solr does not work on IIS. the main search module for the web site uses solr for searching contents. When I try to search I get the following message:
An error occurred while trying to search with Solr: "0" Status: Request failed: No connection could be made because the target machine actively refused it..
I have looked at this but I am not clearly understanding how I would put this in place for the drupal site to function properly.
using Solr with IIS
Please help.
Related
I want to know when the IIS is stopped can I show a custom html page instead of 404 error message? I stop IIS with help of cmd(net stop WAS ). I have tried app_offline.htm. it works fine. But when I start deploy by stopping the IIS the html page is not shown. I have searched a lot for this. But everywhere the Q is about only stopping the site. I want to know the reason why I can't show and also if there is any solution to that please help me. I am almost new in professional line. And my senior won't believe me because I can't explain why doesn't it work.
The web page is able to be showed due to that the IIS provides the hosting service. As long as the related IIS service is stopped, these web pages no longer been served.
The blog written by IIS official shows the IIS core service used to host the web page.
https://blogs.iis.net/tomwoolums/the-services-behind-internet-information-services-7-0
Feel free to let me know if there is anything I can help with.
We are facing a weird issue specific only on one website even though we are hosting more than 150 websites on same server using Kentico CMS 11.
We have turned on "www" prefix settings from Kentico -> Urls & SEO for all the websites and all these sites are working without any issue.
But there is a specific website on which all the requests are getting redirected to home page if try to access with "www" prefix.
I have tried checking at code level and could not find any issue. If it would be code issue then it should appear for other websites as well.
We are using Azure app service for hosting our application so I have checked in application insight as well and could not get any lead as all the request which are logged for this specific websites are of home page.
Please help me in understanding if I need to see through this issue at some other place. I have checked with Client's IS team and they could not find any DNS settings difference when compared to other websites which are working fine.
Please check the web.config file of this site. It may contain a wrong URL redirect associated with "www" so that probably this redirect just cuts all the path from URL.
I know a similar question was raised on this in 2009, but I am really baffled by this.
I have a Windows XP development machine which is used for maintenance on a classic ASP web application. IIS 5.1 is the web server.
The problem: some sites serve up classic ASP with no problem, other sites give the "The type of page you have requested is not served because it has been explicitly forbidden. The extension '.asp' may be incorrect. " error in a ASP.Net looking way. Suggesting that asp.dll isn't being used to serve up the pages!? The list of which dll to use with which file extension is the same for both sites. Any new site created appears to have the same issue with serving cASP.
If IIS was consistently failing to server cASP on all sites I would be looking at common configuration, but as it's working on a some and not others I am utterly baffled.
Any help would be appreciated!
I've developed a site in modx but after migrating it to the live server if I enter a page that doesn't exist (eg http://mysite.com/index.php?id=5) I'm getting the default IIS error page rather than the page specified in Tools->Configuration->site->Error page
Any idea why this could be happening?
For the record I developed on Apache but am deploying to IIS.
The only thing I can think of is that IIS is over-riding the modX error page somehow.
I know on Apache I can fiddle with the .htaccess file to set ErrorDocument, but I don't know how IIS works.
Perhaps previous SO questions on "custom 404 page on IIS" might give you some clues as to how your system is setup.
I generated a new web site in IIS. Under the new web site, there are some asp .net 2.0 applications. Tomcat is also running on the same server and they are working correctly.
But when I try to open an asp .net application, I am taking page can not be found error message. Then I changed the configuration settings of asp .net version from 2.0 to 1.1 then it is not giving page can not be found message but it gives an error message about web config. What can I do?
You haven't given many details. This could be a couple of things:
you have used an incorrect URL
you have used an incorrect protocol (i.e. http instead of https)
you are specifying a directory but you have no default document set up (i.e. you are going to http://mywebsite/myvirtualdir/, but you have no default.aspx)
you haven't installed ASP.NET so there are no handlers for aspx pages
until you give more details then no-one can say for sure what your problem is.