- An error has occurred, which probably means the feed is down. Try again later.
Archive for November, 2014
#REBOOT – Biggest Community Event in the Country
Many of you are aware about the Community Platform last year with the brand #REBOOT and hosted seminars in 2 cities (Bangalore and Hyderabad) in a parallel track model. Reboot is an annual event where MVP’s with Support from Microsoft conduct seminars on selected technologies and it is hosted by MVPs across selected cities in India.
We are planning to do it this time in Pune, Delhi, Hyderabad and Bangalore. Any changes in Venue will be announced.
Agenda is not up yet so as soon as Venue decided we will share agenda as well with you folks….. Stay Tuned…………………….
SharePoint server Reports and Monitoring system
Introduction:
SharePoint is architecture to proactively monitor lot of system and manage them. Sole purpose is to catch issues before they occur. Still if issues do occur, the system should give the administrator the capability to debug the issues with the least amount of resistance.
Lets talk about logging database. Logging collects information from all the servers and store it in 1 database. They are similar to ULS logs. ULS logs are stored in 14\logs folder collected and in event logs. It strengthens the logging database and make it a valuable tool.
Another area to concentrate on is Reporting services. These Reports are present for site collection level and they are pretty robust. Administrators utilized them as what they are searching for, and uncovers where functionality is lacking. SharePoint 2010 health monitoring jobs have the ability to uncover issues, report them, and then SharePoint is able to automatically correct the issue (in some cases).
Monitoring and reporting capabilities together makes administrator to be proactive when it comes to SharePoint farm management. These capabilities can be leveraged with other SharePoint functions such as alerts, so that the team managing the SharePoint farm should be well versed in the performance of the installation.
SharePoint 2010 logging database information:
SharePoint 2010 logging database is a major enhancement to monitoring, debugging, and protecting the health of the farm.
By default, the database is called WSS_Logging . This database should be the starting point for administrators to collect and analyze information.
ULS Logs are available at C:\Program files\Common Files\Microsoft Shared\Web Server Extensions\14\Logs.
Access logging from SQL server:
- Open up SQL Server Management Studio.
- When asked for authentication, log in to the correct instance where SharePoint is running using your windows authentication credentials.
- Navigate to the WSS_Logging database and click on the plus sign to expand it.
- Under the toolbar at the top, click on the New Query button.
- In the new query window, type in the following query: Select * from RequestUsage.
- Click Execute.
Configuring what gets logged
SharePoint logging database capturing information can be modified via the Central Administration interface. The advantage of this being that the collection of information can be voluminous, which can also be the disadvantage.
Disk space, I/O, and just the amount of data needed to retain this information can become an issue. Being able to reduce the type of information that gets captured is critical to the wellness of your farm.
How to do it…
- Open the SharePoint 2010 Central Administration website.
- Click Monitoring.
- Under the Reporting section, click Configure usage and health data collection.
How it works…
The options presented in the usage and health data collection are logged to the logging database and to the ULS logs.
The health logging schedule can be modified to fit the needs (also known as Service Level Agreements) of your organization. It is important to remember that there is a hidden cost associated with the increased logging. The hidden cost is mainly in the form of storage and possibly performance.
The ULS logs have the potential to grow large. The logs can be moved to a new physical location (physical spindle), which does not contain the operating system or WFE/Application server software. The physical location reference must exist on all servers in the farm.
The location of the logs is set within Central Administration. To access the setting, go to Central Administration, click Monitoring, and then select Configure diagnostic logging. Under the Trace Log section is the Path. This contains the location of the ULS logs.
The logging information is retained for a period of 14 days by default. Using PowerShell you can change this parameter, using the following command:
Set-SPUsageDefinition -Identity <GUID> [-Enable] -DaysRetained 14
To be continued
When try to Publish webpart get below error “Invalid SPlistItem. The SPListItem provided is not compatible with a Publishing Page
When try to Publish webpart get below error “Invalid SPlistItem. The SPListItem provided is not compatible with a Publishing Page”
Event code: 3005
Event message: An unhandled exception has occurred.
Event time: 18/11/2014 08:59:05
Event time (UTC): 18/11/2014 08:59:05
Event ID: e2e43649e2164e399fe0aa85892a002c
Event sequence: 165799
Event occurrence: 17
Event detail code: 0
Application information:
Application domain: /LM/W3SVC/1827921427/ROOT-1-130607489469090399
Trust level: WSS_Custom
Application Virtual Path: /
Application Path: C:\inetpub\wwwroot\wss\VirtualDirectories\SITE\
Machine name: Machinename
Process information:
Process ID: 7392
Process name: w3wp.exe
Account name: Domain\SPaccountname
Exception information:
Exception type: ArgumentException
Exception message: Invalid SPListItem. The SPListItem provided is not compatible with a Publishing Page.
Request information:
Request URL: https://SiteURL/Pages/Test1.aspx
Request path: /Pages/Test1.aspx
User host address: IPAddress
User: Domain\SPaccountname
Is authenticated: True
Authentication Type: Negotiate
Thread account name: Domain\SPaccountname
Thread information:
Thread ID: 41
Thread account name: Domain\SPaccountname
Is impersonating: False
Stack trace: at Microsoft.SharePoint.Publishing.PublishingPage.GetPublishingPage(SPListItem sourceListItem) at Microsoft.SharePoint.Publishing.Internal.WebControls.PublishingPageStateControl.RaisePostBackEventForPageRouting(String ventArgument, SPRibbonCommandHandler control, RaisePostBackEventDelegate raisePostBackEventDelegate) at Microsoft.SharePoint.Publishing.Internal.WebControls.PublishingPageSaveAndStopEditHandler.RaisePostBackEvent(String eventArgument) at System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument) at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
Resolution :
DeActive and then ReActivate Sharepoint Site Publishing Infrastructure feature at both Site And Web level Scope.
To Deactivate at web level:
1. Open SharePoint Site -> Click on Site Actions -> Site Settings
2. Then click on Manage site features -> then Deactivate Publishing Infrastructure feature
3. Similarly you can deactivate at site level, Open SharePoint Site -> Click on Site Actions -> Site Settings, then Site collection administration -> then go to Site collection features
4. There deactivate Publishing Infrastructure feature.
To Reactivate again the feature, again follow above steps
You can try below powershell as well
$web = get-spweb “http://siteURL”
$correctId = $web.Lists[“Pages”].ID
$web.AllProperties[“__PagesListId”] = $correctId.ToString()
$web.Update()
$web.AllProperties[“__PublishingFeatureActivated”] = “True”
$web.Update()
Note: The key point is PublishingFeatureActivated bag which has to be true.
PowerPivot Thumbnail Rendering Error
Snapshots will not work if you have chosen to open the workbooks in the Client application. To remedy this, follow the below instructions:
To set the default open behavior for site collections
- In the SharePoint site collection, click Site Actions, and then click Site Settings.
- On the Site Settings page, under Site Collection Administration, click Site Collection Features.
- On the Features page, for the Open Documents in Client Applications by Default feature, click Activate (OpenInClient Feature is enabled) to open documents in the client application. Click Deactivate (OpenInClient Feature is disabled) to open documents in the browser.
To set the default open behavior for a document library by using the document library settings page
- On the <document library>: All Documents page, under Library Tools, click Library.
- In the library toolbar, click Library Settings.
- On the Document Library Settings page, click Advanced Settings.
- On the Advanced Settings page, in Opening Document in the Browser, select one of the following options:
Open in the client application When a user clicks on a document in this library, the document will open in the corresponding client application (if available). - Open in the browser When a user clicks on a document in this library, the document will open in the Web browser Web app for that document type. When the document is opened in the Web app, the user can then decide to open the document in the client application
- Use the server default When a user clicks on a document in this library, the document will open by using the default open behavior specified for the server on which SharePoint 2010 Products is installed.
You need to invoke the Getshapshot.exe (which is located here: C:\inetpub\wwwroot\wss\VirtualDirectories\80\bin>GetSnapshot.exe)*Note: Browse to C:\inetpub\wwwroot\wss\VirtualDirectories\80\bin>GetSnapshot.exe and make sure it is 50/56kb. I have seen instances where is is corrupt 0kb and it needs to be replaced.
To invoke the Getsnapshot.exe (re-title a workbook) via:
PowerPivot Gallery > Select a Report > Documents > Edit Properties > Title (give the workbook a title):
If None of the above solve your problem, Please try this also it solved my issue.
Under browser settings on the server (all SharePoint servers in the server farm), uncheck “Check for server certificate revocation”
Powellshell Script to backup WSP files
.But, what is we are creating a replica of an environment manually and we do not have WSP backup file or source code for the solution deployed in the farm. There is no option left for us to deploy the same solution into another environment without this two approaches.
For these kind of situations, please use below mentioned Powershell command
$farm = Get-SPFarm
$file = $farm.Solutions.Item(“solution.wsp”).SolutionFile
$file.SaveAs(“c:\Solution.wsp”)
This way, we can take backup of the solution which is already deployed into the server farm and can re-use it into another environment.
Download and Install Cumulative Update November 2014 for SharePoint 2013
Microsoft has released another SharePoint 2013 Cumulative Update in November 2014. Let me help you know how we can install November 2014 on SharePoint 2013 server.
Its per-requisites is either SharePoint 2013 SP1 or SharePoint 2013 March PU.
Now the most important part is how to install SharePoint server November 2014 Cumulative Update.
Previous releases of the SharePoint Server 2013 cumulative update included both the executable and the .CAB file in the same self-extracting executable download. Because of the file size, the SharePoint Server 2013 package has been divided into several separate downloads. One contains the executable file, while the others contain the CAB file. All are necessary and must be placed in the same folder to successfully install the update. All are available by clicking the same Hotfix Download Available link in the KB article for the release.
Here is link for all the updates:
Sharepoint Foundation 2013 has only 1 setup file 479983_intl_x64_zip.exe
Download SharePoint Foundation 2013 November 2014 CU
Now here the twist starts, SharePoint 2013 update has 3 setup files 479926_intl_x64_zip.exe, 479925_intl_x64_zip.exe, 479924_intl_x64_zip.exe: You can download this from:
Download SharePoint Server 2013 November 2014 CU
Project Server 2013 update has 3 setup files 480040_intl_x64_zip.exe, 479930_intl_x64_zip.exe, 479929_intl_x64_zip.exe: You can download this from below
Download Project Server 2013 November 2014 CU
The KB articles for September CU are available at the following locations:
- KB 2899468 – SharePoint Foundation 2013 November 2014 CU
- KB 2889944 – SharePoint Server 2013 November 2014 CU
- KB 2889949 – SharePoint Server 2013 with Project Server November 2014 CU
- No Office Web Apps Server 2013 CU released this month
Once the updated the downloaded you need to extract all the updates in 1 folder as shown below:
- Now when you run the main setup file ubersrv.exe file, you will be able to extract and install the update.
- Once you install these updates, you need to reboot the server
- Now system needs to be restarted.
- Follow the same steps on all SharePoint servers in farm.
- SharePoint PSconfig wizard on all servers.
- Finally it is installed
Note : SharePoint Server 2013 update contains the SharePoint Foundation update.Where as SharePoint Server 2013 with Project Server update contains Project Server update, SharePoint Server update and SharePoint Foundation update.
[Update 2014-11-12] When trying to download the fix for KB 2889944 (SharePoint Server 2013 November 2014 CU) you will notice that there are 4 files listed rather than the usual 3 files. One of the files is corrupt and does not belong to the CU. You can ignore it. When receiving the mail with the download links just skip the file with name 479985_intl_x64_zip.exe.
[Update 2014-11-12] When trying to download the fix for KB 2889949 (SharePoint Server 2013 with Project Server November 2014 CU) you will notice that there are 4 files listed rather than the usual 3 files. One of the files is corrupt and does not belong to the CU. You can ignore it. When receiving the mail with the download links just skip the file with name 479984_intl_x64_zip.exe.
For more information:
http://blogs.technet.com/b/stefan_gossner/archive/2014/11/11/november-2014-cu-for-sharepoint-2013-has-been-released.aspx
The .NET Core is now (OSS) Open Source Software
Satya Nadella is seriously changing the company. It doesn’t take a genius to realize that tech companies need to stop forcing their will manifested in managerial meetings down the customers throats and change it to be the other way around. Collaboration is now the new key success.
Microsoft not only did .NET get open sourced, they accepted the FIRST COMMUNITY PR TOO. This is an epic day. To get more details of this .NET (OSS) Open Sourced Software
https://github.com/dotnet/corefx/pull/31
MS committed a long time ago not to bring patent suits over the .NET specifications (the ECMA CIL specifications). This means anyone can freely implement the .NET specifications (which define the languages, platform, etc., but not all of the APIs for things like WinForms, ASP .Net, etc.), this is why Monopoly exists. They committed to this something like 10 years ago, and they have never violated that promise.
What happened today, is that they’ve opened the implementation, not just the specification. Which is awesome-sauce. But I just want to emphasize that parts of the platform (the specs) have been open for a long time.
As per my opinion Microsoft’s .NET is a very mature, very complete programming world.
- Great IDE
- Great language (C#, VB.NET I guess too)
- Can create extremely robust windows applications
- Can create great web applications (using asp.net webforms if you’re old school and ASP.NET MVC if you’re in the new stuff)
- Azure support “baked in” which greatly simplifies going to the cloud
- Free version of SQL Server that is extremely powerful (SQL Server Express, includes reporting services and full text indexing) and has, again, arguably the best tooling support of any RDBMS
Historically this has all been limited to the Windows stack (has to run on a windows server and developed on a windows computer, with expensive licenses). This move (and the previous moves leading up to this, and the vNext stuff coming) is beginning to tear down this restriction.