• Upgrade your Internet Experience
  • Sign in
  • Microsoft.com
  • United States (English)
    Brasil (Português)Česká republika (Čeština)Deutschland (Deutsch)España (Español)France (Français)Italia (Italiano)Россия (Русский)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語)香港特别行政區 (中文)
 
 
Microsoft Developer Network
 
 
Home
 
 
Library
 
 
Learn
 
 
Downloads
 
 
Support
 
 
Community
 
 
Forums
 
 
 
Microsoft Developer Network > SharePoint Products and Technologies Forums > SharePoint - Development and Programming > stsadmin error: "Object reference not set to an instance of an object"
Ask a questionAsk a question
Search Forums:
  • Search SharePoint - Development and Programming Forum Search SharePoint - Development and Programming Forum
  • Search All SharePoint Products and Technologies Forums Search All SharePoint Products and Technologies Forums
  • Search All MSDN Forums Search All MSDN Forums
 

Answerstsadmin error: "Object reference not set to an instance of an object"

  • Thursday, February 22, 2007 2:45 PMThomas N. Sørensen Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Vote As Helpful
    0

    Hi,

    I have made a standard single server MOSS installation. Everything appears to be working fine, but I get errors when using stsadm to add solutions. (i.e. the Application Template Core, part of the server admin templates - http://www.microsoft.com/downloads/details.aspx?FamilyId=C1039E13-94DA-4D7D-8CAE-3B96FA5A4045&displaylang=en).

    Running i.e. "stsadm -o addsolution -filename ApplicationTemplateCore.wsp" gives the following error:

    Object reference not set to an instance of an object. ApplicationTemplateCore.wsp: The Solution installation failed.

    I get the excact same error, when I try to deploy Solutions using VSEWSS (November CTP).

    Any ideas to solve this would be greatly appreciated.

     

    Regards,

    Thomas N. Sørensen

    • ReplyReply
    • QuoteQuote
     

Answers

  • Thursday, February 07, 2008 5:37 PMksat Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    Vote As Helpful
    1

    Guilherme is close - it is permissions-related. 

     

    But, from what I've discovered this morning, it also has to do with the SQL Admin Content database.  The user executing the STSADM command must have full control access to this DB.  I had this same problem and had my DBA add my user account to this DB w/ full control and reran the scripts with full success. 

     

     

     

    • ReplyReply
    • QuoteQuote
     

All Replies

  • Tuesday, April 03, 2007 7:22 AMaki1 Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Vote As Helpful
    0
    I seem to have the exact same issue, did you manage to solve this?
    • ReplyReply
    • QuoteQuote
     
  • Monday, April 16, 2007 7:38 AMjos van vlimmeren Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Vote As Helpful
    0
    I have the same problem when i try to deploy webparts for moss 2007 in visual studio 2005. I'm making webparts on the same computer for a couple of months but it's only since a couple of day's I get this error with every project I try to deploy (even if there are no files in it).  I would appreciate it very much if anyone knows the solution to this
    • ReplyReply
    • QuoteQuote
     
  • Tuesday, April 24, 2007 4:07 PMJanie Pumphrey Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Vote As Helpful
    0
    I had the same error.  I didn't have permission on the configuration & content database.  After getting permission to the database, the error went away.  I'm not sure if this is what's causing the problem in your case, but it worked for me.
    • ReplyReply
    • QuoteQuote
     
  • Tuesday, May 08, 2007 2:39 PMGeorge Olson Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Vote As Helpful
    0

    I am having the same problem with Visual Studio.  Here is what I am doing as a work around.  If you look in the bin folder there is a batch file called setup.bat.  It is a pain, but you can remove and deploy the part by opening the command prompt and navigating to the bin folder.  Enter setup /uninstall or setup /install to remove or deploy the solution.  This is not installing the assembly in the GAC so you will still need to do this manually.  As a refresher go to start, then run and type 'assembly'.  Just drag and drop your assembly there.  Or as an alternative you can add some lines to the setup.bat, for example:

    Code Snippet

    @rem----------------------------------------------------------------------
    @rem    LDeploy
    @rem----------------------------------------------------------------------
    :LDeploy
        echo Adding solution %PackageName% to the SharePoint ...
        "%SPAdminTool%" -o addsolution -filename "%PackageFile%"

        echo Deploying solution %PackageName% ...
        "%SPAdminTool%" -o deploysolution -name "%PackageName%" -local -allowGacDeployment -url %TargetWebUrl%

        echo Activating feature WebPart5 ...
        "%SPAdminTool%" -o activatefeature -id 5be720ad-e963-404d-8026-2eecb5c4f6d0 -url %TargetSiteUrl%

        "%programfiles%\Microsoft Visual Studio 8\SDK\v2.0\Bin\gacutil.exe" -if WebPart5.dll

        iisreset

        goto :EOF

     

     

    • ReplyReply
    • QuoteQuote
     
  • Tuesday, October 16, 2007 12:57 PMKlaus Kurzawa Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Vote As Helpful
    0

     

    I do also get this error trying install radEditorMOSS.wsp (telerik.com).

     

    I have full permission in the farm but there must be something else that I should have permissions to.

     

    Any help appreciated...

     

    Klaus Kurzawa,

    Sweden

     

    (Updated by Klaus)
    Found a solution of my problem:

    My Computer -> Manage -> Added myself to WSS_RESTRICTED_WPG (Group for the Windows SharePoint Services farm administrator. This group is required for the WSS Administration Service to function.)

    • ReplyReply
    • QuoteQuote
     
  • Tuesday, October 23, 2007 9:50 AMSunildalavay Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Vote As Helpful
    0

    I am getting this error while trying to add the solution using stsadm -o addsolution -filename "<drive>:\ApplicationTemplateCore.wsp" command


    Initialization failure

    <drive>:\ApplicationTemplateCore.wsp: The Solution installation failed.


    Any help appreciated.


    Sunil

    • ReplyReply
    • QuoteQuote
     
  • Friday, November 02, 2007 1:09 PMJohn Truxton Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Vote As Helpful
    0

    I am getting the same thing  Sad  Anyone found a soultion yet?

     

     

    C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN>stsadm -o addsolution -filename d:\applicationtemplatecore.wsp

     

    Object reference not set to an instance of an object.
    d:\applicationtemplatecore.wsp: The Solution installation failed.

    • ReplyReply
    • QuoteQuote
     
  • Tuesday, November 06, 2007 1:42 PMGuilherme Rodrigues Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Vote As Helpful
    0

    According to this link: http://www.telerik.com/community/forums/thread/b311D-bachea.aspx, the problem is permission. First you have to be part of the Farm Administrator's. If you already part, go to My Computer --> Manage --> and add your user to the group WSS_RESTRICTED_WPG.
    • ReplyReply
    • QuoteQuote
     
  • Wednesday, June 11, 2008 9:32 PMBrad Cote Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Vote As Helpful
    0

    ksat -

     

    I am having the same problem. Someone else in my company set up SharePoint, and running deploysolution fails for any solution. Two questions -

     

    Which database - SharePoint Central Administration content database (SharePoint_AdminContent_guid)?

     

    Which database role memeberships do you check off to get full control? db_owner?

     

    Thanks

    Brad Cote

    • ReplyReply
    • QuoteQuote
     
  • Tuesday, November 25, 2008 10:28 AMinsy09 Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Proposed Answer
    Vote As Helpful
    0
    I experienced the same problem, I had extracted and coipied the file and had this error.

    Answer:
    Within propertises of the *.wsp file check the security tab. Ensure the 'users' account has full control and re-run. This worked for me you may need to add permissions for a different user though.

    Hope this helps.

    • Proposed As Answer byinsy09 Tuesday, November 25, 2008 10:28 AM
    •  
    • ReplyReply
    • QuoteQuote
     
Need Help with Forums? (FAQ)
 
© 2009 Microsoft Corporation. All rights reserved.
Terms of Use
|
Trademarks
|
Privacy Statement