EV Mobile search 8 installation issues: website not being served

[Sym-City]

Hello all,

The Mobile Search server is running Windows 2003 SP 2 (32 bit)

I created a self-signed cert in IIS6 on the box, and have configured IIS to require SSL on port 443.

After that was set up, I ran the install package and followed all the instructions then cycled IIS just in case

Here's the trouble:

When I go to the url https://server/mobilesearch I get a page not found.

Everything seems to be in order...

I've re-generated the cert, uninstalled and re-installed mobile search and have had no luck.

I would appreciate any suggestions at this point

Thanks

[JesusWept3]

if you use http:// instead of https:// does it work?
Also if you browse to the physical location of where the mobilesearch virtual directory is pointing to, can you then look at one of those files (beit ASPX or html or whatever) and then go to

http://server/mobilesearch/fileYouFound.aspx and be able to view the page there?
It may simply be a case of the default home page on the virtual directory not being set correctly

i.e. its looking for index.html or index.asp but the real page maybe start.aspx etc

[Rob_Wilcox1]

Do the IIS logs containing anything useful?  (ie which page is giving the error)

[Sym-City]

Hi Gents,

Thanks for the feedback, here's what happens:

If I go to http://mobilesearchserver/mobilesearch I get: "page must viewed over a secure channel"

If I go to Https://mobilesearchserver  I get "under construction"

If I go to Https://mobilesearchserver/login.aspx I still get page not found

Before unchecking SSL required:

If I use the "browse" function of IIS to attempt to view any of the constituent parts of the mobilesearch website, I get the "page must viewed over a secure channel" error

After unchecking SSL required:

If I try to use the "browse" function in IIS for any of the constituent parts of the mobilesearch website, they all come back with "Page not found."

I've attached a screenshot of what my IIS console looks like, in it I have drilled down into the mobilesearch site

Here's the IIS logfile dump:

#Date: 2011-08-05 18:57:00
#Fields: date time s-sitename s-ip cs-method cs-uri-stem cs-uri-query s-port cs-username c-ip cs(User-Agent) sc-status sc-substatus sc-win32-status
2011-08-05 18:57:00 W3SVC1 139.48.205.110 GET /search.aspx - 443 - 139.48.205.110 Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+5.2;+Trident/4.0;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727;+.NET+CLR+3.0.04506.30;+.NET+CLR+3.0.4506.2152;+.NET+CLR+3.5.30729) 404 2 1260
2011-08-05 19:00:04 W3SVC1 139.48.205.110 GET /search.aspx - 80 - 139.48.205.110 Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+5.2;+Trident/4.0;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727;+.NET+CLR+3.0.04506.30;+.NET+CLR+3.0.4506.2152;+.NET+CLR+3.5.30729) 403 4 5
2011-08-05 19:02:57 W3SVC1 139.48.205.110 GET / - 80 - 139.48.205.110 Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+5.2;+Trident/4.0;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727;+.NET+CLR+3.0.04506.30;+.NET+CLR+3.0.4506.2152;+.NET+CLR+3.5.30729) 403 4 5
2011-08-05 19:03:04 W3SVC1 139.48.205.110 GET /iisstart.htm - 443 - 139.48.205.110 Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+5.2;+Trident/4.0;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727;+.NET+CLR+3.0.04506.30;+.NET+CLR+3.0.4506.2152;+.NET+CLR+3.5.30729) 200 0 0
2011-08-05 19:03:04 W3SVC1 139.48.205.110 GET /pagerror.gif - 443 - 139.48.205.110 Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+5.2;+Trident/4.0;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727;+.NET+CLR+3.0.04506.30;+.NET+CLR+3.0.4506.2152;+.NET+CLR+3.5.30729) 200 0 0
2011-08-05 19:03:04 W3SVC1 139.48.205.110 GET /favicon.ico - 443 - 139.48.205.110 Mozilla/4.0+(compatible;+MSIE+8.0;+Windows+NT+5.2;+Trident/4.0;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727;+.NET+CLR+3.0.04506.30;+.NET+CLR+3.0.4506.2152;+.NET+CLR+3.5.30729) 404 0 2

As always, thanks for your help!
 

[JesusWept3 · Accepted solution]

So heres your deal

2011-08-05 18:57:00 W3SVC1 139.48.205.110 GET /search.aspx - 443  - 404 2 1260

Can you check whether ASP.NET is actually allowed to run on that machine?
Open up Internet Information Services and go to Web Service Extensions, does ASP.NET show Allowed or prohibited?

404.2 is an error thrown when the web service is not allowed to run, this could also be due to the URLScan if you have that installed.

[Sym-City]

Ah HAH!

You were spot on, thank you very much all. While ASP 1.5 and 2.0.5 were installed, 2.0.5 wasn't properly registered

Thank you again!