Microsoft Support

Page 41 of 708« First...102030...3940414243...506070...Last »

How to configure Exchange Server 2003 so that users can log on to OWA without entering a domain name

This article describes how to configure Microsoft Exchange
Server 2003 so that users can log on to Microsoft Outlook Web Access without
entering a domain name.
When users try to log on to Outlook Web Access, they receive
a logon dialog box that requires them to enter a user name and a password. By
default, the user name should be entered in the following format in the
Exchange Server 2003 logon dialog box:

Domain NameUser Name

However, if you have users who are from different domains and who
access Outlook Web Access, you may want to configure Exchange Server 2003 so
that users can access Outlook Web Access without entering the domain
name.

Important

  • If you configure Exchange Server 2003 to accept a logon to
    Outlook Web Access without the domain name, this behavior is implemented by
    similar entries that are automatically made in Microsoft Internet Information
    Services (IIS) for the Microsoft Exchange Web site.

    If you configure
    Exchange Server 2003 to accept logons to Outlook Web Access without the domain
    name, the LookupAccountName function in IIS will first verify the local domain for the user
    account name. Then, the other domains in the forest are verified until the LookupAccountName function finds a matching account name.

    When a matching
    account name is found for the user, the password is verified. If the password
    that the user entered in the logon dialog box does not match the password in
    Active Directory directory services, the logon is rejected.

    Therefore, you must make sure that you have unique user names across
    all domains if the following conditions are true:

    • You have users from multiple domains who access Outlook
      Web Access.
    • You configure Exchange Server 2003 so that users do not
      have to enter a domain name when they log on to Outlook Web Access.
  • Basic Authentication is less secure than Integrated Windows
    authentication. If you configure Exchange 2003 to accept logons to Outlook Web
    Access without the domain name, we recommend that you use Basic Authentication
    with Secure Sockets Layer (SSL) to help make your environment more secure. For
    more information about how to configure SSL, visit the “Reference”
    section.

To configure Exchange Server 2003 so that users can log on to
Outlook Web Access without a domain name, the following conditions must be
true:

  • The Microsoft Exchange server must be running Microsoft
    Windows Server 2003 Service Pack 1 (SP1).
  • If Windows Server 2003 SP1 is not installed, you must have
    the hotfix that is in the following Microsoft Knowledge Base article installed
    on the Exchange server.
    827991

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

    “HTTP error 401.1 – Unauthorized: Access is denied due to invalid credentials” error message if the Basic

  • The Exchange virtual directory must be configured to accept
    only Basic Authentication.

To enable Outlook Web Access to accept user logons without the
domain name, follow these steps on all Microsoft Exchange servers including
front-end and back-end servers:

  1. Start Exchange System Manager.
  2. Expand Administrative Groups, expand
    Administrative_Group_Name, and then
    expand Servers.
  3. Expand
    Your_Server_Name, expand
    Protocols, and then expand HTTP.
  4. Expand Exchange Virtual Server,
    right-click Exchange, and then click
    Properties.
  5. Click the Access tab, and then click
    Authentication.
  6. Click to select the Basic authentication (password
    is sent in clear text)
    check box.
  7. Click to clear all other check boxes.
  8. In the Default domain box, type a
    backslash to replace the domain name that is already entered in the
    box.
  9. Click OK two times.
  10. Right-click Public, and then click
    Properties.
  11. Click the Access tab, and then click
    Authentication.
  12. Click to select the Basic authentication (password
    is sent in clear text)
    check box.
  13. Click to clear all other check boxes.
  14. In the Default domain box, type a
    backslash to replace the domain name that is already entered in the
    box.
  15. Click OK two times.
  16. Quit Exchange System Manager.

Note
If this Exchange Server 2003 server is a single server (there is no front-end server), and
if you are using Exchange ActiveSync, configure the Exchange ActiveSync clients to
synchronize with the Exchange Server 2003 server after you make these changes. To do this, follow Method 2 in the “Resolution”
section in the following article in the Microsoft Knowledge Base:

817379

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

Exchange ActiveSync and Outlook Mobile Access errors occur when SSL or forms-based authentication is required for Exchange Server 2003

For more information about SSL for Outlook Web Access in
Exchange Server 2003, visit the following Microsoft TechNet Web site:

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


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

See the article here:
How to configure Exchange Server 2003 so that users can log on to OWA without entering a domain name

Windows Server System software not supported within a Microsoft Virtual Server environment

The following Windows Server System software is not supported within a Microsoft Virtual Server environment: Note Microsoft ISA Server 2006 is supported within a Microsoft Virtual Server 2005 R2 environment.

Article ID: 897614 – Last Review: June 20, 2014 – Revision: 14.0


Applies to
  • Microsoft Virtual Server 2005 Enterprise Edition
  • Microsoft Virtual Server 2005 Standard Edition
  • Microsoft Virtual Server 2005 R2 Enterprise Edition
  • Microsoft Virtual Server 2005 R2 Standard Edition
  • Microsoft Exchange Server 2007 Enterprise Edition
  • Microsoft Exchange Server 2007 Service Pack 1
  • Microsoft Exchange Server 2007 Standard Edition
kbhowto kbinfo fep2010swept KB897614

View article:
Windows Server System software not supported within a Microsoft Virtual Server environment

How to register a store event sink using Regevent.vbs on Exchange

This article describes:
  • The step-by-step guide on how to register store event
    sinks
  • The steps on how to delete store event sinks
  • More examples of commands used for event sink
    registrations

Note Besides using regevent.vbs to register an event sink, there are
also other methods to register event sinks. For example, a developer can
complie the codes into .dll files, and then register these .dll files directly
on the Exchange server. This article introduces one method of registering event
sinks when using regevent.vbs.

A step-by-step guide on how to register store event sinks
Before you use regevent.vbs to register the event sink VB
script, you need to register a new COM+ application on the Exchange server to
properly execute script-based store events. Please follow the steps below:
  1. To start the Component Services console, click Start,
    select Programs, Administrative Tools, and Component Services.
  2. In the Component Services snap-in, expand the list in the
    following order: Component Services, Computers, and My Computer.
  3. Right-click COM+ Applications in the left pane, and select
    New and Application.
  4. Click Next and then choose the “Create An Empty
    Application” button.
  5. Enter ScriptEventSink as the name for the new
    application.
  6. Confirm that the Server Application radio button is
    selected and click Next.
  7. Click Next and click Finish.
  8. Select a user that will have owner permissions for the
    application you are creating, or choose the current user by selecting
    “Interactive User – The Current Logged On User” radio button.

    Note If you choose Interactive User, make sure the account that you
    are currently logged on with has one of the following permissions:

    • Explicit “Full mailbox access” right on the mailbox you
      plan to publish the sink to
    • Explicit Allow for the “Receive As” right on the
      mailbox store
  9. Open the newly created COM+ Application you just created,
    right-click on the Components subfolder, and choose New and, then, select
    Component.
  10. Click Next, then choose Install New
    Component(s).
  11. Browse the file system and select
    ExchsrvrBinexodbesh.dll. Click Next and Finish.

After registering the new COM+ application, you need to write
the event sink VB script file. Here is a sample event sink that does nothing
but log its’ existence:


We assume that the sink is now saved in the testscript.vbs., you can now
register this event sink VB script using the following steps:

  1. Click Start, select Run, and type “cmd” (without the
    quotation marks) to enter the command prompt.
  2. Change the directory to ExchsrvrBin and type the
    following 2 commands:

    regsvr32 exodbesh.dll
    regsvr32
    exodbprx.dll

  3. Copy the regevent.vbs (located in the Program
    FilesExchange SDKSDKSupportOLEDBScripts directory.) and the event sink VB
    script files onto the root of the C drive.
  4. Start the command prompt, and change to the directory of
    C:. Type the command to run the regevent.vbs. The following command is one
    example:

    cscript regevent.vbs add “onsave;ondelete”
    ExOleDB.ScriptEventSink.1
    “file://./backofficestorage/contoso.com/MBX/smith/inbox/testsink” -m deep -file
    “c:testscript.vbs”

    Note This command is used to register the event sink VB script named
    testscript.vbs in the Inbox of the mailbox named smith. In the command above,
    you replace contoso.com with the default domain name referenced on the “Local
    path” field in the Virtual Directory tab of the Exchange virtual directory
    properties in the Internet Information Services snap-in.

How to delete store event sinks

If you want to delete the event sink you registered in a
particular mailbox, you can perform the following steps:

  1. Start the command prompt, and change to the directory where
    the regevent.vbs is located.
  2. Type the command to run regevent.vbs. The following code is
    one example of the command:

    cscript regevent.vbs delete
    “file://./backofficestorage/contoso.com/MBX/smith/inbox/testsink”

More examples of commands for event sink registrations

Example 1
The above command example is to register a specific mailbox.
To register event sinks to a specific store with the regevent.vbs script, here
is an example:

cscript regevent.vbs add OnSyncSave test.sink
“file://./backofficestorage/contoso.com/MBX/SystemMailbox9ADEA9EA-3924-401F-9C70-0
3B6B7378C9D/StoreEvents/GlobalEvents/testsink” -m deep

In the above
command, the event sink is actually registered to the system mailbox named
SystemMailboxGUID in the mailbox store. To determine the GUID:

  1. In the Exchange System Manager, find the mailbox store that
    you want to register the event sink to.
  2. Select the “Mailboxes” node under the mailbox store to see
    the list of its’ mailboxes. You will see a mailbox called
    “SystemMailboxGUID.” The GUID is the GUID you want.

Example 2
The following example uses the RegEvent script to register an
OnSyncSave event to a mailbox:

cscript regevent.vbs add OnSyncSave
ExOleDB.ScriptEventSink.1
“file://./backofficestorage/contoso.com/user1/inbox/eventsink1″ -m deep -file
“c:script1.vbs”

Example 3
The following example uses the regevent script to register an
OnSave and OnDelete event to the public folder named folder1 under the Public
Folders tree:

cscript regevent.vbs add “OnSave;OnDelete”
ExOleDB.ScriptEventSink.1 “file://./backofficestorage/contoso.com/Public
Folders/folder1/testsink” -m deep -file “c:vbscript1.vbs”

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


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

Originally posted here:
How to register a store event sink using Regevent.vbs on Exchange

FIX: Some PAL format digital video cameras are incorrectly detected as NTSC format digital video cameras

Some Phase Alternating Line (PAL) format digital video (DV) cameras are incorrectly detected as National Television Standards Committee (NTSC) format DV cameras. This problem can cause corrupted video output.
If a PAL-format DV camera incorrectly reports that it supports MPEG2TS data format, the PAL-format DV camera is incorrectly assumed to be an NTSC format DV camera.
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next release that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone 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.

The following file is available for download from the Microsoft Download Center:

Collapse this imageExpand this image

Download the WindowsXP-KB893008-x86-ENU.exe package now.

(http://download.microsoft.com/download/c/7/f/c7f94029-880d-49e6-8eb6-1f95817e9892/WindowsXP-KB893008-x86-ENU.exe)

For additional information about how to download Microsoft Support files, click the following article number to view the article in the Microsoft Knowledge Base:

119591

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

How to obtain Microsoft support files from online services

Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help to prevent any unauthorized changes to the file.

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.

   Date         Time   Version            Size    File name
   --------------------------------------------------------------
   19-Jan-2005  20:21  5.3.2600.2601      51,200  Msdv.sys
Microsoft has confirmed that this is a bug in the Microsoft products that are listed in the “Applies to” section.

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

kbtshoot kbfix kbqfe kbhotfixserver KB893008

Excerpt from:
FIX: Some PAL format digital video cameras are incorrectly detected as NTSC format digital video cameras

Description of the Microsoft GDI+ Detection Tool: September 14, 2004

As part of the September, 2004 Microsoft Security Bulletin release process, we have created the Microsoft GDI+ Detection Tool that detects
if you have any one of the Microsoft programs installed on your computer that are listed in the
“Applies To” section. If the tool detects these programs, you will be redirected to a
Web page that contains the latest security information and security
bulletins.

We
recommend that you frequently visit the Microsoft Windows Update Web site and
the Microsoft Office Update Web site to install security updates on your
computer.

We have released security bulletin, MS04-028. The
security bulletin contains all the relevant information about the security
update, including the file manifest information and the deployment options. To view the
complete security bulletin, visit the following Microsoft Web site:

Note This article describes the tool. If you click No in the “How to run the Microsoft GDI+ Detection Tool” section, you can go to the Microsoft GDI+ Detection Tool download by clicking the following link:

Prerequisites

You must be logged on to the computer with administrator
permissions or you must be a member of the administrators group to run the Microsoft GDI+
Detection Tool. If you do not have administrator permissions, you will receive
the following error message when you try to run the tool:

You do not have administrators privileges on this
computer. Some installations cannot be completed successfully unless they are
run by an administrator.

When you click Continue and
then you accept the license agreement, you receive the following error
message:

You do not have administrator privileges on this
machine. This installation cannot be completed correctly unless it is run by an
administrator.

How to obtain the Microsoft GDI+ Detection Tool from the Windows Update Web site or from the Download Center

  1. To download the Microsoft GDI+ Detection Tool from the
    Microsoft Download Center, visit the following Microsoft Web site:

    Notes

    • We recommend that you download the Microsoft GDI+ Detection Tool from the following Microsoft Windows Update Web site: http://update.microsoft.com

      (http://update.microsoft.com)

      If you download the tool from the Windows Update Web site,

      you can run the tool only one time. To run the tool again, you must download the tool
      from the Microsoft Download Center.

    • If you download and then run the Microsoft GDI+ Detection Tool from the Windows Update Web site, start following procedures from step 2 of the “How to run the Microsoft GDI+ Detection Tool”
      section.
  2. Click Download, and then click Save.

    If want to download the Microsoft GDI+ Detection Tool for a
    different language, click the Change language drop-down list,
    and then choose the language you want.

  3. In the Save As dialog box, choose the
    location where you want to save the Microsoft GDI+ Detection Tool, and then click
    Save.
  4. Click Close when the download has
    completed.

How to run the Microsoft GDI+ Detection Tool from the Windows Update Web site or from the Download Center

  1. In the location where you saved the Microsoft GDI+ Detection
    Tool, double-click the Gdidettool.exe file.
  2. Click Yes to accept the license
    agreement.
  3. If the Microsoft GDI+ Detection Tool detects any one of the
    Microsoft programs that are listed in the “Applies To” section, you will receive
    the following message:
    The software tool has detected
    that you are running Microsoft software that may contain a security
    vulnerability. There are security updates available from Microsoft that fix
    this security vulnerability.

    Would you like to learn more about the
    security vulnerability as well as the necessary security updates that address
    it? (Note that if you click No this tool will not prompt you
    again.)

  4. If you receive the message, use one of the following procedures:
    • Click No to the message in step 2, and then click OK. You receive the
      following message:
      The software tool has detected that
      you are running Microsoft software that may contain a security vulnerability.
      If you do not install the latest security updates, your system may be at risk.
      To learn more about the security vulnerability and how to install the latest
      security updates, or to run the software tool again, we encourage you to
      visit:

      http://support.microsoft.com/?kbid=873374

      After you complete this step, the GDI+ Dectection Tool quits.

    • Click Yes to the message in
      step 2. After you click Yes, you are redirected to visit the Microsoft TechNet Security Resource
      Center for the latest security information and security bulletins. This choice is highly recommended.

Install Microsoft Windows security updates from the Microsoft Windows Update Web site

We recommend that you visit the Microsoft Windows Update
Web site to determine whether your computer requires security updates for the
version of Microsoft Windows you have installed. To find information about Windows security updates, visit the following Microsoft Web site:

Install Microsoft Office program security updates from the Microsoft Office Update Web site

We recommend that you visit the Microsoft Office Update
Web site to determine whether your computer requires security updates for the
Microsoft Office programs that you have installed on your computer. To find information about Microsoft Office program security updates, visit the following Microsoft Web site:

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


Applies to
  • Microsoft .NET Framework 1.1
  • Microsoft .NET Framework 1.0
  • Microsoft Digital Image Suite 9
  • Microsoft Digital Image Pro 9
  • Microsoft Greetings 2002 Standard Edition
  • Microsoft Picture It! Digital Image Pro 7.0
  • Microsoft Picture It! Photo 2002 Premium Edition
  • Microsoft Picture It! Publishing 2002 Platinum Edition
  • Microsoft Picture It! Publishing 2002 Gold
  • Microsoft Picture It! Photo 7.0 Premium Edition
  • Microsoft Visual Studio .NET 2003 Academic Edition
  • Microsoft Visual Studio .NET 2003 Enterprise Architect
  • Microsoft Visual Studio .NET 2003 Enterprise Developer
  • Microsoft Visual Studio .NET 2003 Professional Edition
  • Microsoft Visual Studio .NET 2002 Academic Edition
  • Microsoft Visual Studio .NET 2002 Enterprise Architect
  • Microsoft Visual Studio .NET 2002 Enterprise Developer
  • Microsoft Visual Studio .NET 2002 Professional Edition
  • Microsoft Office Professional Edition 2003
  • Microsoft Office Basic Edition 2003
  • Microsoft Office Small Business Edition 2003
  • Microsoft Office 2000 Premium Edition
  • Microsoft Office 2000 Professional Edition
  • Microsoft Office 2000 Small Business Edition
  • Microsoft Office 2000 Standard Edition
  • Microsoft Office 2000 Developer Edition
  • Microsoft Office XP Small Business Edition
  • Microsoft Office XP Standard Edition
  • Microsoft Office XP Developer Edition
kbqfe atdownload kbsecbulletin kbsecurity KB873374

See the article here:
Description of the Microsoft GDI+ Detection Tool: September 14, 2004

How to disable the ADODB.Stream object from Internet Explorer

An ADO stream object contains methods for reading and writing binary files and text files. When an ADO stream object is combined with known security vulnerabilities in Microsoft Internet Explorer, a Web site could execute scripts from the Local Machine zone. To help protect your computer from this kind of attack, you can manually modify your registry.

An ADO stream object represents a file in memory. The stream
object contains several methods for reading and writing binary files and text
files. When this by-design functionality is combined with known security
vulnerabilities in Microsoft Internet Explorer, an Internet Web site could
execute script from the Local Machine zone. This behavior occurs because the ADODB.Stream object permits access to the hard disk when the ADODB.Stream object is hosted in Internet Explorer.
Any line-of-business Web application that requires a file to
be loaded or to be saved to the hard disk may use the ADODB.Stream object in Internet Explorer. For example, if an intranet server
hosts a form that an employee must download and fill out, the ADODB.Stream object is used to obtain the file and to save the file locally.
After the user edits the file locally and submits the file back to the server,
the ADODB.Stream object is used to read the file from the local hard disk and to
send the file back to the server.

We strongly recommend that you use
different methods to provide this functionality. For example, you may use an
application or a control that requires the user to deliberately access the hard
disk.

Software update information

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:

322756

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

How to back up and restore the registry in Windows

Microsoft has provided three ways to disable the ADODB.Stream object from Internet Explorer. You can use Microsoft Windows
Update to update your computer, you can download an update file from the
Microsoft Download Center, or you can disable the ADODB.Stream object manually.

These methods work by creating the
following registry key:

HKEY_LOCAL_MACHINESOFTWAREMicrosoftInternet
ExplorerActiveX Compatibility0000566-0000-0010-8000-00AA006D2EA4

This registry key has a GUID for the ADODB.Stream object. When Internet Explorer recognizes this registry key,
Internet Explorer does not permit the component to be started in the browser.

Important notes

  • If you are running the ADODB.Stream object from a server (middle tier), disabling the ADODB.Stream object on the server does not affect ADODB.Stream object functionality with Microsoft Internet Information Services
    (IIS).
  • If you are running the ADODB.Stream object from a client by using Internet Explorer, disabling the ADODB.Stream object stops the ADODB.Stream object from being created in Internet Explorer.

Windows Update

To install this update, visit the following Microsoft Web site:

Microsoft Download Center update

To disable the ADODB.Stream object by using a registry key update that is available from the
Microsoft Download Center, visit one of the following Microsoft Web sites,
depending on your operating system:

Windows XP, Windows 2000, Windows NT, Windows Server 2003

Windows 9x, Windows MeWindows XP Version 2003, 64-Bit Edition
, Windows Server 2003, 64-Bit Edition
Additional information and download instructions are available on
the Microsoft Download Center Web site.

Manual process

To disable the ADODB.Stream object by manually creating the registry key, follow these steps:

  1. Close any open Internet Explorer browser
    windows.
  2. Click Start, and then click
    Run.
  3. In the Open box, type
    Regedit, and then click OK.
  4. In Registry Editor, locate the following registry key:

    HKEY_LOCAL_MACHINESOFTWAREMicrosoftInternet
    ExplorerActiveX Compatibility

  5. Right-click ActiveX Compatibility, point
    to New, and then click Key.
  6. Type the following name for the key:

    00000566-0000-0010-8000-00AA006D2EA4

  7. Right-click the new key, point to New,
    and then click DWORD Value.
  8. Name the value Compatibility
    Flags
    .
  9. In the right pane, right-click Compatibility
    Flags
    , and then click Modify.
  10. In the Edit DWORD Value dialog box, make
    sure that the Hexadecimal option is selected, type
    400 in the Value data box, and then
    click OK.
  11. Close Registry Editor.

When you set the compatibility flag, the ADODB.Stream object cannot access the hard disk of your computer in Internet
Explorer. However, the ADODB.Stream object can still access your hard disk outside Internet Explorer.

Important notes

When you add this registry key, only the ADODB.Stream object in Internet Explorer is affected. No other ADO objects are
affected by this change.

After you apply the update, you will receive
the following error message when you try to use an ADO stream object from an
HTML page in Internet Explorer:

ActiveX component can’t
create object: ‘ADODB.Stream’

If you are running an application in a
corporate intranet environment, and the corporate intranet environment
currently uses the ADODB.Stream object with Internet Explorer, applying this update may cause the
application to break. To restore application functionality, Microsoft
recommends that you first set your Internet Explorer browser security level to
High, and then you must clear the compatibility flag of the ADODB.Stream object

  1. To set your Internet Explorer browser security to high,
    follow these steps:

    1. In Internet Explorer, click Internet
      Options
      on the Tools menu.
    2. Click the Security tab. Under
      Select a Web content zone to specify its security settings,
      click Internet.
    3. Click Default Level, and then move the
      slider to High.
    4. Click Apply, and then click
      OK to close the Internet Options dialog
      box.
  2. Clear the compatibility flag of the ADODB.Stream object for Internet Explorer by setting the value to zero (0×0).
    Setting the value to zero (0×0) disables the key and restores functionality. To
    manually set the compatibility flag to zero, follow these steps:

    1. Click Start, and then click
      Run.
    2. In the Open box, type
      Regedit, and then click OK.
    3. In Registry Editor, locate the following registry key:

      HKEY_LOCAL_MACHINESOFTWAREMicrosoftInternet
      ExplorerActiveX Compatibility0000566-0000-0010-8000-00AA006D2EA4

    4. In the right pane, double-click Compatibility
      Flags
      .
    5. In the Edit DWORD Value dialog box,
      make sure that the Hexadecimal option is selected, type
      0 in the Value data box, and then click
      OK.
    6. Close Registry Editor.

Note You must restart Internet Explorer for your changes to take
effect.

For
additional information about how to strengthen the Local Machine zone in
Internet Explorer, click the following article number to view the article in
the Microsoft Knowledge Base:
833633

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

How to strengthen the security settings for the Local Machine zone in Internet Explorer

For more information about Internet security, visit
the following Microsoft Web site: For additional information about
how to stop ActiveX controls from running on your system, click the following
article number to view the article in the Microsoft Knowledge Base:

240797

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

How to stop an ActiveX control from running in Internet Explorer

Article ID: 870669 – Last Review: June 20, 2014 – Revision: 7.0


Applies to
  • Microsoft Internet Explorer 5.5
  • Microsoft Internet Explorer 6.0
  • Microsoft Data Access Components 2.5
  • Microsoft Data Access Components 2.6
  • Microsoft Data Access Components 2.7
kbpubtypekc atdownload kbinfo KB870669

Read More:
How to disable the ADODB.Stream object from Internet Explorer

The folder view always returns to the Inbox folder after you click Options in Microsoft Office Outlook Web Access for Exchange Server 2003

When you access a folder other than the Inbox folder in Microsoft Office Outlook Web Access for Exchange Server 2003, you may not return to the same folder after you click Options. Instead, you may return to the Inbox folder. For example, this may occur when you follow these steps:

  1. Click any folder other than the Inbox folder, such as the Deleted Items folder.
  2. Click Options, and then click Save and Close.

Instead of returning to the Deleted Items folder, the view is returned to the Inbox folder.

This behavior may occur when you install Exchange 2003 on a computer that contains nonstandard characters in its computer name. An example of a nonstandard character is a semicolon.

When you use Outlook Web Access to connect to the Exchange 2003 mail server that has nonstandard characters in its computer name, the nonstandard characters may cause your Web browser to not accept or to not generate HTTP cookies. Cookies are required for Outlook Web Access to function correctly. Without the required cookie, you may experience unexpected behavior, such as the behavior that is mentioned in the “Symptoms” section.

To resolve this issue, you must move the Exchange Server 2003 server to an Exchange Server 2003 server that has only standard characters in the computer name.

For additional information about nonstandard characters that are in a computer name, click the following article numbers to view the articles in the Microsoft Knowledge Base:

222823

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

Warning message after typing DNS name

228275

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

Computer name setup allows invalid characters in computer name

Exchange front-end servers

If your Exchange Server 2003 computer is a front-end server and it contains no mailboxes, you must install a new Exchange Server 2003 front-end server.

For additional information about how to make an Exchange Server 2003 computer a front-end server, click the following article number to view the article in the Microsoft Knowledge Base:

818476

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

You can configure either Exchange Server 2003 Standard Edition or Exchange Server 2003 Enterprise Edition as a front-end server

Exchange mailbox servers

If your Exchange Server 2003 computer is a mailbox server, you must install the Exchange Server 2003 server on a computer with only standard characters in the computer name.

For additional information about how to move mailboxes to another Exchange server, click the following article numbers to view the articles in the Microsoft Knowledge Base:

821829

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

Moving mailboxes in Exchange Server 2003

822892

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

Move Mailbox improvements in Exchange 2003

What to do after your new Exchange Server 2003 computer has been installed

After your new Exchange Server 2003 computer is installed, you can remove the Exchange Server 2003 computer that has the nonstandard DNS characters in the computer name from the Exchange organization.

For additional information about how to remove Exchange Server 2003 from your computer, click the following article number to view the article in the Microsoft Knowledge Base:

833396

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

How to remove Exchange Server 2003 from your computer

Important If the Exchange Server 2003 computer is the first server that is installed in an administrative group, see the following Microsoft Knowledge Base article.

822931

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

How to remove the first Exchange Server 2003 computer from the site

For additional information about Outlook Web Access behavior with nonstandard Exchange computer names, click the following article number to view the article in the Microsoft Knowledge Base:

822696

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

“An error occurred while trying to empty the Deleted Items folder” error message when you try to empty deleted items in Outlook Web Access

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

125329

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

Deployment and troubleshooting Outlook Web Access (OWA)

Article ID: 870917 – Last Review: June 20, 2014 – Revision: 3.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

More:
The folder view always returns to the Inbox folder after you click Options in Microsoft Office Outlook Web Access for Exchange Server 2003

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

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

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

Page 41 of 708« First...102030...3940414243...506070...Last »

Recent Comments

    Archives

    Categories