locked
ProClarity Analytics 6.3 fails to install RRS feed

  • Question

  • Hello,

    I am unable to install ProClarity 6.3 on a new server. It seems to be some sort of problem creating the web sites etc on IIS. There are no new web sites or virtual directories created in IIS, and the ProClarity Admin Tool cannot connect to the server.

    The diagnostics file is reproduced below.

    I have also tried:

    1. Installing ProClarity 6.2
    2. Uninstalling and re-installing IIS (several times)
    3. New or existing PAS database

    Thanks,

    Les

    ProClarity Diagnostic Report

    PCDiagnosticTool.exe version: 6,3,129,200

    July 14, 2011 - 4:43 pm

     

    System Information

    System Processor :Intel(R) Xeon(R) CPU X5670 @ 2.93GHz

    Vendor ID : GenuineIntel

    Processor ID : x86 Family 6 Model 26 Stepping 4

    Processor Speed : 2934 MHz

    Memory Information

    Total Physical Memory : 2,097,151 KB

    Total Available Physical Memory : 2,097,151 KB

    Total Paging File Size : 4,194,303 KB

    Total Available Paging File Memory : 4,194,303 KB

    Statistics for Drive C:

    Sectors Per Cluster : 8

    Bytes Per Sector : 512

    Free Space : 47,087 MB

    Total Space : 61,439 MB

    Statistics for Drive D:

    Sectors Per Cluster : 8

    Bytes Per Sector : 512

    Free Space : 43,175 MB

    Total Space : 102,399 MB

    Statistics for Drive E:

    Sectors Per Cluster : 8

    Bytes Per Sector : 512

    Free Space : 32,859 MB

    Total Space : 33,785 MB

    Statistics for Drive F:

    Sectors Per Cluster : 8

    Bytes Per Sector : 512

    Free Space : 19,609 MB

    Total Space : 23,548 MB

    Operating System Information

    Platform : Windows 2003

    OS Version : 5.2.3790

    Service Pack : Service Pack 2

    OS Language : English (United States)

    User Default Locale : English (Australia)

    System Default Locale : English (Australia)

    Installed ProClarity Components

    Software Information

    Internet Explorer Version : 7.0.5730.11

    Netscape Navigator Version : - Key Does Not Exist -

    Analysis Services 2000 Version : 8.0.2039.0

    Default MSOLAP Provider :Microsoft OLE DB Provider for Analysis Services 9.0

    .NET Framework Versions : v1.1.4322, v2.0.50727

    Office 2003 File Version Information

    EXCEL.EXE :- File Not Found -

    OUTLOOK.EXE :11.0.5510

    POWERPNT.EXE :- File Not Found -

    WINWORD.EXE :- File Not Found -

    MSACCESS.EXE :- File Not Found -

    Pivot Table Services File Version Information

    MSOLAP.DLL :7.0.1458.0219

    MSMDCUBE.DLL :7.0.1458.0219

    MSMDGDRV.DLL :7.0.1460.0531

    MSOLAPR.DLL :7.0.1458.0219

    MSOLAPUI.DLL :7.00.1458

    MSDMENG.DLL :8.00.2039

    MSDMINE.DLL :8.00.2039

    MSMDCB80.DLL :8.00.2039

    MSMDGD80.DLL :8.00.2039

    MSOLAP80.DLL :8.00.2039

    MSOLUI80.DLL :8.00.2039

    MSDMINE.RLL :8.00.2039

    MSOLAP80.RLL :8.00.2039

    OLAPUIR.RLL :8.00.2039

    MSMDUN80.DLL :2000.080.2039.00

    XMLRW.DLL :2.00.3604.0 built by: (_sqlbld)

    XMLRWBIN.DLL :2.00.3604.0 built by: (_sqlbld)

    MSMGDSRV.DLL :2005.090.1399.00

    MSMDLOCAL.DLL :2005.090.1399.00

    MSOLAP90.DLL :2005.090.1399.00

    MSOLUI90.DLL :2005.090.1399.00

    MSMDSRV.RLL :2005.090.1399.00

    MSOLUI90.RLL :2005.090.1399.00

    Microsoft Data Access Components File Version Information

    MSADER15.DLL :2.82.3959.0 (srv03_sp2_rtm.070216-1710)

    MSADO15.DLL :2.82.4795.0 (srv03_sp2_gdr.101103-0357)

    MSADO20.TLB :2.82.4795.0 (srv03_sp2_gdr.101103-0357)

    MSADO21.TLB :2.82.4795.0 (srv03_sp2_gdr.101103-0357)

    MSADO25.TLB :2.82.4795.0 (srv03_sp2_gdr.101103-0357)

    MSADOMD.DLL :2.82.4795.0 (srv03_sp2_gdr.101103-0357)

    MSADOR15.DLL :2.82.3959.0 (srv03_sp2_rtm.070216-1710)

    MSADOX.DLL :2.82.4795.0 (srv03_sp2_gdr.101103-0357)

    MSADRH15.DLL :2.82.3959.0 (srv03_sp2_rtm.070216-1710)

    MSJRO.DLL :2.82.4795.0 (srv03_sp2_gdr.101103-0357)

    MSADCE.DLL :2.82.3959.0 (srv03_sp2_rtm.070216-1710)

    MSADCER.DLL :2.82.3959.0 (srv03_sp2_rtm.070216-1710)

    MSADCF.DLL :2.82.3959.0 (srv03_sp2_rtm.070216-1710)

    MSADCFR.DLL :2.82.3959.0 (srv03_sp2_rtm.070216-1710)

    MSADCO.DLL :2.82.4795.0 (srv03_sp2_gdr.101103-0357)

    MSADCOR.DLL :2.82.3959.0 (srv03_sp2_rtm.070216-1710)

    MSADCS.DLL :2.82.4795.0 (srv03_sp2_gdr.101103-0357)

    MSADDS.DLL :2.82.3959.0 (srv03_sp2_rtm.070216-1710)

    MSADDSR.DLL :2.82.3959.0 (srv03_sp2_rtm.070216-1710)

    MSDAPRSR.DLL :2.82.3959.0 (srv03_sp2_rtm.070216-1710)

    MSDAPRST.DLL :2.82.3959.0 (srv03_sp2_rtm.070216-1710)

    MSDAREM.DLL :2.82.3959.0 (srv03_sp2_rtm.070216-1710)

    MSDAREMR.DLL :2.82.3959.0 (srv03_sp2_rtm.070216-1710)

    MSDFMAP.DLL :2.82.3959.0 (srv03_sp2_rtm.070216-1710)

    MSDADC.DLL :2.82.3959.0 (srv03_sp2_rtm.070216-1710)

    MSDAENUM.DLL :2.82.3959.0 (srv03_sp2_rtm.070216-1710)

    MSDAER.DLL :2.82.3959.0 (srv03_sp2_rtm.070216-1710)

    MSDAORAR.DLL :2.82.3959.0 (srv03_sp2_rtm.070216-1710)

    MSDAOSP.DLL :2.82.3959.0 (srv03_sp2_rtm.070216-1710)

    MSDAPS.DLL :2.82.3959.0 (srv03_sp2_rtm.070216-1710)

    MSDASC.DLL :2.82.3959.0 (srv03_sp2_rtm.070216-1710)

    MSDASQL.DLL :2.82.3959.0 (srv03_sp2_rtm.070216-1710)

    MSDASQLR.DLL :2.82.3959.0 (srv03_sp2_rtm.070216-1710)

    MSDATL3.DLL :2.82.3959.0 (srv03_sp2_rtm.070216-1710)

    MSDATT.DLL :2.82.3959.0 (srv03_sp2_rtm.070216-1710)

    MSDAURL.DLL :9.2.3959.0 (srv03_sp2_rtm.070216-1710)

    MSXACTPS.DLL :2.82.3959.0 (srv03_sp2_rtm.070216-1710)

    OLEDB32.DLL :2.82.3959.0 (srv03_sp2_rtm.070216-1710)

    OLEDB32R.DLL :2.82.3959.0 (srv03_sp2_rtm.070216-1710)

    SQLOLEDB.DLL :2000.086.3959.00 (srv03_sp2_rtm.070216-1710)

    SQLOLEDB.RLL :2000.086.3959.00 (srv03_sp2_rtm.070216-1710)

    SQLXMLX.DLL :2000.086.3959 (srv03_sp2_rtm.070216-1710)

    SQLXMLX.RLL :2000.086.3959 (srv03_sp2_rtm.070216-1710)

    Chart Version Information

    ChartFX.ClientServer.Annotation.dll:- File Not Found -

    ChartFX.ClientServer.Borders.dll:- File Not Found -

    ChartFX.ClientServer.CategBar.dll:- File Not Found -

    ChartFX.ClientServer.Core.dll:- File Not Found -

    ChartFX.ClientServer.Data.dll:- File Not Found -

    File Version Information

    MSXML.DLL :8.00.7002.0

    MSXML3.DLL :8.100.1051.0

    MSXML3R.DLL :8.20.8730.1

    MSXML4.DLL :4.20.9876.0

    MSXML4R.DLL :4.10.9404.0

    MSXML6.DLL :6.20.2003.0

    MSXML6R.DLL :6.00.3883.0

    OLEAUT32.DLL :5.2.3790.4202

    OLEPRO32.DLL :5.2.3790.3959

    STDOLE2.TLB :5.2.3790.3959

    ASYCFILT.DLL :5.2.3790.4676

    MSVCRT.DLL :7.0.3790.3959 (srv03_sp2_rtm.070216-1710)

    MSVCP70.DLL :- File Not Found -

    MSVCR70.DLL :7.00.9466.0

    MSVCP71.DLL :7.10.3077.0

    MSVCR71.DLL :7.10.3052.4

    MSVCP80.DLL :- File Not Found -

    MSVCR80.DLL :- File Not Found -

    XML Tests

    Active XML Library File - msxml3.dll

    Test File Name: C:\Documents and Settings\a-lrussell\Application Data\ProClarity\Client\testPCDT.xml

    Passed - XML Document Object Creation Test

    Passed - XML Element Object Creation Test

    Passed - XML Child Object Append Test

    Passed - XML File Save Test

    Passed - XML Child Object Removal Test

    Passed - XML File Load Test

     

    ProClarity Analytics Server Report

    Product Version: 6,3,129,200

    ASP Path: C:\Inetpub\wwwroot\PAS\

    IIS Virtual Directory: PAS

    Registered Servers:

    WNRYDDB02

    Machine Name: WNRYDDB02

    URL: http://WNRYDDB02/PAS

    Comparing against ProClarity Analytics Server version 6,3,129,200 ...

    Different version: C:\Program Files\Common Files\ProClarity\Server\SetupGuide.pdf

     

    CreateControl Tests

    -- All Components Created Successfully --

     

    CreateCOMObject Tests

    Failure - PACCESS.PAccessMgr

    Error Message: The system cannot find the path specified

     

     


    Les
    • Edited by Les R Thursday, July 14, 2011 7:04 AM Spelling
    Thursday, July 14, 2011 6:57 AM

All replies

  • Hello again,

    When proClarity 6.3 fails to install there is no real indication of a problem until you try to browse to the PAS website. However we have also tried to install v6.2, and when that fails to install, it produces the following in the IIS log:

    #Software: Microsoft Internet Information Services 6.0
    #Version: 1.0
    #Date: 2011-07-19 05:11:28
    #Fields: date time s-sitename s-ip cs-method cs-uri-stem cs-uri-query s-port cs-username c-ip cs(User-Agent) sc-status sc-substatus sc-win32-status
    2011-07-19 05:11:28 W3SVC1 10.209.9.22 GET /PAS/PStoreSDL50.asp - 80 - 10.209.9.22 ProClarity 200 0 0
    2011-07-19 05:11:28 W3SVC1 10.209.9.22 POST /PAS/PStore.asp |15|800a01a8|Object_required:_'PListener' 80 - 10.209.9.22 ProClarity 500 0 0

    Hope this may help someone came up with a solution ...

    Note that I've posted something similar on www.iis.net forum "IIS 5.x and 6.0" --> Troubleshooting


    Les
    • Edited by Les R Tuesday, July 19, 2011 6:33 AM Spelling
    Tuesday, July 19, 2011 6:17 AM
  • Hello again,

    We have been trying for a week now to install ProClarity, with not much progress. We have reached a point where if we browse ProClarity.asp, we get:

    -----------------------------------------------------------

    Active Server Pages error '00000000'

     

    Create object failed

     

    ?

     

    An error occurred while creating object 'AccessMgr'.

     

    Active Server Pages error '00000000'

     

    Create object failed

     

    ?

     

    An error occurred while creating object 'AccessMgr'.

     

    Active Server Pages error '00000000'

     

    Create object failed

     

    ?

     

    An error occurred while creating object 'AccessMgr'.

     

    Active Server Pages error '00000000'

     

    Create object failed

     

    ?

     

    An error occurred while creating object 'AccessMgr'.

     

    Microsoft VBScript runtime error '800a01ae'

     

    Class doesn't support Automation: 'AccessMgr'

     

    /LM/W3SVC/1/ROOT/PAS/global.asa, line 84

     

    -----------------------------------------------------------

     

    This has been mentioned in other posts. We have tried running the Application Pool and the installation as several different accounts, including Local System and a Local Admin account. We are running this on  Windows Server 2003 sp2 32-bit, which works fine in our old environment.

     

    Any other ideas on what we can try?

     

    Thanks,

     

     


    Les
    Thursday, July 21, 2011 5:59 AM
  • Hello,

    We've got exactly the same issue on our Windows Server 2003 SP2 32 bit server.  I tried installing 6.3 and the exact same issue is happening to us.

    Has anybody got any ideas?

    Are the Microsoft ProClarity team even reading these posts?

    Andy

    Thursday, July 21, 2011 2:38 PM
  • Another update:

    During a painstaking search through the differences  between the IIS setups, I've found that in the broken installation PHttpFilter does not exist as an ISAPI Filter on the Default Web Site (under which PAS sits). It does exist on both our working implemntations (ProClarity 6.2 and 6.3). I tried adding it manually (the dll file exists and is in the correct place), but it refuses to update the Priority and the status remains as Unknown.

    I'm clutching at straws here, but since the code seems to be missing some functions, this may be a clue?

    Thanks,


    Les
    Friday, July 22, 2011 7:53 AM
  • I got this ISAPI filter installed (all that is required is that you try to browse to the site) - no change to the installation i.e. it still gives the "Failed to create object AccessMgr" error.
    Les
    Monday, July 25, 2011 1:37 AM
  • Hi,

    Are you installing using a domain account when performing the install? We had the same problem when installing using a domain account (albeit that was on a x64 server). The COM objects simply fail to create as a result of which Proclarity Analytics server doesn't work. The soluting which worked for us was to do the following

    1. Uninstall any existing Proclarity installations
    2. Log in using a local user account (or local admin account) on the system when you wish to install proclarity
    3. install proclarity
    4. after installing run the proclarity diagnostics

    You should not get the  "CreateCOMObject Tests Failure - PACCESS.PAccessMgr  Error Message: The system cannot find the path specified" message.

    Hope this helps,

    Regards,
    Leighton

    Monday, July 25, 2011 6:53 PM
  • Leighton,

    Thanks. We have tried that: by which I mean:

    1. create a local user,
    2. add the user to the local Administrators group
    3. uninstall ProClarity,
    4. manually delete website (it always fails to do this on uninstall)
    5. delete ProClarity common files
    6. install ProClarity (6.2 or 6.3)

    The result is always the same. It is the same on several servers. There is some simple problem buried somewhere in there but no-one seems to be able to put their finger on it. The symptoms look very similar to those seen by some people who try this on 64-bit machines, but the solutions don't work.

    The operating system is 2003 R2 SP2, running on VMWare and using Kaspersky anti-virus. Not much else I can think of, it all seems to be stock-standard.


    Les
    Monday, July 25, 2011 11:57 PM
  • Not that it helps you Les, but I'm seeing the exact same problem on almost identical hardware with a 32 bit installation as well.  I'd love to see a resolution/see what they recommend you do to fix this issue.

    We had ProClarity on a Windows Server 2008 machine until about a week ago.  Due to hardware reallocation I had to move it to a box that has Windows Server 2003 SP2 installed.  The machine hasn't had anything aside from SQL server 2000 on it.  I ran windows updates, installed IIS using the SP2 installation CD, and then installed Proclarity as the local administrator.  After I installed Proclarity I patched up to the latest hot-fix (2233) as recommended on the ProClarity blog.  

    I just can't seem to get the system to pass the create com object test.  I've re-installed IIS, I've re-installed Proclarity, I've fiddled with pretty much every setting that looks obvious in IIS, and I've banged my head against the desk a few times for good measure.

     

    Here's my diagnostic output:

    ProClarity Diagnostic Report

    PCDiagnosticTool.exe version: 6,3,2233,101

    August 1, 2011 - 1:55 pm

     

    System Information

    System Processor    :      Intel(R) Xeon(TM) CPU 2.80GHz

    Vendor ID           :                       GenuineIntel

    Processor ID        :   x86 Family 15 Model 2 Stepping 9

    Processor Speed     :                           2799 MHz

     

    Memory Information

    Total Physical Memory              :        2,096,596 KB

    Total Available Physical Memory    :        1,367,188 KB

    Total Paging File Size             :        4,042,296 KB

    Total Available Paging File Memory :        3,385,220 KB

     

    Statistics for Drive C:

    Sectors Per Cluster :                                  8

    Bytes Per Sector    :                                512

    Free Space          :                          29,008 MB

    Total Space         :                          40,100 MB

     

    Statistics for Drive D:

    Sectors Per Cluster :                                  8

    Bytes Per Sector    :                                512

    Free Space          :                         147,736 MB

    Total Space         :                         198,373 MB

     

    Operating System Information

    Platform              :                     Windows 2003

    OS Version            :                         5.2.3790

    Service Pack          :                   Service Pack 2

    OS Language           :          English (United States)

    User Default Locale   :          English (United States)

    System Default Locale :          English (United States)


    CreateControl Tests

    -- All Components Created Successfully --

     

    CreateCOMObject Tests

    Failure - PACCESS.PAccessMgr

     Error Message:  The system cannot find the path specified


    Monday, August 1, 2011 8:21 PM
  • Hello all,

    We finally got this to install (as well as ProClarity 6.2 on another server).

    We got the server re-provisioned as Windows 2003 Standard Edition SP2 (instead of Windows 2003 Standard Edition R2 SP2), and installed the .NET Framework only up to 2.0 (instead of 3.5).

    I'm not sure what made the difference, but ProClarity 6.3 and 6.2 both install perfectly on the new machines. I have not tried the hot-fix as yet.

    Sorry Justin - this probably doesn't help you!

    Regards,


    Les
    Thursday, August 4, 2011 2:14 AM
  • Hello all,

     

    We've been struggling with this problem for some time now even on a brand new Windows 2003 Standard Edition SP2 server. The new server helped me as eventviewer showed an issue with the IISRESET command during the install where IIS was not shutting down correctly but forcing a close and an earlier message showed minor issues with the Windows Remote Mangement Service.

    I stoppeed and disabled this service, re-ran the PAS installation and it completed successfully. Hurrah!

    I've now done this on 2 servers that I was having problems with and it worked both times. The service can be re-enabled after the install.

    I hope this helps some of you.

    Paul

    Wednesday, August 31, 2011 9:41 AM