.NET Questions and Solutions

As a software engineer, I focus on .NET, especially asp.net, C#, WCF and so on, and I am also very interested in Search Engine Optimization.

Entries Tagged ‘microsoft knowledge base’

FIX: A dump file may be generated in the Reporting Services Logfiles folder and you may receive an error message when you try to render a report in SQL Server 2008 Reporting Services

Symptoms
Consider the following scenario. In Microsoft SQL Server 2008 Reporting Services, you create a report. The report contains a Tablix data region item, a Subreport item, or a Chart item. The item has the NoRowsMessage property set, and there are no rows in the data region. Or, the report contains a Subreport item that displays error messages. The text box that is generated to display the error messages is split across a report page. You try to render the report. In this scenario, a dump file may be generated in the Reporting Services Logfiles folder. Additionally, you may receive an error message that resembles the following:

Assert in function = Microsoft.ReportingServices.Rendering.HPBProcessing.Paragraph.get_SpaceBefore file =line = 0 expression = Unhandled managed exception: Type = System.NullReferenceException, Message = Object reference not set to an instance of an object.
Resolution
The fix for this issue was first released in Cumulative Update 1. For more information about how to obtain this cumulative update package for SQL Server 2008, click the following article number to view the article in the Microsoft Knowledge Base:
956717?(http://support.microsoft.com/kb/956717/) Cumulative update package 1 for SQL Server 2008Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix.For more information, click the following article number to view the article in the Microsoft Knowledge Base:
956909?(http://support.microsoft.com/kb/956909/)The SQL Server 2008 builds that were released after SQL Server 2008 was released

FIX: “Exception caught: Object reference not set to an instance of an object” error message when you compile a large map in BizTalk Server 2004

Symptoms
In Microsoft BizTalk Server 2004, you may receive the following error message when you try to compile a large map:

Exception Caught: Object reference not set to an instance of an object.
Resolution
Service pack informationTo resolve this problem, obtain the latest service pack for Microsoft BizTalk Server 2004. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
888751?(http://support.microsoft.com/kb/888751/) How to obtain the latest BizTalk Server 2004 service pack
Hotfix informationThe English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.

DateTimeVersionSizeFile name——————————————————————————————01-Apr-200402:313.0.5267.0676,864Btsxmltools.dll01-Apr-200402:573.0.5267.0274,432Microsoft.biztalk.basefunctoids.dll01-Apr-200402:573.0.5267.045,056Microsoft.biztalk.crossreferencing.dll01-Apr-200402:573.0.5267.040,960Microsoft.biztalk.crossreferencingfunctoids.dll01-Apr-200402:573.0.5267.0249,856Microsoft.biztalk.mapper.dll01-Apr-200402:573.0.5267.01,114,112Microsoft.biztalk.tom.dll
NoteBecause of file dependencies, the most recent hotfix that contains these files may also contain additional files.

Fatal Exception 0028 in VXD Helpwgrd

Symptoms
When you start Windows 98, you may receive the following error message:

Fatal Exception 0028 in VXD HELPWGRDNOTE: To more effectively search the Microsoft Knowledge Base, use keywords that relate to your issue. If you are searching for troubleshooting information that is not mentioned in this article, search the Microsoft Knowledge Base again by using keywords that are listed in the following Microsoft Knowledge Base article:
242450?(http://support.microsoft.com/kb/242450/EN-US/) How to Query the Microsoft Knowledge Base Using Keywords
Resolution
This behavior can occur if the Dr. Solomon’s Anti-Virus program is installed on your computer. The Dr. Solomon’s Anti-Virus program is not compatible with Windows 98.

Exception message when you use a Collaboration Data Objects (CDO) 1.21-based application to call the Respond method on the parent of a recurring meeting request on Exchange Server 2003 SP2: “[MAP …

Symptoms
When you use a Collaboration Data Objects (CDO) 1.21-based application to call the Respond method on the parent of a recurring meeting request, the application will throw the following CDO exception:

[MAPI_E_NOT_FOUND (8004010F)]
Resolution
Hotfix information A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
If the hotfix is available for download, there is a “Hotfix download available” section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or tocreate a separate service request, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=support(http://support.microsoft.com/contactus/?ws=support)Note The “Hotfix download available” form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.Prerequisites Because of file dependencies, this hotfix requires Microsoft Exchange Server 2003 Service Pack 2.
For more information about the latest service packs for Exchange Server 2003, click the following article number to view the article in the Microsoft Knowledge Base:
836993?(http://support.microsoft.com/kb/836993/) How to obtain the latest service packs for Exchange Server 2003Restart requirementYou do not have to restart thecomputer after you apply this hotfix. Hotfix replacement informationThis hotfixdoes not replace any other software updates.File informationThe English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformCdo.dll6.5.7651.38717,82426-Jul-200616:29×86

Description of the PerformancePoint Server 2007 hotfix package: April 28, 2009

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.

Description of the Outlook 2007 hotfix package: June 12, 2007

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.