UPDATE
Hotfix 950279 is available via contacting MS Support. After some "wrangling" ... this worked for us.
Overview
If you have just ran an "all content" deployment successfully ... don't start celebrating yet. Sure, it may have taken over a week with a hotfix or two to get it working. Just keep in mind that you will most likely want to setup deployment on a schedule for "only new, changed" content. That process turns out to be just as fun.
Issue
The first attempt at running a "only new, changed" content deployment (after a successful "all content" deploy) ended quickly with the following error:
Violation of PRIMARY KEY constraint 'PK__#ExportObjects____2F364608'. Cannot insert duplicate key in object 'dbo.#ExportObjects'. The statement has been terminated. at ...
Solution for pre-SP1 installations
Hotfix 936867 will fix this issue IF YOU HAVE NOT INSTALLED (the SP1s).
No Solution Yet for SP1 ...
If you have installed the SP1s, there is a much more drawn out solution. If you have previously installed 936867 and you install SP1 after ... your error will most likely return. Microsoft claims in their description of the MOSS SP1 ("2007 Microsoft Office servers Service Pack 1") that 936867 is included in the SP ... and this is it one of the "Issues that the service pack fixes" ... um LIE!
Great discussion about this issue here on MS's SharePoint forum.
April 18, 2008
April 15, 2008
Reporting Services ... Customizing the RSViewerPage.aspx Page
Overview ... Monday morning QB
Upon installation of Reporting Services there is a ReportServer folder created under the LAYOUTS directory that contains the .aspx files necessary to display reports. The primary file used for the display or reports is RSViewerPage.aspx. This page contains a large web part called ReportViewerWebPart. This web part includes both the toolbar/actions menu of the report, the report itself, and the parameters pane ... all in that one webpart. Mistake #1 by MS.
Another fun fact I noticed is that these pages are not child pages of a master. They are just stand alone .aspx files. Mistake #2 by MS. Hints, these pages do not include the global placeholders/navigation of the default.master nor the neighboring application.master (also found in the LAYOUTS directory).
When you deal with MS support these are they types of answers you get when you bring up such issues ... basically, wait till the next version.
Goal
Since by default the RSViewPage.aspx does not contain the global SharePoint navigation ... let's take a look at how to include it in the report page.
Solution
1. Make a backup of RSViewPage.aspx
2. Register the following at the top of the page:

3. Inlcude the following references inside the HEAD tag:

4. Place the following OnLoad event inside the BODY tag:
onload="javascript:if (typeof(_spBodyOnLoadWrapper) != 'undefined') _spBodyOnLoadWrapper();
5. Add the folowing lines of code:
That should do it!
I ran into some other issues that were installation specific ... so don't expect this to work perfectly for everyone ... but it will get you at least 90% of the way there.
Upon installation of Reporting Services there is a ReportServer folder created under the LAYOUTS directory that contains the .aspx files necessary to display reports. The primary file used for the display or reports is RSViewerPage.aspx. This page contains a large web part called ReportViewerWebPart. This web part includes both the toolbar/actions menu of the report, the report itself, and the parameters pane ... all in that one webpart. Mistake #1 by MS.
Another fun fact I noticed is that these pages are not child pages of a master. They are just stand alone .aspx files. Mistake #2 by MS. Hints, these pages do not include the global placeholders/navigation of the default.master nor the neighboring application.master (also found in the LAYOUTS directory).
When you deal with MS support these are they types of answers you get when you bring up such issues ... basically, wait till the next version.
Goal
Since by default the RSViewPage.aspx does not contain the global SharePoint navigation ... let's take a look at how to include it in the report page.
Solution
1. Make a backup of RSViewPage.aspx
2. Register the following at the top of the page:

3. Inlcude the following references inside the HEAD tag:

4. Place the following OnLoad event inside the BODY tag:
onload="javascript:if (typeof(_spBodyOnLoadWrapper) != 'undefined') _spBodyOnLoadWrapper();
5. Add the folowing lines of code:- The ms-globalTitleArea TD class will contain the background image for the theme.
- The Logo.gif image represents the site logo
- Use id=onetIdTopNavBarContainer and class=ms-bannerContainer for the TopNavBar
- The wssuc:TopNavBar is the SharePoint top navigation.
I ran into some other issues that were installation specific ... so don't expect this to work perfectly for everyone ... but it will get you at least 90% of the way there.
March 25, 2008
64 bit database migration (the easy way)
DB Installation: Win 2k3 R2 SP2, SQL Server 2005 32 bit
Goal: Win 2k3 R2 SP2, SQL Server 2005 64 bit
If you are planning on migrating from 32 to 64 bit for your SQL Server ... look no further. After reading though blogs, white papers, and books ... I decided to that there was an easier way to handle all this nonsense. In simple terms:
Keep in mind that if you have a DB server naming convention like SQL64SharePoint ... it probably won't work ... or if you cannot take the 32 bit DB offline ... that won't work either, etc, etc ...
If you have the means, this is ridiculously easier then trying this through STSADM ...
Things to remember:
Goal: Win 2k3 R2 SP2, SQL Server 2005 64 bit
If you are planning on migrating from 32 to 64 bit for your SQL Server ... look no further. After reading though blogs, white papers, and books ... I decided to that there was an easier way to handle all this nonsense. In simple terms:
- Backup the databases on the 32 bit DB server (let's call it SharePointDBServer)
- Take the web server offline, stop all services, sites, app pools
- Take SharePointDBServer offline
- Bring up a different 64 bit DB server with the same name as the old one (SharePointDBServer)
- Restore the backups to the 64 bit DB server.
- Reboot the web server
- Restart any services on the web server that were stopped
Keep in mind that if you have a DB server naming convention like SQL64SharePoint ... it probably won't work ... or if you cannot take the 32 bit DB offline ... that won't work either, etc, etc ...
If you have the means, this is ridiculously easier then trying this through STSADM ...
Things to remember:
- Pay attention to the Owner of the databases after they are created on the new 64 bit server ... this will most likely be domain/Administrator ... which may not be the Owner of the previous DBs.
- The services running on the new DB server will not be using the identities that were customized for the old DB server ... you will need to put in the correct user for some of those services.
March 12, 2008
Content Deployment ... 5323 and 4958
Overview
While attempting a simple content deployment the following errors where holding back the import phase ...
Event Type: Error
Event Source: Office SharePoint Server
Event Category: Content Deployment
Event ID: 5323
Date: 3/10/2008
Time: 10:22:57 PM
User: N/A
Computer: ServerName
Description:
Failed to transfer files to destination server for Content Deployment job 'Entire Site Collection'. Exception was: 'System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a send. ---> System.IO.IOException: Unable to write data to the transport connection: An established connection was aborted by the software in your host machine. ---> System.Net.Sockets.SocketException: An established connection was aborted by the software in your host machine
--------------------------------------------------------------------------------------------------------------------------------------------------
Event Type: Error
Event Source: Office SharePoint Server
Event Category: Content Deployment
Event ID: 4958
Date: 3/10/2008
Time: 10:22:58 PM
User: N/A
Computer: ServerName
Description:
Publishing: Content deployment job failed. Error: 'System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a send. ---> System.IO.IOException: Unable to write data to the transport connection: An established connection was aborted by the software in your host machine. ---> System.Net.Sockets.SocketException: An established connection was aborted by the software in your host machine
Solution
Turns out, this is related to "TCP Chimney" (read more here). There a registry value that needs to be changed here: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters in order for the content deployment to function.
Set the value of EnableTCPChimney = 0.
OR Command line: Netsh int ip set chimney DISABLED
Then reboot the server.
Setting the following values to zero will also be include in a soon to be released hotfix ...
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters - EnableRSS = 0
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters - EnableTCPA = 0
While attempting a simple content deployment the following errors where holding back the import phase ...
Event Type: Error
Event Source: Office SharePoint Server
Event Category: Content Deployment
Event ID: 5323
Date: 3/10/2008
Time: 10:22:57 PM
User: N/A
Computer: ServerName
Description:
Failed to transfer files to destination server for Content Deployment job 'Entire Site Collection'. Exception was: 'System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a send. ---> System.IO.IOException: Unable to write data to the transport connection: An established connection was aborted by the software in your host machine. ---> System.Net.Sockets.SocketException: An established connection was aborted by the software in your host machine
--------------------------------------------------------------------------------------------------------------------------------------------------
Event Type: Error
Event Source: Office SharePoint Server
Event Category: Content Deployment
Event ID: 4958
Date: 3/10/2008
Time: 10:22:58 PM
User: N/A
Computer: ServerName
Description:
Publishing: Content deployment job failed. Error: 'System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a send. ---> System.IO.IOException: Unable to write data to the transport connection: An established connection was aborted by the software in your host machine. ---> System.Net.Sockets.SocketException: An established connection was aborted by the software in your host machine
Solution
Turns out, this is related to "TCP Chimney" (read more here). There a registry value that needs to be changed here: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters in order for the content deployment to function.
Set the value of EnableTCPChimney = 0.
OR Command line: Netsh int ip set chimney DISABLED
Then reboot the server.
Setting the following values to zero will also be include in a soon to be released hotfix ...
February 15, 2008
15 days later ... more 6398, 6482, 7076s
Overview
They are back! After 15 long days of clear event logs (that's very long for SharePoint) the errors have returned.
While the "Attempted to read or write protected memory. This is often an indication that other memory is corrupt." specific errors are a memory ...
The new kids on the block are "Not enough storage is available to process this command.".
Solution
Installed the .NET 2.0 SP1 (available through Windows Update) and the errors have been gone for 11 days now ... that doesn't mean they won't be back!
They are back! After 15 long days of clear event logs (that's very long for SharePoint) the errors have returned.
While the "Attempted to read or write protected memory. This is often an indication that other memory is corrupt." specific errors are a memory ...
The new kids on the block are "Not enough storage is available to process this command.".
Solution
Installed the .NET 2.0 SP1 (available through Windows Update) and the errors have been gone for 11 days now ... that doesn't mean they won't be back!
Subscribe to:
Posts (Atom)
