Re: deploying webpart on two front end web server

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

{\rtf1\ansi\ansicpg936\deff0\deflang1033\deflangfe2052{\fonttbl{\f0\fnil\fprq2\fcharset0 MS Sans Serif;}}
\viewkind4\uc1\pard\lang2052\f0\fs20 Hi Rafia,
\par
\par How is everything going?
\par
\par Sincerely,
\par
\par Steven Cheng
\par
\par Microsoft MSDN Online Support Lead
\par \tab
\par
\par This posting is provided "AS IS" with no warranties, and confers no rights.
\par
\par
\par \pard\li720 --------------------
\par From: stcheng@xxxxxxxxxxxxxxxxxxxx (Steven Cheng[MSFT])
\par Organization: Microsoft
\par Date: Tue, 05 Feb 2008 07:48:09 GMT
\par Subject: Re: deploying webpart on two front end web server
\par
\par Hi Rafia,
\par
\par As for front-end multiple virtual server scenario, when you deploy webpart packages through stsadm.exe ,I think you'll need to do the deploy for each of those virtual servers(no matter whether they've shared the same persistence database or not).
\par
\par Sincerely,
\par
\par Steven Cheng
\par
\par Microsoft MSDN Online Support Lead
\par
\par
\par This posting is provided "AS IS" with no warranties, and confers no rights.
\par
\par
\par
\par
\par
\par \pard\li1440 --------------------
\par From: "Rafia Tapia" <deltaedge@xxxxxxxxxxxxx>
\par Subject: Re: deploying webpart on two front end web server
\par Date: Mon, 4 Feb 2008 12:41:16 -0500
\par
\par The problem is deploying in a farm environment consisting of multiple front
\par end web server. I was able to deploy the solution to a box that was stand
\par alone.
\par
\par I also want to know what is the best practise for deploying web parts in a
\par farm environment. The way I tried to do it through Visual studio was that
\par each of the webpart is a feature and then created a solution (.wsp) that
\par would install and activate the features. One of things I am not sure how it
\par would work in farm deployment is that when I add and delpoy the solution
\par using stsadm utility, would it put my webpart dll on all the front end web
\par server's GAC and would it also change the web.config file on all the front
\par end servers.
\par
\par "Steven Cheng[MSFT]" <stcheng@xxxxxxxxxxxxxxxxxxxx> wrote in message
\par news:U4pOrGKZIHA.360@xxxxxxxxxxxxxxxxxxxxxxxxx
\par > Thanks for your reply Rafia,
\par >
\par > So manually install webpart works, there might be something got incorrect
\par > in the feature based deployment. Have you tried a simplified scenario that
\par > create a single standard webpart and deploy it into the SPS server? I'm
\par > wondering whether this is a specific case or a common problem that might
\par > be
\par > related to the SPS server.
\par >
\par > Sincerely,
\par >
\par > Steven Cheng
\par >
\par > Microsoft MSDN Online Support Lead
\par >
\par >
\par > This posting is provided "AS IS" with no warranties, and confers no
\par > rights.
\par >
\par >
\par >
\par > --------------------
\par > From: "Rafia Tapia" <deltaedge@xxxxxxxxxxxxx>
\par > References: <us1y3W7YIHA.5900@xxxxxxxxxxxxxxxxxxxx>
\par > <l2eCUM$YIHA.4720@xxxxxxxxxxxxxxxxxxxxxx>
\par > Subject: Re: deploying webpart on two front end web server
\par > Date: Thu, 31 Jan 2008 11:02:54 -0500
\par >
\par > I have used the visual studio extension so it is visual studio that is
\par > creating all the different xml files and .webpart file. and yes I can
\par > deploy
\par > it manually and it works fine but when I try to install using the solution
\par > (.wsp) that visual studio has produce, I am running into problems.
\par >
\par > "Steven Cheng[MSFT]" <stcheng@xxxxxxxxxxxxxxxxxxxx> wrote in message
\par > news:l2eCUM$YIHA.4720@xxxxxxxxxxxxxxxxxxxxxxxxx
\par >> Hi Rafia,
\par >>
\par >> It seems you met some problem when try deploying your well developed
\par >> webpart controls.
\par >>
\par >> As you mentioned the features, are you deploying them as features
\par >> mentioned
\par >> in the following article?
\par >>
\par >> #Deploying web parts as a feature
\par >>
\par > http://sharepointnutsandbolts.blogspot.com/2007/05/deploying-web-parts-as-fe
\par >> ature.html
\par >>
\par >> For general test, I suggest you try a simplified webpart and also deploy
\par >> it
\par >> manually to see whether it works:
\par >>
\par >> #Writing Custom Webparts for Sharepoint 2007
\par >>
\par > http://blah.winsmarts.com/2006/05/14/writing-custom-webparts-for-sharepoint-
\par >> 2007.aspx
\par >>
\par >> Sincerely,
\par >>
\par >> Steven Cheng
\par >>
\par >> Microsoft MSDN Online Support Lead
\par >>
\par >>
\par >> This posting is provided "AS IS" with no warranties, and confers no
\par >> rights.
\par >>
\par >>
\par >>
\par >> --------------------
\par >> From: "Rafia Tapia" <deltaedge@xxxxxxxxxxxxx>
\par >> Subject: deploying webpart on two front end web server
\par >> Date: Wed, 30 Jan 2008 22:00:46 -0500
\par >>
\par >> Hi all
\par >> I have developed couple of web part using VS extension for sharepoint. I
\par >> have the setup.bat file as well as the solution file that VS creates. I
\par >> copied the setup.bat, mywebpart.wsp and all the file in the solution
\par >> directory to one of the front end web server but when I run setup.bat it
\par >> gives me an error on activating the features that comprises my web part.
\par >> The
\par >> error I am getting is that no features is installed in the farm and
\par >> therefore cannot be activated. Running setup.bat file is putting my .dll
\par >> in
\par >> gac and also copying all the files related to my features in the
\par >> appropriate
\par >> directories but when I look at the site feature via the web, I don't see
\par >> any
\par >> feature listed in the gallery.
\par >>
\par >> Can anyone please tell me what I am going wrong. What is the best way to
\par >> deploy web part in an environmental that consists of multiple front end
\par >> web
\par >> servers.
\par >>
\par >> Thanks
\par >>
\par >>
\par >>
\par >
\par >
\par >
\par
\par
\par \pard\li720
\par
\par \pard
\par
\par }

Relevant Pages

  • Re: deploying webpart on two front end web server
    ... \par Subject: Re: deploying webpart on two front end web server ... \par The problem is deploying in a farm environment consisting of multiple front ... \par would install and activate the features. ...
    (microsoft.public.sharepoint.portalserver.development)
  • Re: deploying webpart on two front end web server
    ... \par Subject: Re: deploying webpart on two front end web server ... \par creating all the different xml files and .webpart file. ... \par> It seems you met some problem when try deploying your well developed ... \par> As you mentioned the features, are you deploying them as features ...
    (microsoft.public.sharepoint.portalserver.development)
  • Re: deploying webpart on two front end web server
    ... The problem is deploying in a farm environment consisting of multiple front ... would it put my webpart dll on all the front end web ... deploying webpart on two front end web server ... As you mentioned the features, are you deploying them as features ...
    (microsoft.public.sharepoint.portalserver.development)
  • Re: deploying webpart on two front end web server
    ... I have used the visual studio extension so it is visual studio that is ... creating all the different xml files and .webpart file. ... It seems you met some problem when try deploying your well developed ... As you mentioned the features, are you deploying them as features ...
    (microsoft.public.sharepoint.portalserver.development)
  • RE: deploying webpart on two front end web server
    ... \par It seems you met some problem when try deploying your well developed webpart controls. ... \par As you mentioned the features, are you deploying them as features mentioned in the following article? ...
    (microsoft.public.sharepoint.portalserver.development)