Sharepoint deployment

Hi Sir,
Unable to see the deployed visual web parts after deployment. In my Visual Stdio 2013 I was successfully deploy the solution, but they are not reflecting in the gallery when I am trying to access the web parts in the aspx page. Please suggest where I could
be going wrong. I have also activated the feature for the site. I would kindly request for suggesting me where i could be wrong as I am new to sharepoint
Regards,
Satish
Sathiish Reddy

Hi Sathish,
These are key steps below. Please make sure that visual web part scope is at site level.
http://sharepoint.stackexchange.com/questions/66902/custom-webpart-is-not-displayed-in-gallery
Please remember to click 'Mark as Answer' on the answer if it helps you

Similar Messages

Crawl issue - warning: "This URL is part of a host header SharePoint deployment and the search application is not configured to crawl individual host header sites. This will be crawled as a part of ....a start address"

Hello all,
I have a multi-tenant environment in SharePoint 2010 server. Different tenants are hosted by one web app.
One content source has been created to crawl the all shared environment. (the only URL added in the content source settings = URL of the
web app)
Crawl everything under the hostname for each start address has been selected when creating this content source.
Now I have created a new tenant hosted by the same web app. For this new tenant I want to have a different crawl schedule. Simple , I just create a new content source and add the host URL of this tenant. With the same settings has the other content source.
After having started a full crawl I get 0 success and 1 warning : “This URL is part of a host header SharePoint deployment and the search application is not configured to crawl
individual host header sites. This will be crawled as a part of the host header Web application if configured as a start address.”
The first content source is well crawling the new tenant freshly created. Could you tell me where I’m wrong?
Thanks in advance
Regards
Baldo

Baldo,
In the configuration that you described you now have 2 content sources set to crawl the same content. If you have a content source with a start address of http://servername/ then it is going to crawl everything past that address. If you are now changing
the crawl schedule based on the individual site collections, you will need to move your start addresses further down the URL.
For Example:
1st Content Source:
http://servername/ as a start address would now become
http://servername/site1
http://servername/site2
2nd Content Source:
http://servername/site3
Also remember that all crawling must happen on the default zone. If you are trying to crawl a zone that the web application has been extended into, that will not work.
ScottC - Microsoft SharePoint Support

SharePoint Development,Deployment,Staging Environment system requirements(Hardware,Software,Required services)

Hi
   I want to know,
       1. System requirement for VM based Sharepoint 2013 development environment for minimum 3 user's
       2. SharePoint Topologies based on system architecture,system requirements
       3. General SharePoint Development environment with all required services
       4. SharePoint Deployment/Staging environment with all required services
Please help me to get the detailed informations on the above
Regards,
Siva

Hi Siva_SREC,
My environment built for three developers is a 3-tier SharePoint farm. The physical hardware has 32 GB RAM divided as the following virtual machines that all get hosted inside Windows Server 2012 Hyper-V (Datacenter edition)
Active Directory - 2 GB: Used to provide authentication to all joined virtual machines in the farm.
Enterprise Database - 6GB: Used to host all SharePoint databases and TFS database.
3 x SharePoint Farm - 6GB: It depends on how big your project are. For example, if you need each develop to develop SharePoint in particular farm then you should separate 3 farms. Each farm has a SharePoint farm configuration database and relevant database.
If you need multiple developers to develop on the same farm then you need to join another server to the existing farm.
Team Foundation Server - 4GB: Used to store source code and files and for development collaboration
We have remaining 2 GB and it's quite enough for the physical host to run Hyper-V. I've also had a few other machines for specific purpose. For example, I've done building a single WAC farm that provides Office Web App service to SharePoint. I could turn
off one of SharePoint machines when my developer isn't working in order to test OWA. If you are having chances to work on SharePoint 2013 app development project so you would need to have a dedicated machine acting as a Provider that is responsible for providing
web service to the SharePoint. Of course in this case you use provider-hosted app or the combination of SharePoint-hosted app and provider-hosted app. Personally, this machine shouldn't be joined to the AD domain controller. It should be a separate AD because
in real-world scenario, your provider isn't the same AD with client's environment.
In terms of SharePoint topology design, I'd consider configuring 2-tier farm (WFE & App) because in many cases, you would have to deploy your solution in the environment that has many machines separated each other.
At the end of the day, it all depends on your budget and the size of your project. I would say there is no silver bullet on the hardware requirement. For example, the hardware needed for large project is totally different from the one for just SharePoint
branding task.
Hope this helps you.
Regards,
-T.s
Thuan Soldier
A 23-year-old man loving Microsoft technologies and making crazy ideas on business journey.
SharePoint Vietnam |
Blog | Twitter

SharePoint Active Directory version support

Dear All,
My active directory is on windows server 2003 and now planning to install SharePoint 2013. I have windows server 2012 with seperate hardware and want to install Sharepoint on this server. I have some queries relates on the Sharepoint deployment.
Sharepoint 2013 is integrated with windows server 2003 Active Directory or need to upgrade with 2008 or R2 Active Directory?
Sharepoint 2013 integrates with Exchange server 2007 and 2010 or requried Exchange 2013 ?
Is there any specific edition of windows server and exchange server requirement e.g. (Standard/Enterprise) for SharePoint 2013 ?
Hi,
I also have some question that can Exchange Server 2007 be integrated with SharePoint 2013 Server. I know Exchange 2013 has more features and advantages but still wanted to confirm if this is possible, then how ?
Kindly reply at your earliest to assist me on queries.
Thanks

SharePoint 2013 will support Active Directory in a 2003 Native functional mode. The 2003 Domain Controllers should be running 2003 Service Pack 2.
SharePoint 2013 features, such as SiteMailbox, require Exchange 2013, as do other features (such as Project Server's tasks).
For SharePoint 2013, needs Standard or higher for Windows Server. There is no specific Exchange requirement.
For Exchange 2007 and SharePoint 2013, you should be able to use the OWA webparts (I believe they still offer them, haven't looked at it in a long time) and you can of course use Incoming and Outgoing email.
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

Configuring Apps for SharePoint 2013 - Host Header Sites

Hi All
I am busy planning our Apps for SharePoint deployment and one gotcha seems to be sites that use host headers. Our current deployment consists of the following:
2x WFE's (WFESRV1 and WFESRV2)
2x App Servers (APPSRV1 and APPSRV2)
The WFE's are load-balanced and we have 2 sites, portal.intranet.com and mysite.intranet.com. Both use host headers. I have gotten to the point where I will have a DNS zone called companyapps.com and a CNAME *.companyapps.com.
To which site do I point the CNAME to and what if I need both sites to be App enabled? Also, a lot of sites mention I need a empty site collection on a separate IP in order to use Apps with host headers. How would I use this empty site collection and
what would I name it?
We are on the March 2013 update.

May Be I understand your question as *.companyapps.com should be pointed to sharepoint server but where in IIS binding would you map *.companyapps.com
Actually, When you configure the APPS on server, the central admin > apps > you have to mention this *.companyapps.com. Now all apps will be "(yourname)-guid.companyapps.com"
Then you will have to create a app catalog where all the app related details will be stored
When App service application is created it is automatically added to default service connection. and this service connection to mapped to other web application(Application management, you see service connection)
If all is configured well apps will automatically work for all web apps

How to localize a custom FieldType in SharePoint 2013?

I'm trying to localize a custom FieldType that has been a functional part of our SharePoint deployment for some time. I've localized the field's configuration ASCX and backend code, but the portion of it which is installed via the fldtypes_*.xml files
eludes me. There are some distantly related examples here that don't seem to apply, and one or two that are bang on - but which unfortunately link to no longer existent pages. Can anyone spot what I'm doing wrong in the fldtype_*.xml file following
(or in other places perhaps)? Other portions of the UI are successfully localized using the same ApplicationResources resource file, however when I view the configuration of a list with one of these fields, its type is displayed as "$Resources:ApplicationResources,ResourceField_Name;"
instead of the localized value.
<FieldTypes>
<FieldType>
<Field Name="TypeName">ResourceField</Field>
<Field Name="TypeDisplayName">$Resources:ApplicationResources,ResourceField_Name;</Field>
<Field Name="TypeShortDescription">$Resources:ApplicationResources,ResourceField_Description;</Field>
<Field Name="ParentType">URL</Field>
<Field Name="UserCreatable">TRUE</Field>
<Field Name="ShowOnListCreate">TRUE</Field>
<Field Name="ShowOnSurveyCreate">TRUE</Field>
<Field Name="ShowOnDocumentLibraryCreate">TRUE</Field>
<Field Name="ShowOnColumnTemplateCreate">TRUE</Field>
<Field Name="Sortable">TRUE</Field>
<Field Name="Filterable">TRUE</Field>
<Field Name="FieldTypeClass">...</Field>
<Field Name="FieldEditorUserControl">...</Field>
<PropertySchema>
<Fields>
<Field Name="ModelViewName" DisplayName="ModelViewName" Type="Text" Hidden="TRUE">Model View Name</Field>
<Field Name="ContextProperty" DisplayName="ContextProperty" Type="Text" Hidden="TRUE"/>
<Field Name="RichText" DisplayName="RichText" Type="Boolean" Hidden="TRUE" Value="TRUE" />
<Field Name="RichTextMode" DisplayName="RichTextMode" Type="Text" Hidden="TRUE" Value="FullHtml" />
</Fields>
</PropertySchema>
</FieldType>
</FieldTypes>

Hi,
How about removing the semicolon at the end of your resource referenced string?
Feel free to reply with the test result if the issue still exists.
Thanks
Patrick Liang
Forum Support
Please remember to mark the replies as answers if they
help and unmark them if they provide no help. If you have feedback for TechNet
Subscriber Support, contact [email protected]
Patrick Liang
TechNet Community Support

Error importing SharePoint site collection - "there is an error during importing the Roles tag"

Hi, we are having trouble restoring a SharePoint 2010 site collection using our DPM 2012 installation. The recovery process goes fine (restore of the database, attach to the sql server, export into WFE's filesystem) and the last phase, the SharePoint import,
seems to end with an exception. We see this in the WssCmdletsWrapperCurr.errlog file:
Caught Exception while trying to import Url .....
Exception message =
There is an error during importing the Roles tag
Exception Stack =
at Microsoft.SharePoint.Deployment.ReadAttribute.String(....
It looks like it is a SharePoint import issue, but I'm not sure. We have tried to restore the site into an empty one, and the exception appears again, although it *seems* that the content has been recovered. We have imported using the security info
on the recovery point.
I've searched for that error message in the Net but I've been unable to find anything appropriate.
Do you have any hints?
Thanks.

Hi, we are having trouble restoring a SharePoint 2010 site collection using our DPM 2012 installation. The recovery process goes fine (restore of the database, attach to the sql server, export into WFE's filesystem) and the last phase, the SharePoint import,
seems to end with an exception. We see this in the WssCmdletsWrapperCurr.errlog file:
Caught Exception while trying to import Url .....
Exception message =
There is an error during importing the Roles tag
Exception Stack =
at Microsoft.SharePoint.Deployment.ReadAttribute.String(....
It looks like it is a SharePoint import issue, but I'm not sure. We have tried to restore the site into an empty one, and the exception appears again, although it *seems* that the content has been recovered. We have imported using the security info
on the recovery point.
I've searched for that error message in the Net but I've been unable to find anything appropriate.
Do you have any hints?
Thanks.

Search not working in SharePoint 2013 - Event ID 1314 - Crawler:Gatherer Plugin

I have one web application and three host-named site collections. I had read an article that I just need to have the web application URL in the content source for the search to work, but that didn't resolve my issue.
https://webapplication - main root web application
https://staff.domain.com - Host name site collection
https://services.domain.com Host name site collection
https://sharepoint.domain.com host name site collection.
I have also created the registry entry for BackConnectionHostNames also.
Under Search Application topology I have all green check marks, but searchable items are listed as 0.
I am getting the following errors on my SharePoint 2013 server.
The start address https://sharepoint.domain.com cannot be crawled.
Context: Application 'Connect_Search', Catalog 'Portal_Content'
Details:
This URL is part of a host header SharePoint deployment and the search application is not configured to crawl individual host header sites. This will be crawled as a part of the host header Web application if configured as a start address.
(0x80040de4)
The start address https://webapplication cannot be crawled.
Context: Application 'sharepoint_Search', Catalog 'Portal_Content'
Details:
The secure sockets layer (SSL) certificate sent by the server was invalid and this item will not be crawled.   (0x80041223)
The start address https://services.domain.com cannot be crawled.
Context: Application 'sharepoint_Search', Catalog 'Portal_Content'
Details:
This URL is part of a host header SharePoint deployment and the search application is not configured to crawl individual host header sites. This will be crawled as a part of the host header Web application if configured as a start address.
(0x80040de4
The start address https://staff.domain.com cannot be crawled.
Context: Application 'Sharepoint_Search', Catalog 'Portal_Content'
Details:
This URL is part of a host header SharePoint deployment and the search application is not configured to crawl individual host header sites. This will be crawled as a part of the host header Web application if configured as a start address.
(0x80040de4)
any help would be greatly appreciated.

Hello Derek,
as I see you are using Host Named Site Collections.
You have two Problems.
First:
The start address https://webapplication cannot be crawled.
Context: Application 'sharepoint_Search', Catalog 'Portal_Content'
Details:
The secure sockets layer (SSL) certificate sent by the server was invalid and this item will not be crawled.   (0x80041223)
You Need to fix this first!! You have a Problem with your SSL Certificate!
The Webapplication is where normally the Search Crawler would enter the crawl in a Host Named Site Collection Scenario.
As soon as you fix this, remove the entries for your Host Named Site Collections from the Crawler. Just leave your Webapplication in it. The HNSC will be crawled automatically. This is the following of your Errors:
The start address https://services.domain.com cannot be crawled.
Context: Application 'sharepoint_Search', Catalog 'Portal_Content'
Details:
This URL is part of a host header SharePoint deployment and the search application is not configured to crawl individual host header sites. This will be crawled as a part of the host header Web application if configured as a start address.
(0x80040de4
Be sure that you created your Webapplication NOT
AS A HOST NAMED WEB APPLICATION!
If you can check everything I mentioned above, your search should hopefully start to work.
King regards!

Changing sql server service and sql server agent service startup account in SQL Server hosting SharePoint DB

Hi
i have a sharepoint deployment with one SQL Server (running on VM) hosting the config DB and another SQL Server (Physical Host because VM was running out of space) to host the huge Content DBs. I need to schedule automatic backups of the Content DBs to a
network share. For that i need to run the SQL Server Service with an account having permissions to the share as suggested in https://support.microsoft.com/kb/207187?wa=wsignin1.0
I tried changing the logon as a service account to a domain
account which has permissions to the Network Share and is also in local Administrators group of SQL Server and has "public and sysadmin" roles in SQL Server but that caused an issue. the SharePoint Web Application started showing a White Screen so
I had to revert back to the default accounts i.e. NT Service\SQLSERVERAGENT and NT Service\MSSQLSERVER. I viewed the event logs . These are the types of error i got after changing the logon as a service account to a domain account
1) Information Rights Management (IRM): Retried too many times to initialize IRM client. Cannot retry more. Retried times is:0x5.
System
Provider
[ Name]
Microsoft-SharePoint Products-SharePoint Foundation
[ Guid]
{6FB7E0CD-52E7-47DD-997A-241563931FC2}
EventID
5148
Version
15
Level
2
Task
9
Opcode
0
Keywords
0x4000000000000000
TimeCreated
[ SystemTime]
2015-02-02T04:46:04.750899500Z
EventRecordID
176477
Correlation
[ ActivityID]
{8FACE59C-1E17-50D0-7135-25FDB824CDBE}
Execution
[ ProcessID]
6912
[ ThreadID]
8872
Channel
Application
Computer
Security
[ UserID]
S-1-5-21-876248814-3204482948-604612597-111753
EventData
hex0
0x5
2)
Unknown SQL Exception 0 occurred. Additional error information from SQL Server is included below.
The target principal name is incorrect. Cannot generate SSPI context.
System
Provider
[ Name]
Microsoft-SharePoint Products-SharePoint Foundation
[ Guid]
{6FB7E0CD-52E7-47DD-997A-241563931FC2}
EventID
5586
Version
15
Level
2
Task
3
Opcode
0
Keywords
0x4000000000000000
TimeCreated
[ SystemTime]
2015-02-02T07:01:35.843757700Z
EventRecordID
176490
Correlation
[ ActivityID]
{50B4E59C-5E3A-50D0-7135-22AD91909F02}
Execution
[ ProcessID]
6912
[ ThreadID]
5452
Channel
Application
Computer
Security
[ UserID]
S-1-5-17
EventData
int0
0
string1
The target principal name is incorrect. Cannot generate SSPI context.

Hi Aparna,
According to your description, you get the above two errors when scheduling backups of Content DB. Right?
Based on those two error messages, they are related to the service principal name(SPN) for SQL Server service. Please verify the if the SPN is registered successfully. You can view it in ADSI Edit or use command line. Please see:
http://blogs.msdn.com/b/psssql/archive/2010/03/09/what-spn-do-i-use-and-how-does-it-get-there.aspx
When installing SQL Server, those two services below should be registered:
MSSQLSvc/servername:1433
MSSQLSvc/servername
Please check if those SPNs or duplicated SPNs exist. You can use command to reset SPN or remove duplicated SPN and add new one. See:
Setspn.
We have also met this issue when this SPN is registered under Administrator. Please try to register it under Computer. You can add it in ADSI Edit.
If you have any question, please feel free to ask.
Simon Hou
TechNet Community Support

Citrix Netscaler AppXpert with Sharepoint 2010 Page Edit Issue

Posting this as a questions and discussion point.
The issue is in using Citrix Netscaler with AppXpert with SharePoint 2010. I've seen this issue for two customers.
Configurations:
- Citrix Netscaler as the load Balancer
- Netscaler AppXpert for SharePoint deployed on Netscaler (using either AppXpert version 1.1 or 2.0)
- SharePoint 2010 Standard or Enterprise editions
Issue:
A SharePoint user with appropriate rights go to a SharePoint page. They choose Edit page, make changes and want to save changes. At this point all SharePoint ribbon options on the top are greyed out. End result, users are not able to make changes to their
site pages. Issue happens for everyone including Farm Admins.
Cases:
a. The users are able to edit and save SharePoint wiki pages if I point user's PC to the SharePoint web server WFE by changing their local host file.
b. On Citrix Netscaler, if I use the traditional load balancing i.e. without Citrix AppXpert, then the users are able to edit and save the pages. That is an option if the customer is using SharePoint 2010 Standard. That is not an option if a customer is
using InfoPath forms. InfoPath is a feature of SharePoint 2010 Enterprise edition. Citrix AppXpert for SharePoint is needed to make the InfoPath work. Else the users get session errors when they use InfoPath Web forms.
c. The issue happens on almost all combination of OS and browser. XP, vista, Win 7, Win8, Win8.1, IE8, 9, 10, 11 and other browsers like chrome etc as well.
Please share your ideas and suggestions.

Hi Faisal,
As I understand, the issue will be solved when end users directly connect to SharePoint WFE servers. Since the issue is related to third party products, I'd recommend you contact their support engineer for sufficient resource and assistance. For your convenience:
http://discussions.citrix.com/forum/150-support-forums/
Should you need more assistance, let me know. Thanks for the understanding.
Regards,
Rebecca Tu
TechNet Community Support

SP2013 - Unable to Debug/Deploy from VS2013/VS2012

I've been working on this issue for a while and troubleshooted from every angle I can think.   Can someone please help me squash this so I can get back to
work?
Problem:
I’m receiving very generic errors when trying to deploy/debug either an SP2013 App project or Web Part project from VS2013 or VS2012. I’m leaning towards this being a permissions related error even though I’ve granted myself Admin to almost every layer.
What I’ve tried so far:
VS is running as Administrator
I’m a Local Admin, SharePoint Farm Admin, Site Collection Administrator (on the root site as well as the App Catalog site collection), SPShellAdmin
I’m a DBO on all SP Content DBs as well as a sysadmin
I’m using the hosts file IP redirect (Custom Host Header fix)
I’ve tried from both VS 2012 and 2013 (both installed on the SP dev box)
I’ve added my user to the User Policy Permissions for the Web Application with Full Control
The App Management and Subscription Settings Service Applications are configured and running
The App Prefix has been configured
App DNS has been configured and tested with: ping Apps-12345678ABCDEF.<domainname>.com
Web Part deployment error:
Active Deployment Configuration: Default
Skipping deployment step because a pre-deployment command is not specified.
Error occurred in deployment step 'Recycle IIS Application Pool': A task was canceled.
Exception Message: A task was canceled.
Exception Type Name: System.Threading.Tasks.TaskCanceledException
Exception Stack Trace:    at Microsoft.VisualStudio.SharePoint.SharePointConnectionInternal.WaitOnExecuteCommandTask(Task task, CancellationTokenSource cts)
   at Microsoft.VisualStudio.SharePoint.SharePointConnectionInternal.ExecuteCommand[T,TResult](String commandId, T arg)
   at Microsoft.VisualStudio.SharePoint.SharePointCachedConnection.ExecuteCommand[T,TResult](String commandId, T arg)
   at Microsoft.VisualStudio.SharePoint.SharePointProjectCommands.DoesSolutionWithIdExist(ISharePointConnection connection, Guid arg)
   at Microsoft.VisualStudio.SharePoint.Deployment.RecycleApplicationPoolStep.CanExecute(IDeploymentContext context)
   at Microsoft.VisualStudio.SharePoint.Deployment.ConfigurationExecutor.Execute()
   at Microsoft.VisualStudio.SharePoint.Deployment.WspDeploymentHandler.Deploy()
Error when attempting to add a new item (List) to the App project:

Hi,
A suggestion is that you can check whether you have configured your develop environment for SharePoint 2013 correctly.
The links below about how to configure develop environment for SharePoint 2013 for your reference:
http://msdn.microsoft.com/en-us/library/office/ee554869.aspx
http://blogs.msdn.com/b/timquin/archive/2013/01/22/setting-up-visual-studio-2012-for-sharepoint-2013-development-offline.aspx
http://www.instantquick.com/index.php/configuring-visual-studio-2012-for-sharepoint-2013-and-office-2013-development
Feel free to reply if there are still any questions.
Best regards
Patrick Liang
TechNet Community Support

Content deployment problem

An incremental content deployment job that has been working for years between two SharePoint 2007 farms has stopped working. There seems to be a problem with one of the sub-sites, but excluding it from the deployment job does not solve the problem and
as far as the logs say, some parts of that site are still being exported and imported (unsuccessfully).
The farms are both post SP3 but not exactly the same version. There also seems to be a slight difference between a specific list in the root sire between the two sites. I am sure the first difference has been around for a long time, the second one I am not
sure but I am quite positive the error in the import process does not refer to the list in question.
This is the relevant log fragment:
[3/16/2015 8:38:44 PM]: Verbose: Updating field ContentTypeId.
[3/16/2015 8:38:44 PM]: Verbose: Updating field _HasCopyDestinations.
[3/16/2015 8:38:44 PM]: Verbose: Updating field _CopySource.
[3/16/2015 8:38:44 PM]: FatalError: Object reference not set to an instance of an object.
   at Microsoft.SharePoint.Deployment.ContentTypeSerializer.GetContentType(SPContentType sourceContentType, ImportObjectManager importObjectManager, Boolean isParentSystemObject)
   at Microsoft.SharePoint.Deployment.ContentTypeSerializer.ProcessContentType(SPContentType sourceContentType, String contentTypeXml, ImportObjectManager importObjectManager, Boolean IsParentSystemObject)
   at Microsoft.SharePoint.Deployment.ContentTypeSerializer.SetObjectData(Object obj, SerializationInfo info, StreamingContext context, ISurrogateSelector selector)
   at Microsoft.SharePoint.Deployment.XmlFormatter.ParseObject(Type objectType, Boolean isChildObject)
   at Microsoft.SharePoint.Deployment.XmlFormatter.DeserializeObject(Type objectType, Boolean isChildObject, DeploymentObject envelope)
   at Microsoft.SharePoint.Deployment.XmlFormatter.Deserialize(Stream serializationStream)
   at Microsoft.SharePoint.Deployment.ObjectSerializer.Deserialize(Stream serializationStream)
   at Microsoft.SharePoint.Deployment.ImportObjectManager.ProcessObject(XmlReader xmlReader)
   at Microsoft.SharePoint.Deployment.SPImport.DeserializeObjects()
   at Microsoft.SharePoint.Deployment.SPImport.Run()
[3/16/2015 8:38:44 PM]: Progress: Import Completed.
[3/16/2015 8:38:44 PM]: Finish Time: 3/16/2015 8:38:44 PM.
[3/16/2015 8:38:44 PM]: Completed with 0 warnings.
[3/16/2015 8:38:44 PM]: Completed with 1 errors.
Changing the site selection or creating a new job with just the root site selected did not solve the problem either.
We currently cannot run a full deployment job because of disk space limitations.
Can we do anything besides creating a new content database and starting over?

Have you had a look at Troubleshoot content deployment and Stefan Goßner's Content
Deployment - Best Practices?
You may need to increase the ULS logging level for Content Deployment to see more information about what is happening.
Jason Warren
@jaspnwarren
jasonwarren.ca
habaneroconsulting.com/Insights

Retain Items and item history on feature re-deployment

Using SharePoint feature/solution I have created a list instance with 4 fields and is currently in production.
I got a request to add another 3 fields to existing list instance so making it 7 fields now.
While deploying the updated package the data and its version history is vanished too.
Is there any other way to retain data/version history and also add 3 new columns to the list schema?
One way is to do it with Powershell but just wondering if there is anything provided by SharePoint deployment of features?

Hi,
Solution re-deployment will extract the old list instance, create a new list instance, therefore, the data with version history will lose.
A workaround is that you can export the existing list items with version history to somewhere, re-deployment, then import these items back.
Two links about accessing list items using PowerShell for your reference:
http://blogs.msdn.com/b/rcormier/archive/2012/11/16/how-to-copy-sharepoint-documents-between-site-collections-using-powershell.aspx
http://get-spscripts.com/2011/10/copy-sharepoint-lists-and-document.html
What I would recommend is that, if you just want to update a list instance(not list definition), add fields using PowerShell would be an easier and cleaner way. In
this way, it could be finished with just a few lines of script without extract and deploy the solution in your environment, what’s more, there is no need to worry about the data loss in the process.
About how to add fields using PowerShell:
http://adicodes.com/add-fields-to-list-with-powershell-in-sharepoint-2010/
Thanks
Patrick Liang
Forum Support
Please remember to mark the replies as answers if they
help and unmark them if they provide no help. If you have feedback for TechNet
Subscriber Support, contact [email protected]
Patrick Liang
TechNet Community Support

SharePoint 2013 On premise Multi-Tenancy vs full SharePoint

Hi,
We have requirements coming in from joint ventures who need their own site collections/sites.
Rather than trying to implement them on our current full Enterprise SharePoint environment we would setup a seperate SharePoint deployment in multi-tenancy mode with partitioned service applications.
Before I offer this up as an option I need to let them know if there are any limitations to a multi-tenant environment over the full versions. I have seen reference to PerformancePoint not being available and it being harder to migrate to O365 in the
future if needed however I have not found a definitive list.
Does anyone know where I can find a list of the limitations (if one exists!)?
Thanks,
Mark

There is no specific list of limitations in one concise spot. But if you read Spence Harbar's articles on Multi-tenancy (for 2010 and 2013) you will find lists of things that don't work in multi-tenancy. For example, there are several services
like the Visio graphics service that don't support partitioning of their databases and are therefore a problem for multi-tenancy. As you mentioned PerformancePoint is another one. Read both articles and you should be able to compile a list of what
you need to know.
http://www.harbar.net/articles/sp2010mt1.aspx
http://www.harbar.net/articles/sp2013mt.aspx
Paul Stork SharePoint Server MVP
Principal Architect: Blue Chip Consulting Group
Blog: http://dontpapanic.com/blog
Twitter: Follow @pstork
Please remember to mark your question as "answered" if this solves your problem.

Sharepoint 2010 appended port number in the public URL when redirect

I'm new in sharepoint so please bear with me.
We have a sharepoint deployment that has 4 WFEs, each WFE has 4 sites, all on a different port number. For example;
Site 1: http://site1.server1:11111
Site 2: http://site1.server1:22222
Site 3: http://site1.server1:33333
Site 4: http://site1.server1:44444
We have a load balancer that use a public URL to all these sites. For example;
Site 1: http://site1
Site 2: http://site2
Site 3: http://site3
Site 4: http://site4
Here is the problem. Some of the link in the sharepoint site, when click, the URL is appended with the port number at the end of the public URL. For example, http://site1:11111.
I tried playing around with the AAM but it doesnt yield anything. Any advise from the expert would be appreciated.

Hi,
Look at your default AAM. This controls how the URL is appended or not. You also need to look at the site bindings in IIS and make sure you have them for each site, for port 80. And you need an alternate access mapping that routes site.server:Port
to site if your desired outcome is to have any load balanced call route back to the default alternate access mapping of http://site1
you would have a binding on http://site1 on port 80 in iis, and a host header associated with this site.
Also, if you are using path based sites, this will only work for one site. You can tell if you're using path based site collections if you see a / in front of their names inside view all site collections.
Microsoft recommends using Host named site collections, check out this technet
http://technet.microsoft.com/en-us/library/cc424952(v=office.15).aspx
Stacy www.sharepointpapa.com

Sharepoint deployment

Similar Messages

Maybe you are looking for