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

Description of the separate Checks check box in the Paid Sales Transaction Removal window in Microsoft Dynamics GP

This article describes why a separate Checks check box exists in the Paid Sales Transaction Removal window in Microsoft Dynamics GP and in Microsoft Business Solutions – Great Plains.

In the Paid Sales Transaction Removal window, the only documents that are moved to history are the invoices if the following conditions are true:
  • You click to select the Paid Transactions check box.
  • You leave the Checks check box clear.

All the payments will remain in the open table, even if the payments are fully paid. The payments will remain in the open table even if the payments are cash payments, check payments, or credit card payments.

However, there is a reason why you may want to do this. Checks can only be voided if the checks are in the open table or in the work table. After checks are in the history table, you cannot void the checks. Many people set a cutoff date to remove transactions a month before the checks are automatically moved to the history table. When you do this, you can still void a payment if the bank account that the check was drawn on has insufficient funds.

Article ID: 865554 – Last Review: January 16, 2015 – Revision: 5.0


Applies to
  • Microsoft Dynamics GP 10.0
  • Microsoft Dynamics GP 9.0
  • Microsoft Business Solutions–Great Plains 8.0
  • Receivables Management
kbnosurvey kbarchive kbhowto kbinfo kbexpertisebeginner kbexpertiseinter kbmbsmigrate KB865554

View the original here:
Description of the separate Checks check box in the Paid Sales Transaction Removal window in Microsoft Dynamics GP

Error message when you try to sequence a program in Microsoft SoftGrid: "SystemGuard download failed (error code 53256)"

When you try to sequence a program for use with Microsoft SoftGrid, you receive the following error message:

SystemGuard download failed (error code 53256)

Additionally, the following information may be logged in the sft-seq-log.txt file:

 

By default, this file is located in the following folder:

%ProgramFiles%SoftricitySoftGrid SequencerLogs

This problem may occur if the SoftGrid Sequencer component tries to parse the manifest of a .dll file that is encoded by using a character set that the SoftGrid Sequencer does not recognize. Typically, this problem occurs if the SoftGrid Sequencer tries to parse the manifest of a .dll file that is encoded by using the UCS-2 Unicode character set.

Note The UCS-2 character set is an earlier version of UTF-16.

To resolve this problem, modify the manifest that corresponds to the affected .dll file. To do this, follow these steps.

Step 1: Determine which file the SoftGrid Sequencer cannot parse

To determine which file the SoftGrid Sequencer cannot parse, follow these steps.

Note These steps are performed on the sequencing station.

  1. Open the Sft-seq-log.txt file by using any text editor such as Notepad.

    By default, the Sft-seq-log.txt file is located in the following folder:

    %ProgramFiles%SoftricitySoftGrid SequencerLogs

  2. Search for the text string “53256″ to locate an entry that resembles the following:
     
  3. Locate an entry that resembles the following. This entry appears several lines above the entry that you located in step 2.
     

The .dll file that appears in this entry represents the .dll file that the SoftGrid Sequencer cannot parse successfully.

Step 2: Modify the manifest file

Modify the manifest file to enable the SoftGrid Sequencer to parse the .dll file. To do this, you must use a resource explorer tool that can open .dll files and that can expose the various resources that the .dll file uses.

The following list contains some third-party resource explorer tools:

Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.

To modify the manifest file, follow these steps:

  1. Use the resource explorer tool to open the .dll file with which you experience the problem.
  2. Move to the Manifest section of the .dll file, and export the Manifest section as a file. For example, save the Manifest section of the .dll file as OriginalFileName.dll.manifest.
  3. Delete the Manifest section from the .dll file, and then save the modified file as OriginalFileName.dll.
  4. Repeat steps 1 through 3 for each .dll file with which you experience the problem.

After you follow these steps, you have the following:

  • One or more modified .dll files that are named OriginalFileName.dll
  • One or more corresponding Manifest files that are named OriginalFileName.dll.manifest

Important Store these pairs of files in a safe location.

Step 3: Sequence the program

Sequence the program again. However, follow these steps when you sequence the program:

  1. Reset the sequencing computer.
  2. Start the sequencing operation. Before you click Stop Monitoring, follow these steps:
    1. Copy and paste the modified OriginalFileName.dll file or files into the folder that contains the original .dll file or files with which you experienced the problem. This action overwrites each original .dll file with the modified .dll file(s).
    2. Copy and paste the corresponding OriginalFileName.dll.manifest file or files into the folder that contained the original .dll file or files.
  3. After the modified files are pasted into the appropriate folder, click Stop Monitoring.
  4. Follow the remaining steps to finish the sequencing operation.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the “Applies to” section.

For more information about sequencing in Microsoft SoftGrid, click the following article numbers to view the articles in the Microsoft Knowledge Base:

932137

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

Best practices to use for sequencing in Microsoft SoftGrid

939796

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

Prescriptive guidance for sequencing 2007 Office programs in Microsoft SoftGrid

The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.

Article ID: 945621 – Last Review: January 16, 2015 – Revision: 2.0


Applies to
  • Microsoft Application Virtualization for Windows Desktops
  • Microsoft Application Virtualization for Remote Desktop Services
kbnosurvey kbarchive kberrmsg kbtshoot kbprb KB945621

More here:
Error message when you try to sequence a program in Microsoft SoftGrid: "SystemGuard download failed (error code 53256)"

How the named printers feature selects a printer in Microsoft Dynamics GP

This article describes how the named printers feature selects a printer in Microsoft Dynamics GP.
The named printers feature is a workstation-based feature. Each workstation has a machine ID that is stored in the Dex.ini file. This machine ID is typically based on the network ID of the workstation.

When a printer task is assigned to a printer class, you can select one of the following printer classes in the Assign Named Printers window:

  • System
  • User
  • Company
  • User & Company

  • Any Printer ID

  • Manual Selection

  • None

For more information about these printer classes, see the following descriptions.

System

If you select System in the Printer Class field, the named printers feature uses the selected printer ID for all users and for all companies.

User

If you select User in the Printer Class field, you must select a printer ID that is assigned to the User printer class for each user in the Assign Named Printers window.

Company

If you select Company in the Printer Class field, you must select a printer ID that is assigned to the Company printer class for each company in the Assign Named Printers window.

User & Company

If you select User & Company in the Printer Class field, you must select a printer ID that is assigned to the “User & Company” printer class. You must select this printer ID for each user in the Assign Named Printers window and for each company combination in the Assign Named Printers window.

Note If you select one of the following four options, and you do not select a printer ID, the named printers feature prompts you to define a printer ID that is assigned to the same printer class:

  • System
  • User
  • Company
  • User & Company

You are prompted for this printer ID when you print a document.

Any Printer ID

If you select Any Printer ID in the Printer Class field, you are prompted for the printer ID when you print a document. You can select the printer ID from any printer class.

Manual Selection

If you select Manual Selection in the Printer Class field, the Printer Selection window opens when you print a document. This is the same window that opens when you click Print Setup on the File menu.

Note If no valid printer selection can be made for the current user, and if the current user is mapped to a template user ID, the named printers feature repeats the selection process. However, the named printers feature uses the template user ID to find a valid printer selection. Template users can be configured in the “Setup Named Printers – Advanced” window. To open the “Setup Named Printers – Advanced” window, follow these steps:

  1. On the Tools menu, point to Setup, point to System, and then click Named Printers.
  2. In the Assign Named Printers window, click Setup.
  3. In the Setup Named Printers window, click Advanced.

If a printer task is assigned to the User printer class, the Machine ID window prompts you for a printer ID for all users on a workstation. For an example of why you are prompted for a printer ID, consider the following scenario:

  1. A workstation has a machine ID. A printer ID that is assigned to the User printer class is created for User A. When User A is selected in the User ID field in the Assign Named Printers window, the printer class for a printer task is changed to User. The printer ID that was previously created is selected.

  2. User B logs on to the workstation. User B prints this printer task. The named printers feature sees that the printer task is assigned to the User printer class. But there is no printer ID selected for User B.
  3. The named printers feature checks whether the current user is associated with a template user. If the current user is associated with a template user, the named printers feature looks for a valid printer ID selection for the template user ID.
  4. If no printer ID can be selected, the Named Printers window prompts the user to enter a printer ID that is assigned to the User printer class.

Note To prevent the Machine ID window from appearing, use one of the following methods:

  • Define a printer ID for each user of the workstation.
  • Use a template user, and then assign other users to the template user.

We recommend that you set up a template user when you set up a system on which Terminal Server is installed. In this situation, you can group users who need the same printer configuration. Additionally, you can set up a template user by using a single user ID.

Article ID: 935790 – Last Review: January 16, 2015 – Revision: 3.0


Applies to
  • Microsoft Dynamics GP 2010
  • System Manager, when used with:
    • Microsoft Dynamics GP 9.0
    • Microsoft Business Solutions–Great Plains 8.0
kbnosurvey kbarchive kbexpertiseadvanced kbexpertiseinter kbinfo kbmbsmigrate KB935790

View original post here:
How the named printers feature selects a printer in Microsoft Dynamics GP

Active Directory Connectors cannot replicate a distribution list, and event ID 8270 is logged in Exchange 2003

In a Microsoft Exchange Server 2003 organization, Active
Directory Connectors (ADCs) cannot replicate a distribution list
if the following conditions are true:

  • The alias name of the distribution list starts with a space.
  • The alias name of the distribution list starts with an
    asterisk (*) that is followed by a space.
  • The alias name of the distribution list contains 15 or more characters.
  • Another distribution list that has a similar alias name has
    been replicated already in Active Directory. This occurs when the first 14
    characters of the alias names are the same for the two distribution
    lists.

Additionally, the following event is logged in the
Application log:

Event ID:
8270
Event Type: Error
Event Category: LDAP Operations
Event
Source: MSADC
Description: LDAP returned the error 44 Already Exists
when importing the transaction dn: cn= User name
,cn=Recipients,cn=Recipients,ou= Organizational unit ,o= Organization
changetype: Add admin-display-name: User name distinguishedname:OU= User name
,cn=Recipients,cn=Recipients,ou= Organizational unit ,o= Organization
createtimestamp:20030327164659.0Z objectguid: GUID replication-signature: GUID
msexchadcglobalnames:forest:o= Organization GUID : EX5:cn= User name
,cn=Recipients,ou= Organizational unit ,o= Organization :container$to… : NT5:
GUID : FOREST: GUID container-info:-2147483647
ReplicatedObjectVersion:

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

Microsoft Exchange Server 2003 Service Pack 2 (SP2) must be
installed before you apply this hotfix.

Restart requirement

You do
not have to restart the computer after you apply this hotfix.
However, the Active Directory Connector service is automatically restarted when
you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released
hotfix.

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.

Collapse this tableExpand this table

File name File version File
size
Date Time
Adc.exe 6.5.7653.20 697,344 14-Nov-2007 17:41
To work around this problem, rename the alias name of
distribution list in
Microsoft Exchange
Server 5.5
without using
an asterisk as
the first character and a
space
as the second character.
Microsoft
has confirmed that this is a problem in the Microsoft products that are listed
in the “Applies to” section.
For more information about
software update terminology, click the following article number to view the
article in the Microsoft Knowledge Base:
824684

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

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

For more information about the
naming schema for Exchange Server software updates, click the following article
number to view the article in the Microsoft Knowledge Base:

817903

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

New
naming schema for Exchange Server software update packages

Article ID: 943573 – Last Review: January 16, 2015 – Revision: 3.0


Applies to
  • Microsoft Exchange Server 2003 Standard Edition
  • Microsoft Exchange Server 2003 Enterprise Edition
kbnosurvey kbarchive kbautohotfix kbexpertiseinter kbHotfixServer kbqfe kbfix KB943573

See the original article here:
Active Directory Connectors cannot replicate a distribution list, and event ID 8270 is logged in Exchange 2003

How to enable the MAPI global catalog server reconnect logic in Exchange 2003 or in Exchange 2000

This article has been archived. It is offered “as is” and will no longer be updated.

This article has been archived. It is offered “as is” and will no longer be updated.

This article describes how to enable the MAPI global catalog server reconnect logic to work correctly in a MAPI profile. This logic is added when you install either of the following Microsoft Exchange Server updates:
  • Microsoft Exchange Server 2003 Service Pack 1 (SP1)
    For more information, visit the following Microsoft Web site:
  • The August 2004 Exchange 2000 post-Service Pack 3 (SP3) Update Rollup

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

    870540

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

    Availability of the August 2004 Exchange 2000 Server Post-Service Pack 3 Update Rollup

If a global catalog server is unavailable, the MAPI global catalog server reconnect logic lets a MAPI program recover dynamically by releasing the unavailable server. Then, the MAPI global catalog server reconnect logic obtains a new referral from Exchange Server without starting a new MAPI session.

The MAPI global catalog reconnect logic uses the following properties in a MAPI profile:

    PR_PROFILE_ABP_ALLOW_RECONNECT
    • Any value that is greater than zero enables the reconnect logic.

    PR_PROFILE_ABP_MTHREAD_TIMEOUT_SECS

    • This property indicates the number of seconds that multiple threads that are accessing the address book at the same time should block while they wait for the first thread that enters the reconnect logic to finish.

    PR_PROFILE_SERVER_VERSION

    • The Exchange Server address book provider (EMSABP32.dll) checks this property on the global profile section to determine the Exchange Server version. A value of 3000 indicates Exchange 2000.

Therefore, you must set the PR_PROFILE_ABP_ALLOW_RECONNECT property to a positive value to turn on the reconnect logic. Additionally, set the PR_PROFILE_SERVER_VERSION property to 3000 if there are no servers that are running Microsoft Exchange Server 5.5 servers in your organization.

These properties are set on the EMSABP profile section. Use the OpenProfileSection function and the following UID.

#define MUIDEMSAB "xDCxA7x40xC8xC0x42x10x1AxB4xB9x08x00x2Bx2FxE1x82"

To enable the MAPI global catalog server reconnect logic to work correctly in a MAPI profile, follow these steps:

  1. Start Microsoft Visual C++ 6.0.
  2. On the File menu, click New.
  3. Click Win32 Console Application, type GCReconnect in the Project Name box, and then click OK.
  4. Click An empty project, and then click Finish.
  5. In the Workspace window, click the FileView tab.
  6. In the Workspace window, right-click Header Files, and then click Add Files to Folder.
  7. In the File name box, type Profiles.h, and then click OK.
  8. In the Microsoft Visual C++ dialog box, click Yes.
  9. In the Workspace window, right-click Profiles.h, and then click Open.
  10. In the Microsoft Visual C++ dialog box, click Yes.
  11. Add the following code to the Profiles.h file.
    #pragma once
    
    // PROF SECT GUIDS
    
    #define pbGlobalProfileSectionGuid            "x13xDBxB0xC8xAAx05x10x1Ax9BxB0x00xAAx00x2FxC4x5A"
    
    #define MUIDEMSAB "xDCxA7x40xC8xC0x42x10x1AxB4xB9x08x00x2Bx2FxE1x82"
    
    // FLAGS
    
    #define MAPI_FORCE_ACCESS       0x00080000
    
    STDMETHODIMP CreateProfile(LPSTR lpszProfileName,
    
                                                                               LPSTR lpszExchangeServer,
    
                                                                               LPSTR lpszMailbox);
    
    STDMETHODIMP DeleteProfile(LPSTR lpszProfileName);
    
    STDMETHODIMP OpenGlobalProfileSection(LPSTR lpszProfile, LPPROFSECT * lppProfSect);
    
    STDMETHODIMP SvcAdminOpenProfileSection(LPSERVICEADMIN lpSvcAdmin, 
    
                                                                                                                            LPMAPIUID lpUID, 
    
                                                                                                                            LPCIID lpInterface, 
    
                                                                                                                            ULONG ulFlags, 
    
                                                                                                                            LPPROFSECT FAR * lppProfSect);
    
    STDMETHODIMP ProvAdminOpenProfileSection(LPPROVIDERADMIN lpProvAdmin, 
    
                                                                                                                             LPMAPIUID lpUID, 
    
                                                                                                                             LPCIID lpInterface, 
    
                                                                                                                             ULONG ulFlags, 
    
                                                                                                                             LPPROFSECT FAR * lppProfSect);
    
    STDMETHODIMP EnableReconnect(LPSTR lpszProfile);
    

  12. In the Workspace window, right-click Source Files, and then click Add Files to Folder.
  13. In the File name box, type Profiles.cpp, and then click OK.
  14. In the Microsoft Visual C++ dialog box, click Yes.
  15. In the Workspace window, right-click Profiles.cpp, and then click Open.
  16. In the Microsoft Visual C++ dialog box, click Yes.
  17. Add the following code to the Profiles.cpp file.
    #include
    
    
    #include
    
    
    #include 
    
    #include "Profiles.h"
    
    /***********************************************************************
    
      STDMETHODIMP CreateProfile(LPSTR lpszProfileName,
    
                                                                                 LPSTR lpszExchangeServer,
    
                                                                                 LPSTR lpszMailbox)
    
                - lpszProfileName:                    in Name of profile to be created
    
                - lpszExchangeServer:   in Name of the Exchange server
    
                - lpszMailbox:                           in Name of the mailbox
    
      This procedure is fairly straightforward. It creates a profile by using the MAPI interfaces.
    
    ***********************************************************************/
    
    STDMETHODIMP CreateProfile(LPSTR lpszProfileName,
    
                                                                               LPSTR lpszExchangeServer,
    
                                                                               LPSTR lpszMailbox)
    
                HRESULT         hRes = S_OK;                                   // Result from MAPI calls                      
    
        LPPROFADMIN     lpProfAdmin = NULL;             // Profile Admin object
    
                // Get an IProfAdmin interface
    
                hRes = MAPIAdminProfiles(0,                             // Flags
    
                                                                                         &lpProfAdmin); // Pointer to new IProfAdmin
    
                if(SUCCEEDED(hRes) && lpProfAdmin)
    
                            // Create a new profile
    
                            hRes = lpProfAdmin->CreateProfile((LPTSTR)lpszProfileName,          // Name of new profile
    
                                                                                                                              NULL,                                               // Password for profile
    
                                                                                                                              NULL,                                               // Handle to parent window
    
                                                                                                                              NULL);                                  // Flags
    
                            if(SUCCEEDED(hRes))
    
                                        LPSERVICEADMIN  lpSvcAdmin = NULL;              // Service Admin object
    
                                        // Get an IMsgServiceAdmin interface off the IProfAdmin interface
    
                                        hRes = lpProfAdmin->AdminServices((LPTSTR)lpszProfileName,       // Profile that we want to modify
    
                                                                                                                                          NULL,                                               // Password for that profile
    
                                                                                                                                          NULL,                                               // Handle to parent window
    
                                                                                                                                          0,                                           // Flags
    
                                                                                                                                          &lpSvcAdmin);                      // Pointer to new IMsgServiceAdmin
    
                                        if(SUCCEEDED(hRes) && lpSvcAdmin)
    
                                                    // Create the new message service for Exchange
    
                                                    hRes = lpSvcAdmin->CreateMsgService((LPTSTR)"MSEMS",                       // Name of service from MAPISVC.INF
    
                                                                                                                                                                NULL,                         // Display name of service
    
                                                                                                                                                                NULL,                         // Handle to parent window
    
                                                                                                                                                                NULL);                                    // Flags
    
                                                    if(SUCCEEDED(hRes))
    
                                                                // We now have to obtain the entry ID for the new service.
    
                                                                // You can do this by obtaining the message service table
    
                                                                // and by obtaining the entry that corresponds to the new service.
    
                                                                LPMAPITABLE     lpMsgSvcTable = NULL;  // Table to hold services
    
                                                                hRes = lpSvcAdmin->GetMsgServiceTable(0,                                      // Flags
    
                                                                                                                                                                              &lpMsgSvcTable);       // Pointer to table
    
                                                                if(SUCCEEDED(hRes) && lpMsgSvcTable)
    
                                                                            LPSRowSet       lpSvcRows = NULL;             // Rowset to hold results of table query
    
                                                                            SRestriction      sres;                                                     // Restriction structure
    
                                                                            SPropValue                  SvcProps;                                            // Property structure for restriction
    
                                                                            // Set up restriction to query table.
    
                                                                            sres.rt = RES_CONTENT;
    
                                                                            sres.res.resContent.ulFuzzyLevel = FL_FULLSTRING;
    
                                                                            sres.res.resContent.ulPropTag = PR_SERVICE_NAME_A;
    
                                                                            sres.res.resContent.lpProp = &SvcProps;
    
                                                                            SvcProps.ulPropTag = PR_SERVICE_NAME;
    
                                                                            SvcProps.Value.lpszA = "MSEMS";
    
                                                                            // Query the table to obtain the entry for the newly created message service.
    
                                                                            // This indicates the columns that we want to be returned from HrQueryAllRows
    
                                                                            enum iSvcName, iSvcUID, cptaSvc;
    
                                                                            SizedSPropTagArray(cptaSvc,sptCols) =  cptaSvc, PR_SERVICE_NAME_A, PR_SERVICE_UID ;
    
                                                                            hRes = HrQueryAllRows(lpMsgSvcTable,
    
                                                                                                                                          (LPSPropTagArray)&sptCols,
    
                                                                                                                                          &sres,
    
                                                                                                                                          NULL,
    
                                                                                                                                          0,
    
                                                                                                                                          &lpSvcRows);
    
                                                                            if(SUCCEEDED(hRes) && lpSvcRows)
    
                                                                                        // Set up a SPropValue array for the properties that you have to configure.
    
                                                                                        SPropValue rgval2;
    
                                                                                        int i = 0;
    
                                                                                        // First, the server name
    
                                                                                        ZeroMemory(&rgvali, sizeof(SPropValue) );
    
                                                                                        rgvali.ulPropTag = PR_PROFILE_UNRESOLVED_SERVER;
    
                                                                                        rgvali++.Value.lpszA = lpszExchangeServer;
    
                                                                                        // Next, the mailbox name
    
                                                                                        ZeroMemory(&rgvali, sizeof(SPropValue) );
    
                                                                                        rgvali.ulPropTag = PR_PROFILE_UNRESOLVED_NAME; 
    
                                                                                        rgvali++.Value.lpszA = lpszMailbox;
    
                                                                                        hRes = lpSvcAdmin->ConfigureMsgService((LPMAPIUID)lpSvcRows->aRow0.lpProps1.Value.bin.lpb, // Entry ID of service to configure
    
                                                                                                                                                                                                       NULL,                                                                                                                                              // Handle to parent window
    
                                                                                                                                                                                                       0,                                                                                                                                                      // Flags
    
                                                                                                                                                                                                       i,                                                                                                                                                       // Number of properties that we are setting
    
                                                                                                                                                                                                       rgval);                                                                                                                                                // Pointer to SPropValue array
    
                                                                            if (lpSvcRows) FreeProws(lpSvcRows);
    
                                                                }
    
                                                                if (lpMsgSvcTable) lpMsgSvcTable->Release();
    
                                                    }
    
                                        }
    
                                        if (lpSvcAdmin) lpSvcAdmin->Release();
    
                            }
    
                }
    
                if (lpProfAdmin) lpProfAdmin->Release();
    
                return hRes;
    
    }
    
    /***********************************************************************
    
      STDMETHODIMP DeleteProfile(LPSTR lpszProfileName)
    
                - lpszProfileName:                    in Name of profile to delete
    
      This procedure is fairly straightforward.  It deletes the indicated profile by using the
    
      MAPI interfaces.
    
    ***********************************************************************/
    
    STDMETHODIMP DeleteProfile(LPSTR lpszProfileName)
    
                HRESULT                               hRes = S_OK;
    
                LPPROFADMIN     lpProfAdmin = NULL;
    
                // Get an IProfAdmin interface
    
                hRes = MAPIAdminProfiles(0,                             // Flags
    
                                                                                         &lpProfAdmin); // Pointer to new IProfAdmin
    
                if(SUCCEEDED(hRes) && lpProfAdmin)
    
                            hRes = lpProfAdmin->DeleteProfile(lpszProfileName, 0);
    
                if (lpProfAdmin) lpProfAdmin->Release();
    
                return hRes;
    
    }
    
    STDMETHODIMP OpenGlobalProfileSection(LPSTR lpszProfile, LPPROFSECT * lppProfSect)
    
                HRESULT hRes = S_OK;
    
                LPPROFADMIN lpProfAdmin = NULL;
    
                hRes = MAPIAdminProfiles(0, &lpProfAdmin);
    
                if(SUCCEEDED(hRes) && lpProfAdmin)
    
                            LPSERVICEADMIN lpSvcAdmin = NULL;
    
                            hRes = lpProfAdmin->AdminServices((LPTSTR)lpszProfile,
    
                                                                                                                              NULL,
    
                                                                                                                              NULL,
    
                                                                                                                              0,
    
                                                                                                                              &lpSvcAdmin);
    
                            if(SUCCEEDED(hRes) && lpSvcAdmin)
    
                                        hRes = lpSvcAdmin->OpenProfileSection((LPMAPIUID)&pbGlobalProfileSectionGuid,
    
                                                                                                                                                      NULL,
    
                                                                                                                                                      0,
    
                                                                                                                                                      lppProfSect);
    
                                        lpSvcAdmin->Release();
    
                            lpProfAdmin->Release();
    
                }
    
                return hRes;
    
    }
    
    STDMETHODIMP SvcAdminOpenProfileSection(LPSERVICEADMIN lpSvcAdmin, 
    
                                                                                                                            LPMAPIUID lpUID, 
    
                                                                                                                            LPCIID lpInterface, 
    
                                                                                                                            ULONG ulFlags, 
    
                                                                                                                            LPPROFSECT FAR * lppProfSect)
    
                HRESULT hRes = S_OK;
    
                // Note: We have to open the profile section with full access.
    
                // MAPI discriminates  who can modify profiles, especially
    
                // in certain sections.  The way to force access has changed in
    
                // different versions of Outlook. Therefore, there are two methods.  See KB article 822977
    
                // for more information.
    
                // First, let us try the easier method of passing the MAPI_FORCE_ACCESS flag
    
                // to OpenProfileSection.  This method is available only in Outlook 2003 and in later versions of Outlook.
    
                hRes = lpSvcAdmin->OpenProfileSection(lpUID,
    
                                                                                                                              lpInterface,
    
                                                                                                                              ulFlags ;
    
                            IOpenSectionHack** ppProfile = (IOpenSectionHack**)((((BYTE*)lpSvcAdmin) + 0x48));
    
                            // Now, we want to open the Services Profile Section and store that
    
                            // interface with the Object
    
                            hRes = (*ppProfile)->OpenSection(lpUID, 
    
                                                                                                                             ulFlags, 
    
                                                                                                                             lppProfSect);
    
                            // 
    
                            ///////////////////////////////////////////////////////////////////
    
                }
    
                return hRes;
    
    }
    
    STDMETHODIMP ProvAdminOpenProfileSection(LPPROVIDERADMIN lpProvAdmin, 
    
                                                                                                                             LPMAPIUID lpUID, 
    
                                                                                                                             LPCIID lpInterface, 
    
                                                                                                                             ULONG ulFlags, 
    
                                                                                                                             LPPROFSECT FAR * lppProfSect)
    
                HRESULT hRes = S_OK;
    
                hRes = lpProvAdmin->OpenProfileSection(lpUID,
    
                                                                                                                               lpInterface,
    
                                                                                                                               ulFlags 
    
                return hRes;
    
    }
    
    STDMETHODIMP EnableReconnect(LPSTR lpszProfile)
    
                HRESULT hRes = S_OK;
    
                LPPROFADMIN lpProfAdmin = NULL;
    
                hRes = MAPIAdminProfiles(0, &lpProfAdmin);
    
                if(SUCCEEDED(hRes) && lpProfAdmin)
    
                            LPSERVICEADMIN lpSvcAdmin = NULL;
    
                            hRes = lpProfAdmin->AdminServices((LPTSTR)lpszProfile,
    
                                                                                                                              NULL,
    
                                                                                                                              NULL,
    
                                                                                                                              0,
    
                                                                                                                              &lpSvcAdmin);
    
                            if(SUCCEEDED(hRes) && lpSvcAdmin)
    
                                        LPPROFSECT lpABProfSect = NULL;
    
                                        hRes = SvcAdminOpenProfileSection(lpSvcAdmin, 
    
                                                    (LPMAPIUID)&MUIDEMSAB, NULL, MAPI_MODIFY, &lpABProfSect);
    
                                        if(SUCCEEDED(hRes) && lpABProfSect)
    
                                                    SPropValue spReconnectProps2 = 0;
    
                                                    spReconnectProps0.ulPropTag = PR_PROFILE_ABP_ALLOW_RECONNECT;
    
                                                    spReconnectProps0.Value.l = 1;
    
                                                    spReconnectProps1.ulPropTag = PR_PROFILE_ABP_MTHREAD_TIMEOUT_SECS;
    
                                                    spReconnectProps1.Value.l = 10;
    
                                                    hRes = lpABProfSect->SetProps(2, spReconnectProps, NULL);
    
                                                    if(SUCCEEDED(hRes))
    
                                                                LPPROFSECT lpGlobalProfSect = NULL;
    
                                                                hRes = SvcAdminOpenProfileSection(lpSvcAdmin, 
    
                                                                            (LPMAPIUID)&pbGlobalProfileSectionGuid, NULL, MAPI_MODIFY, &lpGlobalProfSect);
    
                                                                if(SUCCEEDED(hRes) && lpGlobalProfSect)
    
                                                                            SPropValue spServerVersion = 0;
    
                                                                            spServerVersion.ulPropTag = PR_PROFILE_SERVER_VERSION;
    
                                                                            spServerVersion.Value.l = 3000;
    
                                                                            hRes = lpGlobalProfSect->SetProps(1, &spServerVersion, NULL);
    
                                                                }
    
                                                                if(lpGlobalProfSect)
    
                                                                            lpGlobalProfSect->Release();
    
                                                    }
    
                                        }
    
                                        if(lpABProfSect)
    
                                                    lpABProfSect->Release();
    
                            }
    
                            if(lpSvcAdmin)
    
                                        lpSvcAdmin->Release();
    
                }
    
                if(lpProfAdmin)
    
                            lpProfAdmin->Release();
    
                return hRes;
    
    }
    

  18. In the Workspace window, right-click Source Files, and then click Add Files to Folder.
  19. In the File name box, type Main.cpp, and then click OK.
  20. In the Microsoft Visual C++ dialog box, click Yes.
  21. In the Workspace window, right-click Main.cpp, and then click Open.
  22. In the Microsoft Visual C++ dialog box, click Yes.
  23. Add the following code to the Main.cpp file.
    #include
    
    
    #include
    
    
    #include 
    
    #include 
    
    //#include 
    
    #include "Profiles.h"
    
    struct MYOPTIONS
    
                BOOL bDisplayUsage;
    
                LPSTR lpszMailbox;
    
                LPSTR lpszServer;
    
                LPSTR lpszResolveTarget;
    
    ;
    
    void DisplayUsage()
    
                printf("USAGE: GCReconnect -? -m MAILBOX -s SERVER -r RESOLVE NAMEnn");
    
                printf("tARGUMENTSn");
    
                printf("t-?n");
    
                printf("t  OPTIONAL. Displays this usage information.nn");
    
                printf("t-m MAILBOXn");
    
                printf("t  REQUIRED. Specifies the mailbox to log on to.nn");
    
                printf("t-s SERVERn");
    
                printf("t  REQUIRED. Specifies the Exchange server where MAILBOX resides.nn");
    
                printf("t-r RESOLVE NAMEn");
    
                printf("t  REQUIRED. Specifies the name to resolve with ResolveNamen");
    
    BOOL ParseArgs(int argc, char * argv[], MYOPTIONS * pRunOpts)
    
                if(!pRunOpts)
    
                            return FALSE;
    
                ZeroMemory(pRunOpts, sizeof(MYOPTIONS));
    
                for(int i = 1; i < argc; i++)
    
                            if (_stricmp(argvi, "-?") == 0)
    
                                        // User requests usage. Exit.
    
                                        pRunOpts->bDisplayUsage = TRUE;
    
                                        return TRUE;
    
                            else if (_stricmp(argvi, "-m") == 0)
    
                                        // Mailbox name
    
                                        pRunOpts->lpszMailbox = argv++i;
    
                            else if (_stricmp(argvi, "-s") == 0)
    
                                        // Server name
    
                                        pRunOpts->lpszServer = argv++i;
    
                            else if (_stricmp(argvi, "-r") == 0)
    
                                        // Name to resolve
    
                                        pRunOpts->lpszResolveTarget = argv++i;
    
                }
    
                if(!pRunOpts->lpszMailbox || !pRunOpts->lpszServer || !pRunOpts->lpszResolveTarget)
    
                            return FALSE;
    
                return TRUE;
    
    }
    
    void DoMAPI(LPSTR lpszProfile, LPSTR lpszResolveTarget)
    
                HRESULT hRes = S_OK;
    
                LPMAPISESSION lpSession = NULL;
    
                printf("Calling MAPILogonExn");
    
                hRes = MAPILogonEx(0, lpszProfile, NULL, MAPI_NEW_SESSION 
    
                                                                                        MAPIFreeBuffer(lpVal);
    
                                                                            }
    
                                                                }
    
                                                                else if(hRes == MAPI_E_END_OF_SESSION)
    
                                                                            printf("Session ended.  Retrying OpenEntry call.n");
    
                                                                else
    
                                                                            printf("Error calling OpenEntry. HRESULT = 0x%08Xn", hRes);
    
                                                                if (lpABUser) lpABUser->Release();
    
                                                                lpABUser = NULL;
    
                                                    }
    
    /*                                             printf("Starting ResolveName loop. Hit any key to exit...n");
    
                                                    while (!_kbhit())
    
                                                                LPADRLIST lpAdrList = NULL;
    
                                                                int cb = CbNewADRLIST(1);
    
                                                                hRes = MAPIAllocateBuffer(cb, (LPVOID*)&lpAdrList);
    
                                                                if(SUCCEEDED(hRes) && lpAdrList)
    
                                                                            hRes = MAPIAllocateBuffer(sizeof(SPropValue), (LPVOID FAR*)&lpAdrList->aEntries0.rgPropVals);
    
                                                                            if(SUCCEEDED(hRes) && lpAdrList->aEntries0.rgPropVals)
    
                                                                                        lpAdrList->cEntries = 1;
    
                                                                                        lpAdrList->aEntries0.cValues = 1;
    
                                                                                        lpAdrList->aEntries0.rgPropVals0.ulPropTag = PR_DISPLAY_NAME;
    
                                                                                        lpAdrList->aEntries0.rgPropVals0.Value.lpszA = lpszResolveTarget;
    
                                                                                        hRes = lpAdrBook->ResolveName(0, 0, NULL, lpAdrList);
    
                                                                                        if(SUCCEEDED(hRes))
    
                                                                                                    printf("Resolved %s successfully.n", lpszResolveTarget);
    
                                                                                        else if(hRes == MAPI_E_END_OF_SESSION)
    
                                                                                                    printf("Session ended.  Retrying ResolveName call.n");
    
                                                                                        else
    
                                                                                                    printf("Error calling ResolveName. HRESULT = 0x%08Xn", hRes);
    
                                                                            }
    
                                                                }
    
                                                                else
    
                                                                            printf("Error allocating new address list. HRESULT = 0x%08Xn", hRes);
    
                                                                if(lpAdrList)FreePadrlist(lpAdrList);
    
                                                                lpAdrList = NULL;
    
                                                                Sleep(1000);
    
                                                    }*/
    
                                        }
    
                                        else
    
                                                    printf("Error opening address book. HRESULT = 0x%08xn", hRes);
    
                            }
    
                }
    
                else
    
                            printf("Error logging on. HRESULT = 0x%08Xn", hRes);
    
    }
    
    void main(int argc, char* argv[])
    
                MYOPTIONS ProgOpts = 0;
    
                if(!ParseArgs(argc, argv, &ProgOpts) || ProgOpts.bDisplayUsage)
    
                            DisplayUsage();
    
                            return;
    
                printf("GC Reconnect Testernn");
    
                printf("tMailbox: %sn", ProgOpts.lpszMailbox);
    
                printf("tServer: %sn", ProgOpts.lpszServer);
    
                printf("tResolve Name: %snn", ProgOpts.lpszResolveTarget);
    
                HRESULT hRes = S_OK;
    
                hRes = MAPIInitialize(NULL);
    
                if(SUCCEEDED(hRes))
    
                            char szProfile256 = 0;
    
                            SYSTEMTIME SysTime = 0;
    
                            GetSystemTime(&SysTime);
    
                            hRes = sprintf(szProfile, "GCReconnect%d%d%d%d%d%d", SysTime.wMonth, SysTime.wDay, 
    
                                        SysTime.wYear, SysTime.wHour, SysTime.wMinute, SysTime.wSecond);
    
                            if(SUCCEEDED(hRes))
    
                                        hRes = CreateProfile(szProfile, ProgOpts.lpszServer, ProgOpts.lpszMailbox);   
    
                                        if(SUCCEEDED(hRes))
    
                                                    hRes = EnableReconnect(szProfile);
    
                                                    if(SUCCEEDED(hRes))
    
                                                                printf("Profile "%s" created and enabled for reconnect.nn", szProfile);
    
                                                                DoMAPI(szProfile, ProgOpts.lpszResolveTarget);
    
                                                    else
    
                                                                printf("Error enabling reconnect. HRESULT = 0x%08Xn", hRes);
    
                                        }
    
                                        else
    
                                                    printf("Error creating profile. HRESULT = 0x%08Xn", hRes);
    
                                        hRes = DeleteProfile(szProfile);
    
                                        if(SUCCEEDED(hRes))
    
                                                    printf("Successfully deleted profile.n");
    
                                        else
    
                                                    printf("Error deleting profile. HRESULT = 0x%08Xn", hRes);
    
                            }
    
                            else
    
                                        printf("Error formatting profile name string. HRESULT = 0x%08Xn", hRes);
    
                            MAPIUninitialize();
    
                }
    
                else
    
                            printf("Error initializing MAPI. HRESULT = 0x%08Xn", hRes);
    
    }
    

  24. On the Build menu, click Rebuild All.
The latest Edkmdb.h file is available at the Microsoft Download Center.

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

Collapse this imageExpand this image

Download the ExchangeSDKTools.exe package now.

(http://www.microsoft.com/downloads/details.aspx?FamilyID=4afe3504-c209-4a73-ac5d-ff2a4a3b48b7&DisplayLang=en)

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

929439

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

A MAPI program may not obtain a referral server when the global catalog server to which the MAPI program points is shut down

Article ID: 934877 – Last Review: January 16, 2015 – Revision: 2.0


Applies to
  • Microsoft Exchange Server 2003 Enterprise Edition
  • Microsoft Exchange Server 2003 Standard Edition
  • Microsoft Exchange 2000 Enterprise Server
  • Microsoft Exchange 2000 Server Standard Edition
kbnosurvey kbarchive kbcode kbhowto kbexpertiseadvanced kbinfo KB934877

Contact us for more help

Connect with Answer Desk for expert help.

Read more here:
How to enable the MAPI global catalog server reconnect logic in Exchange 2003 or in Exchange 2000

Error message "The bank country/region assigned to the vendor’s remit-to address is missing or inactive" when you generate an EFT file for Payables Management in Microsoft Dynamics GP

When you generate an Electronic Funds Transfer (EFT) file
for Payables Management in Microsoft Dynamics GP after you upgrade from an
earlier version, you receive the following error message:

The bank country/region assigned to the vendor’s remit-to address
is missing or inactive. Assign the bank country/region to the address or
activate the format.

This error message can occur for the following reasons:

  • The checkbook ID that you use does not have a prenote
    generated. See Method 1 to resolve.
  • The vendor does not have a default remit-to address ID
    populated in the Vendor Maintenance window. This remit-to address ID is referred to as the VADCDTRO field. See Method 2 to resolve.
  • The VADCDTRO (Vendor Address Code – Remit To) field does not match the VADCDTRO that is used for this vendor in the PM00200 (PM _Vendor_Master) or PM20100 (PM_Apply_to_OPEN_OPEN_temporary tables. See Method 3 to resolve.
To resolve this problem, use one of the following methods.

Note Before you follow the instructions in this article, make sure
that you have a complete backup copy of the database that you can restore if a
problem occurs.

Method 1

This error message can occur if the checkbook ID that you use has
not had a prenote generated. To resolve the problem, follow these steps:

  1. On the Cards menu, point to
    Financial, and then click Checkbook.
  2. In the Checkbook Maintenance window, select the checkbook
    ID by using the Lookup button in
    the Checkbook ID field.
  3. In the Checkbook Maintenance window, click EFT
    Bank
    button.
  4. In the Checkbook EFT Bank Maintenance window, click the
    Payables Options button.
  5. In the Checkbook EFT Payables Options window, follow one of
    the following options:

    1. If the Payables Prenote Required check
      box is selected, go to step 6.
    2. If the Payables Prenote Required check
      box is not selected, go to Method 2.
  6. In the Checkbook EFT Payables Options window, click
    Generate Prenotes.
  7. In the Generate EFT Prenotes window, select the checkbook
    ID in the Checkbook ID field, select the Vendors
    Only
    option in the Prenotes For section, select the
    prenote format ID in the Prenote Format ID field, and then
    click Process.

Method 2

This error message can occur if you do not have a default remit to
address ID populated in the Vendor Maintenance window. To resolve this problem,
follow these steps:

  1. On the Cards menu, point to
    Purchasing, and then click Vendor.
  2. In the Vendor Maintenance window, select the vendor ID by
    using the Lookup button in
    the Vendor ID field.
  3. In the Vendor Maintenance window, click the
    Lookup button in the Remit To field, and then
    select your remit to address ID that is set up as EFT.
  4. Click Save.

Note Beginning in Microsoft Dynamics GP 9.0, a new field was added to
the PM Transaction Open File table (PM20000). This field is the VADCDTRO (Vendor Address Code – Remit To) field. Every time that an
Electronic Funds Transfer (EFT) invoice is entered into the system, the VADCDTRO field is populated to record the remit-to information for the
invoice.

Method 3

This error message can occur if the VADCDTRO (Vendor Address Code – Remit To) field in the PM20000 table for your posted invoices does not match the address ID that you have mapped to EFT. Check the PM20000 (PM_Transaction_Open) table to make sure that the vendor addresses in the VADCDTRO column are the same addresses for the vendors in an earlier version of Microsoft Dynamics GP if you recently upgraded. The VADCDTRO column in the PM20000 table must match the VADCDTRO column in the PM00200 (PM_Vendor_Master) table for each vendor. To resolve this problem, follow these steps:

  1. Start the Support Administrator Console, Microsoft SQL Query
    Analyzer, or SQL Server Management Studio. To do this, use one of the following
    methods depending on the program that you are using.

    Method 1: For SQL Server 2000

    If you are using SQL Server 2000, start SQL Query Analyzer. To do
    this, click Start, point to All Programs,
    point to Microsoft SQL Server, and then click Query
    Analyzer
    .

    Method 2: For SQL Server 2005

    If you are using SQL Server 2005, start SQL Server Management
    Studio. To do this, click Start, point to All
    Programs
    , point to Microsoft SQL Server 2005, and
    then click SQL Server Management Studio.

    Method 3: For SQL Server 2008

    If you are using SQL Server 2008, start SQL Server Management
    Studio. To do this, click Start, point to All
    Programs
    , point to Microsoft SQL Server 2008, and
    then click SQL Server Management Studio.

  2. Run the following script against the company database to
    update the VADCDTRO field for the records in the PM20000 table.
    UPDATE PM20000 SET VADCDTRO = PM00200.VADCDTRO FROM PM20000 INNER JOIN PM00200 ON PM20000.VENDORID = PM00200.VENDORID

    Note This script will assign the value in the VADCDTRO field for all the posted invoices to be the same as the remit to
    address ID in the Vendor Maintenance window. This script assumes that the remit
    to address ID in the Vendor Maintenance window is the address ID that you have
    mapped to EFT.

    Note Or, you can use the following script to update the VADCDTRO field for a specific vendor in the PM20000 transaction table.

    UPDATE PM20000 SET VADCDTRO = 'XXX' WHERE VENDORID = 'YYY'

    Note XXX is a placeholder for the remit-to address code. YYY is a placeholder for the vendor ID.

  3. Additionally, if there are records for this vendor in the PM20100 remittance table, make sure that the VADCDTRO column in the PM20100 (PM_Apply_To_OPEN_OPEN_temporary) remittance table matches the VADCDTRO column in the PM00200 table and the PM20000 (PM_Transaction_Open) table. Use the following script against the company database to update the VADCDTRO field for a specific vendor in the PM20100 remittance table.
    Update PM20100 set VADCDTRO='XXX' where VENDORID='YYY' 

    Note XXX is a placeholder for the remit-to address code. YYY is a placeholder for the vendor ID.

  4. Test generating the EFT file again. When the VADCDTRO field matches between the PM00200, PM20000 and PM20100 tables for this vendor, you should not receive the error message.
For more information about the EFT setup for Payables
Management, see “Chapter 2: EFT setup for Payables Management” in the Microsoft
Dynamics GP Electronic Banking manual. To do this, visit the following
Microsoft Web site: For more information and troubleshooting tips to generate the
EFT file for Payables Management in Microsoft Dynamics GP 10.0, click the
following article number to view the article in the Microsoft Knowledge Base:
945955

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

Guidelines to follow when you generate EFT files or EFT prenote files in Electronic Funds Transfer for Payables Management in Microsoft Dynamics GP 10.0

Article ID: 944441 – Last Review: January 16, 2015 – Revision: 4.0


Applies to
  • Microsoft Dynamics GP 2010
  • Microsoft Dynamics GP 10.0
  • Electronic Funds Transfer for Payables Management
  • Payables Management
kbnosurvey kbarchive kbexpertiseadvanced kberrmsg kbtshoot kbmbsmigrate kbprb kbexpertiseinter KB944441

Read the original:
Error message "The bank country/region assigned to the vendor’s remit-to address is missing or inactive" when you generate an EFT file for Payables Management in Microsoft Dynamics GP

Error message when some Microsoft Exchange Server attributes are accessed after you extend the Active Directory schema for Exchange Server 2007: "Access denied"

This article has been archived. It is offered “as is” and will no longer be updated.

This article has been archived. It is offered “as is” and will no longer be updated.

Consider the following scenario:
  • You run Setup /PrepareSchema to extend the Active Directory directory service schema for Microsoft Exchange Server 2007.
  • You do this before you run setup.com /PrepareAD or before you finish installing Exchange 2007.

In this scenario, some programs may try to access extended attributes on User objects in Active Directory. When this occurs, the programs report the following error message:

Some Exchange Server attributes were available in the Public Information property set or in the Personal Information property set. This issue occurs because these attributes are moved to the new Exchange Information property set or to the new Exchange Personal Information property set. Because the Exchange 2007 installation is in an incomplete state, the new property set and the attributes that are associated with the new property set may be inaccessible.

The definition of the Exchange Information property set can be imported when you run setup.com /PrepareAD.

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

Method 1: Import the Rights.ldf file

Import the Rights.ldf file so that the Exchange Information property set and the Exchange Personal Information property set can be resolved by existing programs. To do this, follow these steps:

  1. Log on to the domain controller that is hosting the operations master roles (also known as flexible single master operations or FSMO) by using an account that has Enterprise Administrator permissions.
  2. Locate the Rights.ldf file in the SetupData folder on the Exchange 2007 source files.
  3. Click Start, click Run, type cmd in the Open box, and then click OK.
  4. At the command prompt, type the following command:

    ldifde.exe –i –s Schema Master DC -f INSTALLPOINTSetupDatarights.ldf

    Schema Master DC is the name of the domain controller that hosts the operations master roles. INSTALLPOINT is the folder name or the share name that hosts the Exchange 2007 installation files.

Method 2: Complete the Exchange 2007 installation

To complete the Exchange 2007 installation, run setup.com /PrepareAD. When you do this, setup.com /PrepareAD loads the Rights.ldf file and allows for the Exchange Information property set and the Exchange Personal Information property set to be resolved by existing programs.

It is common practice to stage the deployment of Exchange 2007 by extending the schema before you install Exchange 2007. You can extend the schema before you install Exchange 2007. However, this may cause unexpected behavior in some programs that require access to the Exchange attributes in the original Public Information property set or the original Personal Information property set.

A property set is a logical grouping of Active Directory attributes. You can control access to this grouping of Active Directory attributes. To do this, set a single access control entry (ACE) instead of setting an ACE on each property. Property sets are usually used to delegate control of Active Directory.
An attribute belongs to a property set if the attributeSecurityGUID property in the corresponding attributeSchema object contains the same GUID value as the rightsGuid property in the controlAccessRight object for the property set.

Exchange 2007 is the first product to implement these new property sets. The new property sets support the split administrative model that is used in Exchange 2007.

The following examples display one sample Exchange Schema Object for the Exchange Information property set and one sample Exchange Schema Object for the Exchange Personal Information property set.

In this example, the rightsGuid property of the Exchange Extended Rights object is the same GUID of the attributeSecurityGUID property. These values determine a specific schema object as part of a specific property set.

Note Changing property sets is not supported.

Sample Exchange Schema Object for the Exchange Information property set

-----------
>> Dn: CN=ms-Exch-ADC-Global-Names,CN=Schema,CN=Configuration,DC=contoso,DC=com
	2> objectClass: top; attributeSchema;
	1> cn: ms-Exch-ADC-Global-Names;
	1> distinguishedName: CN=ms-Exch-ADC-Global-Names,CN=Schema,CN=Configuration,DC=contoso,DC=com;
	1> instanceType: 0x4 = ( IT_WRITE );
	1> whenCreated: 05/16/2006 14:46:56 Central Standard Time Central Daylight Time;
	1> whenChanged: 07/17/2006 19:07:59 Central Standard Time Central Daylight Time;
	1> uSNCreated: 13980;
	1> attributeID: 1.2.840.113556.1.4.7000.102.63;
	1> attributeSyntax: 2.5.5.12;
	1> isSingleValued: FALSE;
	1> uSNChanged: 45303;
	1> showInAdvancedViewOnly: TRUE;
	1> adminDisplayName: ms-Exch-ADC-Global-Names;
	1> adminDescription: ms-Exch-ADC-Global-Names;
	1> oMSyntax: 64;
	1> searchFlags: 1;
	1> lDAPDisplayName: msExchADCGlobalNames;
	1> name: ms-Exch-ADC-Global-Names;
	1> objectGUID: af6461ef-8806-460a-ad1e-aa441e4168ef;
	1> schemaIDGUID: 9062f090-b093-11d2-aa06-00c04f8eedd8;
	1> attributeSecurityGUID: 1f298a89-de98-47b8-b5cd-572ad53d267e;
	1> isMemberOfPartialAttributeSet: TRUE;
	1> objectCategory: CN=Attribute-Schema,CN=Schema,CN=Configuration,DC=contoso,DC=com;

Sample Exchange Schema Object for the Exchange Personal Information property set

-----------
>> Dn: CN=ms-exch-UM-Pin-Checksum,CN=Schema,CN=Configuration,DC=contoso,DC=com
	2> objectClass: top; attributeSchema;
	1> cn: ms-Exch-UM-Pin-Checksum;
	1> distinguishedName: CN=ms-Exch-UM-Pin-Checksum,CN=Schema,CN=Configuration,DC=contoso,DC=com;
	1> instanceType: 0x4 = ( IT_WRITE );
	1> whenCreated: 07/17/2006 19:07:40 Central Standard Time Central Daylight Time;
	1> whenChanged: 07/17/2006 19:15:09 Central Standard Time Central Daylight Time;
	1> uSNCreated: 45219;
	1> attributeID: 1.2.840.113556.1.4.7000.102.50344;
	1> attributeSyntax: 2.5.5.10;
	1> isSingleValued: TRUE;
	1> rangeLower: 160;
	1> rangeUpper: 160;
	1> uSNChanged: 46981;
	1> showInAdvancedViewOnly: TRUE;
	1> adminDisplayName: ms-Exch-UM-Pin-Checksum;
	1> adminDescription: ms-Exch-UM-Pin-Checksum;
	1> oMSyntax: 4;
	1> searchFlags: 0;
	1> lDAPDisplayName: msExchUMPinChecksum;
	1> name: ms-Exch-UM-Pin-Checksum;
	1> objectGUID: 11f86b10-0fe3-45b9-9e9c-5191299e76de;
	1> schemaIDGUID: 3263e3b8-fd6b-4c60-87f2-34bdaa9d69eb;
	1> attributeSecurityGUID: b1b3a417-ec55-4191-b327-b72e33e38af2;
	1> isMemberOfPartialAttributeSet: TRUE;
	1> objectCategory: CN=Attribute-Schema,CN=Schema,CN=Configuration,DC=contoso,DC=com;
-----------

Exchange Information Extended Right Object

>> Dn: CN=Exchange-Information,CN=Extended-Rights,CN=Configuration,DC=contoso,DC=com
	2> objectClass: top; controlAccessRight;
	1> cn: Exchange-Information;
	1> distinguishedName: CN=Exchange-Information,CN=Extended-Rights,CN=Configuration,DC=contoso,DC=com;
	1> instanceType: 0x4 = ( IT_WRITE );
	1> whenCreated: 07/17/2006 19:19:56 Central Standard Time Central Daylight Time;
	1> whenChanged: 07/17/2006 19:19:57 Central Standard Time Central Daylight Time;
	1> displayName: Exchange Information;
	1> uSNCreated: 47304;
	1> uSNChanged: 47311;
	1> showInAdvancedViewOnly: TRUE;
	1> name: Exchange-Information;
	1> objectGUID: 67fba274-b3b0-4214-a5a1-fe05eba72b1f;
	1> rightsGuid: 1F298A89-DE98-47b8-B5CD-572AD53D267E;
	7> appliesTo: bf967aba-0de6-11d0-a285-00aa003049e2; 9CF1AA93-B31C-4725-9D50-AB7AB1D3CA1E; f0f8ffac-1191-11d0-a060-00aa006c33ed; 018849b0-a981-11d2-a9ff-00c04f8eedd8; 4828cc14-1437-45bc-9b07-ad6f015e5f28; bf967a9c-0de6-11d0-a285-00aa003049e2; 5cb41ed0-0e4c-11d0-a286-00aa003049e2;
	1> objectCategory: CN=Control-Access-Right,CN=Schema,CN=Configuration,DC=contoso,DC=com;
	1> validAccesses: 48;

Exchange Personal Information Extended Right Object

>> Dn: CN=Exchange-Personal-Information,CN=Extended-Rights,CN=Configuration,DC=contoso,DC=com
	2> objectClass: top; controlAccessRight;
	1> cn: Exchange-Personal-Information;
	1> distinguishedName: CN=Exchange-Personal-Information,CN=Extended-Rights,CN=Configuration,DC=contoso,DC=com;
	1> instanceType: 0x4 = ( IT_WRITE );
	1> whenCreated: 07/17/2006 19:19:57 Central Standard Time Central Daylight Time;
	1> whenChanged: 07/17/2006 19:19:57 Central Standard Time Central Daylight Time;
	1> displayName: Exchange Personal Information;
	1> uSNCreated: 47312;
	1> uSNChanged: 47319;
	1> showInAdvancedViewOnly: TRUE;
	1> name: Exchange-Personal-Information;
	1> objectGUID: 429f329b-7536-452a-84f0-8ed589bf441a;
	1> rightsGuid: B1B3A417-EC55-4191-B327-B72E33E38AF2;
	7> appliesTo: bf967aba-0de6-11d0-a285-00aa003049e2; 9CF1AA93-B31C-4725-9D50-AB7AB1D3CA1E; f0f8ffac-1191-11d0-a060-00aa006c33ed; 018849b0-a981-11d2-a9ff-00c04f8eedd8; 4828cc14-1437-45bc-9b07-ad6f015e5f28; bf967a9c-0de6-11d0-a285-00aa003049e2; 5cb41ed0-0e4c-11d0-a286-00aa003049e2;
	1> objectCategory: CN=Control-Access-Right,CN=Schema,CN=Configuration,DC=contoso,DC=com;
	1> validAccesses: 48;

For more information about property sets in Exchange 2007, visit the following Microsoft Web site: http://technet.microsoft.com/en-us/library/bb310768.aspx

(http://technet.microsoft.com/en-us/library/bb310768.aspx)

Article ID: 934761 – Last Review: January 16, 2015 – Revision: 2.0


Applies to
  • Microsoft Exchange Server 2007 Enterprise Edition
  • Microsoft Exchange Server 2007 Standard Edition
kbnosurvey kbarchive kbtshoot kbexpertiseinter kbprb KB934761

Contact us for more help

Connect with Answer Desk for expert help.

Read this article:
Error message when some Microsoft Exchange Server attributes are accessed after you extend the Active Directory schema for Exchange Server 2007: "Access denied"

The clustered mailbox server does not fail over after a cluster node loses the public network connection in Exchange Server 2007

After a cluster node loses the public network connection in Microsoft Exchange Server 2007 Enterprise Edition, the IP address resource changes to a failed state. However, the clustered mailbox server does not fail over to another node in the cluster.

When this issue occurs, the following events are logged in the System log:

Event Type: Error

Event Source: ClusSvc

Event Category: IP Address Resource

Event ID: 1077

Date: 3/27/2007

Time: 5:41:51 AM

User: N/A

Computer: Node-CL2

Description:
The TCP/IP interface for Cluster IP Address ‘IP Address (name)’ has failed.

Event Type: Error

Event Source: ClusSvc

Event Category: Failover Mgr

Event ID: 1069

Date: 3/27/2007
Time: 5:41:51 AM

User: N/A

Computer: Node-CL2

Description:
Cluster resource ‘IP Address (name)’ in Resource Group ‘group‘ failed.

This issue occurs when more than one clustered mailbox server failover occurs in a one-hour interval. By default, one failover within one hour is allowed for a clustered mailbox server in Exchange Server 2007.

Note In Microsoft Exchange Server 2003, the default setting is ten failovers within six hours.

This issue typically occurs during the testing phase of an Exchange Server 2007 cluster. For example, this issue may occur if you simulate a network issue on cluster node1 and then simulate the issue on cluster node2 within one hour.

To resolve this issue, modify the default failover threshold setting if the circumstances in your organization predispose you to experience this issue.

Although we believe that the default setting is appropriate for clustered production environments, you may decide to modify the default setting during the testing phase of an Exchange Server 2007 cluster.

To modify the default failover threshold setting, follow these steps:

  1. Start the Cluster Administrator Microsoft Management Console (MMC) snap-in.
  2. Locate and then right-click the cluster group object for the clustered mailbox server, and then click Properties.
  3. Click the Failover tab.
  4. Change the Threshold value to 10.
  5. Click Apply, and then click OK.

Note After you successfully finish the testing phase of an Exchange Server 2007 cluster, we recommend that you set the default failover values for the cluster group object back to one failover within one hour.

Article ID: 935632 – Last Review: January 16, 2015 – Revision: 2.0


Applies to
  • Microsoft Exchange Server 2007 Enterprise Edition
kbnosurvey kbarchive kbexpertiseadvanced kbtshoot kbprb KB935632

Originally posted here:
The clustered mailbox server does not fail over after a cluster node loses the public network connection in Exchange Server 2007

Error message when you build checks or you select a batch in the Build Payroll Checks window in Microsoft Dynamics GP: "This batch cannot be marked for posting"

oneMscomBlade,oneMsomNav,oneMscomFooter,

See the original article here:
Error message when you build checks or you select a batch in the Build Payroll Checks window in Microsoft Dynamics GP: "This batch cannot be marked for posting"

DEFECT ERROR: ADODB Recordset error ’800a0cc1′ Item cannot be found in the collection corresponding to the requested name or ordinal’ when clicking on Unassigned in Workflow

“Error:ADODB Recordset error ’800a0cc1′ Item cannot be found in the collection corresponding to the requested name or ordinal’ when clicking on Unassigned in Workflow”This error occurs when a user clicks on the Unassigned button in the Workflow screen.
This is a known issue (SMR 22449).
ResolutionDownload current service pack to resolve this issue.

Article ID: 963368 – Last Review: January 16, 2015 – Revision: 2.0


Applies to
  • Microsoft Business Solutions for AnalyticsForecaster 6.7
kbnosurvey kbarchive KB963368

Follow this link:
DEFECT ERROR: ADODB Recordset error ’800a0cc1′ Item cannot be found in the collection corresponding to the requested name or ordinal’ when clicking on Unassigned in Workflow

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

Recent Comments

    Archives

    Categories