Problems while installing SSR2011-MS SP1

Ok well, to be honest, i had no problems at all so far with my install yesterday These were my steps. I installed server 2008 r2 std, but did not install sp1 and IE9. I did patch it up all the way with the current windows updates and it also installed dot net 4 framework which i was wary off. I then installed dot net 3.5 through roles and then iis through roles. I then went ahead and installed the SSR2011 MS INSTALL. During readiness checks it pointed out that there was an error with asp and iis 6 comptability. When i hit the fix the iis component through the link underneath it automatically fixed the asp part as well.  This morning I updated my SSR MS 10.0.0 to SSR MS SP1 10.0.1 So far so good.

Well that's a different evironment, I have a server that is SP1 and have to install on it, I waited a long time for the SP1 of SSR, but now that it is out I get this error trying to install :(

Is this a fresh install of IIS on the server? I have seen in the past that if IIS has been installed on the server and multiple installs of ServiceDesk are done the binding become corrupt in IIS.

I would recommend adding an arbitrary web binding than removing the standard ones (http:80, https:443) than reading them. I know it sounds strange but give it a go and let me know how it turns out, there are a few other tricks that I would try if this does not work.

I tried, but the problem is still here.

It is not a fresh install, on the server is running exchange 2010 (don't know about any compatibility issue with it, right?).

nobody?

I am running SSR with Exchang 2010 and have had no issues to date.  What are the errors you are getting now?

-ASP.NET mapping scpript for IIS not instaleld o properly configured

look at attachment at 6th post

no way to install it....:(

That could also be it thet fact that you have exchange. I am running my  server soley for the purposes of symantec management solution. It could be that there is some IIS conflict with exchange and maybe symantec and something in there needs to be configured ??

maybe....but I don't know what....hope some symantec employ answers :)

I wanted to install on that server cause I have another one but iis a DC and I think it's better not to install it on a DC, another one has Symantec endpoint management instaleld and I know that it's better to install the two management solutions on different servers...so ther only available server was the exchange one...