Page 434 of 995« First...102030...432433434435436...440450460...Last »

Link state issues and routing issues in Exchange 2000 Server and in Exchange Server 2003

Microsoft Exchange 2000 Server and Microsoft Exchange Server 2003 use routing groups to control message transport in your Exchange organization. A routing group is a group of “well-connected” Exchange Server computers. Each routing group has a computer that acts as the routing group master. This computer coordinates the link state changes that occur between routing groups in your organization. The link state is the status of the connection that is established between routing groups. Changes in the link state are recorded in link state tables. Connection problems between routing groups may include one or more of the following:

  • The routing group master stops responding.
  • A routing member node is not connected to the routing group master.
  • More than one computer determines that it is the routing group master.
  • Link state information is incorrect.

Several tools and methods are available to help troubleshoot these problems. You can use the WinRoute tool and increased diagnostic logging to help determine the cause of the routing problem.

This article discusses common link state issues and common
routing issues that you may experience in Microsoft Exchange 2000 Server and in
Microsoft Exchange Server 2003.

The purpose of a routing group

The routing group is the smallest unit of servers that are likely
to always be connected to one another. The routing group can be assumed to be
one node on the graph of connector paths, with multiple possible connectors
between routing groups.

To configure the way that messages are routed
between servers so that point-to-point connections between servers are always
made, the servers must be grouped in routing groups, and the Routing Group
connectors must be defined.

In a routing group, link state
information updates and routing information updates are pushed between master
nodes and member nodes through a persistent port 691 Transmission Control
Protocol (TCP) connection. Between two routing groups, servers advertise the
X-LINK2STATE verb to exchange link state information by comparing the MD5
digest in the Exchange organization information packet of the two routing group
bridgeheads. A mismatch triggers an exchange of link state information between
the two servers through SMTP port 25.

The role of a routing group master

The routing group master coordinates changes to link states that
are learned by servers in its routing group and retrieves updates from the
directory service. By having a single server coordinate the changes, you can
treat a routing group as a single entity for the purposes of computing a
least-cost path between routing groups in an organization.

What occurs when the routing group master stops responding

All servers in the routing group continue to operate on the same
information that they had at the time that they lost contact with the master.

When the routing group master comes back up, it examines the status
of all other servers, reconstructs the link state information, processes the
State Change Queue (SCQ), and then updates members in the routing group.

Common issues

The following sections present several routing issues that you
may experience. Additionally, the following sections suggest methods that you
can use to troubleshoot the issues.

Routing member node is not connected to master

When you use the WinRoute tool (Winroute.exe) to view Exchange
organization routing, you may see the words “connected to master – NO” and a
red X next to the organization’s name. These words and the red X indicate that
the routing member node is not connected to the master.

Collapse this imageExpand this image

In a routing group, the routing group nodes, including the
master, must be connected to the master node on Transmission Control Protocol
(TCP) port 691 to propagate routing information and link state information to
and from the master node.

Note To download the Microsoft Exchange Server 2003 WinRoute tool for
troubleshooting routing in an Exchange 2000 and Exchange 2003 mail-handling
environment, visit the following Microsoft Web site.
The following
file is available for download from the Microsoft Download
Center:

Collapse this imageExpand this image

Download
the Winroute.exe package now.

(http://www.microsoft.com/downloads/details.aspx?FamilyId=C5A8AFBF-A4DA-45E0-ADEA-6D44EB6C257B&displaylang=en)

For more 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 prevent
any unauthorized changes to the file.

To resolve this issue, follow these steps:

  1. Make sure that the Exchange Routing Engine Service (RESvc
    service) is started on all affected servers in the routing group and that it
    remains in a controlled state. If the service is in an unstable state, the
    server may not connect to master nodes. Investigate the root cause of any
    unstable services before you go to the next step.
  2. Verify that a firewall does not restrict TCP port 691. To
    do this, initiate a Telnet session to port 691 on the affected servers and on
    the master node. A Microsoft Routing Engine banner indicates an active state.
  3. At the command prompt, run the netstat –a –n command. The output of this command reveals all member nodes and
    the master itself connecting to TCP port 691 on the master node.
  4. In Event Viewer, check the application logs for any events
    that indicate a failure to authenticate by using the computer account , such as
    DomainserverName$. Events such as Transport events 962 and 961 indicate a
    failure of the RESvc service to connect.
  5. Verify that the affected servers or the Exchange Domain
    Server group that they belong to do not have the SendAs right missing, denied,
    or denied from a nested membership of another group. To do this, run the
    Exchange Trace Utility (Regtrace.exe), and then restart the RESvc service.
    For more information about
    RegTrace setup on Exchange 2000, click the following article number to view the
    article in the Microsoft Knowledge Base:
    238614

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

    How to set up Regtrace for Exchange 2000

    Note For additional information about tools and processes that you can
    use to troubleshoot and to diagnose transport issues and routing issues in
    Exchange 2003, download the Exchange Server 2003 Transport and Routing Guide online book. To download this book, visit the following Microsoft
    Web site:

  6. Verify that the affected servers can generate a
    ServicePrincipalName (SPN) for authentication. To verify this, check the
    network address attribute of the affected servers by using the ADSI Edit tool
    (ADSIEdit.exe) or by using the Lightweight Directory Protocol tool (Ldp.exe).

    Nodes in a routing group have to mutually authenticate with the
    routing group master to be connected. To do this, they use the ncacn_ip_tcp
    value in the Network address attribute of the Exchange Server computer to
    generate the SPN for the master node by using Kerberos authentication. Make
    sure that this value is a Fully Qualified Domain Name (FQDN) instead of a
    NetBIOS name or an IP address. Restart the RESvc service.

  7. Check the application log and the system log on all the
    affected servers for any Kerberos authentication errors. Kerberos
    authentication errors may be caused by an expired domain computer account
    password. To gain additional information about this issue, run the NLTEST
    utility with debug flags.
    For more information about how to run the NLTEST
    utility with debug flags, click the following article number to view the
    article in the Microsoft Knowledge Base:
    109626

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

    Enabling debug logging for the Net Logon service

    Important If the domain computer account password has apparently expired,
    you must contact Microsoft Product Support Services (PSS) to confirm and to
    correct the issue. For a complete list of Microsoft Product Support Services
    phone numbers and information about support costs, visit the following
    Microsoft Web site:

  8. Verify that the FQDN of the virtual server matches the FQDN
    in Domain Name System (DNS).
  9. If the membership of the routing group spans multiple
    domains, make sure that DNS is correctly designed and implemented between the
    domains.
  10. Look for any third-party applications that use Group Policy
    objects to restrict permissions or to restrict security settings.

Routing group master wars

In a routing group, the first server installed in the routing
group is automatically elected as the master node. As other servers are
installed, the administrator has the option to appoint another server as
master.

When the new routing group master is elected, only one server
should be assigned the master role at a time. This rule is enforced by an
algorithm that is based on the formula “(N/2) +1″
(where N denotes the number of servers in the
routing group). The algorithm calculates the number of servers in the routing
group that must agree and that must acknowledge the master. Therefore, the
member nodes send link state ATTACH data (information about the routing group)
to the master.

It is not uncommon for two or more servers to have
erroneous information about which server is the current routing group master.
For example, if a routing group master was moved or was deleted, and another
master node was not chosen, the MsExchRoutingMasterDN attribute may point to a
non-existent server.

This issue may also occur when an old master
does not detach as master, or when a problematic node keeps sending incorrect
link state ATTACH information.

Note In Microsoft Exchange Server 2003, if a routing group points to a
deleted object, the master node gives up its role as master and initiates a
shutdown.

To resolve this issue, use one of the following methods:

  • Look for link state data propagation through TCP port 691,
    for firewall hindrances such as firewall blocking of TCP port 691, and for SMTP
    filters.
  • Look for Active Directory replication latencies.
  • Look for network problem and latencies.
  • Look for deleted routing group masters or servers that no
    longer exist. If this is the case, a Transport event 958 that references a
    routing group master distinguished name that no longer exists is logged in the
    application log. Use the Lightweight Directory Protocol (Ldp.exe) tool or the
    ADSI Edit (Adsiedit.exe) tool to verify that this is the case.

Deleted routing groups are followed by object_not_found_in_DS

When servers are moved between routing groups, and when the
routing groups are subsequently deleted, if you use Winroute.exe you may see
the text object_not_found_in_DS next to the object name.

Collapse this imageExpand this image

This issue may occur if the routing engine
service tries to correlate an object that still exists in a dynamic routing
library that is maintained by the server with objects in Active Directory,
where the object does not exist any more.
Tips to resolve this issue:

  • Restart all servers in the organization at the same time.
    This action updates routing information. Additionally, this action removes
    deleted routing groups and deleted connectors.
  • Use the Remonitor.exe tool in injection mode.

    Note Contact Microsoft Product Support Services for information about
    the Remonitor.exe tool in injection mode. For a complete list of Microsoft
    Product Support Services phone numbers and information about support costs,
    visit the following Microsoft Web site:

  • Make sure that the servers are on a recent build of
    Exchange Server and that they have the Exchange Server service pack rollups
    installed.

    Note Applying the hotfix that is described in the following Knowledge
    Base article is no longer necessary if your servers are on a recent build of
    Exchange Server and have the current Exchange Server service pack rollups
    installed. If you cannot install the most recent Exchange Server service pack
    rollups, apply the hotfix that is described in the following Knowledge Base
    article:

    330279

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

    Deleted routing groups are listed in the WinRoute tool; fix requires Exchange 2000 SP3

  • Restart all Exchange Server services and Windows Management
    Instrumentation (WMI) services on all Exchange Server computers in the
    organization. This resolution is effective only if all servers are restarted at
    the same time.

    Note Contact Microsoft Product Support Services for information about
    restarting all servers at the same. For a complete list of Microsoft Product
    Support Services phone numbers and information about support costs, visit the
    following Microsoft Web site:

  • Make sure that the account that is logged on to the server
    has sufficient permissions. To do this, run Winroute.exe under the System
    Account.

    Note The lack of sufficient read permissions may cause Winroute.exe to
    incorrectly report object_not_found_in_DS.

Connectors are not reported to be marked as “DOWN”

When you use the Winroute.exe tool to view Exchange routing
topology, you may see that connectors that are unavailable are reported as
being available ( they are marked as “UP”). This behavior may occur for the
following connectors:

  • Connectors that use DNS to route. For example, this
    behavior may occur for SMTP connectors that use DNS instead of smart
    host.
  • Microsoft Exchange 5.5 Server connectors or Exchange
    Development Kit (EDK) connectors. These connectors do not use link state
    routing.
  • Routing group connectors with source bridgeheads of the
    “any” type.
  • Any connectors where one bridgehead is an Exchange 5.5
    Server computer.
  • Connectors that use smart host settings and recently
    changed smart hosts.

Link state oscillations: connectors are repeatedly marked as “UP” and then as “DOWN”

This common scenario involves connectors being marked as “UP” and
then as “DOWN” repeatedly. It causes excessive link state updates between
servers. These excessive link state updates cause a very expensive and frequent
recalculation of routes within the server. This is also indicated by Event 4005
Reset Routes. This issue may occur in the following scenarios:

  • Network problems. Use a network trace to diagnose this
    scenario.
  • A reaction to link status notification calls from
    underlying protocol services, such as SMTP/AQ and message transfer agent (MTA).
    This behavior is caused by interference on the X.400 protocol levels or on the
    SMTP protocol levels by third-party applications.

    In this scenario,
    only a network monitor capture can reveal the issues that are involved.
    Additionally, if you notice very frequent changes of the major versions, of the
    minor versions, and of the user versions in the WinRoute tool, this may also
    indicate a link state problem (see the WinRoute routing version changes section).

To reduce link state oscillations, apply the hotfix that is
described in the following article in the Microsoft Knowledge Base:

825314

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

Link state traffic saturates slow links between servers

After the hotfix has been applied, you must enable
the AttachedTimeout registry subkey to make sure that the hotfix works as
expected.

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

To enable the AttachedTimeout registry value,
follow these steps:

  1. Click Start, click Run,
    type regedit, and then click
    OK.
  2. Locate the

    HKLMSYSTEMCurrentControlSetServicesRESvcParameters

    subkey.

  3. Right-click the Parameters subkey, point
    to New, and then click DWORD
    value
    .
  4. Name the new value
    AttachedTimeout.
  5. Double-click AttachedTimeout, and then
    type any data value from 1 to
    604800. Click to select Decimal for the
    Base type.

    Note The AttachedTimeout value represents time in seconds. The valid
    range for this value is 1 second to 604,800 seconds (7 days).

  6. Click OK, and then quit Registry
    Editor.

Note Contact Microsoft Product Support Services for more information
about the AttachedTimeout registry subkey. For a complete list of Microsoft
Product Support Services phone numbers and information about support costs,
visit the following Microsoft Web site:

How connector states affect link states

A connector can be located anywhere in any routing group in the
Exchange organization. A specific connector that is frequently marked as “UP”
and as “DOWN” may seriously affect the possible routes that a message can take
through the organization. Such a connect may even lead to mail loops.

Exchange routing chooses the most optimal path, based on variables
such as cost, message type, and restrictions. Exchange routing locates the next
server for a message to make the next hop to, and then Exchange routing gives
the name of the next server to Message Queuing. Because the oscillating state
of a connector causes link state changes, Exchange has to repeatedly
recalculate the optimal path. This recalculation process involves queries to
the directory service.

How link states affect connector states

When Message Queuing detects that a link to the bridgehead server
on a connector failed, it calls into routing by using a method that is named
LinkStateNotify( ). Routing then suppresses this information for up to 10
minutes to prevent connector state fluctuation, and then routing relays this
information to the routing group master. If routing decides to mark the
connector as “DOWN,” this change is propagated to all computers in the
organization, including the computer where the original failure occurred. This
behavior leads to a very expensive process that is named “reset routes.”
Thereafter, the routing engine no longer recommends that the Advanced Queuing
engine (AQ) connect to the “failed” next-hop computer. The reverse is true for
a connector that is marked as “UP.”

WinRoute routing version changes

The WinRoute tool reports routing versions in the following
format: “RoutingGroup (d5.2.3).” The three numbers that are separated by
periods that follow the routing group name are the major version, the minor
version, and the user version.

Major version changes are typically
changes in directory service that involve routing and connectors. If there is a
frequent change here, monitor it by using the Remonitor.exe tool, and then
investigate it for a probable root cause. For example, an administrator may
make significant changes in directory service. A major version of zero is shown
for isolated routing groups with no routing and no link state exchange with
other nodes. Additionally, a major version of zero is shown for Microsoft
Exchange 5.5 Server-based sites because they do not use link state information.

A minor version change may indicate changes to the state of a
connector. Frequent changes may be caused by faulty links or by links that
fluctuate between the “UP” state and the “DOWN” state. AQ tries to send a
message over a connector. If AQ fails, it sends a notification to routing to
mark the connector as “DOWN.” Then, AQ initiates retry pings to the connector.
After AQ detects that the connector is up, AQ notifies routing by calling the
LinkStateNotify() method.

User version changes may occur in the
following situations:

  • Servers attach to or detach from master nodes.
  • WMI services send data to the routing group master.
  • There is callback registration by routing clients such as
    MTA or SMTP.
  • There are routing group membership changes.
  • You rename the routing group
  • A new master node is elected.

Base-level callbacks

Routing base-level callbacks are updates that occur after a
routing group object is modified, and after the updates are then propagated
throughout the organization. The Winroute.exe major version changes may be
triggered by the following events:

  • Renaming a routing group
  • Electing a new routing group master
  • Removing a routing group member
  • Adding a routing group member

One-level callbacks

One-level callbacks are typically updates to routing when changes
that are one level below the routing group object are detected. Some examples
of this are deleting a connector in the routing group and adding a connecter to
the routing group.

DNS

Incorrect configuration of Domain Name System (DNS) may cause
several routing issues. These issues are addressed in the following
sections.

The DNS Resolver sink event on the SMTP virtual server

The DNS Resolver sink event is primarily for resolving external
SMTP domains. Your internal Active Directory servers and DNS servers still have
to be able to resolve all Exchange Server computers internally.

The
SMTP virtual server DNS Resolver sink event is synchronous and can affect
performance on a heavily used server. To slightly improve the situation,
increase the number of threads that are used for DNS lookups.

The DNS
Resolver sink event is used only when a server is not in the Exchange
organization. Exchange Server determines this by querying Active Directory
directory service.

Windows 2000 DNS API

If you use the DNS Resolver tool for name resolution, the lookups
that are created by this tool are asynchronous and are much faster than using
the default settings of the external DNS Resolver sink event.

Exchange DNS that uses the Windows DNS API or the Exchange DNS Resolver sink
event has to be able to resolve an Internet Protocol address (IP address) in
the following ways:

  • mail exchanger resource record (MX record)-to-IP
    address
  • MX record -to-A record-to-IP address
  • MX record-to-CNAME record-to-A record-to-IP
    address
  • CNAME record-to-A record-to-IP address
  • A record-to-IP address

DNS records that are incorrectly configured, especially MX
records and CNAME records, may seriously affect mail flow.

Note Although Microsoft Exchange Server 2003 does provide limited
support for chained CNAME records, we do not recommend implementing this
configuration.

In Microsoft Exchange Server 2003, the external DNS
Resolver sink event has been improved. Additionally, you can use the DNS
Diagnostic utility (DNSdiag.exe) from the Windows Server 2003 Resource Kit to
troubleshoot DNS issues that involve the external SMTP resolver and the Windows
TCP/IP DNS. DNSdiag.exe shows the asynchronous queries and the synchronous
queries to Global DNS servers or to the DNS server that are called by the DNS
sink event. Additionally, DNSdiag.exe shows any corresponding failures or
errors.

Note The DNS Diagnostic utility is also known as also known as the DNS
Resolver tool. They are the same file, DNSdiag.exe. The following file is available for download from the Microsoft
Download Center:

Collapse this imageExpand this image

Download
the Dnsdiag.exe package now.

(http://www.microsoft.com/downloads/details.aspx?familyid=9d467a69-57ff-4ae7-96ee-b18c4790cffd&displaylang=en)

For more 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 prevent
any unauthorized changes to the file.

See the original post:
Link state issues and routing issues in Exchange 2000 Server and in Exchange Server 2003

Overview of the Exchange Server 2003 Connector for Lotus Notes

Welcome to the first edition of the Exchange Support Voice
column. We hope that you enjoy it and will return for more. This month we will
provide a concise overview of the Microsoft Exchange Server 2003 Connector for
Lotus Notes. This article aims to give existing administrators and support
individuals more detail about the inner workings of the Connector for Lotus
Notes. For details about how to set up the environment for the Connector for
Lotus Notes, please review the articles that are referenced throughout this
article.

Introduction

What are Lotus Domino and Lotus Notes?

Lotus Domino is the messaging platform that is produced by IBM.
Lotus Notes is the client software that allows users to connect to their
mailboxes on Domino servers.

Each Notes user exists in a Domino
domain. When you send mail from Exchange to a Domino user, you can type the
following format.

One-off addressing

  • Notesuser1@Domino_domain
  • “NOTES:Notesuser1@Domino_domain

What is the Connector for Lotus Notes, what is it used for, and what does it require?

The Connector for Lotus Notes is included with Exchange Server
2003. This connector enables Exchange administrators to implement messaging
coexistence between Exchange Server and Lotus Domino organizations. The
connector provides mailflow connectivity and the ability to synchronize the two
directories. In this article, we will cover details about both mailflow and
directory synchronization.

Periodic updates for the Connector for
Lotus Notes, known as Web Releases, are available on the following Microsoft
Web site:

The most recent version of the connector requires the Exchange
Server 2003 connector server to be running the latest service pack for Exchange
Server 2003.

The Web Release versions of the Connector for Lotus
Notes and the Calendar Connector come with their own installers. This means
that you can install the connectors at any time. You are not required to
install the Connector for Lotus Notes as part of the Exchange Server 2003
installation. However, the Connector for Lotus Notes requires the Lotus Notes
client to be installed before you install the connector. If there is an
existing connector, it will be upgraded.

During installation, the
new connector creates a log file that is named the
Exchange_Lotus_Notes_Connector_Setup_Progress.log file. The account that is
being used to install the connector should have at least an Exchange
administrator in the local administrative group plus a member of the
Administrators group on the local server.

How does the Connector for Lotus Notes work?

To interact with Domino, the Connector for Lotus Notes uses Notes
API calls. For this reason, a Lotus Notes client must be installed on the
connector server. More details about this requirement are provided in the
following sections.

Preparing the Lotus Domino environment

For details about how to prepare the Domino environment, see the
“Exchange Server 2003 Coexistence and Migration for Lotus Domino Mail” topic on
the following Microsoft Web site:

Preparing the Exchange Server 2003 environment

The latest version of the Connector for Lotus Notes (Web Release
2.2) was released on December 7, 2005. The Connector for Lotus Notes Web
Release 2.7 will be released in June, 2006. Requirements for these versions
include:

  • Exchange Server 2003 Service Pack 2
  • Windows Server 2003
  • Lotus Notes client 6.5.x (tested with version 6.5.4)
  • Connectivity to a Domino server

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

316035

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

Lotus Notes Client versions that are tested with the Exchange Notes Connector

Exchange Server 2003 Service Pack 2 with the
Connector for Lotus Notes Web Release 2.2 requires Windows Server 2003. The
Notes client should be running Lotus Notes version 6.5.4.

After you
install and configure the connector, you need to enable Notes proxy addresses
on the recipient policy. This is required for mailflow and directory
synchronization. The Recipient Update Service will then automatically generate
the proxy addresses for each mailbox-enabled and mail-enabled account in the
Exchange organization by using a proxy address generator.

Typically,
the Exchange user’s Notes proxy address uses the Notes domain name “Exchange”.
If you need to change the Notes proxy addresses, you need to modify recipient
policies in Exchange System Manager.

For more information, see the
“Interoperating with and Migrating from Lotus Notes/Domino Messaging
Infrastructures to Exchange Server 2003″ topic on the following Microsoft
TechNet Web site:

Message flow between Exchange and Domino

Executables used by the connector

The Connector for Lotus Notes works in conjunction with the
Microsoft Exchange Connectivity Controller (MSExchangeCoCo) service.

The executable for the Connectivity Controller service is
Lscntrl.exe. The Connector for Lotus Notes, the Connector for Novell GroupWise,
and the Calendar Connector are dependent on the Connectivity Controller
service, which has the responsibility of managing these services.

The
following executables are loaded by the Connector for Lotus Notes:

  • Notes interface: Dispatch.exe
  • Transport to Exchange: Lsmexin.exe
  • Transport from Exchange: Lsmexout.exe
  • Exchange to Notes conversion: Lsmexnts.exe
  • Notes to Exchange conversion: Lsntsmex.exe
  • Notes Directory Synchronization: Lsdxa.exe

Diagnostic logging for each of these categories can be changed
by selecting the “LME-NOTES” service under the server properties in Exchange
Service Manager.

When the Connector for Lotus Notes service starts,
the DISPATCH process is started. This process starts each of the other five
processes.

Collapse this imageExpand this image

What message formats are used

Natively, Exchange keeps messages in TNEF (MAPI) format, and Notes
uses Composite Data (CD), which is the rich text formatting that is used in
Notes. Exchange and Notes can handle formats such as HTML/MIME.

Where do messages in transit reside?

A message going over the connector can be in any of the following
areas:

  • MTS-IN
  • MTS-OUT
  • READYIN
  • READYOUT
  • BADMAIL

These areas are MAPI queues that are located in the private
information store database. You can see these queues in the Exchange System
Manager. Messages in these queues are in Exchange format (TNEF).

A
message going over the connector can also be in any of the following areas:

  • EXCHANGE.BAD
  • MAIL.BOX
  • EXCHANGE.BOX

The areas are databases on the Domino side. You can examine
these databases by using the Lotus Notes client on the connector or by using
the Domino administrator program.

Note The BADMAIL folder is in the store, and it is used when the
LSMEXNTS or LSNTSMEX processes encounter problems with MAPI messages.

The EXCHANGE.BAD database is a Notes database. Corrupt messages will
be copied to this database when the LSMEXNTS or LSNTSMEX process fails to
convert a message.

Message flow from Exchange to Domino

Messages are transferred from Outlook on Exchange Server to Lotus
Notes on Domino by using the following process:

  1. Based on the recipient address (the target address or the
    one-off address), Exchange Categorizer determines that the message is destined
    for Domino. It then hands the message to the message transfer agent (MTA).
  2. The MTA delivers the message to the MTS-OUT folder (queue)
    in the connector mailbox. The LSMEXOUT process polls this folder and retrieves
    the message. This process converts the address from an X.400-based address to a
    Lotus Domino address. Then, it delivers the message to the READYOUT folder
    (queue) in the connector mailbox.
  3. The LSMEXNTS process polls this READYOUT queue, picks up
    the message, and then converts it to a Lotus Domino format, such as Composite
    Data (CD). Then, this process delivers the message (by using Notes API calls)
    to the Domino router mailbox, the MAIL.BOX file, on the Lotus Domino server.

Message flow from Domino to Exchange

  1. A Lotus Notes user sends a message to an Exchange user. The
    message is placed in the Mail.box mail router database on the Domino server.
    The mail router determines that the message is for Exchange and deposits it in
    the EXCHANGE.BOX database file.
  2. The Connector for Lotus Notes process, LSNTSMEX, polls the
    EXCHANGE.BOX file every 15 seconds by default. This process picks up the
    message by using Notes API calls. Then, this process converts the message to
    TNEF format and delivers it to the READYIN folder on the Exchange
    server.
  3. The LSMEXIN process takes the message in the READYIN
    folder, converts the address from a Lotus Domino address to an X.400 address,
    and then deposits it into the MTS-IN folder. Then, the Information Store
    service processes the message from the MTS-IN folder and places it in the SMTP
    service MTS-OUT folder. The message is routed from this folder.

Directory synchronization

Collapse this imageExpand this image

For each object (contact or Windows user) that is
created by directory synchronization in Active Directory, the object’s ImportedFrom attribute in Active Directory will be populated with the
connector’s ObjectGUID.

In the Domino directory, for the users that
are created during directory synchronization, the connector will add its
ObjectGUID from Active Directory to the $NotesDXAStamp field on the person
document in Domino. This is how the connector can identify the objects that it
created in each directory.

If you use the Immediate Full
Reload
option for Exchange to Domino synchronizations, all users that
are included for directory synchronization (when the OU containers were
selected) will be sent to Domino whether they have been synchronized previously
or not.

If you use the Immediate Update option for
Exchange to Domino synchronizations, only the objects that were modified since
the last synchronization will be resent.

If you use the
Immediate Full Reload option for Domino to Exchange
synchronizations, all Domino users will be sent to Active Directory even if
they were synchronized previously.

If you use the Immediate
Update
option for Domino to Exchange synchronizations, only the
objects that were modified in the Domino directory since the last directory
synchronization will be sent to Active Directory.

Lsdxa.exe uses the
following DLLs to perform directory synchronization:

  • Dxamex.dll: This DLL pulls and puts directory entries into
    Active Directory.
  • Dxanotes.dll: This DLL pulls and puts directory entries
    into the Notes Name and Address Book (NAB).

These two DLLs work in conjunction. They use the
ExchsrvrConndataTemp folder to share data.

Directory synchronization from Exchange and Active Directory to Domino

Dxamex.dll pulls entries from Active Directory and places the
results in the ExchsrvrConndataTempDxanotes.txt file. Then, Dxanotes.dll
imports this data into the Domino directory.

If a full directory
synchronization is initiated, the following steps take place:

  1. LSDXA calls Dxamex.dll, which polls Active Directory by
    using Active Directory Service Interfaces (ADSI).
  2. Dxamex.dll requests a complete list of users from the
    Export containers.
  3. When Dxamex.dll extracts the list of users from Active
    Directory, it writes them to the ExchsrvrConndataTempDxanotes.txt file. When
    Dxamex.dll starts to write to this file, LSDXA spawns a second instance of
    itself, which starts Dxanotes.dll.
  4. Dxanotes.dll reads this text file and creates or updates
    the user in NAB by using Notes API calls.
  5. The two LSDXA processes work in tandem. When one process
    writes to the Dxanotes.txt file, the other process reads from it.
  6. When directory synchronization is complete, the temporary
    text file is deleted, and the Usn.tbl file is updated.

If an update directory synchronization is initiated, the
following steps take place:

  1. LSDXA calls Dxamex.dll, which polls Active Directory by
    using Active Directory Service Interfaces (ADSI).
  2. The connector keeps track of the highest USN number for
    the last completed directory synchronization cycle. It records this number in
    Usn.tbl file that is located in ExchsrvrConndataDxamex folder.
  3. The connector requests a list of changed users from the
    Export containers that have USN numbers that are higher than the last directory
    synchronization cycle.
  4. When the connector extracts the list of users from Active
    Directory, it writes this list to the ExchsrvrConndataTempDxanotes.txt file.
    When it is starts to write to this file, LSDXA spawns a second instance of
    itself, which starts Dxanotes.dll.
  5. Dxanotes.dll reads this text file and creates or updates
    the user in NAB by using Notes API calls.
  6. The two LSDXA processes work in tandem. When one process
    writes to the Dxanotes.txt, the other process reads from it.
  7. When directory synchronization is complete, the temporary
    text file is deleted, and the Usn.tbl file is updated.

When the connector writes Active Directory users into the
Domino directory, it creates a field for these users named “$NotesDXAstamp”.
The connector populates this field with the connector server’s GUID. This is
how the connector keeps track of which Notes user documents were created by the
connector.

Directory synchronization from Domino to Exchange and Active Directory

Dxanotes.dll pulls entries from the Domino directory,
specifically, the NAB, and places the results in the
ExchsrvrConndataTempDxamex.txt file. Then, Dxamex.dll imports this data into
Active Directory.

If a full directory synchronization is initiated,
the following steps will take place:

  1. LSDXA calls Dxanotes.dll, which uses Notes API calls to
    issue a request for all Domino directory users.
  2. LSDXA writes the Domino users to the
    ExchsrvrConndataTempdxamex.txt file. Then, it spawns a second instance of
    itself, which starts Dxamex.dll.
  3. Dxamex.dll reads this text file and creates or updates the
    users in Active Directory by using ADSI.
  4. When directory synchronization is complete, the temporary
    text file is deleted, and the ExchsrvrConndataDxanotesPcta.tbl file is
    updated so that the “LastExtract” line is set to the date and time of the
    directory synchronization cycle that was just completed. This file is used
    during updates to determine changes.

If an update directory synchronization is initiated, the
following steps take place:

  1. LSDXA calls Dxanotes.dll, which looks up the last
    directory synchronization cycle date and time in the
    ExchsrvrConndataDxanotesPcta.tbl file. Then, LSDXA uses Notes API calls to
    initiate a request for any users that were modified since this last directory
    synchronization cycle.
  2. LSDXA writes the Domino users to the
    ExchsrvrConndataTempDxamex.txt file. Then, LSDXA spawns a second instance of
    itself, which starts Dxamex.dll.
  3. Dxamex.dll reads this text file and creates or updates the
    users in Active Directory by using ADSI.
  4. When directory synchronization is complete, the temporary
    text file is deleted, and the ExchsrvrConndataDxanotesPcta.tbl file is
    updated so that the “LastExtract” line is set to the date and time of the
    directory synchronization cycle that was just completed. This file is used
    during updates to determine changes.

When the connector creates Notes users’ representation in Active
Directory (usually as Contacts), it will add a field named “ImportedFrom”,
which is populated with the connector server GUID. This is how the connector
will keep track of the Notes users it created in Active Directory.

Factors that affect directory synchronization

Mapping files

You may have an issue where a full directory synchronization from
Active Directory and Exchange works, but an update directory synchronization
does not work. This can happen if the Usn.tbl file is out of sync.

For more information about this issue
and a resolution, click the following article number to view the article in the
Microsoft Knowledge Base:

902459

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

Active Directory cannot replicate the object to the Lotus Notes directory when you configure the Exchange Connector for Lotus Notes to use the “Immediate update” mode in the Exchange System Manager in Exchange 2000 Server or in Exchange Server 2003

When the connector is installed, it populates the
connector properties in Active Directory with the global catalog name that it
used. This information is stored in the msExchServer1NetworkAddress attribute. If this domain controller is no longer available,
directory synchronization may fail.

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

321287

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

Directory synchronization from Exchange 2000 to a foreign mail system fails in Exchange 2000

To keep track of the contacts’ user name changes in
Domino, a secondary Notes proxy address is applied to every contact. This proxy
address uses the Notes unique identifier (UID) that is obtained from each Notes
Person Document. Domino assigns a unique UID to each Person Document, much like
GUIDs in Active Directory.

Customizing directory synchronization

The default directory synchronization behavior can be changed to
fit an organization’s requirements. The mapping tables can be modified to
provide enough flexibility to meet most needs, such as synchronizing additional
attributes or changing the format of an attribute. For more detail about
customizing directory synchronization, see the “Connector for Lotus Notes
Directory Synchronization- Part 1″ blog entry on the following Web site:

Additional reading

For an online comprehensive resource on this subject, see the
“Exchange Server 2003 Coexistence and Migration for Lotus Domino Mail” topic on
the following Microsoft Web site: You can also download this topic in a help file format,
NotesDirAndMailMigrat.chm, from the following Microsoft Web site: To view the “Interoperating with and Migrating from Lotus
Notes/Domino Messaging Infrastructures to Exchange Server 2003″ topic, visit
the following Microsoft Web site: You can find several interesting blogs, including articles about
Notes DocLinks and how the connector provides support for them, at the
following Web site:

View post:
Overview of the Exchange Server 2003 Connector for Lotus Notes

FIX: You intermittently receive an error when you visit a Microsoft Commerce Server Web site that runs the Basket pipeline

When you visit a Microsoft
Commerce Server 2007 Web site or a Microsoft Commerce Server 2009 Web site,
you intermittently
receive
the following error message:
Server Error in '/' Application. 

Component Execution failed for component0x0  hr: 0x0
ProgID: Commerce.QueryCatalogInfo
Type 'Microsoft.CommerceServer.Runtime.Configuration.CommerceResourceCollection' in Assembly 'Microsoft.CommerceServer.Shared, Version=6.0.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' is not marked as serializable.
Description: An unhandled exception occurred during the execution of the current Web request. Please review the stack trace for more information about the error and where it originated in the code.

Notes

  • When this problem occurs, the error may disappear if you reload

    the
    Web
    site.

  • This problem typically occurs when the Basket pipeline is running.
This problem occurs because of an error in the QueryCatalogInfo pipeline component that is included in the Basket
pipeline.

Note The QueryCatalogInfo pipeline component is used to retrieve catalog information for each
item in the order form.

IMPORTANT  The initial hotfix for this problem was released in 2009, and a new version of this hotfix is now available. We strongly recommend you to install the latest version of this hotfix.  

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.

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, submit a request to 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

You must have Microsoft
Commerce Server 2007 Service Pack 2 (SP2) or Commerce Server 2009 installed to
apply this hotfix.

Restart requirement

You do not have to restart the computer after you apply this
hotfix. However, you must restart Internet Information Services (IIS) and the
Commerce Server Catalog Import Host COM+ application after you apply this
hotfix. To restart IIS, open a command prompt, type
the following command, and then press ENTER:

IISRESET /RESTART

Note This option stops all IIS services that are
running, and then restarts them.

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 item in Control
Panel.

Commerce Server 2007

Collapse this tableExpand this table

File name File version File size Date Time Platform
Microsoft. commerceserver.shared.dll 6.0.4109.50 224,056 10-Nov-10 13:38 x86
Commerce Server 2009

Collapse this tableExpand this table

File name File version File size Date Time Platform
Cs2009hotfixhelper.exe 6.0.4171.30 13,080 15-Oct-10 12:48 x86
Microsoft.commerceserver.shared.dll 6.0.4171.30 224,056 15-Oct-10 12:48 x86

Known issues

After you install or uninstall the hotfix for Commerce Server 2009, both Commerce Server 2009 and Commerce Server 2007 appear on the Start menu. You can safely ignore or delete the Commerce Server 2007 menu item.

Microsoft
has confirmed that this is a problem in the Microsoft products that are listed
in the “Applies to” section.
For more information about how to run a
pipeline, visit the following Microsoft Developer Network (MSDN) Web site:For more information about the QueryCatalogInfo pipeline component, visit the following MSDN Web site:You can turn on pipeline
logging
to troubleshoot pipeline
problems. For more information, visit the following MSDN Web site:

Article ID: 976815 – Last Review: September 22, 2013 – Revision: 4.0


Applies to
  • Microsoft Commerce Server 2007 Developer Edition
  • Microsoft Commerce Server 2007 Enterprise Edition
  • Microsoft Commerce Server 2007 Standard Edition
  • Microsoft Commerce Server 2009 Enterprise
  • Microsoft Commerce Server 2009 Standard
kbautohotfix kbexpertiseadvanced kbsurveynew kbqfe KB976815

Read more here:
FIX: You intermittently receive an error when you visit a Microsoft Commerce Server Web site that runs the Basket pipeline

SDP 3c3612788-17bb-4ec0-b0fd-f332576ee30d Commerce Server SharePoint Log Collector

The Commerce Server SharePoint Log Collector was designed to collect information used in troubleshooting support issues for Commerce Server 2009 and Commerce server 2009 R2.
This article describes the information that may be collected from a machine when running Commerce Server SharePoint Log Collector.

Information Collected

Collapse this tableExpand this table

Description File Name
SharPoint logs. ComputerName-timestamp.log (multiple files),

ComputerName-timestamp.usage (multiple files)

Additional Information

Commerce Server SharePoint Log Collector enables SharePoint Loggings and collects SharePoint logs whose lastModified timestamp is later than the logging enable time. Commerce Server SharePoint Log Collector only supports Commerce Server 2009 and R2 SharePoint sites, and only supports SharePoint Server 2010 and MOSS 2007.

References                                                                                                                            

KB 973559 – Frequently asked questions about the Microsoft Support Diagnostic Tool (MSDT) for Windows 7
http://support.microsoft.com/kb/973559

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

Note This is a “FAST PUBLISH” article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use

(http://go.microsoft.com/fwlink/?LinkId=151500)

for other considerations.

Article ID: 2564437 – Last Review: September 22, 2013 – Revision: 2.0


Applies to
  • Microsoft Commerce Server 2007 Developer Edition
  • Microsoft Commerce Server 2007 Enterprise Edition
  • Microsoft Commerce Server 2007 Service Pack 1
  • Microsoft Commerce Server 2007 Standard Edition
  • Microsoft Commerce Server 2009 Enterprise
  • Microsoft Commerce Server 2009 R2 Enterprise
  • Microsoft Commerce Server 2009 R2 Standard
  • Microsoft Commerce Server 2009 Standard

View the original here:
SDP 3c3612788-17bb-4ec0-b0fd-f332576ee30d Commerce Server SharePoint Log Collector

Manifest files that comply with Windows Server 2008 certification requirements are missing after you install Commerce Server 2007

Files Description C:Program FilesMicrosoft Commerce Server
2007pipeeditor.exe C:Program Files (x86)Common Filesmicrosoft
sharedEnterprise ServersCommerce ServerCSDWDbgSrv.exe C:Program Files (x86)Common Filesmicrosoft
sharedEnterprise ServersCommerce ServerSetupSetup.exe C:Program Files (x86)Common Filesmicrosoft
sharedEnterprise ServersCommerce ServerSetupPlatformrunmsi.exe Common setup application to launch MSIs from setup.exe C:Program Files (x86)Common Filesmicrosoft sharedHelp
8Microsoft Document Explorer 2005install.exe Merge module for
Document Explorer 2005, used to install our .hxs help files. C:Program Files (x86)Microsoft Commerce Server
2007cabarc.exe Tool used to build & extract files from CABs; used
by our site packing / unpacking (PuP) tool. (Cabinet SDK) C:Program Files (x86)Microsoft Commerce Server
2007Caxolap.exe C:Program Files (x86)Microsoft Commerce Server
2007CSConfig.exe C:Program Files (x86)Microsoft Commerce Server
2007CSConfig_old.exe C:Program Files (x86)Microsoft Commerce Server
2007CSDWImportWizard.exe C:Program Files (x86)Microsoft Commerce Server
2007CSHealthMonitor.exe C:Program Files (x86)Microsoft Commerce Server
2007CSVSSWriter.exe C:Program Files (x86)Microsoft Commerce Server
2007dmlrun.exe C:Program Files (x86)Microsoft Commerce Server
2007DMLService.exe C:Program Files (x86)Microsoft Commerce Server
2007pipeeditor.exe C:Program Files (x86)Microsoft Commerce Server
2007PuP.exe C:Program Files (x86)Microsoft Commerce Server
2007PupStatusUI.exe C:Program Files (x86)Microsoft Commerce Server
2007Business User ApplicationsCatalogAndInventorySchemaManager.exe C:Program Files (x86)Microsoft Commerce Server
2007Business User ApplicationsCatalogManager.exe C:Program Files (x86)Microsoft Commerce Server
2007Business User ApplicationsCustomerAndOrdersManager.exe C:Program Files (x86)Microsoft Commerce Server
2007Business User ApplicationsMarketingManager.exe C:Program Files (x86)Microsoft Commerce Server
2007Business User ApplicationsMuiSelectionTool.exe C:Program Files (x86)Microsoft Commerce Server
2007StagingBinCSCD.exe C:Program Files (x86)Microsoft Commerce Server
2007StagingBinCSS.exe C:Program Files (x86)Microsoft Commerce Server
2007StagingBinCSSsrv.exe C:Program Files (x86)Microsoft Commerce Server
2007StarterSiteSampleDataImport.exe C:Program Files (x86)Microsoft Commerce Server
2007Supporttracefmt.exe Tool used to format ETW traces into human
readable form (WDK) C:Program Files (x86)Microsoft Commerce Server
2007Supporttracelog.exe Tool used to capture ETW diagnostic traces
from the product (WDK) C:Program Files (x86)Microsoft Commerce Server
2007ToolsCatalogCycleCop.exe C:Program Files (x86)Microsoft Commerce Server
2007ToolsCreateCatalogAuthorizationStore.exe C:Program Files (x86)Microsoft Commerce Server
2007ToolsCreateProfilesAuthorizationStore.exe C:Program Files (x86)Microsoft Commerce Server
2007ToolsExpirePromoCodeReservations.exe C:Program Files (x86)Microsoft Commerce Server
2007ToolsExportCatalog.exe C:Program Files (x86)Microsoft Commerce Server
2007ToolsExportProfileXsd.exe C:Program Files (x86)Microsoft Commerce Server
2007ToolsImportCatalog.exe C:Program Files (x86)Microsoft Commerce Server
2007ToolsInventoryConsistencyChecker.exe C:Program Files (x86)Microsoft Commerce Server
2007ToolsOrderMapping.exe C:Program Files (x86)Microsoft Commerce Server
2007ToolsPipeReg.exe C:Program Files (x86)Microsoft Commerce Server
2007ToolsProfileKeyManager.exe C:Program Files (x86)Microsoft Commerce Server
2007ToolsPurgeCommerceData.exe C:Program Files (x86)Microsoft Commerce Server
2007ToolsRCXml2Resx.exe C:Program Files (x86)Microsoft Commerce Server
2007ToolsReportInstaller.exe C:Program Files (x86)Microsoft Commerce Server
2007UpgradeCS2007Upgrade.exe

Link:
Manifest files that comply with Windows Server 2008 certification requirements are missing after you install Commerce Server 2007

How to read the Flags value in the registry for Commerce Server Staging projects that run on Commerce Server 2007

This article describes how to read the Flags value in the
registry for Microsoft Commerce Server Staging (CSS) projects that run on
Microsoft Commerce Server 2007. Additionally, this article includes all the
possible Flags values and how to set these values from the command
line.
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 your operating system. Microsoft cannot
guarantee that these problems can be solved. Modify the registry at your own
risk.
All CSS configuration
information is contained in the following Microsoft Windows NT registry subkey:

HKEY_LOCAL_MACHINESOFTWAREMicrosoftCSS

Some of this information is available, such as the
TransactionMethod registry entry. The value of this registry entry can be set
to YES or to NO.

The
following information shows how to set and to verify the Flags value on a
computer that is running Commerce Server 2007.

Set a flag from the command line

To set a Flags value, run one of the following commands at a
command prompt:

  • CSS AddProj ProjectNameDirectory Dest1 Flags=VALUE

    Note ProjectName is a placeholder for the
    name of the project. VALUE is a placeholder for a
    numeric value that is always checked for validity. However, the token “Flags”
    will not be checked. If you mistakenly enter the word “Flag,” a new value will
    be created.

  • CSS EditProj ProjectName FLAGS=VALUE

    For example, to add the Force flag to an existing project that is named Test1, run the
    following command:

    CSS EditProj Test1 FLAGS=Force

    To turn off all the flags of an existing project that
    is named Test1, run the following command:

    CSS EditProj Test1 FLAGS=0

Verify flags by using Registry Editor

The content replication system project information is located in
the following registry subkey:

HKEY_LOCAL_MACHINESOFTWAREMicrosoftCSSProjects

The Flags value shows how the customer has configured CSS. To
determine the configuration, use the following table.

Collapse this tableExpand this table

Flags value Command line Bit value
1 Flags=NoDelete 00000000 00000000 00000000
00000001
2 Flags=ACLs 00000000 00000000 00000000
00000010
4 Flags=DirsOnly 00000000 00000000 00000000
00000100
8 Flags=Force 00000000 00000000 00000000
00001000
16 Flags=Permit 00000000 00000000 00000000
00010000
64 Flags=Incremental 00000000 00000000
00000000 01000000
128 Flags=Fastmode 00000000 00000000 00000000
10000000
256 Flags=Automatic 00000000 00000000
00000001 00000000
512 Flags=Route 00000000 00000000 00000010
00000000
1024 Flags=Notify 00000000 00000000 00000100
00000000
4096 Flags=ExcludeAll 00000000 00000000
00010000 00000000

Article ID: 920675 – Last Review: September 22, 2013 – Revision: 2.0


Applies to
  • Microsoft Commerce Server 2007 Enterprise Edition
  • Microsoft Commerce Server 2007 Developer Edition
  • Microsoft Commerce Server 2007 Standard Edition

Originally posted here:
How to read the Flags value in the registry for Commerce Server Staging projects that run on Commerce Server 2007

Commerce Server 2002 site and application support definitions

This article supplements and clarifies any earlier versions of Microsoft Commerce Server 2002 documentation or Microsoft.com reference documents with definitions, glossary terms, and product limitations. This article clarifies Commerce Server definitions and their usage for deployment purposes regarding Commerce Server 2002. These definitions now include any Commerce Server 2002 service packs or Commerce Server 2002 Feature Pack 1.

Definitions

  • Commerce Server site:
    A Commerce Server site is a collection of site resources and ASP or ASP.NET-based applications that use these resources through the Commerce Server object model. With a Commerce Server site, you can administer the applications in the site as a group.

    Note A Commerce Server site is not the same thing as the concept of a Web site in Microsoft Internet Information Services (IIS).

  • Commerce Server resource: A Commerce Server resource adds functionality to the applications in a Commerce Server site. You can use the Commerce Server Manager MMC snap-in to configure properties in a Commerce Server resource. Resources are either site resources or global resources. Global resources can be shared across Commerce Server sites. Site resources cannot be shared across Commerce Server sites. For example, the Product Catalog resource is a site resource, and the Data Warehouse resource is a global resource.
  • Commerce Server application: A Commerce Server application is a logical representation of an application in IIS. The Commerce Server application appears in both the Commerce Server Manager and in IIS console trees. In the IIS console tree, a Commerce Server application is either at the root directory level of the Web site or at a subdirectory level of the Web site.

    A Commerce Server application may be one of the following:

    • A Business Desk application
    • A Web Service application, if Commerce Server Feature Pack 1 (FP1) is installed
    • A Web site application, such as the “Retail” Solution site.
  • Commerce Server deployment: A Commerce Server deployment is made up of one or more physical installations of Commerce Server 2002 that are directed to or share a single Commerce Server 2002 administrative database (MSCSAdmin Database). All Commerce Server sites that share a common MSCSAdmin database make up a single Commerce Server deployment.
  • Web server:
    In Commerce Server, a Web server is a computer that has IIS 5.0 or IIS 6.0 installed. The Web server contains the virtual directories, the files, and the subfolders for a Commerce site. A Commerce deployment can have multiple Web servers that together form a Web farm.
  • IIS-based Web site: An Internet Information Services-based Web site runs on a specific TCP port number. For example, by default, the “Default Web Site” or “Administration” Web site is installed with IIS 5.0 or IIS 6.0.

Product limitations

Commerce Server has the following limitations, regarding the definitions that are in the “Definitions” section:

Collapse this tableExpand this table

Enterprise Edition Standard Edition Developer Edition
Commerce Server sites for each deployment 10 10 10
Commerce applications for each Commerce site Unlimited 2* Unlimited
Commerce Server sites for each Commerce Server global resource * 10 10 10
Physical servers Unlimited 2 Unlimited
Physical processors 32 2 4

*Notes

  • Feature Pack Web services do not apply against the limit of Commerce Server Standard Edition with Commerce Server 2002 Feature Pack 1 installed.
  • Commerce Server Standard Edition is limited to two applications for each Commerce site. Therefore, the supported configuration for Commerce Server Standard Edition is made up of a single Web site with a Business Desk application.
  • Commerce Server sites can share the following Commerce Server global resources:
    • CS Authentication
    • Data Warehouse
    • Direct Mailer
    • Predictor
    • Profiles

Collapse this tableExpand this table

Edition Description
Evaluation Edition Includes the same features as the Enterprise Edition.

Upgrades to Enterprise Edition.

Does not upgrade to Standard Edition.

Has a 120-day limit.

Developer Edition Includes the same features as Enterprise Edition.

Cannot be used in a production environment.

Cannot upgrade to Standard Edition or Enterprise Edition. You can migrate your work to those editions.

Additional information

As the number of Commerce applications increase on a single IIS Web server, you may experience potential usability issues with the Commerce Server Manager MMC snap-in and the Commerce Server Site Packager (Pup.exe). With each additional application, the query to obtain data from the Commerce administrative database grows. This behavior may cause performance degradation with the Commerce Server Manager MMC snap-in and Pup.exe.

The addition of multiple Commerce applications and sites may consume more memory, may increase processor use, and may potentially cause SQL contention. We recommend that you test your environment and add more physical IIS servers or other hardware resources as applicable, based on your individual site performance.

Article ID: 888655 – Last Review: September 22, 2013 – Revision: 2.0


Applies to
  • Microsoft Commerce Server 2002 Standard Edition

See more here:
Commerce Server 2002 site and application support definitions

SDP 3a49a37cb-5f86-49fd-b27a-5a1019430468 Commerce Server DirectMail Log Errors and Config data Collector

The Commerce DirectMail Log Errors and Config Data Collector were designed to collect information used in troubleshooting support issues for Commerce Server 2007, Commerce Server 2009 and Commerce Server 2009 R2.
This article describes the information that may be collected from a machine when running Commerce Server DirectMail Log Errors and Config Data Collector.

Information Collected

Collapse this tableExpand this table

Description File Name
Commerce Server Direct Mailer logs dml_mmddyyyy.log (multiple)

Collapse this tableExpand this table

Description File Name
Commerce Server DirectMail Configuration Data from Commerce Server Administration database _DMConfig.txt

Collapse this tableExpand this table

Description File Name
Commerce server DirectMail Pipeline configuration file DMLPipe.pcf

Collapse this tableExpand this table

Description File Name
Commerce Server DirectMail Errors and Jobs from DirectMailer database _DMErrors.txt, _DMJobs.txt

Additional Information

Commerce Server DirectMail Log Errors and Config Data Collector need to be run on the server where DirectMailer is installed.

References                                                                                                                            

Frequently asked questions about the Microsoft Support Diagnostic Tool (MSDT) for Windows 7
http://support.microsoft.com/kb/973559

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

Note This is a “FAST PUBLISH” article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use

(http://go.microsoft.com/fwlink/?LinkId=151500)

for other considerations.

Article ID: 2564416 – Last Review: September 22, 2013 – Revision: 3.0


Applies to
  • Microsoft Commerce Server 2007 Developer Edition
  • Microsoft Commerce Server 2007 Enterprise Edition
  • Microsoft Commerce Server 2007 Service Pack 1
  • Microsoft Commerce Server 2007 Standard Edition
  • Microsoft Commerce Server 2009 Enterprise
  • Microsoft Commerce Server 2009 R2 Enterprise
  • Microsoft Commerce Server 2009 R2 Standard
  • Microsoft Commerce Server 2009 Standard

Follow this link:
SDP 3a49a37cb-5f86-49fd-b27a-5a1019430468 Commerce Server DirectMail Log Errors and Config data Collector

SDP 3929b37f4-29b2-4459-b665-64d236d886f3 Commerce Server Staging Log Collector

The Commerce Server Staging Log Collector was designed to collect information used in troubleshooting support issues for Commerce Server 2007, Commerce Server 2009 and Commerce Server 2009 R2.
This article describes the information that may be collected from a machine when running Commerce Server Staging Log Collector.

Information Collected

Collapse this tableExpand this table

Description File Name
Commerce Server Staging Logs CSSSRV.LOG, CSSSRV.OLD, CSSAPI.LOG

Collapse this tableExpand this table

Description File Name
Commerce Server Staging Projects Status log database StagingLog.mdb, or StagingLog.sdf

Collapse this tableExpand this table

Description File Name
Commerce Server Staging Events Database events.mdb, events.ldb

Collapse this tableExpand this table

Description File Name
Commerce Server Staging Registry ComputerName_reg_HKLM_Wow6432Node_CommerceServer2007 Staging.TXT, or ComputerName_reg_HKLM_CommerceServer2007 Staging.TXT

Additional Information

Commerce Server Staging Log Collector will enable Commerce Server Staging Logging and restart Staging Service, Staging logs, Staging Project Status Log Database, Staging Event database, Staging Registry then will be collected after issue is reproduced. Users can choose to leave Staging logging on or turn it off after files after collected. Turning off Staging logging requires Staging service restart.

References                                                                                                                            

KB 973559 – Frequently asked questions about the Microsoft Support Diagnostic Tool (MSDT) for Windows 7
http://support.microsoft.com/kb/973559

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

Note This is a “FAST PUBLISH” article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use

(http://go.microsoft.com/fwlink/?LinkId=151500)

for other considerations.

Article ID: 2564422 – Last Review: September 22, 2013 – Revision: 2.0


Applies to
  • Microsoft Commerce Server 2007 Developer Edition
  • Microsoft Commerce Server 2007 Enterprise Edition
  • Microsoft Commerce Server 2007 Service Pack 1
  • Microsoft Commerce Server 2007 Standard Edition
  • Microsoft Commerce Server 2009 Enterprise
  • Microsoft Commerce Server 2009 R2 Enterprise
  • Microsoft Commerce Server 2009 R2 Standard
  • Microsoft Commerce Server 2009 Standard

View the original here:
SDP 3929b37f4-29b2-4459-b665-64d236d886f3 Commerce Server Staging Log Collector

SDP 334ae4e0e-298c-4eb0-80f8-5ef5d554d63a Commerce Server Pipeline log Collector

The Commerce Server Pipeline log Collector  was designed to collect information used in troubleshooting support issues for Commerce Server 2007, Commerce Server 2009, and Commerce Server 2009 R2, all editions.
This article describes the information that may be collected from a machine when running Commerce Server Pipeline Log Collector.

Information Collected

Collapse this tableExpand this table

Description File Name
Commerce Server Pipeline Logs All files with extension pipelog under Commerce Site Root folderPipelinesLog

Additional Information

Commerce Server Pipeline Log Collector will read Commerce Server IIS Site web.config and enable pipeline logging based on users’ selection then collect pipeline logs after issue is reproduced. Pipeline logging will be turned off after logs are collected.

References                                                                                                                            

KB 973559 – Frequently asked questions about the Microsoft Support Diagnostic Tool (MSDT) for Windows 7
http://support.microsoft.com/kb/973559

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

Note This is a “FAST PUBLISH” article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use

(http://go.microsoft.com/fwlink/?LinkId=151500)

for other considerations.

Article ID: 2564373 – Last Review: September 22, 2013 – Revision: 2.0


Applies to
  • Microsoft Commerce Server 2007 Developer Edition
  • Microsoft Commerce Server 2007 Enterprise Edition
  • Microsoft Commerce Server 2007 Service Pack 1
  • Microsoft Commerce Server 2007 Standard Edition
  • Microsoft Commerce Server 2009 Enterprise
  • Microsoft Commerce Server 2009 R2 Enterprise
  • Microsoft Commerce Server 2009 R2 Standard
  • Microsoft Commerce Server 2009 Standard

Read More:
SDP 334ae4e0e-298c-4eb0-80f8-5ef5d554d63a Commerce Server Pipeline log Collector

Page 434 of 995« First...102030...432433434435436...440450460...Last »

Recent Comments

    Archives

    Categories