Page 322 of 973« First...102030...320321322323324...330340350...Last »

XFOR: How to View or Delete Messages in MTS-IN and MTS-OUT Queues

This article was previously published under Q165505

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

IMPORTANT: This article contains information about modifying the registry. Before you
modify the registry, make sure to back it up and make sure that you understand how to restore
the registry if a problem occurs. For information about how to back up, restore, and edit the
registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986

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

Description of the Microsoft Windows Registry

In some cases you may need to view or delete messages in the Exchange Server Internet Mail Service (in Exchange Server version 4.0 the Internet Mail Connector IMC) or the Microsoft Exchange Connector for Lotus cc:Mail
queues that are located in the message store. This article explains how to view messages in the queues and how to delete mail from them by using the
Microsoft Exchange MDB Viewer utility.

To view or delete messages in the MTS-IN and MTS-OUT queues:

  1. Log on using the service account to the server that is running the IMC, Internet Mail Service (IMS) or the Connector for cc:Mail.
  2. Run the Profinst program to create a profile with a unique name (for example, IMC, IMS or ccmc):
    The following file is available for download from the Microsoft Download Center:

    Collapse this imageExpand this image

    Download Profinst.exe now

    (http://download.microsoft.com/download/exch50/Utility/1/NT4/EN-US/Profinst.exe)

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

    119591

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

    How to Obtain Microsoft Support Files from Online Services

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

    The Profinst program can also be obtained from the BackOffice Software Development
    Kit (SDK) version 2.0 or later.

    The following are the parameters for running this utility.

    NOTE: Enter
    GATEWAY for the /Type= parameter.

          MAPI Profile Installation sample.
    
          USAGE: PROFINST Flags
    
            Required Flags
            /SERVICE=    Service name (MSExchangeIMC or MSExchangeCCMC)
            /NAME=    Profile name
            /TYPE=    Profile type (GATEWAY or AGENT)
    
            Optional Flags
            /DELETE   Delete profile
            /HELP or /?  Display help
    

    After you run the Profinst program you have a Messaging Application Programming Interface (MAPI) profile that can be used by any MAPI client. The MDB
    Viewer utility is a MAPI client that gives you full access to the
    MTS-IN and MTS-OUT folders. The executable file is called
    Mdbvu32.exe, and is located on both the Standard and Enterprise edition
    of Exchange Server in the SupportUtilsI386 folder. The
    utility can be run directly from the CD-ROM. The following steps
    outline the procedure to use MDB Viewer to view messages in the MTS-IN and MTS-OUT
    queues and to delete a message.

  3. Start MDB View, click MAPI_Explicit_PROFILE, and then click OK.

    NOTE: If
    the option to select a profile is not available when you start MDB View,
    quit and restart Windows NT Server. Then start MDB View again and
    the profile option should be available.

  4. Click the name of the profile that you created in step 2. On the MDB menu, click
    Open Message Store. In the Store Display Name pane, click either
    Internet Mail Connector (server) or Connector for cc:Mail (server), and then click Open.

    NOTE: The first time that you perform this procedure on a server, Internet Mail Connector (server) is not displayed. Instead, Private Folders is displayed. Both of these names refer to the same thing. Click Private Folders, and then click Open, and continue to perform the following steps.

    When you are finished, close the session, and then open another session the same way. During the second session and during subsequent sessions, because you have already opened Private Folders, Internet Mail Connector (server) is displayed.

  5. On the MDB menu, click Open Root Folder. The MTS-IN and
    MTS-OUT folders are displayed in the Child Folders window. Click either the MTS-OUT Child Folder pane or MTS-
    IN Child Folder pane, and in the Messages in Folder pane, any
    messages that exist in that queue are displayed.
  6. To delete a message, in the
    Message In Folder pane, click the message that you want to delete. In the Operations Available dialog box, click
    lpFLD->DeleteMessages(). Click Call Function, and then click OK to confirm the
    deletion. The message is deleted.

If you are unable to obtain the Profinst.exe program, you can perform the following
steps to create the MAPI profile by using a registry entry.

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

  1. Log on to the server that is running the IMC as the service account. Start the
    Regedt32.exe program and locate the following registry key:


    HKEY_CURRENT_USERSoftwareMicrosoftWindows NTCurrentVersion
    Windows Messaging SubsystemProfiles

  2. A profile called MSExchangeIMC xxxxxxxxxx is displayed. Click the
    profile name key, and on the Registry menu, click Save Key to save
    the profile to your hard disk drive. In Exchange Server 5.0 there are multiple
    MSExchangeIMC xxxxxxxxxx entries. You may select any of the entries.
  3. Under Profiles, add a key and name it something descriptive, such as
    “IMC Profile.” Click the profile key that you just created, click Registry
    Restore
    , and then click the file that you created in step 2.

Article ID: 165505 – Last Review: November 2, 2013 – Revision: 5.0


Applies to
  • Microsoft Exchange Server 4.0 Standard Edition
  • Microsoft Exchange Server 5.0 Standard Edition
  • Microsoft Exchange Server 5.5 Standard Edition
kbnosurvey kbarchive kbdownload kbgraphxlinkcritical kbhowto kbusage KB165505

Continue Reading:
XFOR: How to View or Delete Messages in MTS-IN and MTS-OUT Queues

XL97: Microsoft Excel 97 Viewer Cannot Open Lotus Files

You cannot use Microsoft Excel 97 Viewer to open files that are created in
Lotus 1-2-3. If you try to open a file created in Lotus 1-2-3, you receive
the following error message:

Microsoft Excel Viewer cannot open files of this type.

Microsoft Excel Viewer for Windows 95, version 7.0, can open files created
in Lotus 1-2-3 versions 5.0 and earlier.

To determine which version of Microsoft Excel Viewer you are using, click
About Excel Viewer on the Help menu.

For more information about the Microsoft Excel Viewer, visit the following
Microsoft Web page:

Excel Viewer

(http://www.microsoft.com/en-us/download/details.aspx?id=10)

Article ID: 174139 – Last Review: November 2, 2013 – Revision: 3.0


Applies to
  • Microsoft Excel 97 Standard Edition
kbnosurvey kbarchive kbdownload kbinfo kbofficeupdate KB174139

Read this article:
XL97: Microsoft Excel 97 Viewer Cannot Open Lotus Files

"Filename Is Not Valid" When You Quit Microsoft Excel

When you quit Microsoft Excel, you may receive the “Filename is not valid”
error message, if both of the following conditions are true:

  • You have logged on to the computer with a user name that exceeds eight
    characters.

    -and-

  • You have disabled the use of long filenames.
To work around this problem, do either of the following:

  • Log on to the computer with a user name that has eight or fewer
    characters.

    -or-

  • Enable long filenames.

With Microsoft Excel 5.0 for Windows NT, Microsoft Excel creates toolbar
settings that are user-specific. When you quit Microsoft Excel, it
attempts to create a toolbar file that contains the user name, such as
Username.xlb. For example, if you log on to your computer as the user
“Administrator” and long filenames are disabled, when you quit Microsoft
Excel you will receive the error message because Microsoft Excel attempts
to create a file called Adminstrator.xlb (which exceeds the 8.3 limit).
For additional information, please see the following article(s) in the
Microsoft Knowledge Base:

116342

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

: How To Disable Long Filename Support on FAT Partitions

Article ID: 133707 – Last Review: November 2, 2013 – Revision: 2.0


Applies to
  • Microsoft Excel 95 Standard Edition
kbnosurvey kbarchive KB133707

Read the original:
"Filename Is Not Valid" When You Quit Microsoft Excel

Neither the payment reversal nor the original check appears in the "Bank Reconciliation" form after you cancel the payment on a check in Microsoft Dynamics AX 3.0

After you cancel the payment on a check in Microsoft
Dynamics AX 3.0, neither the payment reversal nor the original check appears in the
Bank Reconciliation form.
This problem occurs because a transaction that cancels
payment on a check is always reconciled.

Hotfix information

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

To resolve this problem
immediately, contact Microsoft Business Solutions Technical Support to obtain
the hotfix. You can log on to the Microsoft Business Solutions Support site and
create a new support request. To do this, visit the following Microsoft Web
site:

You can also contact Microsoft Business Solutions Technical
Support by telephone at (888) 477-7877.

Note In special cases, charges that are ordinarily incurred for
support calls may be canceled if a Microsoft Business Solutions Support
Professional determines that a specific update will resolve your problem. The
usual support costs will apply to any additional support questions and issues
that do not qualify for the specific update in
question.If you are a customer and if you do not have
a Premier Support Agreement with Microsoft, you must contact your partner to
obtain this hotfix.

Installation information

If you have customizations to one or more of the methods or the
tables that are affected by this hotfix, you must follow these steps:

  1. Review the changes that are documented in the .xpo file.
  2. Apply these changes in a test environment before you apply
    the hotfix in a production environment.

For more information about how
to install this hotfix, click the following article number to view the article
in the Microsoft Knowledge Base:

893082

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

How to install a Microsoft Dynamics AX Hotfix

Prerequisites

You must have Service Pack 3 for Microsoft Dynamics AX 3.0
installed to apply this hotfix.

Removal information

You cannot remove this hotfix.

Restart requirement

If you are prompted to restart the computer, you must restart the
computer after you apply this hotfix.

Objects that are affected

This hotfix affects the following objects:

  • ClassesBankChequeCancelClassDeclaration
  • ClassesBankChequeCancelcancelCheque
  • ClassesBankChequeCanceldialog
  • ClassesBankChequeCancelgetFromDialog
  • ClassesBankChequeCancelunpack
  • ClassesBankChequeCancelparmReconcile
  • ClassesBankChequeCancelnewBankChequeTable
Microsoft
has confirmed that this is a problem in the Microsoft products that are listed
in the “Applies to” section.

Article ID: 913331 – Last Review: November 2, 2013 – Revision: 3.0


Applies to
  • Microsoft Dynamics AX 3.0
  • Financials
kbnosurvey kbarchive kbhotfixserver kbnofix kbqfe kbmbsmigrate KB913331

Taken from:
Neither the payment reversal nor the original check appears in the "Bank Reconciliation" form after you cancel the payment on a check in Microsoft Dynamics AX 3.0

OFF97: Some Office Assistants Are Not Available

In Microsoft Office 97 (floppy disk version only), the Small Business
Edition (SBE) of Microsoft Office 97, and the stand-alone Office 97
programs listed above, only two Office Assistants are included, Clippit and
The Windows Logo.

There are additional Office Assistants available on the Microsoft Web site.
The characters available are:

Dot
Earl
The Genius
Hoverbot
Logo
PowerPup
Quiet Logo
Mother Nature
Scribble
Will

You can download these Assistants from the following address:
NOTE: These characters are ONLY available on the Microsoft Web site.

For additional information, please see the following article in the
Microsoft Knowledge Base:

155143

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

OFF97: One Office Assistant Installed With Complete Setup

Article ID: 168620 – Last Review: November 2, 2013 – Revision: 3.0


Applies to
  • Microsoft Office 97 Standard Edition
  • Microsoft Office 97 Small Business Edition
  • Microsoft Access 97 Standard Edition
  • Microsoft Excel 97 Standard Edition
  • Microsoft Outlook 97 Standard Edition
  • Microsoft PowerPoint 97 Standard Edition
  • Microsoft Word 97 Standard Edition
kbnosurvey kbarchive kbinfo kbofficeupdate KB168620

View article:
OFF97: Some Office Assistants Are Not Available

ACC2000: Pages Option Button Is Not Available in CommonDialog Control

The Pages option button of the CommonDialog ActiveX control is unavailable when the Flags property is set to cdlPDPageNums.
This behavior occurs because the default value for Min and Max of the CommonDialog control is 0 when the Flags property is set to cdlPDPageNums. Therefore, you cannot enter a valid page rage in the From and To boxes.
Microsoft provides programming examples for illustration only, without warranty either expressed or implied. This includes, but is not limited to, the implied warranties of merchantability or fitness for a particular purpose. This article assumes that you are familiar with the programming language that is being demonstrated and with the tools that are used to create and to debug procedures. Microsoft support engineers can help explain the functionality of a particular procedure, but they will not modify these examples to provide added functionality or construct procedures to meet your specific requirements.

To resolve this behavior, the Max property of the CommonDialog control needs to be set to a value
greater than 0, and greater than the value of the control’s Min property.
To enable the Pages option button, follow these steps:

  1. Follow steps 1 through 6 of the “Steps to Reproduce Behavior” section later in this article.
  2. Set the On Click property for the command button to the following event procedure:
    Private Sub Command1_Click()
       Dim cd As CommonDialog
       Set cd = Me!CmnDlg.Object
       With cd
          .Flags = cdlPDPageNums
    
          ' Allow a page range of 1 - 50 to be entered in
          ' the dialog box.
          .Min = 1
          .Max = 50
    
          ' Default the From box to 1, and the To box to 50.
          ' Note that the FromPage property must be greater than or
          ' equal to the Min property, and the ToPage property
          ' must be less than or equal to the Max property.
          .FromPage = 1
          .ToPage = 50
          .ShowPrinter
       End With
    End Sub
    					

  3. On the View menu, click Form View.
  4. Click the command button.

Note that the Pages option button and associated edit controls are enabled, and the page range is set from 1 to 50 by default.

Steps to Reproduce Behavior

  1. Start Microsoft Access and open any database.
  2. Create a new, blank form in Design view, not based on any table or query.
  3. On the Insert menu, click ActiveX Control.
  4. Select Microsoft Common Dialog Control, version 6.0, and then click OK.
  5. Set the Name property of the CommonDialog control to CmnDlg.
  6. Add a command button to the form.
  7. Set the command button’s On Click property to the following event procedure:
    Private Sub Command1_Click()
       Dim cd As CommonDialog
       Set cd = Me!CmnDlg.Object
       ' Enable Pages option button.
       cd.Flags = cdlPDPageNums
       cd.ShowPrinter
    End Sub
    					

  8. On the View menu, click Form View.
  9. Click the command button.

Note that the Pages option button and associated edit controls are unavailable, even though the Flags property is set to the cdlPDPageNums constant.

Article ID: 207689 – Last Review: November 2, 2013 – Revision: 4.0


Applies to
  • Microsoft Access 2000 Standard Edition
kbnosurvey kbarchive kbprb KB207689

More:
ACC2000: Pages Option Button Is Not Available in CommonDialog Control

XL: PivotTable Refresh Overwrites Formatting

When you apply formatting to individual cells in a PivotTable, this
individual formatting is lost when the PivotTable data is refreshed.
Change the automatic PivotTable formatting, which is applied in the
last step of the PivotTable Wizard. To do this, follow these steps to autoformat the table:

  1. On the Format menu, click AutoFormat.
  2. In the Table Format box, click an autoformat.
  3. Click OK.

Refreshing the data does not change the applied autoformat.

Note that if other cells not contained within the PivotTable are included
in the AutoFormat process, formatting is lost from the PivotTable
when the data is refreshed. To prevent this from occurring, make sure that
the autoformatting applied to the PivotTable is not also applied to
adjacent cells.

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

118371

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

XL: Data Number Formatting Lost When You Create PivotTable

“User’s Guide,” version 5.0, Chapter 25

For more information about formatting PivotTables, choose the Search button in Help and type:

Pivot Tables

For more information about AutoFormat, choose the Search button in
Help and type:

AutoFormat

Article ID: 110602 – Last Review: November 2, 2013 – Revision: 2.0


Applies to
  • Microsoft Excel 5.0 Standard Edition
  • Microsoft Excel 95 Standard Edition
kbnosurvey kbarchive kbprb KB110602

View the original here:
XL: PivotTable Refresh Overwrites Formatting

The Application Object Server (AOS) server may stop responding when a Microsoft SQL statement is run in Microsoft Dynamics AX 3.0

When a Microsoft SQL statement is run in Microsoft Dynamics AX 3.0, the Application Object Server (AOS) server may stop responding.
This problem occurs because the Microsoft SQL statement causes a heap corruption.

Hotfix information

A supported hotfix is now available from Microsoft. The hotfix corrects the problem that is described in this article. Apply the hotfix only to systems that are experiencing this specific problem.

To resolve this problem immediately, contact Technical Support for Microsoft Dynamics and related products to obtain the hotfix. You can log on to the Microsoft Dynamics site and create a new support request. To do this, visit the following Microsoft Web site:

You can also contact Technical Support for Microsoft Dynamics and related products by telephone at (888) 477-7877.

Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Technical Support Professional for Microsoft Dynamics and related products determines that a specific update will resolve your problem. The usual support costs will apply to any additional support questions and issues that do not qualify for the specific update in question.
If you are a customer and if you do not have a Premier Support Agreement with Microsoft, you must contact your partner to obtain this hotfix.

Installation information

If you have customizations for one or more of the methods or the tables that are affected by this hotfix, you must follow these steps:

  1. Review the changes that are documented in the .xpo file.
  2. Apply these changes in a test environment before you apply the hotfix in a production environment.

For more information about how to install this hotfix, click the following article number to view the article in the Microsoft Knowledge Base:

893082

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

How to install a Microsoft Dynamics AX hotfix

Prerequisites

You must have Kernel Rollup 2 for Microsoft Dynamics AX 3.0 installed to apply this hotfix.

Removal information

You cannot remove this hotfix.

Restart requirement

You must restart the AOS service after you apply this hotfix.

File information

The global 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.
Microsoft Dynamics AX 3.0 server

Collapse this tableExpand this table

File name File version File size Date Time Platform
Eula.rtf Not Applicable 36,352 09-Jan-2006 19:37 Not Applicable
Kr2_serverpatch30.msp Not Applicable 1,503,232 12-Feb-2007 02:04 Not Applicable
Setup.exe 1.0.15.0 531,240 22-Jun-2006 00:47 x86
Setup.xml Not Applicable 1,293 12-Feb-2007 02:08 Not Applicable

Microsoft Dynamics AX 3.0 client

Collapse this tableExpand this table

File name File version File size Date Time Platform
Eula.rtf Not Applicable 36,352 09-Jan-2006 19:37 Not Applicable
Kr2_clientpatch30.msp Not Applicable 4,584,960 12-Feb-2007 01:51 Not Applicable
Setup.exe 1.0.15.0 531,240 22-Jun-2006 00:47 x86
Setup.xml Not Applicable 1,367 12-Feb-2007 02:08 Not Applicable
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the “Applies to” section.

Article ID: 932356 – Last Review: November 2, 2013 – Revision: 3.0


Applies to
  • Microsoft Dynamics AX 3.0
  • Axapta Object Server
kbmbskernel kbqfe kbmbsmigrate kbhotfixserver KB932356

View original post here:
The Application Object Server (AOS) server may stop responding when a Microsoft SQL statement is run in Microsoft Dynamics AX 3.0

PRB: BizTalk: XML Validation may Fail for Float Data Type

The following error message may appear in the Application Event Log upon submitting XML data to BizTalk Server 2000:

An error occurred in BizTalk Server.
Details:
The XML document has failed validation for the following reason: Error parsing ’0.00′ as float datatype

Validating XML data that contains a Float data type may fail if the Language settings for the system are set to a different locale than the settings for the user account configured to run the BizTalk Messaging service. The XML Float data type is dependent on the Locale settings to correctly validate the punctuation used in the data.
To resolve this issue make sure that your computer is configured to use the same Locale settings as the user account that is used to run the BizTalk Messaging Service.

To configure the locale settings for the system and the account used by the BizTalk Messaging service, use these steps:

  1. Log on to the BizTalk Server as the account that is used to run the BizTalk Messaging Service.
  2. On the taskbar, click Start, point to Settings, and then click Control Panel. In the Control Panel dialog box, double-click Regional Options. In the Regional Options dialog box, click the General tab.
  3. Ensure that the locale selected for the current user matches one of the locales selected under Language settings for the system.
This behavior is by design.
To determine under which user account the BizTalk Service is running, use these steps:

  1. On the taskbar, click Start, point to Settings, and then click Control Panel. In the Control Panel dialog box, double-click Administrative Tools. In the Administrative Tools dialog box, double-click Services.
  2. In the Details pane, double-click BizTalk Messaging Service.
    The BizTalk Messaging Service Properties (Local Computer) dialog box appears.
  3. In the BizTalk Messaging Service Properties (Local Computer) dialog box, click the Log On tab.

Article ID: 281183 – Last Review: November 2, 2013 – Revision: 4.0


Applies to
  • Microsoft BizTalk Server 2000 Standard Edition
kbnosurvey kbarchive kbprb KB281183

Continue Reading:
PRB: BizTalk: XML Validation may Fail for Float Data Type

The DDEU022 table is updated incorrectly after you post a direct debit type transaction and then you post a debit note transaction in Sales Order Processing in Microsoft Dynamics GP 9.0

After you post a direct debit (DDR) type transaction and you post a debit note transaction in Sales Order Processing (SOP) in Microsoft Dynamics GP 9.0, the expected separate entry is not created in the DDEU022 table. Additionally, the existing entry is unexpectedly updated.

Service pack information

To resolve this problem, obtain the latest service pack for Microsoft Dynamics GP 9.0. For more information, visit one of the following Microsoft Web sites, depending on whether you are a partner or a customer.

Partners

Customers

Hotfix rollup information

To resolve this problem, install hotfix rollup 936946.

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

936946

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

Hotfix rollup 936946 is available for Microsoft Dynamics GP 9.0

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the “Applies to” section. This problem was first corrected in Microsoft Dynamics GP 9.0 Service Pack 3.

Article ID: 938264 – Last Review: November 2, 2013 – Revision: 5.0


Applies to
  • Microsoft Dynamics GP 9.0
  • Sales Order Processing
kbnosurvey kbarchive kbqfe kbexpertisebeginner kbmbsmigrate kbexpertiseinter KB938264

Follow this link:
The DDEU022 table is updated incorrectly after you post a direct debit type transaction and then you post a debit note transaction in Sales Order Processing in Microsoft Dynamics GP 9.0

Page 322 of 973« First...102030...320321322323324...330340350...Last »

Recent Comments

    Archives

    Categories