Site Manager Problem - SP1a
Windows Server Forum Index Windows Server
Server discussion on Windows platform.
 
 FAQFAQ   MemberlistMemberlist     RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 
 
Google
 
Web winserverhelp.com
Site Manager Problem - SP1a

 
Post new topic   Reply to topic    Windows Server Forum Index -> CMS Server
Author Message
rdcpro
Guest





Posted: Sat Jan 08, 2005 4:11 am    Post subject: Site Manager Problem - SP1a Reply with quote

Hi all,

We've installed MSMS using the integrated SP1a disk from our MSDN
subscription on a dev server, but I've got the common problem:

Could not connect to the Microsoft Content Management Server wpsdevcms01:80.
Either the web service is not running, or there are network problems that are
keeping you from connecting to the server, or the server is not accessible
through MCMS Site Manager. Source: LinkConfig::LaunchLogon

I've read the FAQ:

1. Yes, MCMS is configured to port 80.
2. No global.asa in inetpub/wwwroot.
3. J# redistributable VJSharpSxS10.dll is version 1.1.4322.0
4. SCA shows as Read-Write
5. Here's an interesting result. trying:

http://localhost/NR/System/ClientUI/login.asp

causes a login dialog, and when I add my credentials, returns a 500 server
error. So I put a "hello world" asp page there:

http://localhost/NR/System/ClientUI/test.asp

I get the login dialog, and when I enter my credentials, I get "Hello World".

I've read that the NR virtual directory needs Anonymous access (though my
VPC based version of the site works fine without it). But if I allow
anonymous in NR, I get the same result. When I set NR to anonymous access,
and uncheck Windows Integrated and run either login.asp or test.asp, I get:

HTTP Error 401.1 - Unauthorized: Access is denied due to invalid credentials.

What's weird is I have this same site running on a Win2k3 virtual PC, no
problem, even though I don't have anonymous access in IIS checked. But on
the hardware Win2k3 server, no joy.

I've even tried connecting remotely from the VPC Site Manager to the problem
child, but I get the same result.

The hardware-based server was built with an ADS script our network services
folks have set up, and the VPC server was done from a "default" installation
of Win2k3. Therefore, the environment between the two is different, but I
can't see what it could be. I do know the ADS script is pretty strict.

I'm pretty sure, then, that Site Manager's authentication, and our Windows
2003 security templates are at odds, but I can't see how.


Any suggestions?

Many thanks in advance,
Mike Sharp
Back to top
Stefan [MSFT]
Guest





Posted: Sat Jan 08, 2005 7:49 am    Post subject: Re: Site Manager Problem - SP1a Reply with quote

Hi Mike,

first of all: /NR and /MCMS directory need anonymous access enabled.
This is a must for MCMS.
As you get a login dialog it seems that this is not the case in your
situation.

Please check if the problem is gone after you enabled anonymous access on
this directories.

Cheers,
Stefan.

"rdcpro" <rdcpro@community.nospam> wrote in message
news:E2581A7D-8FCF-43A0-9426-1FBF1E363573@microsoft.com...
Quote:
Hi all,

We've installed MSMS using the integrated SP1a disk from our MSDN
subscription on a dev server, but I've got the common problem:

Could not connect to the Microsoft Content Management Server
wpsdevcms01:80.
Either the web service is not running, or there are network problems that
are
keeping you from connecting to the server, or the server is not accessible
through MCMS Site Manager. Source: LinkConfig::LaunchLogon

I've read the FAQ:

1. Yes, MCMS is configured to port 80.
2. No global.asa in inetpub/wwwroot.
3. J# redistributable VJSharpSxS10.dll is version 1.1.4322.0
4. SCA shows as Read-Write
5. Here's an interesting result. trying:

http://localhost/NR/System/ClientUI/login.asp

causes a login dialog, and when I add my credentials, returns a 500 server
error. So I put a "hello world" asp page there:

http://localhost/NR/System/ClientUI/test.asp

I get the login dialog, and when I enter my credentials, I get "Hello
World".

I've read that the NR virtual directory needs Anonymous access (though my
VPC based version of the site works fine without it). But if I allow
anonymous in NR, I get the same result. When I set NR to anonymous
access,
and uncheck Windows Integrated and run either login.asp or test.asp, I
get:

HTTP Error 401.1 - Unauthorized: Access is denied due to invalid
credentials.

What's weird is I have this same site running on a Win2k3 virtual PC, no
problem, even though I don't have anonymous access in IIS checked. But on
the hardware Win2k3 server, no joy.

I've even tried connecting remotely from the VPC Site Manager to the
problem
child, but I get the same result.

The hardware-based server was built with an ADS script our network
services
folks have set up, and the VPC server was done from a "default"
installation
of Win2k3. Therefore, the environment between the two is different, but I
can't see what it could be. I do know the ADS script is pretty strict.

I'm pretty sure, then, that Site Manager's authentication, and our Windows
2003 security templates are at odds, but I can't see how.


Any suggestions?

Many thanks in advance,
Mike Sharp
Back to top
rdcpro
Guest





Posted: Sat Jan 08, 2005 9:39 am    Post subject: Re: Site Manager Problem - SP1a Reply with quote

Thanks for your reply...actually I did have anonymous set--I"ve tried it both
ways, but on my other machine it doesn't seem to matter which way I have it
set--I authenticate either way. On the problem machine, if I set the VDir to
anonymous, I get HTTP Error 401.1 - Unauthorized: Access is denied due to
invalid credentials.

After spending a great deal of time chasing wild geese, a few minutes ago I
just discovered what the problem was (though I'm not sure what part of our
build process is responsible yet--That's a task for next week!).

It turns out that our "shared" directory was located at: /NR/public/shared.

When I realized the SSI wasn't finding the include file, I moved it to
/NR/shared, and that now allowed me to get to the login page. I've no idea
how shared got where it was.

Anyway, then when I tried to log in, I was getting "insufficient privileges"
for my login (I didn't originally set this machine up), and so I re-ran the
Database configuration, giving myself Admin access, and then it all worked
great. *WHEW*

Thanks for your attention, though. It's comforting to know that you and
Angus and the others are so responsive. Now if I could just get that kind of
response from the Sharepoint group! ;^) Actually, I've got my sharepoint
search controls working pretty nicely now as well. Life is good!

Regards,
Mike Sharp

"Stefan [MSFT]" wrote:

Quote:
Hi Mike,

first of all: /NR and /MCMS directory need anonymous access enabled.
This is a must for MCMS.
As you get a login dialog it seems that this is not the case in your
situation.

Please check if the problem is gone after you enabled anonymous access on
this directories.

Cheers,
Stefan.

"rdcpro" <rdcpro@community.nospam> wrote in message
news:E2581A7D-8FCF-43A0-9426-1FBF1E363573@microsoft.com...
Hi all,

We've installed MSMS using the integrated SP1a disk from our MSDN
subscription on a dev server, but I've got the common problem:

Could not connect to the Microsoft Content Management Server
wpsdevcms01:80.
Either the web service is not running, or there are network problems that
are
keeping you from connecting to the server, or the server is not accessible
through MCMS Site Manager. Source: LinkConfig::LaunchLogon

I've read the FAQ:

1. Yes, MCMS is configured to port 80.
2. No global.asa in inetpub/wwwroot.
3. J# redistributable VJSharpSxS10.dll is version 1.1.4322.0
4. SCA shows as Read-Write
5. Here's an interesting result. trying:

http://localhost/NR/System/ClientUI/login.asp

causes a login dialog, and when I add my credentials, returns a 500 server
error. So I put a "hello world" asp page there:

http://localhost/NR/System/ClientUI/test.asp

I get the login dialog, and when I enter my credentials, I get "Hello
World".

I've read that the NR virtual directory needs Anonymous access (though my
VPC based version of the site works fine without it). But if I allow
anonymous in NR, I get the same result. When I set NR to anonymous
access,
and uncheck Windows Integrated and run either login.asp or test.asp, I
get:

HTTP Error 401.1 - Unauthorized: Access is denied due to invalid
credentials.

What's weird is I have this same site running on a Win2k3 virtual PC, no
problem, even though I don't have anonymous access in IIS checked. But on
the hardware Win2k3 server, no joy.

I've even tried connecting remotely from the VPC Site Manager to the
problem
child, but I get the same result.

The hardware-based server was built with an ADS script our network
services
folks have set up, and the VPC server was done from a "default"
installation
of Win2k3. Therefore, the environment between the two is different, but I
can't see what it could be. I do know the ADS script is pretty strict.

I'm pretty sure, then, that Site Manager's authentication, and our Windows
2003 security templates are at odds, but I can't see how.


Any suggestions?

Many thanks in advance,
Mike Sharp



Back to top
 
Post new topic   Reply to topic    Windows Server Forum Index -> CMS Server All times are GMT
Page 1 of 1

 
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum




New Topics Powered by phpBB