locked
Acive Server Pages error on ProClarity Web site RRS feed

  • Question

  •  

    We are using ProClarity Analytics Server v 6.2 and about 10 days ago upgraded to Analysis Services 2005. All through months of testing we did not have any problems with these two working together, but now that we are in production, we have twice had to do an IISRESET on our ProClarity App Server because all of a sudden the Active Server Pages seem to become unavailable. Specifically, we are seeing the following:

     

    On an individuals browser: Active Server Pages Error "ASP 0241"

     

    In the Application Error Log on the Server:

    Error: File /pas/en/src/PTabs.asp  CreateObject Exception. The CreateObject of '(null)' caused exception C0000005..

     

    Any suggestions?

    Wednesday, April 30, 2008 6:25 PM

All replies

  •  

    Carol,

     

    I saw this error recently when a user was trying to drill on members that didn't have any associated data.  Are there specific views or user actions that are occuring right before the error.  Have you run the PC Diag tool to see if all the files are properly installed?

     

    -Joey

    Wednesday, April 30, 2008 7:14 PM
  • Hi Carol and Joey,

    We have experienced exactly the same problem as well. An IISRESET was enough to resolve this, but we are now seeing that this error has started to recur.

    Please find below a couple of the errors we witnessed:

    1. On the Libraries web page, we see the error:

    Active Server Pages error ‘ASP 0241’

    CreateObject Exception

    2. When attempting to open a book, we see the following error:

    The website cannot display the page

    3. In the event viewer for the ProClarity Analytics Server Administration Tool, there were a number of errors around this time. Chief amongst these were:

     

    CreateObject Exception. The CreateObject of '(null)' caused exception C0000005

    A trappable error (E06D7363) occurred in an external object. The script cannot continue running.

     

    While restarting the IIS service has addressed this, it is still a stop-gap measure. Please could you help us determine the root cause for this behaviour, and guide us on how we could resolve this permanently?

    Thanks very much!

    Arshad

    Thursday, September 1, 2011 8:34 AM