Errors after installing Microsoft Office Web Apps

After installing Microsoft Office Web Apps on a SharePoint 2010 server, I got an error when displaying a word (*.docx) file:


An unexpected error has occurred.

Troubleshoot issues with Microsoft SharePoint Foundation.

Correlation ID: 848a2b82-a1a4-4faf-895e-1451464fa3b0

Date and Time: 3/10/2010 8:18:03 AM




After activating the Microsoft Office Web Apps feature on the site collection:



this error was resolved and Microsoft Office Word online started to show, but with a new error:

Word Web App cannot open this document for viewing due to an unexpected error.  To view this document, open it in Microsoft Word.
Error Id: 557be21f-f14d-4c76-9be5-d07f2a04b8f9, 20100310083103


This was because you need some additional steps when installing Microsoft Office Web App on a DC, see:


But the error was not resolved:

Word Web App cannot open this document for viewing due to an unexpected error.  To view this document, open it in Microsoft Word.
Error Id: 3b5ec400-4f95-495b-b663-320b9b9692be, 20100310124900



Followed the steps on:

Followed the steps on:

Followed the steps on:;_Practical_Tips.aspx


But the error still was not resolved, I am know rebuilding my server and starting from scratch, following the guide:

HTTP Error 500.19 – Internal Server Error after installing Microsoft Office Web Apps on a SharePoint 2010 Server

After installing Microsoft Office Web Apps (following the steps on on a Microsoft SharePoint 2010 server, I got a HTTP Error 500.19 when accessing the SharePiont Sites.



Config section ‘system.webServer/staticContent’ already defined. Sections must only appear once per config file. See the help topic <location> for exceptions

490:     </staticContent>
491:     <staticContent />
492:   </system.webServer




After removing the double <staticContent /> the site started working again.

InfoPath 2010 New Record action on webpart does not reset drop-down list box

If you have two lists in Microsoft SharePoint 2010, [Hardwareitems] and [Hardwaregroups] and the list [Hardwareitems] contains a “foreign key” to the list [Hardwaregroups], you can customize the form of the [Hardwareitems] list to contain a drop-down list representing the [Hardwaregroup]. Than you can show the form on a SharePoint [InfoPath Form Web Part], by connecting the list web part to the [InfoPath Form Web Part], you can directly edit and create new items on the same page as the list. Make sure you set the Postback settings of the [Submit picturebutton] and the [New Item picturebutton] to “Always”. If you don’t set postback settings to “Always” the drop-down list box will not be reset on clicking the [New Item picturebutton]

Some screendumps:





Add a “InfoPath Form Web Part”


Connect “InfoPath Form Web Part” and “List Web Part”



Action on “New item” picture button in InfoPath


Postback settings on “New item” picture button in InfoPath


Configuring Internet Explorer to Remember Your SharePoint Login Credentials


Go to Control Panel
Go to Internet Options
Click the “Security” tab
Click “Local Intranet”
Click “Sites”
Click “Advanced”
Add your SharePoint site into the “Local Intranet” zone.
Click OK to confirm on all Internet Options screens.
Open up Internet Explorer and go to your SharePoint site.  When prompted for username/password make sure you enter your credentials and check “Remember My Password”.
Your username/password should now be passed to the SharePoint site automatically.

Microsoft Sharepoint – Content Editor Webpart table

To use a standard styled table in the content editor webpart, use the following html code en paste the code in the “Source editor…” view of the content editor webpart.


<style type="text/css">
    table.tableIssues { border-collapse: collapse; border: 1px solid #C0C0C0; margin-left: 10px; margin-top: 10px; }
    td.cellIssues { border: 1px solid #C0C0C0; }
<TABLE class="tableIssues" cellSpacing=0 cellPadding=0>
<TD class="cellIssues" height=13 width=170>&nbsp;<STRONG>Subsysteem</STRONG></TD>
<TD class="cellIssues" height=13 width=200><STRONG>&nbsp;Development</STRONG></TD>
<TD class="cellIssues" height=13 width=200><STRONG>Test</STRONG></TD></TR>
<TD class="cellIssues" width=170>&nbsp;Configuratorl</TD>
<TD class="cellIssues" width=200>&nbsp;Jan</TD>
<TD class="cellIssues" width=200>&nbsp;Piet</TD></TR>
<TD class="cellIssues" width=170>&nbsp;Database</TD>
<TD class="cellIssues" width=200>&nbsp;Jan</TD>
<TD class="cellIssues" width=200>&nbsp;Piet</TD></TR>

Microsoft Office Sharepoint Server Automaticly sign-on with Windows Username and password

in IE, go to Internet options.  go to the security tab.  highlight Local Intranet and then click Custom Level.  at the bottom of the settings, make sure "automatic logon with current user name and password" is selected.  then click ok.  make sure Local Intranet is still highlighted and click the button called Sites.  in IE 7, i see a box that has an Advanced button.  click Advanced.  in IE 6, i think it just takes you to that page where you can verify that your sharepoint site is listed.  if it’s not listed, add it in.

IE will then automatically log users in.

Microsoft Office Sharepoint Server Performance and Closed WebParts (default.aspx?contents=1)

After some time a MOSS intranet site got very slow, the statusbar showed JavaScript:false….
After closing all “Closed” web parts, the site performance returned to its normal value.
Deleting all “Closed” web parts can be done on the Web Parts Maintenance page. The Web Parts Maintenance page can be accessed by adding “?contents=1” to your site URL: http://localhost/site1/default.aspx?contents=1
More about “Closed” Web Parts on:

Renaming a Microsoft Office Sharepoint Server or WSS server

When you want to rename you’re MOSS or WSS Server follow the steps on the following site:
But if you’re like me and renamed you’re server before you red that blog post. You’re SharePoint 3.0 Central Administration link will not work, DNS errors.
In mine case it was because I had some old alternate access mappings with the old servername in it,
but I could not change the mappings, because I could not get the Central Administration page loaded, without DNS errors.

To solve this problem I edited the HOST file in C:\Windows\System32\drivers\etc and added    <OLDSERVERNAME>
After a ipconfig /flushdns and ipconfig /registerdns the central administration page was accesible.
After changing the alternate access mappings to the new server name, the original HOST file could be restored