Page 22 of 732« First...10...2021222324...304050...Last »

Event IDs 904, 9635, 8003, and 8019 are logged when you try to restore data to a computer that is running Exchange 2003 Server

When you try to restore Microsoft Exchange Server 2003 data by using a backup utility, such as the Windows Backup Utility, the restore operation may not be successful. One or more of the following events may be logged in the Event Viewer log.

Note The error code number 0xc7fe1f42 that is referenced in the description field of event ID 9635 and event ID 904 indicates that the backup program could not find the database. The 0xc7fe1f42 error code may be returned with both mailbox store restoration issues and public folder store restoration issues.

Event Type: Error

Event Source: MSExchangeIS

Event Category: Exchange Backup Restore

Event ID: 9635

Description:

Failed to find a database to restore to from the Microsoft Active Directory.
Storage Group specified on the backup media is GUID.
Database specified on backup media is DatabaseName (ComputerName), error is
0xc7fe1f42.

Event Type: Error

Event Source: ESE BACKUP

Event Category: Callback

Event ID: 904

Description:

Information Store (4000) Callback function call ErrESECBRestoreGetDestination ended with error 0xC7FE1F42 Database not found.

Event Type: Error

Event Source: NTBackup

Event Category: None

Event ID: 8003

Description:

End Restore to ‘ComputerNameMicrosoft Information StoreFirst Storage Group’
‘Failed’
Verify: Off
Consult the backup report for more detail.

Event Type: Error

Event Source: NTBackup

Event Category: None

Event ID: 8019

Description:

End Operation: Warnings or errors were encountered.
Consult the backup report for more details.

This issue may occur when one of the following causes is true.

Mailbox store recovery cause 1

The mailbox store was not added to the Recovery Storage Group.

Mailbox store recovery cause 2

The mailbox store that you are trying to restore is not configured as part of an existing Recovery Storage Group.

Public folder store cause 3

This cause may occur when one of the following is true:

  1. The storage group that you try to restore contains one or more public folder stores.
  2. You try to restore a single public folder store instead of a storage group.
To work around this issue, use one of the following methods.

Workaround for mailbox store recovery cause 1

To work around this issue, you must first add the mailbox store that you want to the Recovery Storage Group. For additional information about how to add a mailbox store to a Recovery Storage Group, see the “More Information” section.

Workaround for mailbox store recovery cause 2

To work around this issue, delete the Recovery Storage Group and try the restore operation again.

By default, if you delete the Recovery Storage Group, the information store restores the data to the original mailbox store instead of to the Recovery Storage Group. To delete the Recovery Storage Group, follow these steps:

  1. Start Exchange System Manager.
  2. Expand Administrative Groups, expand the administrative group that you want, and then expand Servers.
  3. Click the server that you want, and then right-click Recovery Storage Group in the right pane.
  4. Click Delete, and then click Yes.

Workaround for public folder store cause 3

There are two methods that you can use to work around public folder store cause 3.a or public folder store cause 3.b.

Method 1: Delete the Recovery Storage Group

By default, if you delete the Recovery Storage Group, the information store restores the data to the original mailbox store instead of to the Recovery Storage Group. To delete the Recovery Storage Group, follow these steps:

  1. Start Exchange System Manager.
  2. Expand Administrative Groups, expand the administrative group that you want, and then expand Servers.
  3. Click the server that you want, and then right-click Recovery Storage Group in the right pane.
  4. Click Delete, and then click Yes.
  5. Try the restore operation again.

Method 2: Turn on the Recovery Storage Group override registry value

If you do not want to restore data to the Recovery Storage Group and you do not want to delete the Recovery Storage Group, create the Recovery SG Override value in the

HKEY_LOCAL_MACHINESystemCurrentControlSetServicesMSExchangeISParametersSystem

registry subkey, and then set the value to 1.

When you create this value, the information store ignores the Recovery Storage Group during a restore operation.

To create and configure the Recovery SG Override registry value, follow these steps.

Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

  1. Click Start, click Run, type regedit, and then click OK.
  2. Locate and then click the following registry subkey:

    HKEY_LOCAL_MACHINESystemCurrentControlSetServicesMSExchangeISParametersSystem

  3. On the Edit menu, point to New, and then click DWORD Value.
  4. Type Recovery SG Override, and then press ENTER.
  5. On the Edit menu, click Modify.
  6. In the Value data box, type 1, and then click OK.
  7. Quit Registry Editor.
  8. Try the restore operation again.

Important Make sure that you delete the Recovery SG Override registry value when you no longer require it.

Exchange 2003 supports the restoration of mailbox stores when you use Recovery Storage Groups. However, public folder store restoration is not supported when you use Recovery Storage Groups.

For more information about Recovery Storage Groups, click the following article number to view the article in the Microsoft Knowledge Base:

824126

(http://support.microsoft.com/kb/824126/
)

How to use Recovery Storage Groups in Exchange Server 2003

For more information about backup and restoration procedures in Exchange, click the following article number to view the article in the Microsoft Knowledge Base:

296788

(http://support.microsoft.com/kb/296788/
)

Offline backup and restoration procedures for Exchange

Article ID: 841143 – Last Review: June 20, 2014 – Revision: 4.0


Applies to
  • Microsoft Exchange Server 2003 Enterprise Edition
  • Microsoft Exchange Server 2003 Standard Edition

View original post here:
Event IDs 904, 9635, 8003, and 8019 are logged when you try to restore data to a computer that is running Exchange 2003 Server

FIX: A BizTalk Server project may stop responding when you add schemas and the schemas are opened in Visual Studio .NET

When you add one large schema or multiple schemas to a Microsoft BizTalk Server 2004 project by using the Add Generated Item command or the Add Adapter command on the Project menu, the added schema or schemas are automatically opened in Microsoft Visual Studio .NET. This behavior consumes lots of resources and Visual Studio .NET may stop responding (hang) for a while.

Service pack information

To 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 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 to create a separate service request, visit the following Microsoft Web site:

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

No prerequisites are required.

Restart requirement

You do not have to restart your computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later) 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.

   Date         Time   Version     Size     File name
   --------------------------------------------------------------------------------
   10-Apr-2004  00:05  3.0.5275.0  491,520  Microsoft.biztalk.adapter.framework.dll

Note Because of file dependencies, the most recent hotfix that contains these files may also contain additional files.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the “Applies to” section.
This problem was corrected in BizTalk Server 2004 Service Pack 1.
This hotfix helps save system resources by preventing BizTalk Server from automatically opening added schemas.

For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

824684

(http://support.microsoft.com/kb/824684/
)

Description of the standard terminology that is used to describe Microsoft software updates

Article ID: 839440 – Last Review: June 20, 2014 – Revision: 3.0


Applies to
  • Microsoft BizTalk Server 2004 Developer Edition
  • Microsoft BizTalk Server 2004 Enterprise Edition
  • Microsoft BizTalk Server 2004 Standard Edition
  • Microsoft BizTalk Server 2004 Partner Edition
kbautohotfix kbbiztalk2004sp1fix kbqfe kbhotfixserver kbbiztalk2004presp1fix kbbug kbfix kbprb KB839440

See the original article here:
FIX: A BizTalk Server project may stop responding when you add schemas and the schemas are opened in Visual Studio .NET

You receive a "TDDS failed to read from source database." error message in the application log of a computer that is running BizTalk Server

You receive an error message that is similar to the
following in the application log of a server that is running Microsoft BizTalk
Server 2006 or Microsoft BizTalk Server 2004:

Reading
error. Exception information: TDDS failed to read from source database.
SQLServer: SQLSERVER, Database:
BizTalkMsgBoxDb.

You may also receive one
of the following error messages in the application event log:

Error message 1

Either another TDDS is processing the same
data or there is an orphaned session in SQL server holding TDDS lock. SQL
Server: SQLSERVER Database:
BizTalkMsgBoxDb

Error message 2

Either another TDDS is processing the same
data or there is an orphaned session in SQL server holding TDDS lock. Cannot
open database requested in login ‘Login‘. Login
fails.

Error message 3

Either another TDDS is processing the same
data or there is an orphaned session in SQL server holding TDDS lock.The
ConnectionString property has not been initialized. SQLServer:
SQLSERVER, Database: BizTalkMsgBoxDb

NoteSQLSERVER represents the name of the
computer that is running SQL Server that houses the BizTalk MessageBox
database, Login is a placeholder for a user name,
and BizTalkMsgBoxDb is a placeholder for the name of
the BizTalk Server MessageBox database.

You may receive this error message for the following
reasons:

  • The user account that is specified as the Logon for a
    BizTalk Server Host instance that tracking is enabled for is not a member of
    the BizTalk Application Users group on the computer that is running SQL Server
    that houses the Health and Activity Tracking, Business Activity Monitoring, and
    MessageBox databases.
  • An orphaned SQL Session is preventing the Tracking Data
    Decode Service (TDDS), also known as the BAM Event Bus Service, from
    starting.
To resolve this problem, check the text of the error
description that immediately follows the error text that is listed in the
Symptoms section. Depending upon the text of the error description that
immediately follows the error text, follow these steps:

  • If the error text that appears is similar to the following
    error message:

    EXECUTE permission denied on object
    ‘TDDS_Lock’, table ‘xxx‘, owner
    xxx‘. SQLServer: xxx,
    Database: xxx.

    Make sure that the user
    account that is specified as the Logon for a BizTalk Server Host instance for
    which tracking is enabled is a member of the BizTalk Application Users group on
    the computer that is running SQL Server that houses the Health and Activity
    Tracking, Business Activity Monitoring, and MessageBox databases. Also make
    sure no other BizTalk servers process the same tracking data from the same
    BizTalk MessageBox database.

    Note xxx is a placeholder for the actual
    name of the table, the database owner, the computer that is running SQL Server,
    and the database name.

  • If the error text that appears is similar to the following
    error message:

    Timeout expired. The timeout period
    elapsed prior to completion of the operation or the server is not
    responding.

    Follow the steps that are listed in the following
    Microsoft Developer Network (MSDN) article for troubleshooting orphaned SQL
    sessions:

This
behavior is by design.
The “Either another TDDS is processing the same data or
there is an orphaned session in SQL server holding TDDS lock” error message
indicates that more than one Tracking Data Decode Service (TDDS) is processing
at the same time and on the same data. This behavior locks the data and
prevents access to the data. If you receive this error message in a clustered
or multi-node BizTalk Server environment, follow these steps to make sure that
your domain groups are added to the correct SQL Server database roles that are
created when BizTalk Server is installed.

Note You must follow these steps on each instance of SQL Server on
which BizTalk Server is installed.

Microsoft SQL Server 2005

Configure the BAMArchive database

  1. Open SQL Server Management Studio.
  2. Expand the instance of SQL Server that you want to
    configure, expand Databases, expand
    BAMArchive, expand Security, expand
    Roles, and then click Database
    Roles
    .
  3. Double-click BTS_ADMIN_USERS. If the
    BizTalk Server Administrators group is not a member of this role, add the
    BizTalk Server Administrators group to the role, and then click
    OK.
  4. Click Users. If the BizTalk Isolated Host
    Users group is not a login for this database, add the BizTalk Isolated Host
    Users group login to the database, and then click
    OK.
  5. Click Database Roles, and then
    double-click BTS_HOST_USERS. If the BizTalk Isolated Host
    Users group is not a member of the BTS_HOST_USERS role, add the BizTalk
    Isolated Host Users group login to the BTS_HOST_USERS role, and then click
    OK.

Configure the BAMPrimaryImport database

  1. Under Databases, expand
    BAMPrimaryImport.
  2. Expand Security, and then click
    Users.
  3. Add the BizTalk Service Account (BtsService) account as a
    user. This step is not performed automatically when you run the BizTalk Server
    Configuration Wizard (Configuration.exe). To do this, right-click
    Users, and then click New User, add the user,
    and then click OK.
  4. Expand Roles, and then click
    Database Roles.
  5. Double-click BAM_EVENT_WRITER, add the
    BizTalk Service Account and the BizTalk Server Administrators group logins to
    the BAM_EVENT_WRITER role, and then click OK.
  6. Double-click BAM_ManagementWS, add the
    BizTalk Service Account and the BizTalk Server Administrators group logins to
    the BAM_ManagementWS role, and then click OK.

Configure the BizTalkDTADb database

  1. Under Databases, expand
    BizTalkDTADb.
  2. Expand Security, expand
    Roles, and then click Database
    Roles
    .
  3. Double-click BAM_EVENT_WRITER. Add the
    BizTalk Server Administrators group login and the BizTalk Service Account login
    to the BAM_EVENT_WRITER role, and then click OK.
  4. Double-click HM_EVENT_WRITER. Add the
    BizTalk Server Administrators group login and the BizTalk Service Account login
    to the HM_EVENT_WRITER role, and then click OK.

Configure the BizTalkMgmtDb database

  1. Under Databases, expand
    BizTalkMgmtDb.
  2. Expand Security, expand
    Roles, and then click Database
    Roles
    .
  3. Double-click BAM_CONFIG_READER. Add the
    BizTalk Server Administrators group login and the BizTalk Service Account login
    to the BAM_CONFIG_READER role, and then click OK.

Configure the BizTalkMsgBoxDb database

  1. Under Databases, expand
    BizTalkMgmtDb.
  2. Expand Security, and then click
    Users.
  3. Right-click the right pane, click New
    User
    , add the BizTalk Service account as a login to this database, and
    then click OK.
  4. Expand Roles, and then click
    Database Roles.
  5. Double-click BAM_EVENT_READER, add the
    BizTalk Service account login to the BAM_EVENT_WRITER role, and then click
    OK.

Microsoft SQL Server 2000

Configure the BAMArchive database

  1. Open SQL Server Enterprise Manager.
  2. Expand the instance of SQL Server that you want to
    configure, expand Databases, expand
    BAMArchive, and then click Roles.
  3. Double-click BTS_ADMIN_USERS.

    If
    the BizTalk Server Administrators group is not a member of this role, click
    Add to add the group, and then click
    OK.

    Note If the BizTalk Server Administrators group is not available,
    follow these steps:

    1. Click Cancel.
    2. Click Logins.
    3. Add the BizTalk Server Administrators group as a new
      login for the database, and then click OK.
    4. Click Roles.
    5. Click Add to add the BizTalk Server
      Administrators group to the role.
    6. Click OK.
  4. Click Users.

    If the BizTalk
    Isolated Host Users group is not a login for this database, right-click the
    right pane, click New User, add the BizTalk Isolated Host
    Users group login to the database, and then click
    OK.

  5. Click Roles, and then double-click
    BTS_HOST_USERS.

    If the BizTalk Isolated Host Users
    group is not a member of the BTS_HOST_USERS role, click Add to
    add the BizTalk Isolated Host Users group login to the BTS_HOST_USERS role, and
    then click OK

Configure the BAMPrimaryImport database

  1. Under Databases, expand
    BAMPrimaryImport.
  2. You must add the BizTalk Service Account (BtsService) as a
    user. This step is not performed automatically when you run the BizTalk Server
    Configuration Wizard (ConfigFramework.exe). To do this, follow these steps:

    1. Click Users.
    2. Right-click the right pane, click New
      User
      , and then add the BizTalk Service Account login to this
      database.
    3. Click OK.
  3. Click Roles, and then double-click
    BAM_EVENT_WRITER.
  4. Add the BizTalk Service Account and the BizTalk Server
    Administrators group logins to the BAM_EVENT_WRITER role.
  5. Click OK.
  6. In BizTalk Server 2003, double-click BAMQueryWS under Roles. In BizTalk Server 2006, double-click
    ManagementWS under Roles.
  7. Add the BizTalk Service Account and the BizTalk Isolated
    Host Users group logins to the BAMQueryWS role.
  8. Click OK.

Configure the BizTalkDTADb database

  1. Under Databases, expand
    BizTalkDTADb.
  2. Click Roles, and then double-click
    BAM_EVENT_WRITER.
  3. Add the BizTalk Server Administrators group login and the
    BizTalk Service Account login to the BAM_EVENT_WRITER role.
  4. Click OK.
  5. Under Roles, double-click
    HM_EVENT_WRITER.
  6. Add the BizTalk Server Administrators group and the BizTalk
    Service Account login to the HM_EVENT_WRITER role.
  7. Click OK.

Configure the BizTalkMgmtDb database

  1. Under Databases, expand
    BizTalkMgmtDb.
  2. Click Roles, and then double-click
    BAM_CONFIG_READER.
  3. Add the BizTalk Service Account to the BAM_CONFIG_READER
    role.
  4. Click OK.

Configure the BizTalkMsgBoxDb database

  1. Under Databases, expand
    BizTalkMsgBoxDb.
  2. Click Users.
  3. Right-click the right pane, click New
    User
    , and then add the service account as a login to this
    database.
  4. Click OK.
  5. Under Roles, double-click the
    BAM_EVENT_READER role.
  6. Add the BizTalk Service Account to the BAM_EVENT_READER
    role.
  7. Click OK.

Important By default, these database security settings are already set when
you configure BizTalk Server 2004.

For more information about orphaned
sessions, visit the following Microsoft Developer Network (MSDN) Web site:

Article ID: 841334 – Last Review: June 20, 2014 – Revision: 4.0


Applies to
  • Microsoft BizTalk Server 2004 Developer Edition
  • Microsoft BizTalk Server 2004 Partner Edition
  • Microsoft BizTalk Server 2004 Standard Edition
  • Microsoft BizTalk Server 2006 Developer Edition
  • Microsoft BizTalk Server 2006 Enterprise Edition
  • Microsoft BizTalk Server 2006 Standard Edition
  • Microsoft BizTalk Server 2006 R2 Developer Edition
  • Microsoft BizTalk Server 2006 R2 Enterprise Edition
  • Microsoft BizTalk Server 2006 R2 Standard Edition
  • Microsoft BizTalk Server 2009 Developer
  • Microsoft BizTalk Server 2009 Enterprise
  • Microsoft BizTalk Server 2009 Standard

See the original post:
You receive a "TDDS failed to read from source database." error message in the application log of a computer that is running BizTalk Server

An e-mail message may not be formatted correctly when an Exchange Server 2003 mailbox user sends an e-mail message to an external user

When a Microsoft Exchange Server 2003 mailbox user sends an e-mail message to an external user, the e-mail message may not be formatted correctly.
This problem may occur when the following conditions are true:  
  • The e-mail message is relayed by a smart host from one Exchange computer to another.
  • The e-mail message contains a line of text that has more than 998 characters.
  • The Exchange Server 2003 computer uses 7-bit encoding to send messages in MIME format.
  • One of the following character sets or code pages is used to compose the e-mail message:
    ISO-2022-KR,
    ISO-2022-JP,
    csISO2022JP,
    or UTF-7.

This problem occurs when some Asian character sets are used to compose an e-mail message, and the message is sent in MIME format by using 7-bit encoding. The problem occurs because the lines in the text that are longer than 998 characters cannot be wrapped, and the characters are labeled with incorrect 7-bit encoding during transport to the final mailbox server.

The default MIME encoding in Exchange Server 2003 is 7-bit transfer encoding. The MIME encoding in some Asian languages must be set to an encoding method that is different from 7-bit encoding. The lines of text that contain more than 998 characters can then be wrapped.

Service pack information

To resolve this problem, obtain the latest service pack for Exchange Server 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

836993

(http://support.microsoft.com/kb/836993/EN-US/
)

How to obtain the latest service packs for Exchange Server 2003

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 to create a separate service request, visit the following Microsoft Web site:

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

No prerequisites are required.

Restart requirement

You must restart your computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The 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.

After you apply this hotfix, you can use registry values to set the MIME encoding method in the following registry subkey:

HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesMSExchangeISParametersSystemInternetContentTransferEncodingFor7bit

The hotfix that resolves this issue lets an administrator use the registry to select the transfer encoding for all the character sets that are affected. The administrator must set the encoding method correctly based on the clients and their encoding capability.

Use the appropriate value from the following table to control the MIME encoding behavior.

Collapse this tableExpand this table

Value Behavior
0 Always use 7-bit encoding for both HTML and plain text.
1 Always use quoted-printable encoding for both HTML and plain text.
2 Always use Base64 encoding for both HTML and plain text.
5 Use quoted-printable encoding for HTML and plain text. If plain-text line wrapping is enabled, use quoted-printable encoding for HTML, and use 7-bit encoding for plain text.
6 Use Base64 encoding for HTML and plain text. If plain-text line wrapping is enabled, use Base64 encoding for HTML, and use 7-bit encoding for plain text.
13 (=0x0D) Always use quoted-printable encoding for HTML, and always use 7-bit encoding for plain text.
14 (=0x0E) Always use Base64 encoding for HTML, and always use 7-bit encoding for plain text.

Exchange uses the default value of zero for 7-bit encoding if the registry subkey value contains a value that is not listed in this article, or if a value is not present.
After you change the value of the TransferEncodingFor7bit subkey, you must stop and then restart the Microsoft Exchange Information Store service on the Exchange 2003 computer.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the “Applies to” section.

This problem was first corrected in Exchange Server 2003 Service Pack 2.

For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

824684

(http://support.microsoft.com/kb/824684/
)

Description of the standard terminology that is used to describe Microsoft software updates

For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

817903

(http://support.microsoft.com/kb/817903/
)

New naming schema for Exchange Server software update packages

Article ID: 835992 – Last Review: June 20, 2014 – Revision: 6.0


Applies to
  • Microsoft Exchange Server 2003 Standard Edition
  • Microsoft Exchange Server 2003 Enterprise Edition
kbautohotfix kbqfe kbhotfixserver kbfix kbbug kbexchange2003presp1fix KB835992

Read More:
An e-mail message may not be formatted correctly when an Exchange Server 2003 mailbox user sends an e-mail message to an external user

Excel statistical functions: VAR and VARP improvements and pivot tables

The Microsoft Office Excel statistical functions, VAR and VARP, are computed with
better precision in Microsoft Office Excel 2003 and later versions of Excel. The same algorithmic
improvements were made for VAR and VARP when used to summarize data for pivot
tables. Unfortunately, some computational issues remain unresolved. Use extreme
caution when you summarize data with VAR and VARP in Excel 2003 and later versions of Excel. This
article describes the remaining problem.

You may notice different
values when worksheets that were created in earlier versions of Excel are
recalculated in Excel 2003 and later versions of Excel. This article describes the values that are more
accurate in Excel 2003 and later versions of Excel and the values that are less accurate.

Microsoft Excel 2004 for Macintosh Information

The statistical functions in Microsoft Office Excel 2004 for Macintosh were updated using the same algorithms as Excel 2003 and later versions of Excel. Any information in this article that describes how a function works or how a function was modified for Excel 2003 and later versions of Excel also applies to Excel 2004 for Macintosh.

The articles on VAR and VARP describe how a two-pass
procedure has replaced the “calculator formula” for computing these measures.
With infinite precision arithmetic, both procedures return the same results and
the calculator formula takes half the computation time. However, with finite
precision arithmetic, the potential for round off errors becomes a factor. The
result of using the two-pass procedure is less susceptibility to round off
errors in extreme situations in Excel 2003 and later versions of Excel. However, you may not notice the
effect of these improvements because for most data sets, there are not enough
significant digits in the data to cause different results from the calculator
formula and the two-pass procedure. VAR and VARP are always more accurate in
Excel 2003 and later versions of Excel, but VAR and VARP differences between earlier
versions of Excel and Excel 2003 are likely to be noticeable only when data values contain
many significant digits and yet have small variation.

Microsoft
recommends that you read the article about VAR because it explains
modifications in the computational procedure and it also provides a worksheet
for more extensive experimentation with adding a power of ten to data
values. For additional information about VAR, click the following
article number to view the article in the Microsoft Knowledge Base:

826112

(http://support.microsoft.com/kb/826112/
)

Excel Statistical Functions: VAR

The intent of the improvements was to also
improve separate code for computing VAR for summarizing data in pivot tables.
This code has been improved for part of the pivot table, but problems remain
unresolved for other parts. The numeric example later in this article helps clarify the
situation.

Create a blank Microsoft Office Excel worksheet, copy the table that follows later in this section, and
then select cell A1 in your blank Excel worksheet. Then paste the entries so that the table fills
cells A1:I28 in your worksheet.

Collapse this tableExpand this table

Group Trial Value Modified
Value
Power of 10
1 1 1 =C2+10^$E$2 8
1 1 2 =C3+10^$E$2 All
Excel versions:
1 1 3 =C4+10^$E$2 Var
of Value
Trial
1 2 4 =C5+10^$E$2 Group 1 2 Grand
Total
1 2 5 =C6+10^$E$2 1 1 1 3.5
1 2 6 =C7+10^$E$2 2 4 4 14
2 1 2 =C8+10^$E$2 3 1 1 3.5
2 1 4 =C9+10^$E$2 Grand
Total
2.5 6.25 8.35294117647059
2 1 6 =C10+10^$E$2
2 2 8 =C11+10^$E$2 Excel
2002 values with E2 set to 8:
2 2 10 =C12+10^$E$2 Var
of Modified Value
Trial
2 2 12 =C13+10^$E$2 Group 1 2 Grand
Total
3 1 3 =C14+10^$E$2 1 0 0 4.8
3 1 4 =C15+10^$E$2 2 4 4 14.4
3 1 5 =C16+10^$E$2 3 0 0 1.6
3 2 6 =C17+10^$E$2 Grand
Total
4 6 7.52941176470588
3 2 7 =C18+10^$E$2
3 2 8 =C19+10^$E$2 Excel 2003 and later versions of Excel values with E2 set to 8:
Var of Modified
Value
Trial
Values with E2 set to
8:
Group 1 2 Grand Total
Excel 2002 Excel 2003 and later versions 1 1 1 4.8
all =VAR(C2:C19) 7.52941176470588 8.35294117647059 2 4 4 28.7
group
1
=VAR(C2:C7) 4.8 3.5 3 1 1 1.6
group
2
=VAR(C8:C13) 14.4 14 Grand
Total
7500000450000010 0 7058824164705910
group
3
=VAR(C14:C19) 1.6 3.5
trial 1 =VAR(C2:C4, C8:C10,
C14:C16)
4 2.5
trial 2 =VAR(C5:C7, C11:C13,
C17:C19)
6 6.25

Note After you paste this table into your new Excel worksheet, click Paste Options, and then click Match
Destination Formatting
. With the pasted range still selected, use one of the following methods:

  • In Microsoft Office Excel 2007, click the Home tab, click Format in the Cells group, and then click AutoFit Column Width.
  • In Microsoft Office Excel 2003 and earlier versions of Excel, point to
    Column on the Format menu, and then click
    AutoFit Selection.

Data for pivot tables are in cells
A1:D19. Columns F through I show values that are obtained in three pivot
tables. The first shows VAR of Value (column C). The other two pivot table
results are the same. By using this worksheet, you can create Modified Values
(column D) by adding the power of 10 in cell E2 to each Value. Adding a
constant to each data value will not affect variances. The second pivot table
demonstrates that all variances are incorrect in Microsoft Excel 2002 and earlier
versions if the data is modified by adding the large constant 10^8 to each
value. This produces data with many significant digits but small variance. Such
extreme data is unlikely to occur in practice, and you are unlikely to be
affected by this degree of numeric imprecision. This experiment is designed to
magnify round off errors. All results in this table, while incorrect, are
consistent with results from computing various VARs by using the Excel VAR
function in cells D23:D28.

The third pivot table shows results from Excel 2003 and later versions of Excel. The good news is that VAR has been correctly upgraded for the interior
of the table, cells G22:H24. Values in these six cells agree with corresponding
values in the first pivot table as they should. However, something yet
unresolved is significantly wrong in the Grand Total row and Grand Total column.
Cells E23:E28 show results from computing various VARs by using the Excel 2003 and later versions of Excel
VAR function for Modified Values with cell E2 set to 8. These results agree
with entries in the Grand Total row and Grand Total column of the first pivot
table as they should.

Unfortunately, this author recommends
that you ignore values in the Grand Total row and Grand Total column when you
use VAR to summarize data in an Excel pivot table. For earlier versions of
Excel, all entries in such pivot tables are likely to be correct provided that
data values are not so extreme as to cause significant round off problems. To
examine the accuracy of any VAR in the table, identify the range of data, Range,
of whose VAR you want. For earlier versions of Excel, the correct value is
obtained by computing DEVSQ(Range) / (COUNT(Range) – 1). For Excel 2003 and later versions of Excel,
the correct value comes from VAR(Range).

The same comments and same
performance issues apply to VARP. To verify the accuracy of any VARP in the
table in any version, identify the range of data, Range, of whose VARP that
you want. For earlier versions of Excel, the correct value is obtained by
computing DEVSQ(Range) / COUNT(Range). For Excel 2003 and later versions of Excel, the correct value comes
from VARP(Range).

Results in Earlier Versions of Excel

Use of the calculator formula in earlier versions of Excel makes
VAR and VARP, STDEV, STDEVP more susceptible to round off errors. However, round off errors are very rarely significant enough that a typical user will notice them.
These errors are likely to occur only in extreme situations, particularly when
data contains many significant digits but small variations.

Results in Excel 2003 and later versions of Excel

An improved procedure that involves two passes through the data is
correctly implemented for the interior of a pivot table. On the first pass, the
sample mean is calculated; on the second pass, the sum of squared deviations
about this sample mean is calculated. This sum is then divided by the number of
observations minus 1 for VAR or by the number of observations for VARP. This
procedure is generally recommended over the calculator formula to minimize the
risk of round off errors.

Unfortunately, this has not been correctly
implemented for the Grand Total row and Grand Total column. The author suggests
an alternative mechanism for obtaining correct values of these VAR or VARPs.

Conclusions

You will occasionally see differences when you compare the values
of VAR or VARP that are calculated with earlier versions of Excel to values
that are calculated with Excel 2003 and later versions of Excel. In these cases, Excel 2003 and later versions of Excel will
always be more accurate.

If Excel 2003 and later versions of Excel are used to summarize data with
VAR or VARP in a pivot table, you can rest assured that results in the interior
of the table are equally accurate or more accurate than in earlier versions of
Excel. Users of Excel 2003 and later versions of Excel can ignore results in the Grand Total row and Grand
Total column until computational issues with these entries are
resolved.

Article ID: 829250 – Last Review: June 20, 2014 – Revision: 4.0


Applies to
  • Microsoft Office Excel 2007
  • Microsoft Excel 2004 for Mac
kbexpertisebeginner kbinfo KB829250

See the article here:
Excel statistical functions: VAR and VARP improvements and pivot tables

"There is not enough memory available to perform the operation" error message when a MAPI program or a CDO program tries to access a message

When you create a MAPI program or a Collaboration Data Objects (CDO) program to perform operations on messages from a Microsoft Exchange Server 5.5 information store, the program may return a MAPI_E_NOT_ENOUGH_MEMORY error when the program tries to access a particular message. The MAPI_E_NOT_ENOUGH_MEMORY error is also expressed by using the E_OUTOFMEMORY code and by using the hexadecimal error code 8007000E. Additionally, the program user may receive an error message that is similar to the following:

There is not enough memory available to perform the operation.
E_OUTOFMEMORY(8007000E)]

This problem occurs because the Microsoft Exchange Information Store may return a remote procedure call (RPC) response to the client RPC request. The RPC response indicates that the buffer size that is required for the RPC data is larger than the maximum buffer size of 32 kilobytes (KB). The client handles this request to set up a buffer size that is too large as a memory error.

Hotfix Information

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that this article describes. Apply it only to systems that are experiencing this specific problem.

To resolve this problem, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:

Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Prerequisites

You must install Microsoft Exchange Server 5.5 Service Pack 4 (SP4) before you install this hotfix.

For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

191014

(http://support.microsoft.com/kb/191014/
)

XGEN: How to obtain the latest Exchange Server 5.5 service pack

Restart requirement

You do not have to restart your computer after you
apply this hotfix. However, this hotfix installation stops the Microsoft Exchange Information Store service and all the services that are dependent on the Microsoft Exchange Information Store service. These services are restarted automatically when the hotfix installation is complete.

Hotfix replacement information

This hotfix does not replace any
other hotfixes.

File information

The English version of this hotfix has the file attributes (or later) 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.
Component: CDO

Date         Time   Version      Size       File name
-------------------------------------------------------
15-Sep-2003  13:21  5.5.2657.66    491,280  Mdbmsg.dll
15-Sep-2003  13:21  5.5.2657.66  2,631,952  Store.exe
To work around this problem, open the message by using another method, change the message size, and then save it. For example, open the message by using Microsoft Outlook Web Access. Because this problem only occurs with messages of a certain size, the MAPI program or the CDO program can access the message successfully after you change the message size.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the “Applies to” section of this article.

For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

817903

(http://support.microsoft.com/kb/817903/
)

XADM: New naming schema for Exchange Server software update packages

Article ID: 826813 – Last Review: June 20, 2014 – Revision: 2.0


Applies to
  • Microsoft Exchange Server 5.5 Standard Edition
kbhotfixserver kbqfe kbexchange550presp5fix kbbug kbfix KB826813
Retired KB Content Disclaimer

This article was written about products for which Microsoft no longer offers support. Therefore, this article is offered “as is” and will no longer be updated.

More:
"There is not enough memory available to perform the operation" error message when a MAPI program or a CDO program tries to access a message

Contact List Recipients Are Not Listed When You Use the Find Names Dialog Box in OWA

When you use Microsoft Outlook Web Access (OWA) to access your Exchange Server 2003 mailbox, and you use the Find Names dialog box to search for the name of the person or distribution list that you want to send a message to, you may find that you cannot search for names from distribution lists in your Contacts folder.
This problem occurs because you cannot use the Find Names dialog box in OWA to search distribution lists that are in your Contacts folder.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
To use the Find Names dialog box in OWA to search for a person or distribution list that you want to send your message to, do one of the following:
  • Click the Address Book icon on the toolbar.

    -or-

  • Click Inbox, and then on the toolbar, click New. In the new message, click one of the following (as appropriate to your situation):

Article ID: 820280 – Last Review: June 20, 2014 – Revision: 4.0


Applies to
  • Microsoft Exchange Server 2003 Enterprise Edition
  • Microsoft Exchange Server 2003 Standard Edition
  • Microsoft Windows Small Business Server 2003 Premium Edition
  • Microsoft Windows Small Business Server 2003 Standard Edition

Read the original:
Contact List Recipients Are Not Listed When You Use the Find Names Dialog Box in OWA

POP3 client stops responding (hangs) or times out when you try to download messages in Exchange 2000 Server and in Exchange Server 2003

You cannot download and receive e-mail messages by using
Microsoft Outlook, Microsoft Outlook Express, or another POP3 client. The POP3
client may stop responding (hang) or time out when you try to retrieve your
messages.
This issue may occur if one or more of the messages contain
an incorrect POP3Tail, or termination sequence. As a result, the POP3 client
does not detect the termination sequence in the “corrupted” messages and cannot
complete the download of other messages to your Inbox.
To work around this issue, set the

CheckPop3Tail

registry
value to 1. To do so:

WARNING: If you use Registry Editor incorrectly, you may cause serious
problems that may require you to reinstall your operating system. Microsoft
cannot guarantee that you can solve problems that result from using Registry
Editor incorrectly. Use Registry Editor at your own risk.

  1. Click Start, and then click
    Run.
  2. In the Open box, type
    regedit, and then click OK.
  3. Locate, and then click the following registry entry:

    HKEY_LOCAL_MACHINESystemCurrentControlSetServicesPOP3SvcParametersCheckPop3Tail

    Note If the

    CheckPop3Tail

    registry value is not present, create it. To do so:

    1. Locate, and then click the following registry key:

      HKEY_LOCAL_MACHINESystemCurrentControlSetServicesPOP3SvcParameters

    2. On the Edit menu, point to
      New, and then click DWORD Value.
    3. Type CheckPop3Tail, and then
      press ENTER.
  4. On the Edit menu, click
    Modify.
  5. In the Value data box, type
    1, and then click OK.
  6. Quit Registry Editor.

Note: After you complete this procedure, Exchange checks the POP3Tail
of each POP3 message, and adds the correct termination sequence (if it is
missing). Because of this additional processing, you may experience a decrease
in performance in environments where there are many POP3 users.

The termination sequence for POP3 is CRLF.CRLF, as specified
in Request for Comments (RFC) 1939. To view RFC 1939, visit the following
Internet Engineering Task Force (IETF) Web site:

Article ID: 816896 – Last Review: June 20, 2014 – Revision: 3.0


Applies to
  • Microsoft Exchange Server 2003 Standard Edition
  • Microsoft Exchange Server 2003 Enterprise Edition
  • Microsoft Exchange 2000 Server Standard Edition
  • Microsoft Exchange 2000 Enterprise Server

View article:
POP3 client stops responding (hangs) or times out when you try to download messages in Exchange 2000 Server and in Exchange Server 2003

Error message when you cancel the installation of Visual Basic for Applications: "An error occurred"

oneMscomBlade,oneMsomNav,oneMscomFooter,

See original article:
Error message when you cancel the installation of Visual Basic for Applications: "An error occurred"

Troubleshoot sound-related problems with Microsoft games or mapping programs

This article describes how to troubleshoot these sound-related issues in the Microsoft games that are listed in the “Applies to”
section:
  • No sound plays.
  • Sounds are too quiet.
  • Sounds are distorted or scratchy.
  • The computer stops responding (“hangs”) when sounds are
    played.
Troubleshoot the problem by using the following methods in the order that they are presented.

Method 1: Check whether you can hear the sound in Windows

Test the sound in Windows by playing your favorite music or video file. If there is no sound, contact the manufacturer of the computer or of the sound card for more troubleshooting help. If you can hear the sound, go to Method 2.

Method 2: Check whether sound is enabled in the program

Each program has a unique setting to turn on and turn off the sound. Refer to the product documentation (manual) for certain keys or game settings to “toggle” the sound on or off.

If the issue continues to occur, go to Method 3.

Method 3: Restart the computer by using a clean startup procedure

When you start Microsoft Windows, other software may start automatically together with
the operating system. These programs can include antivirus and system
utilities that may interfere with the game. When you perform a clean startup, you prevent these programs from
starting automatically.

You must be logged on as an administrator or as a member
of the Administrators group to complete this procedure. If the computer is
connected to a network, network policy settings may also prevent you from
completing this procedure.

To view detailed steps about how to do a clean startup, see the following Microsoft Knowledge Base article:

331796

(http://support.microsoft.com/kb/331796/
)

Perform a clean startup to determine whether background programs are interfering with your game or program

If the issue continues to occur, go to Method 4.

Method 4: Install the latest version of Microsoft DirectX

To download and install the latest version of DirectX, visit the
following Microsoft Web site:If the issue continues to occur, go to Method 5.

Method 5: Update your sound card driver

Contact the manufacturer of your sound card to obtain and
install the latest version of the driver. For information
about how to contact the manufacturer of your video adapter or sound card, see
the “References” section of this article.

To determine whether applicable driver updates are
available, visit the following Microsoft Windows Update Web site:

To view a video that shows how to use Microsoft Windows Update, click Play to view this streaming media presentation:

<<The embedded streaming media event requires Microsoft Windows Media Player to view.>>

‘;
var sLoading = ‘Loading Microsoft Windows Media Player components…’;
var sWMPInvocation;
var sObjectCode;

if (g_bIsNetscape6)

// Netscape 6
sObjectCode = sLinkForNetscape6;

else if (g_bIsNetscape)
{
// All other Netscape
sObjectCode =

More:
Troubleshoot sound-related problems with Microsoft games or mapping programs

Page 22 of 732« First...10...2021222324...304050...Last »

Recent Comments

    Archives

    Categories