Strange error on UpdateAccountInfo method

I wonder if anyone could shed any light on a odd error I'm receiving when certain users run the UpdateAccountInfoEx2 method.

"Object reference not set to an instance of an object" at Tessitura.WebAPI.TessituraUser.UpdateAccountInfo() at
Tessitura.WebAPI.Tessitura.UpdateAccountInfoEx2


A quick Google seems to suggest this is a fairly common ASP error, but not being an ASP progarmmer I can't really understand what might be causing it.

It's not having any negetive implications on our overall system, but just curious to know what the problem might be. I can't see any difference between those calls which work and those which don't.

Thanks
Mark



[edited by: Mark James at 6:20 AM (GMT -6) on 30 Sep 2013]
Parents
  • Does anything else share the iis server or is it just that one api

    If you have multiple websites/APIs etc does each have its own app pool or do they share "default app pool"?

  • We're actually just sub-licensees to the Southbank Centre so I'm not entirely sure what the set up is like there. I know that there are several websites using the system and it does appear that there are multiple APIs installed on the system (judging purely by the URL we use to access the ASMX page).

    I'll ask our contact at the SBC if he has time to get involved in this conversation.

    Thanks



    [edited by: Mark James at 6:20 AM (GMT -6) on 30 Sep 2013]
Reply
  • We're actually just sub-licensees to the Southbank Centre so I'm not entirely sure what the set up is like there. I know that there are several websites using the system and it does appear that there are multiple APIs installed on the system (judging purely by the URL we use to access the ASMX page).

    I'll ask our contact at the SBC if he has time to get involved in this conversation.

    Thanks



    [edited by: Mark James at 6:20 AM (GMT -6) on 30 Sep 2013]
Children
  • Shame.  I thought it was an app-pool sharing issue between two differing versions of dotNet.

     

    Is this in the client or is it a web issue?

    As its a webservice, it shouldn't care who it is sending the query as its a names sql user that runs this for everyone.

    If you can consistently replicate this, is this person an an area of your network with restrictions?  (You may have to speak to your network manager to find this out.)