Microsoft Support

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

Outlook encryption settings are unavailable after you move an Exchange Server 2010 mailbox to Exchange Server 2013 in Office 365 dedicated/ITAR

After you move a Microsoft Exchange Server 2010 mailbox to Exchange Server 2013 in Microsoft Office 365 dedicated/ITAR, Microsoft Outlook encryption settings are unavailable.

This behavior is by design. In Exchange Server 2010, the default behavior in Outlook is to encrypt data between the client and the server.

Collapse this imageExpand this image

This client-side setting can be disabled in an Outlook profile before you make the move to Exchange 2013. 

After all mailbox migrations to Exchange 2013 are complete, the authentication scheme will change from the current NTLM/NTLM to Kerberos/Anonymous. Then, encryption at the inner layer is no longer an option, and this part of the Outlook user interface is unavailable. Until then, encryption at the inner layer remains a client-side option.

Article ID: 3030462 – Last Review: January 12, 2015 – Revision: 1.0


Applies to
  • Microsoft Business Productivity Online Dedicated
  • Microsoft Business Productivity Online Suite Federal
vkbportal226 kbgraphic kbgraphxlink KB3030462

Read more here:
Outlook encryption settings are unavailable after you move an Exchange Server 2010 mailbox to Exchange Server 2013 in Office 365 dedicated/ITAR

Unexpected lenth of synchronization intervals for provisioning and Active Directory replication in MMSSPP 2013 in Office 365 dedicate/ITAR

When you synchronize for provisioning and Active Directory replication in Microsoft Managed Services Service Provisioning Provider (MMSSPP) 2013 in Microsoft Office 365 dedicated/ITAR, the length of synchronization intervals is unexpected, or synchronizations seem to be uncoordinated.
This behavior is by design. In MMSSPP 13.1 and earlier versions, some objects didn’t sync for a long time because the process restarted every 30 minutes regardless of synchronization success. In MMSSPP 2013, all objects are synchronized during each job run. Each synchronization tries to synchronize all the objects in the queue, and there is a 30-minute interval between each synchronization cycle.
If you consistently see synchronization or provisioning times that are longer than one to two hours, you should escalate to Microsoft Online Services Support and include detailed descriptions of the affected objects.

Article ID: 3030431 – Last Review: January 12, 2015 – Revision: 1.0


Applies to
  • Microsoft Business Productivity Online Dedicated
  • Microsoft Business Productivity Online Suite Federal

View article:
Unexpected lenth of synchronization intervals for provisioning and Active Directory replication in MMSSPP 2013 in Office 365 dedicate/ITAR

Description of the Access 2003 post-Service Pack 3 hotfix package: November 21, 2007

This article describes the Microsoft Office Access 2003 issues that are fixed in the post-Service Pack 3 hotfix package that is dated November 21, 2007.

This article describes the following items about the hotfix package:

  • The issues that the hotfix package fixes.
  • The prerequisites for installing the hotfix package.
  • Whether you must restart the computer after you install the hotfix package.
  • Whether the hotfix package is replaced by any other hotfix package.
  • Whether you must make any registry changes.
  • The files that the hotfix package contains.

Issues that the hotfix package fixes

This hotfix package fixes the following issues that were not previously documented in a Microsoft Knowledge Base article:

  • In Access 2003, you open a record that contains an inserted MIDI Sequence file and then try to play the MIDI file. When you do this, you receive the following error message:

    The Operation on the OLE object failed. The OLE server may not be registered.

  • On a computer that is running Windows Vista, you try to use the Access 2003 Back Up Database utility or the Compact and Repair Database utility in an Access 2003 database project. When you do this, Access 2003 crashes. Additionally, you receive the following error messages:

    Microsoft Office Access has Stopped Working

    Windows is Checking for a Solution to the Problem

    Note This problem occurs if the 2007 Microsoft Office system was installed on the computer.

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there is a “Hotfix download available” section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:

Note The “Hotfix download available” form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

There are no prerequisites for installing this hotfix package.

Restart information

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

Hotfix replacement information

This hotfix is not replaced by any later hotfix.

Registry information

To use one of the hotfixes in this package, you do not have to make any changes to the registry.

File information

This hotfix may not contain all the files that you must have to fully update a product to the latest build. This hotfix contains only the files that you must have to correct the issues that are listed in this article.
The global version of this hotfix uses a Microsoft Windows Installer package to install the hotfix. The dates and the times for these files are listed in Coordinated Universal Time (UTC) in the following table. When you view the file information, the date 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.

Download information

Collapse this tableExpand this table

File name File version File size Date Time Platform
Office2003-kb937560-glb.exe 11.0.8202.0 3,891,256 27-Nov-2007 00:06 x86

Microsoft Windows Installer .msp file information

Collapse this tableExpand this table

File name File version File size Date Time Platform
Msaccess.msp Not applicable 88,000,512 21-Nov-2007 00:37 Not applicable

After the hotfix is installed, the global version of this hotfix has the file attributes, or a later version of the file attributes, that are listed in the following table:

Collapse this tableExpand this table

File name File version File size Date Time Platform
Msaccess.exe 11.0.8202.0 6,704,136 20-Nov-2007 03:41 x86
Msaexp30.dll 11.0.8153.0 136,032 17-Jan-2007 03:32 x86

Additional notes

  • For more information about how to install this hotfix, see the Readme.txt file that is included in the hotfix package.
  • 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

Article ID: 937560 – Last Review: January 12, 2015 – Revision: 2.0


Applies to
  • Microsoft Office Access 2003
kbnosurvey kbarchive kboffice2003presp4fix kbautohotfix kbadp kbexpertisebeginner kbhotfixrollup kbfix kbqfe kbhotfixserver KB937560

Read the original:
Description of the Access 2003 post-Service Pack 3 hotfix package: November 21, 2007

How to create a report that automatically displays the period data for a previous period or for a later period in Microsoft Forecaster 7.0

This article describes how to create a report that automatically displays the period data for a previous period or for a later period in Microsoft Forecaster 7.0.

To automatically display data for a previous period or for a later period, you can use one of the following values in the Code column in the column set:For example, to display data from the previous period, use the following value in the column set:

B2007$-1

The data that is displayed is based on the current period that is defined in the Reporting Periods window.

To display data for the later period, use the following value in the column set:

B2005$+1

Article ID: 937591 – Last Review: January 12, 2015 – Revision: 3.0


Applies to
  • Microsoft Forecaster 7.0
  • Microsoft Dynamics GP 10.0
  • Microsoft Dynamics GP 9.0
  • Microsoft Business Solutions–Great Plains 8.0
  • Microsoft Dynamics SL 7.0
  • Microsoft Dynamics SL 6.5
  • Microsoft Business Solutions–Solomon 6.0
  • Microsoft Dynamics AX 4.0
  • Microsoft Dynamics AX 3.0
  • Microsoft Dynamics NAV 5.0
  • Microsoft Dynamics NAV 4.0
  • Microsoft Business Solutions–Navision 3.70, when used with:
kbnosurvey kbarchive kbtshoot kbsolomonfrx kbnavisionfrx kbgreatplainsfrx kbexpertiseinter kbaxaptafrx kbhowto kbmbsmigrate kbexpertisebeginner KB937591

View article:
How to create a report that automatically displays the period data for a previous period or for a later period in Microsoft Forecaster 7.0

Error message when you try to install Communications Server 2007 Standard Edition to a compressed drive: "Failure 0xC3EC796A MSI installation was unsuccessful"

When you try to install Microsoft Office Communications Server 2007 Standard Edition to a compressed drive, you receive the following error message:

Failure
0xC3EC796A MSI installation was unsuccessful. Please check the log file for more
information.

You view the following log file:

LC Serveryyyy_mm_ddhh_mm_ss.log

This file is in the following folder:

Drive :D ocuments and Settingsuser_nameLocal SettingsTemp

When you do this, you receive the following message:

Error 27765. Failed to create Live Server database.
MSI (s) (CC!F0) 16:52:21:515: Product: Microsoft Office Communications Server
2007 (Beta 3), Standard Edition Server — Error 27765. Failed to create Live
Server database.

Then, you view the LCSSetup_Commands.log file in the following folder:

Drive :D ocuments and Settingsuser_nameLocal SettingsTemp

When you do this, you receive the following message:

Connecting to SQL Server on MSSERVERrtc
(Database rtcconfig doesn’t exist.)
Creating database rtcconfig
Failed to create database rtcconfig
MicrosoftODBC SQL Server DriverSQL ServerThe file “c:lc datartcconfig.mdf” is compressed but does not reside in a read-only database or filegroup. The file must be decompressed.

This problem occurs because the Live Server database files cannot be read or written when the database is compressed.
To resolve this problem, follow these steps:
  1. Manually create a folder on the compressed drive. You will store the database in this folder later.
  2. Right-click the folder, and then click Properties.
  3. On the General tab, click Advanced.
  4. Click to clear the Compress contents to save disk space check box, and then click OK two times.

You can now install Communications Server 2007 Standard Edition to this folder.

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

Article ID: 938293 – Last Review: January 12, 2015 – Revision: 2.0


Applies to
  • Microsoft Office Communications Server 2007 Enterprise Edition
  • Microsoft Office Communications Server 2007 Standard Edition
kbnosurvey kbarchive kbtshoot kbexpertiseinter kbprb KB938293

View article:
Error message when you try to install Communications Server 2007 Standard Edition to a compressed drive: "Failure 0xC3EC796A MSI installation was unsuccessful"

Error message when you try to install Communicator Web Access (2007 release): "You must install ASP.NET v2.0.50727 first"

oneMscomBlade,oneMsomNav,oneMscomFooter,

Read the original:
Error message when you try to install Communicator Web Access (2007 release): "You must install ASP.NET v2.0.50727 first"

Description of the Communicator 2005 hotfix package: June 29, 2007

This article describes the Microsoft Office Communicator 2005 issues that are fixed in the Communicator 2005 hotfix package that is dated June 29, 2007.

This hotfix package has been replaced by the following hotfix package:

942897

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

Description of the Communicator 2005 hotfix package: October 19, 2007

Issues that the hotfix package fixes

This hotfix fixes the following issues:

  • 937104

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

    Error message when you send two messages in Communicator 2005: “The following message could not be delivered to all recipients”

  • 937105

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

    Error message when you send an instant message to a contact in Communicator 2005: “The following message could not be delivered to all recipients, possibly because one or more persons are offline

  • 938023

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

    You cannot automatically sign in to Communicator 2005 on a Windows Vista-based computer when the “Automatically open the main window when Communicator starts” check box is not selected in Communicator 2005

  • 937584

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

    Outlook or Word incorrectly displays the presence status of a Communicator 2005 contact

This hotfix package also fixes the following issues:
  • 936351

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

    The conversation history is cluttered and is difficult to read in Communicator 2005 when Communicator 2007 is used to initiate a conversation and when Multiparty IM is used

  • 934581

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

    You see a black screen or a still video image after a video works briefly in Communicator 2005

  • 935868

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

    Information for users is incorrectly displayed in Office Communicator 2005

  • 936352

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

    A Communicator 2007 user cannot add a video to an audio call that is between a Communicator 2007 client and a Communicator 2005 client

  • 932548

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

    A custom help option that uses a fully qualified domain name does not work in Communicator 2005

  • 932550

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

    An access violation error may occur when you try to exit Communicator 2005

  • 923829

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

    Error message when you try to use Communicator 2005 to log on to Live Communications Server 2005: “Signing in to SIP failed”

  • 925710

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

    Communicator 2005 does not start on a Windows 2000-based computer

  • 923636

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

    Communicator 2005 contact list may incorrectly list a contact as “Status unknown”

  • 905158

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

    Your telephone calls are not forwarded after you sign in to Communicator 2005

  • 905159

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

    Some of the audio control buttons are missing when you resize the Conversation dialog box to its minimum size in Communicator 2005

  • 905160

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

    A contact cannot be found in Communicator 2005

  • 909087

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

    A short delay is experienced before music or a voice message is heard in Communicator 2005

  • 910790

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

    Advanced VoIP calling features are unavailable in Office Communicator 2005

  • 911976

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

    The status indicator may incorrectly display the Away status for your presence status in Communicator 2005

  • 913282

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

    Communicator 2005 may quit unexpectedly when it tries to retrieve the free/busy information from an Outlook calendar

  • 913283

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

    You can use a copy-and-paste operation to transfer the contents of a file when a policy that disables file transfers is applied to a computer that is running Communicator 2005

  • 915585

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

    Internet Explorer unexpectedly closes when you refresh a Web page

  • 920917

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

    A telephone number may contain a clock icon instead of the number zero in Communicator 2005

  • 921113

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

    Error message when you try to shut down Windows: “End Program-WMS Idle”

  • 922479

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

    You experience poor video quality in Communicator 2005 running through a multipoint control unit

  • 922505

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

    Communicator 2005 responds to invitations to conversations with a “Busy” reply

  • 922544

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

    Communicator 2005 stops responding during a video conversation with Communicator 2007

  • 915571

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

    You cannot use Communicator 2005 to participate in a video conversation with Communicator 2007

  • 925399

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

    The font in Communicator 2005 dialog boxes is very large if you install the Multilingual User Interface Pack for Communicator 2005

Hotfix information

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

Collapse this imageExpand this image

Download the Communicator.msp package now.

(http://www.microsoft.com/downloads/details.aspx?familyid=A8C26743-5A77-4947-AAD4-6A6B8EF84F9C)

Release Date: June 15, 2007

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

119591

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

How to obtain Microsoft support files from online services

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

Prerequisites

One of the following operating systems must be installed on the computer before you apply this hotfix:

  • Windows Vista
  • Microsoft Windows XP Professional Service Pack 2 (SP2) or Microsoft Windows XP Home Edition SP2
    For more information about how to obtain Windows XP SP2, click the following article number to view the article in the Microsoft Knowledge Base:
    322389

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

    How to obtain the latest Windows XP service pack

  • Microsoft Windows 2000 Professional SP4

    For more informationabout how to obtain Windows 2000 SP4, click the following article number to view the article in the Microsoft Knowledge Base:

    260910

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

    How to obtain the latest Windows 2000 service pack

  • Microsoft Windows Server 2003 SP1

    For more informationabout how to obtain Windows Server 2003 SP1, click the following article number to view the article in the Microsoft Knowledge Base:

    889100

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

    How to obtain the latest service pack for Windows Server 2003

Restart information

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

Hotfix replacement information

This hotfix is not replaced by any later hotfix.

Registry information

To use one of the hotfixes in this package, you must either create a registry key or modify a registry key.

File information

This hotfix may not contain all the files that you must have to fully update a product to the latest build. This hotfix contains only the files that you must have to correct the issues that are listed in this article.

The English version of this hotfix uses a Microsoft Windows Installer package to install the hotfix. The dates and the times for these files are listed in Coordinated Universal Time (UTC) in the following table. When you view the file information, the date 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.

Download information

Collapse this tableExpand this table

File name File version File size Date Time Platform
Communicator.exe 1.0.559.224 3,901,288 20-Jun-2007 02:13 x86
Dw20.exe 11.0.8160.0 637,272 20-Jun-2007 02:13 x86
Dwdcw20.dll 11.0.8160.0 43,360 20-Jun-2007 02:13 x86
Dwtrig20.exe 11.0.8160.0 39,264 20-Jun-2007 02:13 x86
Lcapi.dll 1.0.559.224 1,370,456 20-Jun-2007 02:13 x86
Lcimsp.dll 1.0.559.224 226,648 20-Jun-2007 02:13 x86
Lcmedia.dll 1.0.559.224 2,458,968 20-Jun-2007 02:13 x86
Lcmsgsc.dll 1.0.559.224 117,592 20-Jun-2007 02:13 x86

When you apply the hotfix, make sure that the REINSTALL=ALL
switch and the REINSTALLMODE=vomus
switch are set according to the following example:

Msiexec /P Communicator.msp REINSTALL=ALL REINSTALLMODE=vomus

This procedure helps make sure that the hotfix is applied correctly across all supported operating systems.

Additional notes

  • For more information about how to install this hotfix, see the Readme.txt file that is included in the hotfix package.
  • 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

Article ID: 937124 – Last Review: January 12, 2015 – Revision: 4.0


Applies to
  • Microsoft Office Communicator 2005
kbnosurvey kbarchive atdownload kbhotfixrollup kbfix kbqfe KB937124

Read More:
Description of the Communicator 2005 hotfix package: June 29, 2007

How to allow for ActiveSync 4.x to function together with LSP applications

Third-party networking applications or corporate proxies that function as layered service providers (LSPs) may interfere with Desktop Passthrough (DTPT) traffic for Microsoft ActiveSync 4.x and for Windows Mobile Device Center (WMDC). Examples of LSPs are parental controls, the ISA proxy, and even some firewalls.
Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756

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

How to back up and restore the registry in Windows

Problems that are related to LSPs interfering with DTPT and problems that occur after you install ActiveSync 4.2, ActiveSync 4.5, or WMDC, are as follows:

  • After you upgrade from ActiveSync 4.1, DTPT connections may fail.
  • When you connect to the desktop, Exchange Server synchronization fails, and you receive the following error code:

When a network request is made from a device through DTPT, two networking connections are made: An incoming connection goes from the device to the desktop over the RNDIS interface, and an outgoing connection goes from ActiveSync to the Internet or to the intranet. The request passes through the Windows networking stack for each connection. Certain proxies and other third-party networking applications may insert themselves into this stack as LSPs. LSPs can prevent Windows Mobile-based devices from making network requests when the Windows Mobile-based devices are connected through DTPT. To try to balance security and corporate policy compliance, ActiveSync and WMDC bypass LSPs on the incoming connection and use LSPs on the outgoing connection. In some cases, the user or the IT administrator may want to change these default settings. An IT administrator may want to use LSPs on the incoming connection for increased security. Or, the user may be experiencing problems because of incompatibilities with the LSP on the outgoing connection. Therefore, the user may want to bypass the LSP.

Starting with ActiveSync 4.1, you must configure the following registry entry to allow for ActiveSync to function together with LSP appliciatons:

HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows CE Services “AllowLSP”=dword:0

By default, this registry key does not exist. This scenario uses the default value of 00000001. The following tables describe what values to use to configure ActiveSync 4.0, ActiveSync 4.1, and ActiveSync 4.2:

ActiveSync 4.0

Collapse this tableExpand this table

Value Incoming connection Outgoing connection
Not Available Use LSPs Use LSPs

ActiveSync 4.1

Collapse this tableExpand this table

Value Incoming connection Outgoing connection
00000000 Bypass LSPs Bypass LSPs
00000001 Use LSPs Use LSPs

ActiveSync 4.2

Collapse this tableExpand this table

Value Incoming connection Outgoing connection
00000001 Bypass LSPs Use LSPs
00000000 Bypass LSPs Bypass LSPs
00000010 Use LSPs Bypass LSPs
00000011 Use LSPs Use LSPs

WMDC

Collapse this tableExpand this table

Value Incoming connection Outgoing connection
00000001 (default) Bypass LSPs Use LSPs
00000000 (more compatible) Bypass LSPs Bypass LSPs
00000010 Use LSPs Bypass LSPs
00000011 (more compliant) Use LSPs Use LSPs

ActiveSync 4.5

Collapse this tableExpand this table

Value Incoming connection Outgoing connection
00000001 (default) Bypass LSPs Use LSPs
00000000 (more compatible) Bypass LSPs Bypass LSPs
00000010 Use LSPs Bypass LSPs
00000011 (more compliant) Use LSPs Use LSPs

Collapse this imageExpand this image

Visit our Windows Phone Forums

(http://social.microsoft.com/Forums/en-US/category/windowsmobile/)

for more helpful hints and ideas.

Article ID: 936858 – Last Review: January 12, 2015 – Revision: 4.0


Applies to
  • Microsoft ActiveSync 4.2
  • Microsoft ActiveSync 4.1
  • Microsoft ActiveSync 4.0
  • Microsoft ActiveSync 4.5
  • Microsoft Windows Mobile Device Center
  • Windows Mobile 6.5 Standard
kbnosurvey kbarchive kbinfo kbhowto KB936858

Taken from:
How to allow for ActiveSync 4.x to function together with LSP applications

Error message when you try to e-mail a document or to export a document in Accounting Professional or in Accounting Express: "PayPal Payments requires a unique document number to recognize your invoice"

When you try to e-mail a document or to export a document by using a PayPal Payments button, you receive the following error message:

PayPal Payments requires a unique document number to recognize your invoice.

There is more than one invoice with the same document number.

Please change the document number for this invoice and try again.

This problem occurs in Microsoft Office Accounting Professional and in Microsoft Office Accounting Express.

This problem occurs for the following reasons:
  • The Allow duplicate document numbers check box is selected in the Company Preferences dialog box.
  • There is a PayPal Payments button in the document that is e-mailed or exported.
To resolve this problem, change the document number to a unique number in the No field in the invoice. Then, click to clear the Allow duplicate document numbers check box in the Company Preferences dialog box. To do this, follow these steps:
  1. Change the document number to a unique number in the invoice. To do this, follow these steps:
    1. Open the document for which you receive the error message.
    2. In the invoice, change the document number to a unique number in the No field.
  2. Click to clear the Allow duplicate document numbers check box. To do this, follow these steps:
    1. On the Company menu, click Preferences.
    2. On the Company tab, click to clear the Allow duplicate document numbers check box.
    3. Click OK.

Article ID: 939301 – Last Review: January 12, 2015 – Revision: 5.0


Applies to
  • Microsoft Office Accounting Professional 2007
  • Microsoft Office Accounting Express 2007
kbnosurvey kbarchive kberrmsg kbexpertisebeginner kbtshoot kbmbsmigrate kbprb kbexpertiseinter KB939301

View the original here:
Error message when you try to e-mail a document or to export a document in Accounting Professional or in Accounting Express: "PayPal Payments requires a unique document number to recognize your invoice"

You cannot use the wizards when you log on to Microsoft Forecaster by using a non-administrative user account

When you log on to Microsoft Forecaster by using a non-administrative user account, you cannot use the wizards. Additionally, you cannot insert lines. This behavior occurs when you are using Microsoft Forecaster together with a Microsoft Office Access database.

Note This user account has permissions to create reports and to modify reports.

This behavior is by design.

Notes

  • Only the administrative user accounts have permissions to use the wizards to build lines, columns, calculations, and formats.
  • This behavior does not occur when you are using Microsoft Forecaster together with a Microsoft SQL Server database or together with an Oracle database.

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: 938422 – Last Review: January 12, 2015 – Revision: 3.0


Applies to
  • Microsoft Forecaster 7.0
  • Microsoft Dynamics GP 10.0
  • Microsoft Dynamics GP 9.0
  • Microsoft Business Solutions–Great Plains 8.0
  • Microsoft Dynamics SL 7.0
  • Microsoft Dynamics SL 6.5
  • Microsoft Business Solutions–Solomon 6.0
  • Microsoft Dynamics AX 4.0
  • Microsoft Dynamics AX 3.0
  • Microsoft Dynamics NAV 5.0
  • Microsoft Dynamics NAV 4.0
  • Microsoft Business Solutions–Navision 3.70, when used with:
kbnosurvey kbarchive kbsolomonfrx kbnavisionfrx kbgreatplainsfrx kbaxaptafrx kbexpertisebeginner kbtshoot kbmbsmigrate kbprb kbexpertiseinter KB938422

Originally posted here:
You cannot use the wizards when you log on to Microsoft Forecaster by using a non-administrative user account

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

Recent Comments

    Archives

    Categories