Site Manager 'usual' Error

[Chrisc]

I am using Windows XP professional
I am using the CMS 2002 with sp1 trial download software

I have followed installation as in the 'Building Websites with Microsoft
Content Management Server' by Lim Ying, Joel Ward, Stefan Gossner.

So far I have managed to install CMS.
I have run the DCA.

I have tried to use the Site Manager to connect to the localhost:80.

I get a 'typical' error:
'Could not connect to the Microsoft Content Server localhost:80'

I have read the FAQs at:
http://download.microsoft.com/download/4/2/5/4250f79a-c3a1-4003-9272-2404e92bb76a/MCMS+2002+-+(complete)+FAQ.htm#HL_E5141EB8-A8CE-4B94-B2CA-5ADC4DDF3D78

and I have got as far as point 5 of the relevant 'answer':
'Try to access http://localhost:80/NR/System/ClientUI/login.asp from
Microsoft Internet Explorer and see if you get an error from Microsoft
Internet Information Server (IIS). If so, put a test (very simple one; e.g.
just say “hello world”) ASP page in \Server\IIS_NR\System\ClientUI\ and try
to access it from Microsoft Internet Explorer. If that test page gives the
same error, work on the issue as a regular IIS access problem. Then try to
open Site Manager again.'

.....now at this point, IE reports the following error:

Error Type:
Server object, ASP 0177 (0x800401F3)
Invalid class string
/NR/System/ClientUI/login.asp, line 9

..... and if I look at line 9:

Set AESession = Server.CreateObject("AeSession.AeSession.1")

.... to which I have found a post that recommends:

'Please reregister the following COM object using regsvr32:
c:\Program Files\Microsoft Content Management
Server\Server\bin\AEServerObject.dll"'

So I tried that but the register fails:

'DllRegisterServer in C:\....bin\AEServerObject.dll failed Return code was:
0x80070005'

I have tried to 'repair' the original installation from the control panel -
add remove programs, but it makes no difference.

(By the way I have 3 J# redistributables on my machine....j# .NET
Redistributable Package 1.1/(ENU) v1.0.4205/2.0 )

I have spent so long trying to install this, and I'm not having any success.
Please help.

[Ireland@discussions.microsoft.com Robert Ireland]

Chris,

Can you confirm that .asp is running on your laptop. Did you put the simple
"Hello World" .asp application in the following place and then run it from
your browser?

<MCMS Installation Path>\Server\IIS_NR\System\ClientUI\helloworld.asp, a
simple

<%
Response.Write ("Hello World")
%>

should do it, then try browsing to the page from the IIS Console.

If asp isn't working check the Event Log to see if there are any errors that
occured when you tried to access the page.

Thanks
Robert

[Stefan Goßner [MSFT]]

Hi Chris,

the error you get on regsvr32 means access denied.

So you have not sufficient priviledges to do this.
Maybe you have locked-down the machine?

Cheers,
Stefan

"Chrisc" <Chr...@discussions.microsoft.com> wrote in message
news:50297E66-11A1-4187...@microsoft.com...

[Chrisc]

OK, I have created the simple asp page that prints helloworld. It works both
in the root of the web directory, and also if I place it into the location
specified. No errors.

[Chrisc]

I have not deliberately locked down anything.... I am able to register other
dlls or make other entries in the registry.

The error originally occured right after successfully using the DCA.

As a further 'user permission test' I logged in as Administrator, and then
as the CMS_System account and tried with those, and still no luck in
registering the dll.

[Stefan Goßner [MSFT]]

Hi Chris,

SP1 is no longer supported.
Please install SP2 and check if the problem is gone.

Cheers,
Stefan

"Chrisc" <Chr...@discussions.microsoft.com> wrote in message
news:50297E66-11A1-4187...@microsoft.com...

[Chrisc]

The service pack installs fine. Unfortunately the same error appears in Site
Manager. To recap, I have never managed to get site manager to connect.

[Stefan Goßner [MSFT]]

Hi Chris,

as long as you are not able to register this DLL you cannot use Site
Manager.
I would suggest to reinstall MCMS. If this does not help, I would recommend
to reinstall the box.

Cheers,
Stefan

"Chrisc" <Chr...@discussions.microsoft.com> wrote in message

news:DFEB2A3E-D621-471D...@microsoft.com...