Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

New install Reporter 4

Status
Not open for further replies.

tnjwinters

Programmer
Jun 15, 2005
390
US
I am trying a new install of CallPilot Reporter on a new server. I've had Reporter up and running for so long that I don't remember how I solved the problem the first time. When I go the the localhost/cpmgr address I get this error:

Active Server Pages error '00000000'

Create object failed

?

An error occurred while creating object 'oARC'.

Microsoft VBScript runtime error '800a01ae'

Class doesn't support Automation: 'oARC'

/LM/w3svc/1/root/cpmgr/global.asa, line 44

Any ideas
 
Make sure you are using the correct version. If a vendor has updated the peps on your callpilot you may have to get a newer version of callpilot reporter.
 
I have the same version as what is installed. Any other ideas?
 
I got this off of the Nortel website.

Active Server Pages error '000000'
Create object failed
?
An error occurred while creating object 'oARC'
Microsoft VBScript runtime error '800a01ae'
Class doesn't support Automation: 'oARC'
/LM/w3svc/1/root/cpmgr/global.asa, line 44

Cause of problem:
Windows 2003 is not supported as a Web server for CallPilot Manager 2.02.
Problem Resolution
Install CallPilot Manager/Reporter on a supported Web server. Refer to CallPilot 2.02 General Release Bulletin GR 2003-0191 Global. The bulletin is available on the Partner Information Center website: Log in and select Products & Solutions>Partner Bulletins>General Release Bulletins>2003 Bulletins>Apply Filters. Scroll down until GR 2003-0191 Global appears.
 
Sounds like the problem, but I have 4.04.04.13 installed, it is on a 2003 R2 server.
I am trying to move it to a new server with the same versions installed.
 
Is that the callpilot manager verion? Is the callpilot server software 2.02?
 
CallPilot is 4.04.04 and CallPilot Manager is 4.04.04.13
 
Can you see the CallPilot manager login screen properly if you go to the callpilot URL?

It could be your java version on your PC.
Make sure you have the appropriate one for the PC.
I think rls 4 needs Java(TM) 2 Runtime Environment (JRE) version 1.3.x

Try going to the IP address,
and try from different PCs as well.
 
I can't see the login screen from the reporter server or any other PC. On the Reporter server all I get is the error noted above. I do have Java 1.3 installed on the server.
 
Go back to the book and verify every step,


Software Administration and Maintenance

Document Number: 555-7101-202

There are a bunch of steps for setting up anonymous logon...

Page 48

 
OK, I was working off the wrong NTP. The one you gave me helped. Now I can log into CallPilot Manager, but when I go to Reporter I get:

Failed to login



The following errors have occured:


Error code: -2146828218, text 1: Permission denied


 
The next time I tried to login I got:

Failed to login



The following errors have occured:


Error code: -2146827858, text 1: Class doesn't support Automation


 
To configure a customer-provided Windows Server 2003 with SP2 for use with CallPilot Manager/Reporter (pre 5.0/SU02)
1. Open Start > Administrative Tools > Component Service.
2. On the left pane of Component Services, go to Component Services > Computers > My Computer > DCOM Config > CallPilot Reporter.
3. Open Security tab in CallPilot Reporter properties.
4. Under Launch and Activation Permissions click Customize, and then click Edit.
5. Add NETWORK group with Remote Activation and Local Activation permissions granted.
6. Add NETWORK SERVICE group with Local Launch and Local Activation permission granted.
7. Click Ok.
8. Click Ok again.
9. Open Start > Administrative Tools > Local Security Policy.
10. On left pane of Local Security Settings go to Local Policies > Security Options.
11. On the right pane click on DCOM: Machine Launch Restrictions in Security Descriptor Definition Language (SDDL) syntax.
12. In DCOM: Machine Launch Restrictions in Security Descriptor Definition Language (SDDL) syntax window click on Edit Security… button.
13. Add NETWORK group with Remote Activation and Local Activation permissions granted.
14. Click Ok.
15. Click Ok again.
16. Reboot the server to full service.
 
Found this in a product bulletin(P-2008-0033) it refers to using 2003 sp2 with pre 5.0/su2 callpilot. Might be worth a try.
 
That was the final piece of the puzzle. Thank you for all the help.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top