.NET Questions and Solutions

Symptoms
This article describes the Microsoft Office PerformancePoint Server 2007 issues that are fixed in the hotfix package that is dated April 28, 2009.
This article describes the following items about the hotfix package:The issues that the hotfix package fixes.The prerequisites for installing the hotfix package.Whether you must restart the computer after you install the hotfix package.Whether the hotfix package is replaced by any other hotfix package.Whether you must make any registry changes.The files that the hotfix package contains.
Resolution
PerformancePoint Server 2007 hotfixes are created for the release version of PerformancePoint Server 2007. All PerformancePoint Server 2007 hotfix packages are cumulative.
A hotfix package is available for PerformancePoint Server 2007. The build of this hotfix package is 3.0.4315.00. The release version of PerformancePoint Server 2007 must be installed before you apply this hotfix. The build of the release version of PerformancePoint Server 2007 is 3.0.3520.0.
Issue that the hotfix package fixesThis hotfix package fixes the following PerformancePoint Server 2007 Monitoring and Analytics issues that were not previously documented in a Microsoft Knowledge Base article.Issue 1: You cannot browse the list of Web parts when you are editing a dashboard that is deployed to a SharePoint siteIn PerformancePoint Dashboard Designer, you edit a dashboard that is deployed to a SharePoint site. When you try to browse the list of Web parts by clicking Next on the Add Web Parts panel, you receive the following error message:

Server Error in ‘/’ Application.
Object reference not set to an instance of an object. Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.NullReferenceException: Object reference not set to an instance of an object.Important After you apply this hotfix, you must redeploy the Dashboard Viewer for SharePoint Services Web part. To redeploy this Web part, follow these steps:Start the Monitoring Server Configuration Manager.Remove the Dashboard Viewer for SharePoint Services Web part.Re-add the Dashboard Viewer for SharePoint Services Web part.Issue 2: Time Intelligence Post Formula filters display the next day’s dateYou link a Time Intelligence Post Formula filter to a scorecard in PerformancePoint Dashboard Designer. When you preview this dashboard, you notice that the Time Intelligence Post Formula filter displays a date that isone day in advance on the scorecard. For example, the date on the client computer is March 6. When you preview this dashboard, you expect the Time Intelligence Post Formula filter to display the date asMarch 6. However, the Time Intelligence Post Formula filter displays that date as March 7. This problem occurs when a a time zone difference causes a one-day differencebetween the client computer and the server.
This problem occurs because the date on the server is not converted from Coordinated Universal Time (Greenwich Mean Time) to local time.Issue 3: Member property values may not be displayed correctly in reports or in chartsWhen a member property value is displayed in reports or in charts, you may encounter one of the following problems:The precision may be lost if the value has more than two decimal places. For example, a value of 0.001 is displayed as 0.00.The value “,00″ is added to the end of the value. For example, a value of 88.00 is displayed as 88.880,00.Issue 4: The connection to SQL Server 2008 Reporting Services fails in PerformancePoint Dashboard DesignerWhen you try to connect to a SQL Server 2008 Reporting Services report in PerformancePoint Dashboard Designer, you receive an “Unable to connect to server” error message.

Symptoms
This article describes the Microsoft Office Outlook 2007 issues that are fixed in the Outlook 2007 hotfix package that is dated June 12, 2007.
This article describes the following items about the hotfix package:The issues that the hotfix package fixes.The prerequisites for installing the hotfix package.Whether you must restart your computer after you install the hotfix package.Whether the hotfix package is replaced by any other hotfix package.Whether you must make any registry changes. The files that the hotfix package contains.
Resolution
Issues that the hotfix package fixesThis hotfix package fixes the following issues that were not previously documented in a Microsoft Knowledge Base article:You try to open a user’s shared calendar in Outlook 2007. If the user’s mailbox is in a different administrative group, the shared mailbox cannot be synchronized correctly. Additionally, an eventthat resembles the following event is logged in the Application log:
Event Type:Warning
Event Source:MSExchangeSA
Event Category:RFR Interface
Event ID:9234
Date:date
Time:time
User:N/A
Computer:server_name
Description: Referral Interface was not able to find an msExchExchangeServer object with legacyExchangeDN ‘/o=Organization_Name/ou=Exchange Administrative Group (group)/cn=Configuration/cn=Servers/cn=server_name’ in the Active Directory.You use a custom solution in a trusted simple MAPI environment to send e-mail messages in Outlook 2007. If an e-mail message contains more than five recipients, the e-mail aliases are not resolved. Additionally, the Outlook security dialog box unexpectedly appears. You have multiple appointments scheduled for a day in the calendar in Outlook 2007. When you print the calendar in Monthly style, only two appointments are printed for the day.
This issue may occur even though there is sufficient room for all the appointments to print for that day. A delegate for your mailbox accepts a meeting request on your behalf. Then,the meeting is updated. When you view the updated meeting request, the No response required button is not displayed. As meeting requests and meeting updates are processed in Outlook, the tracking status and the attendee changes for the meeting requests may cause new style conflicts.
When this issue occurs, the tracking status and the attendee changes are not updated automatically. Therefore,many items may be added to the “Sync Issues” folder and to the Conflicts folder. You send a meeting request that contains anattendee to which youcannot send requests, such as a meeting room. When you reopen the meeting request, the free/busy time for this attendee is not displayed. You send a recurring meeting request to attendees. Then, you update the meeting time for the recurring meeting and then send the update. When you reopen the recurring meeting, the meeting time reverts to the original meeting time. You open a second instance of a recurring meeting. Then, you update the recurring meeting and then send the update. When you do this, the meeting update is sent as expected. However, the changes to the meeting are not saved. You accept an all-day event request. Then, youschedule another all-day event that spans the same times as theall-day event that you accepted. When you switch between events, theevent that you scheduled may disappear. When you switch to the accepted event and then switch back to the scheduled event, the scheduled event reappears.You delete attendees from a recurring meeting and then send the meeting update. When you do this, the update is sent to all attendees. This includes the deleted attendees. You create a meeting exception for a recurring meeting. Then, you restart Outlook and then open the meeting exception. When you do this, the body of the exception message is blank. You are the organizer of a recurring meeting. When you open the recurring meeting, the meeting opens as a Send Cancellation action. You accept a meeting request in Cached Exchange Mode. When you do this, the meeting request is deleted and the meeting acceptance is not sent. Additionally, you may receive the following error message:

Cannot save free/busy information.You create a meeting exception for a recurring meeting. Then,you reopen the meeting exception. When you do this,one of the following symptoms may occur: If the body of the recurring meeting message is small, the body of theexception message is now large.If the body of the recurring meeting message is large, the body of the exception message is now blank.Note A large message body for a personal folders (.pst) file is 8 kilobytes (KB) or larger.When you try to propose a new time for a meeting request, you receive the following error message:

The end date you entered occurs before the start date.You change an existing meeting request. When you click Save and Send Update, the changes to the meeting request are sent as expected. However, the meeting request closes unexpectedly.

Symptoms
This article describes the Microsoft Office Forms Server 2007 issues that are fixed in the hotfix package that is dated October 27, 2009.
Resolution
Issues that this hotfix package fixesYou try to fill a Microsoft Office InfoPath 2007 form that is enabled for display on a mobile device. If the form contains a drop-down list that is bound to a Windows SharePoint list, a NullReferenceException exception occurs.
You use Forms Server 2007 to render an HTML form that contains an Office InfoPath 2007 template. The template is contained in a section of the form. When you use Mozilla Firefox to scroll through the section, the Cannot be blank red asterisks do not scroll together withother items in the section.

Symptoms
This update applies only to Duet client computers and is also known as Hotfix 1 for Duet 1.5 Service Pack 2 (SP2).
Resolution
Issues that this hotfix package fixesFixed incorrect logging of errors that should be warnings. Added logging to identify when Outlook is started with a profile not configured for Duet. During metadata upgrade, increased the time that a user has to close running Office applications to 30 seconds. Improved Client Protocol Handler logging to include BoundItemType, BoundItemId, and CorrelationID values. In a primary or a secondary computer configuration, a metadata upgrade results in an item becoming unbound if it was created on the secondary machine and the Sweeper did not process it yet. Copying and pasting a bound item no longer results in a new bound item. The new item is a standard unbound Outlook item. Improved user feedback if Duet cannot log on to Exchange Server. The Duet add-in for Word no longer automatically loads unless a scenario is installed that needs Word integration. The metadata cache on a client is no longer encrypted. Fixed a scenario in which a Duet utility crashes with a System.NullReferenceException during metadata deployment if calls to the metadata server result in a time-out. Past occurrences of a bound recurring appointment series become unbound during Duet parallel appointment creation. Bound items become unbound if the OBASQLEXPRESS instance becomes unavailable while the Sweeper is running.

Symptoms
This article describes the undocumented change in behavior of the HttpServerUtility.Transfer method call from the Microsoft .NET Framework 1.0 to the Microsoft .NET Framework 1.1.
For more information, visit the following Microsoft Developer Network (MSDN) Web site:
http://msdn2.microsoft.com/en-us/library/aa332847(VS.71).aspx(http://msdn2.microsoft.com/en-us/library/aa332847(VS.71).aspx)
Resolution
The HttpServerUtility.Transfer method contains two parameters. The first parameter is a URL path of the new page on the server to execute.The second optional parameter indicates whether the Form and the QueryString values can pass from the calling page to the page that the user is being transferred to.

HttpServerUtility.Transfer(String, Boolean); In the .NET Framework 1.0, if the second optional parameter of the HttpServerUtility.Transfer method is not specified, the second parameter is set to false.
In the .NET Framework 1.1, if the second optional parameter of the HttpServerUtility.Transfer method is not specified, the second parameter is set to true.
The “Parameters” section of the “HttpServerUtility.Transfer Method (String, Boolean)” topic in MSDN states the following:
path
The URL path of the new page on the server to execute.
preserveForm
If true, the QueryString and Form collections are preserved. If false, they are cleared. The default is false.
The following is the correct information:
path
The URL path of the new page on the server to execute.
preserveForm
If true, the QueryString and Form collections are preserved. If false, they are cleared. In the .NET Framework 1.0, the default value of the preserveForm parameter is false. In the .NET Framework 1.1, the default value of the preserveForm parameter is true.

Symptoms
This article describes critical update 886185. This update helps narrow the definition of the My network (subnet) only, or local subnet, scope option in Windows Firewall. This is helpful in situations where Windows Firewall would consider a large network to be on the local subnet because of how the dial-up software configured the route tables. After you install critical update 886185, you may have to restart your computer.
Resolution
After you set up Windows Firewall in Microsoft Windows XP Service Pack 2 (SP2), you may discover that anyone on the Internet can access resources on your computer when you use a dial-up connection to connect to the Internet. For example, after creating an exception in Windows Firewall for File and Printer Sharing, you may discover that anyone can access shared files and printers.
Note Windows Firewall automatically selects the My network (subnet) only scope option when you create an exception for File and Printer Sharing.