Hot answers tagged

4

For staging environment their is no set of rules, but it is depend what staging means. Best practice is never use the production managed accounts in staging, even never share service accounts between production farms. if you share the accounts then you will risk your production farm. if accounts are used in staging and people gets the password n they can ...


2

You'll need to detach and re-attach your content database. If you go to the central administration and your site collection information are missing do the following (Post restoration of your database) Stsadm -o deletecontentdb -url {Site Url} -databasename {Content Database Name} Stsadm -o addcontentdb -url {Site Url} -databasename {Content Database Name} ...


1

I view the idea of attaching debuggers to servers like staging to be due to a lack of proper logging, error handling, or defensive coding in general. If code is being deployed to staging where problems can't be diagnosed at all, then code is also being deployed to prod where problems can't be diagnosed at all. Instead, from Server-side code, you can write to ...


1

You need to install three environments for the same way , before that , you need to establish the proper environment , https://technet.microsoft.com/en-us/library/dn145990.aspx?f=255&MSPPError=-2147217396 . I suggest you need to apply the same settings between these environment because all settings you need to apply to the production environment , so if ...


1

I am not seeing any issue in this scenario as we had the same type of setup.Create and Configure the SharePoint farm in all 3 environment, same way. But difference will be the user account will be different in each domain. Always try to keep all environment to same patch level. If you want to move the sites from DEV to QA or to Prod..Or Bringing down from ...


1

I eventually used MSBuild to intervene before the WSP packaging step (step 3 from here). What you will need is the AfterLayout step. An explanation on Integrating post-processors in SharePoint builds you can find here.


1

Sorry, but this doesn't sound quite right. A staging environment should match the configuration of the prod environment. I wouldn't just tell someone to create a staging environment, I'd give them the script that configured prod so they could just run the script to duplicate the environment. Without the script, you'd at least need to know the service pack ...


1

Visual studio introduces a lot of changes to the OS, including the installation of many DLLs that wont make their way into a production environment. If all you want is to Debug, you can Debug Remotely by copying the remote debug folder from a visual studio installation into the server and attaching to the process remotely. It can be troublesome at times, ...


1

Wow. I am surprised someone would say that. My problem has been that there are so many ways of doing custom development for SharePoint 2010. Choosing-the-best-one/where-to-start has been my biggest challenge(s). The four that I have tried (and seen the most) are: Customizing the SharePoint templates (to create a different look/feel) Web Parts (.net) ASP....


1

That command is correct, but you need to make sure you run it on all servers. "When the process account for the Windows SharePoint Services Timer service (SPAdmin) is disabled (necessary in some installations for security reasons), the execadmsvcjobs operation must be run on all computers to perform provisioning and other administrative tasks that would ...


Only top voted, non community-wiki answers of a minimum length are eligible