Object reference not set to instance of an object RRS feed

  • Question

  • Hi friends,

    I have one .WSP solution.when i try to add and deploy the solution Through stsadm command it worked fine .Now i want to do same procedure in another server  but it giving me ERROR as object reference not set to an instance of an object.  On doing some R&D  i found that stsadm.exe file is not available in my bin present in some other i copied the stsadm.exe  and pasted in bin folder.Even though it throwing same error.

    Can any one tell me what is the problem. Is this problem with the STSADM.EXE or something else.

    Thanks in advance.




    Tuesday, January 27, 2009 7:40 AM

All replies

  • stsadm.exe should be present , otherwise I doubt that if Sharepoint 2007 is properly installed on that machine. What is the path you are looking at ?



    Tuesday, January 27, 2009 8:30 AM
  • Hi,

    In my experience, object reference not set to an instance of an object is normally a problem with the code.  It is a reasonably common error and you should start debugging your code by checking each object to make sure it is a valid object before attempting to access it.  Have a look on your favourite search engine to get a more detailed explanation of how to fix it.


    Tuesday, January 27, 2009 8:54 AM
  • Hi mike,


      It shouldn't be problem with the code.bcz it worked fine in my demo server but coming to Production server it throwing error as Object reference not set to an instance of an object

    Tuesday, January 27, 2009 9:47 AM
  • Hi madhur,

    Sharepoint installed properly.and i am looking at the following path c:\program files\commonfiles\microsoft shareed\web server extensions\12\bin.



    Tuesday, January 27, 2009 10:01 AM
  • Have you tried examining the 12/Logs to see what might be going wrong?



    My blog on WSS / MOSS development is found at
    Tuesday, January 27, 2009 10:09 AM



    I think it is the issue about the user’s permission.


    1.      The account we use to run stsadm command should have following permission:
          a. Farm Account (System Account)
          b. DB Permission: DBCreator and Security Admin on all SharePoint Databases.
          c. Should be added to Local Administrators Group on all SharePoint Servers.

    2.      Farm account is the one which is being used by Windows SharePoint Timer Server.

    3.      Application Pool Identity of the web application can be different than Farm Account.


    This blog can help you:


    Hope it helps.

    Xue-Mei Chang
    Monday, February 2, 2009 5:41 AM