locked
Deploy Sharepoint Remotely RRS feed

  • Question

  • I am currently attempting to set up continuous integration with a Sharepoint 2007 site, on Server 2008, WSS 3.  I can build the solution, create the wsp file and copy it to the sharepoint test server.  I have a drive mapped to the bin directory on the test server from the build server logging in as an active directory user that is also in the db_owner group on the sharepoint box as well as in the wss groups.  However, when I attempt to run the stsadmn command to add the solution to the store, from the build box I receive the "object not set to an instance.  The solution can not be added" error.  It works from the command line on the sharepoint server, and it will be added to the store if a run a batch file on that server using the mapped drive. Does anyone have any ideas?
    Friday, February 26, 2010 7:15 PM

Answers

  • Mark Russinovich (Sysinternals) has a set of tools (PSTools)

    That would allow the following:

    psexec \\YourRemoteComputer stsadm -o addsolution -filename c:\UploadFolder\YourSolution.wsp where c:\upload is the path on the remote computerMy favorite part is it doesnt require installation Just copy PsExec onto your executable path. Typing "psexec" displays its usage syntax. http://technet.microsoft.com/en-us/sysinternals/bb897553.aspx

    UpLoadWSP a fetaure on Codeplex that allows you to upload the SharePoint Solution Packages (WSP) Files from the Central Administration Web-Based Interface, without the need to write the usual STSADM commands, and without the need to be working remotly inside the Server///
    http://uploadwsp.codeplex.com/


    All in all I still prefer to have local access to the system....



    Cheers,


    -Ivan
    Ivan Sanders My LinkedIn Profile, My Blog, @iasanders.
    • Marked as answer by Mike Walsh FIN Saturday, February 27, 2010 8:11 AM
    Saturday, February 27, 2010 5:30 AM

All replies

  • I have sometime seen this issue in a remote execution set up. You may want to try executing the command from the server where it has to be deployed and check if that works.
    Friday, February 26, 2010 9:05 PM
  • The deployment has to occur locally on the server, you can't run stsadm remotely.
    • Proposed as answer by Ivan Sanders Saturday, February 27, 2010 3:24 AM
    • Unproposed as answer by Mike Walsh FIN Saturday, February 27, 2010 8:11 AM
    Saturday, February 27, 2010 2:06 AM
  • Hi Jeanie,

    Karla is correct..... This is one of the reasons for MSTSC / RDP is the maintainance and installation of applications on remote servers...



    Cheers,



    -Ivan
    Ivan Sanders My LinkedIn Profile, My Blog, @iasanders.
    Saturday, February 27, 2010 3:24 AM
  • Mark Russinovich (Sysinternals) has a set of tools (PSTools)

    That would allow the following:

    psexec \\YourRemoteComputer stsadm -o addsolution -filename c:\UploadFolder\YourSolution.wsp where c:\upload is the path on the remote computerMy favorite part is it doesnt require installation Just copy PsExec onto your executable path. Typing "psexec" displays its usage syntax. http://technet.microsoft.com/en-us/sysinternals/bb897553.aspx

    UpLoadWSP a fetaure on Codeplex that allows you to upload the SharePoint Solution Packages (WSP) Files from the Central Administration Web-Based Interface, without the need to write the usual STSADM commands, and without the need to be working remotly inside the Server///
    http://uploadwsp.codeplex.com/


    All in all I still prefer to have local access to the system....



    Cheers,


    -Ivan
    Ivan Sanders My LinkedIn Profile, My Blog, @iasanders.
    • Marked as answer by Mike Walsh FIN Saturday, February 27, 2010 8:11 AM
    Saturday, February 27, 2010 5:30 AM