Can't access CMC et al from Launchpad 1

[Naith]

Hi,

I'm looking at a CE9 install on NT, with IIS 5.0 on one box, and the same set up on another box. The end goal is to cluster the two installs.

One machine - call it A - is fine. You get to the launchpad, and can access CMC, ePortfolio, etc as normal. Machine B, on the other, is not so good. You can hit the launchpad well enough, but accessing any of the applications there on in returns the Page Not Found error. This machine, incidentally, has Server Extensions installed on IIS. Machine A does not.

I'm thinking that the reason B doesn't recognise the URL for CMC or ePortfolio from the launchpad is because IIS doesn't know what to do with the csp/cwr extensions.

So, I'm in IIS on Machine B checking the properties for .../CE9/launchpad/en, and I can see that the .csp, .cwr., .cri, and .rpt extensions all point to wcsisapi, where they should be, but the path is enclosed in quotes. On Machine A, it isn't. (I'm doing this on the Directory tab of the directory properties.)

I don't have access to the server directly, so I'm using a proxy to modify the settings remotely, but if I try to remove the quotes and commit the change, I get an invalid directory error. Can anyone confirm what impact quotes around the path is having on the afore mentioned pages using wcsisapi.dll, or am I totally barking up the wrong tree?

Cheers,

Naith

 

[Naith]

Okay, I'm now pretty certain the quotes are the problem. I stuck quotes around Machine A's .csp and .cwr mappings, and get the Page Not Found error.

Trouble is, now I can't change it back, because IIS complains that it doesn't recognise the path: "You must enter a valid path". Anyone got any star-worthy ideas on how I can force IIS to accept the path I give it?

Naith

 

[KingfisherINC]

I think I've seen this problem before, it might be a bug in IIS - quotes should help resolve the path, not make it worse.

To work around the problem try moving wcsisapi.dll to a path without spaces (e.g. C:\Windows\System32\wcsisapi.dll) or use the short path name (e.g. C:\progr~1\...).

You still need to ensure your WC points to the correct machineort.

Kingfisher [CECP]

 

[Naith]

Yeah, I did actually dump the Crystal dir into a new dir with no spaces - didn't update you, sorry - which, after restarting the services and setting the App Mapping at Crystal root rather than at launchpad/en, solved the problem.

Cheers for coming back anyway, KF.

Naith

 

[kmcmanus]

I made the change in a similar situation moving CE 8.5 to an IIS 6/ 2003 Server environment. CSP's are recognized but any CWR (like the CMC)is not working (page not found) even though it setup the same.

Stuck and needing help

Kevin

 

[Naith]

In IIS, have you checked that both CSPs and CWRs access are allowed?

Also, check to see if you have urlscan installed on your machine. If so, read urlscan.ini to ascertain if instructions are laid out to disallow cwr. Settings in this file will override IIS.

Naith

 

[KingfisherINC]

IIS6 adds a check box when you add an extension "Check that file exists" or something like that. Since CWR is not a physical file you will get a 404 - uncheck the box and you should be ok.

Kingfisher