Unable to open TM1 WEB page

[Jodha]

I know this is a config issue but just want to know if any one of you have encounter similar issue before so that your advice will be helpful .
I googled it in all microsoft forums but no luck just want to give a final try inthis forum
I installed 10.1 FP1 in windows 2008 R2 server 64 bit with 2010 excel
i have .Net 4.0 installed on machince with all necesaary prerequisites.

[Jodha]

i got below error message in installog under G:\ibm\cognos\tm1_64\instlog

Warning: Failed to get file list for directory "G:\ibm\cognos\tm1_64\maps".

I downloaded package from IBM website not sure how this warning will effect installation

[Andy Key]

Maybe you've done this already, but it might be worth having a look in the web.config itself. From memory there are a whole bunch of lines in there that are specific to .Net 4. I don't recall if you have to do something to include them, or exclude them.

[Jodha]

Thanks Andy for the replay i tried deleting unneccessay line from web.config file and changed basic settings as suggested by IBM but it didnt worked.

[Jodha]

By enabling handler mapping in server solved my problem . It looks more as a config releated stuff which failed to enable during installation .

[ViRa]

By enabling handler mapping in server solved my problem . It looks more as a config releated stuff which failed to enable during installation

Can you please elaborate how you fixed this issue? I'm also running into the same.

[Jodha]

1) Go to c:\inetpub\scripts
2) run this script cscript applyhandlermappings.vbs "Default Web Site" /html /asp.net2.0
(if your using asp.net4.0 try using asp.net 4.0 instead of asp.net2.0 in the end)

if still you had issue in looking at web page try commenting out below parameter lines in web.config file
you can find these parameters in top 10 or 20 lines


scriptResourceHandler...jsonSerialization....profileService.... authenticationService

in case of issue contact windows team in your organization they will solve this .It shouldn't take more than 5 mins for them to resolve this issue.