Page 323 of 754« First...102030...321322323324325...330340350...Last »

Description of the 64-bit operating systems that are supported together with Microsoft Dynamics GP

The following 64-bit operating systems are supported together with Microsoft Dynamics GP 10.0 and Microsoft Dynamics GP 9.0:
  • The 64-bit versions of Windows Vista Business, of Windows Vista Ultimate, and of Windows Vista Enterprise
  • The 64-bit versions of Windows XP
  • The 64-bit versions of Windows Server 2003 including Terminal Server
  • The 64-bit versions of Windows Server 2008 and Windows Server 2008 R2 (Microsoft Dynamics GP 10.0 only)
  • The 64-bit versions of Windows 7 (Microsoft Dynamics GP 10.0 only)

Note When a new installation of Microsoft Dynamics GP is located on 64-bit computer, a specific type of ODBC must be created. This article includes the following additional information:

  • Blank, empty, or missing ODBC menu
  • Missing server name after creating a new instance of Microsoft Dynamics GP

You can find this information in the “More Information” section of this article.

For information about supportability of the 64-bit operating systems, visit the following Microsoft Web sites to view the system requirement matrix:

To run Microsoft Dynamics GP 10.0 or Microsoft Dynamics GP 9.0 on a 64-bit computer or on a 64-bit server, you must satisfy the following prerequisites:

Note Microsoft Dynamics GP only work with a 32-bit ODBC. When Microsoft Dynamics GP is installed on a 64-bit computer, the ODBC is automatically defaulted for 64-bit and the server list will be empty. In this case, a new 32-bit ODBC have to be created.

  • You must use a 32-bit Open Database Connectivity (ODBC) Data Source Name (DSN) when you try to log in to Microsoft Dynamics GP. If you use a 64-bit ODBC DSN, the server list will be empty.

    Note To configure a 32-bit ODBC DSN, follow these steps:

    1. Right-click Start, and then click Explore.
    2. Locate the following folder:

      C:WindowsSysWOW64

    3. Right-click the Odbcad32.exe file, and then click Create Shortcut.
    4. Right-click the shortcut file, and then click Rename.
    5. To rename the shortcut file, type Data Sources (ODBC) 32-bit.
    6. Right-click the shortcut file, and then click Copy.
    7. Expand My Computer, expand Control Panel, and then click Administrative Tools.
    8. Paste the shortcut file in the Administrative Tools folder.
    9. Close Windows Explorer.
    10. Click Start, click Control Panel, double-click Administrative Tools, and then double-click Data Sources (ODBC) 32-bit.
    11. In the ODBC Data Source Administrator dialog box, create an ODBC data source.

      Note Rename the ODBC data source by using a name that clearly identifies this ODBC data source as the 32-bit version. For example, use the name “Dynamics32bit.”

    12. Start Microsoft Dynamics GP.
    13. Select the ODBC data source that you created in step 11.
    14. Double-click the new shortcut to open it.
    15. Reference Microsoft Knowledge Base article 870416 to create an ODBC connection for Microsoft Dynamics GP.

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

      870416

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

      How to set up an ODBC Data Source on SQL Server for Microsoft Dynamics GP

    Note To clearly identify the names of the shortcut files of the ODBC data sources, rename the shortcut file of the 64-bit version as “Data Sources (ODBC) 64-bit.”

  • During installation, remove any information that is in parentheses from the default installation path. For example, the 64-bit ODBC DSN uses the following default path:

    C:Program Files (x86)Microsoft DynamicsGP

    In this case, you must change the installation path of the following path:

    C:Program FilesMicrosoft DynamicsGP

    Note The Field Service notification is incompatible with any x64-based server.

To run Web Services on an x64-based operating system, you must use the following workarounds.

Web Services Runtime workaround

Windows Server 2003 x64 and Microsoft Dynamics GP 10.0 only

  1. In Windows Explorer, locate the system drive, and then open the following folder:

    %SystemRoot%WindowsMicrosoft.NETAuthMon1.2 folder

  2. Drag the Microsoft.Interop.Security.AzRoles.dll file into the %SystemRoot%Windowsassembly folder.
  3. In Windows Explorer, verify that you can see the Microsoft.Interop.Security.AzRoles.dll file in the %SystemRoot%Windowsassembly folder.
  4. Install the x64 Dexterity Common Components on the IIS server. To download the x64 Dexterity Common Components, visit the following Microsoft Web site:
  5. Install Microsoft Dynamics GP 10.0 Service Pack 3 or a later version. To do this, visit the following Microsoft Web site:
  6. Download Web Services Service Pack 3 or a later version. To do this, visit the following Microsoft Web site:
  7. Browse the Web Services installation folder, and then double-click the DynamicsGPWebServices.msi file.
  8. After Web Services is installed successfully, see the “Web Services Management Tools workaround” section.

Windows Server 2008 x64 or x86 and Microsoft Dynamics GP 10.0 only

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

  1. Refer to page 24 in the WebServicesInstallation.pdf file for the Windows Server 2008 roles and role services that must be enabled. To download the WebServicesInstallation.pdf, visit the following Microsoft Web site:
  2. Click Start, click Run, and then type REGEDIT.
  3. Locate the following registry subkey, and then follow these steps:

    HKLMSOFTWAREWow6432NodeMicrosoftWindowsCurrentVersion

    1. Right-click the registry subkey, point to New, click Key, and then name the new key ADAM_Shared.
    2. Open the ADAM_Shared folder.
    3. Right-click the ADAM_Shared folder, point to New, and then click String Value.
    4. Name the new string value InstalledVersion, and then type 1.1.3790.2075 as the value data.
  4. Install the x64 Dexterity Common Components on the IIS server. To download the x64 Dexterity Common Components, visit the following Microsoft Web site:
  5. Install Microsoft Dynamics GP 10.0 Service Pack 3 or a later version. To do this, visit the following Microsoft Web site:
  6. Download Web Services Service Pack 3 or a later version. To do this, visit the following Microsoft Web site:
  7. Browse the Web Services installation folder, and then double-click the DynamicsGPWebServices.msi file.
  8. After Web Services is installed successfully, see the “Web Services Management Tools workaround” section.

Web Services Management Tools workaround

This workaround is necessary for Microsoft Management Console (MMC) to work for Web Services:

  1. The Microsoft Visual C++ 2005 SP1 redistributable package (x86) must be installed on the x64-based computer for the Management Tools to work correctly. To download and install the redistributable package, visit the following Microsoft Web site:
  2. The Web Services Management Tool installation must be started from the “Web Services” folder on CD2 or the Feature Pack DVD. Locate the Microsoft Dynamics GP 10.0 CD2 or the Feature Pack DVD, and then open the AdProdWebServices folder. Double-click the DynamicsGPWebServicesManagementTools.msi file.

For more information about how to set up the ODBC Data Source for Microsoft Business Solutions – Great Plains, click the following article number to view the article in the Microsoft Knowledge Base:

870416

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

ODBC setup on SQL Server 2005, SQL Server 2000, SQL Server 7.0, and SQL Server Desktop Engine 2000 (MSDE)

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

929156

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

Description of the compatibility of Analysis Cubes for Microsoft SQL Server 2005 in Microsoft Dynamics GP and of 64-bit operating systems

Article ID: 918983 – Last Review: October 9, 2012 – Revision: 17.0


Applies to
  • Microsoft Dynamics GP 10.0
  • Microsoft Dynamics GP 9.0
  • System Manager
kbtshoot kbmbsmigrate kbprb KB918983

Other Support Sites

Community

Get Help Now

Continued here:
Description of the 64-bit operating systems that are supported together with Microsoft Dynamics GP

Error message when you try to log on to Live Communications Server 2005 SP1 or to Communicator 2007 by using Communicator Web Access: "The server is unavailable"

When you use Microsoft Office Communicator Web Access to try
to log on to Microsoft Office Live Communications Server 2005 Service Pack
1 (SP1) or to Microsoft Office Communicator 2007, the logon operation fails. Additionally, you may receive the following error message:

The session was ended. Communicator Web Access Server cannot log the user on to the Live Communications Server. (Error Code: 1)

Then,
a second browser window that is intended for the client interface may open and
display the icons for activity. However, you receive the following error message in the browser window:

The server is unavailable. Please sign in again or contact your system administrator.

Additionally, the following event is logged in the Application log
on the server that is running Live Communications Server 2005:

Event Type: Error
Event Source: Communicator Web Access Session Service
Event Category: (2101)
Event ID: 50103

Description:
The Communicator Web Access session service can not establish or maintain MTLS connection to the Live Communications Server.

Virtual server name: servername.com
Live Communications Server: N/A

Error code: 0xc835c3f3

Cause:
This problem is usually caused by an invalid MTLS certificate configured on the Communicator Web Access Server or Live Communications Server.

Resolution:
Review certificate related sections in Microsoft Office Communicator Web Access Planning and Deployment Guide. Ensure the MTLS certificates configured on the Communicator Web Access Server and Live Communications Server are valid. If the problem persists, run Communicator Web Access activation again to repair the server.
For more information, see Help and Support Center at http://support.microsoft.com.

If you experience the symptoms that are mentioned in the “Symptoms” section, a certificate configuration issue
exists. The certificate configuration for Communicator Web Access depends on whether you are
running Live Communications Server Standard Edition or Live Communications Server Enterprise Edition.

Make sure that Live Communications Server Standard Edition and Live Communications Server Enterprise Edition are configured in a supported network configuration.

For Live Communications Server Standard Edition

Whether you are running Communicator Web Access on a separate
server from Live Communications Server Standard Edition or collocated on the
same server as Live Communications Server Standard Edition, certificates must
be configured as follows:

  • MTLS certificate: The subject name must be the FQDN of the
    Communicator Web Access server.
  • HTTPS (SSL) certificate: The subject name must be the host
    name that is used by clients to access the Communicator Web Access server. The subject name may not be the server FQDN. The SSL certificate should match the Web site name
    that the user enters in the browser to access the Communicator Web Access site.

Note If the URL host name does not match the subject name of the
certificate, the user will still be able to access the Web site with security.
However, the user will be prompted with a warning that the host name and the
certificate do not match. For example, if the Communicator Web Access server
FQDN is LCS-01.contoso.com, and clients use http://cwa.contoso.com to connect
to Communicator Web Access, the MTLS certificate subject name would be
LCS-01.contoso.com. Additionally, the HTTPS (SSL) subject name would be
cwa.contoso.com.

For Live Communications Server Enterprise Edition

If you are running Communicator Web Access on one of the
servers in a Live Communications Server Enterprise Edition pool, you must use
the FQDN of the server pool in the MTLS certificate. Certificates must be
configured as follows:

  • MTLS certificate: The subject name must be the FQDN of the
    Live Communications Server pool.
  • HTTPS (SSL) certificate: The subject name must be the host
    name that is used by clients to access the Communicator Web Access server. The subject name may not be the server FQDN. The SSL certificate should match the Web site name
    that the user enters in the browser to access the Communicator Web Access site.

Note If the URL host name does not match the subject name of the
certificate, the user will still be able to access the Web site with security.
However, the user will be prompted with a warning that the host name and the
certificate do not match. For example, if the Live Communications Server pool
FQDN is “LCSPool.contoso.com,” and if clients use http://cwa.contoso.com to connect
to Communicator Web Access, the MTLS certificate subject name would be
“LCSPool.contoso.com.” The HTTPS (SSL) subject name would be “cwa.contoso.com.”

Troubleshooting

  1. Open Microsoft Office Communicator Web Access Manager,
    right-click the server object, and then click Properties. Verify that the MTLS
    certificate has a subject name that matches the computer FQDN for a Standard
    Edition deployment or that matches the pool name for an Enterprise Edition pool.
  2. In Communicator Web Access Manager, right-click the
    Communicator Web Access Virtual Server object, and then click Properties.

    On the
    Connectivity tab, verify that the HTTPS certificate that is selected matches the URL
    name that clients will use to access Communicator Web Access.

  3. Verify that the Communicator desktop client can sign
    in to Live Communications Server by using TLS as the transport.

    If connections are successful by using TCP but
    not TLS, the Live Communications Server server may not be configured to accept TLS connections. Alternatively, there may be a problem with the certificate that is used for TLS connections.

  4. Make sure that the Live Communications Server server is configured for MTLS
    connections.

    This step is frequently missed in deployments that use a single Live Communications Server Standard Edition server that is accessed by using TCP or when Communicator Web Access is deployed on the
    same server as Live Communications Server. An MTLS connection is made from Communicator Web Access to Live Communications Server regardless of whether the applications are on the same server.

  5. Verify that the certificate that is supplied meets the MTLS
    requirements for Live Communications Server. Specifically, verify that the certificate uses a Web Server template with Enhanced Key Usage
    for Server Authentication.
  6. Restart the Live Communications Server services to populate
    the trusted server list. The trusted server list is built into the memory of the Live
    Communications Server 2005 server when the server is
    restarted.
For more information about Live Communications Server 2005 SP1 supported configurations, see the “Live Communications Server 2005 Document: Supportability Guide.” To do this, visit the following Microsoft Web site: For more information about the “Microsoft Office Communicator Web
Access Planning and Deployment Guide,” visit the following Microsoft Web site:For more information about how to configure certificates in Live Communications Server 2005, visit the following Microsoft Web site:

For more information about how to plan for and deploy certificates in Live Communications
Server 2005 Service Pack 1, click the following article number to view the article in the Microsoft Knowledge Base:

925338

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

Support WebCast: How to plan for and deploy certificates in Live Communications Server 2005 Service Pack 1

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

Article ID: 915114 – Last Review: October 9, 2012 – Revision: 4.0


Applies to
  • Microsoft Office Communicator Web Access
  • Microsoft Office Communicator 2007

Read this article:
Error message when you try to log on to Live Communications Server 2005 SP1 or to Communicator 2007 by using Communicator Web Access: "The server is unavailable"

Error message when you start Microsoft Dynamics GP: "Database setup has not been completed for Microsoft Dynamics GP"

When you start Microsoft Dynamics GP, you receive the
following error message:

Database setup has not been
completed for Microsoft Dynamics GP. Use Microsoft Dynamics GP Utilities to
complete the database setup before starting Microsoft Dynamics
GP.

This problem occurs after you perform a new installation of
Microsoft Dynamics GP, after you update to Microsoft Dynamics GP, or after you
install a new client computer.

Cause 1

This problem occurs because a subfeature was installed. However,
Microsoft Dynamics GP Utilities must first be run to create the tables for this
subfeature. To resolve this problem, see Resolution 1.

Cause 2

This problem occurs because not all the subfeatures are updated.
To resolve this problem, see Resolution 2.

Cause 3

This problem occurs because not all the subfeatures that are
installed on the new client computer are installed on the server. To resolve
this problem, see Resolution 3.

Cause 4

This problem occurs because the DynUtils.set file has been
modified and does not contain all features shown in the Dynamics.set file or
through Add or Remove programs.

Resolution 1

On the server that is running Microsoft SQL Server, make sure that
the subfeature is installed. Then, start Microsoft Dynamics GP Utilities to
create the tables for the subfeature.

Resolution 2

On the server that is running SQL Server, start Microsoft Dynamics
GP Utilities. Then, update the subfeatures.

Resolution 3

Compare the Dynamics.set files on the new client computer to the
files on the server. Verify that any subfeatures that are installed on the
client computer are also installed on the server. You can install subfeatures
on the server or remove them from the client computer by using the Add
or Remove Programs or Programs and Features
item in Control Panel. To
remove the subfeature, use the Add or Remove Programs or Programs and
Features
item on the client computer. This will remove the feature
from the Dynamics.set files and from the Dynutil.set files. This will also
remove the dictionary files from the Microsoft Dynamics GP installation folder
and from any registry entries for the subfeatures.

Note If the module cannot be installed from Microsoft Dynamics GP CD
1, these steps may vary.

Remove the subfeature from the client computer

  1. Click Start, point to
    Settings, and then click Control
    Panel
    .
  2. Double-click Add or Remove Programs or Programs
    and Features
    , click Microsoft Dynamics GP, and then
    click Change.
  3. In the Program Maintenance window, click Add/Remove
    Features
    .
  4. In the Select Features window, click the symbol next to the
    module that you want to remove, and then click Do not install
    feature
    .
  5. Use the appropriate method:
    • In Microsoft Dynamics GP 10.0 and in Microsoft Dynamics GP 2010, confirm that the
      Install Location field is correct, and then click
      Next.
    • In Microsoft Dynamics GP 9.0, confirm that the
      Install to field is correct, and then click
      Next.

    Note You must confirm that the field is correct because the folder in
    the field is the folder to which the changes will be made.

  6. In the Install Program window, click
    Install.
  7. When the Installation Complete window opens, click
    Finish.

    Microsoft Dynamics GP Utilities should start.
    If Microsoft Dynamics GP Utilities does not start, click
    Start, point to Programs, point to
    Microsoft Dynamics, and then click GP
    Utilities
    .

  8. Log on as the sa user, and then click Launch
    Microsoft Dynamics GP
    in the Additional Tasks window.
  9. When you are prompted to include new code, click
    Yes.

Install the subfeature on the server

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.

  1. Make sure that all users exit Microsoft Dynamics
    GP.
  2. Back up the DYNAMICS database and the company database. To
    do this, follow these steps:

    1. Use the appropriate method:

      • In Microsoft Dynamics GP 10.0 and in Microsoft Dynamics GP 2010, point to
        Maintenance on the Microsoft Dynamics GP
        menu, and then click Backup.
      • In Microsoft Dynamics GP 9.0, click
        Backup on the File menu.
    2. In the Back Up Company window, enter the company that
      you want to back up in the Company Name field, enter the
      location and the file name in the Select the backup file
      field, and then click OK.
    3. Repeat these steps for each company database.
    4. Back up the system database. To do this, click
      System Database in the Company Name field,
      and then follow the same steps that you follow when you back up the company
      database.
  3. Click Start, point to
    Settings, and then click Control
    Panel
    .
  4. In Control Panel, double-click Add or Remove
    Programs or Programs and Features
    , click Microsoft Dynamics
    GP
    , and then click Change.
  5. In the Program Maintenance window, click
    Add/Remove Features.
  6. In the Select Features window, click the symbol next to
    the module that you want to install, and then click Entire feature will
    be installed on local hard disk drive
    .
  7. Use the appropriate method:
  8. In the Install Program window, click
    Install.
  9. When the Installation Complete window opens, click
    Finish.

    Microsoft Dynamics GP Utilities should start.
    If Microsoft Dynamics GP Utilities does not start, click
    Start, point to Programs, point to
    Microsoft Dynamics, and then click GP
    Utilities
    .

  10. Have all the other users exit Microsoft Dynamics GP.
  11. Log on as the sa user, and then click Launch
    Microsoft Dynamics GP
    in the Additional Tasks window.
  12. When you are prompted to include new code, click
    Yes.
  13. Click Next so that Microsoft Dynamics GP
    detects the earlier version.
  14. Click Next to upgrade the Microsoft
    Dynamics GP system database.
  15. Click Next to update the company
    databases.

Resolution 4

Verify the DynUtils.set file contains all features required to
create a new company or upgrade a company. Modules missing from this file will
not be installed or updated when using Microsoft Dynamics GP Utilities.

  1. Rename the DynUtils.set file to DynUtils.old
  2. Click Start, point to Settings, and then click Control
    Panel.
  3. Double-click Add or Remove Programs or Programs and
    Features, click Microsoft Dynamics GP, and then click Change.
  4. In the Program Maintenance window, click
    Repair.
  5. In the Repair window, click Repair.
  6. In the Repair Complete window, click Ext.
  7. Log on as the sa user.
  8. In the Welcome to Microsoft Dynamics GP Utilities window,
    click Next.
  9. If you are prompted to include new code, click
    Yes.
  10. Click Next so that Microsoft Dynamics GP detects the
    modules to add.
  11. Click Next to upgrade the Microsoft Dynamics GP system
    database.
  12. Click Next to update the company databases.
For more information how to edit a Dynamics.set file, click the
following article number to view the article in the Microsoft Knowledge Base:
872087

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

How to disable third-party products in the Dynamics.set file in Microsoft Dynamics GP

Article ID: 915472 – Last Review: October 9, 2012 – Revision: 7.0


Applies to
  • Microsoft Dynamics GP 10.0
  • Microsoft Dynamics GP 9.0
  • Microsoft Dynamics GP 2010
  • System Manager
kbexpertiseadvanced kbexpertiseinter kbexpertisebeginner kbtshoot kberrmsg kbmbsmigrate kbprb KB915472

Other Support Sites

Community

Get Help Now

See original article:
Error message when you start Microsoft Dynamics GP: "Database setup has not been completed for Microsoft Dynamics GP"

The year-end closing procedures for the Fixed Asset Management module in Microsoft Dynamics GP

This document outlines the recommended year-end closing procedures for Fixed Asset Management in Microsoft Dynamics. This article includes a checklist of the steps that you must follow to complete these procedures. The “More information” section contains detailed information about each step. A series of frequently asked questions (FAQ) follows the description of the procedures.

Read this document before you perform any of the following procedures. If you have any questions, contact Technical Support for Microsoft Dynamics.

Year-end checklist

Step 1: Perform all the year-end closing procedures for Payables Management in Microsoft Dynamics GP

Close Payables Management first. This action guarantees that all the outstanding fixed asset transactions are capitalized.

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

875169

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

Year-end closing procedures for the Payables Management module in Microsoft Dynamics GP

Step 2: Enter all the fixed asset transactions for the current fiscal year

Post all the additions, the changes, the transfers, and the retirements for the current fiscal year.

Note Transfers and undo retirement transactions should never be performed in a historical year.

Step 3: Depreciate all assets through the last day of the current fiscal year

  1. Use the appropriate method:
    • In Microsoft Dynamics GP 10.0 or Microsoft Dynamics GP 2010, point to Tools on the Microsoft Dynamics GP menu, point to Routines, point to Fixed Assets, and then click Depreciate.
    • In Microsoft Dynamics GP 9.0, point to Routines on the Tools menu, point to Fixed Assets, and then click Depreciate.
  2. In the Depreciation Target Date box, type the last date of the current fiscal year.
  3. To insert all the fixed asset books, click All.
  4. Click Depreciate.

Step 4: Perform the GL Posting (GL Interface) process (This step is optional.)

  1. Use the appropriate method:
    • In Microsoft Dynamics GP 10.0 or Microsoft Dynamics GP 2010, point to Tools on the Microsoft Dynamics GP menu, point to Routines, point to Fixed Assets, and then click GL Posting.
    • In Microsoft Dynamics GP 9.0, point to Routines on the Tools menu, point to Fixed Assets, and then click GL Posting.
  2. In the Beginning Period box, type 2012-012.

    Note The 2012-012 placeholder represents period 12 of the fiscal year 2012. If you are not running on a calendar fiscal year, or if you have more than 12 periods, the period that you type is different.

  3. In the Ending Period box, type 2012-012.
  4. In the Transaction Date box, type the last date of the current fiscal year, or type the date when you need the posting to affect the general ledger.
  5. Click Continue.
  6. When you receive a message that the batch number is being created, click Continue.
  7. In the Report Destination window, click to select the Printer check box, and then click OK.

    Note You may want to keep this report as part of the year-end financial records.

Step 5: Run any year-end reports that you want to keep as part of the year-end financial records

The year-to-date depreciation amounts for previous fiscal years are not kept in Fixed Asset Management. Therefore, you must print any reports that contain this information before you close the year.

There are several reports available for fixed assets. We recommend that you print the following reports:

  • Annual Activity

    To print the Annual Activity report, point to Fixed Assets on the Reports menu, and then click Activity.

  • Additions

    To print the Additions report, point to Fixed Assets on the Reports menu, and then click Transaction.

  • Retirements

    To print the Retirements report, point to Fixed Assets on the Reports menu, click Transaction, and then click Retirements in the Reports list.

  • Transfers

    To print the Transfers report, point to Fixed Assets on the Reports menu, click Transaction, and then click Transfers in the Reports list.

  • Depreciation Ledger

    To print the Depreciation Ledger report, point to Fixed Assets on the Reports menu, click Depreciation, and then click Depreciation Ledger in the Reports list.

  • Property Ledger

    To print the Property Ledger report, point to Fixed Assets on the Reports menu, click Inventory, and then click Property Ledger in the Reports list.

  • “Fixed Assets to General Ledger Reconciliation”

    To print the “Fixed Assets to General Ledger Reconciliation” report, point to Fixed Assets on the Reports menu, click Activity, and then click Fixed Assets to General Ledger Reconciliation in the Reports list.

If you have more than one fixed asset book, we recommend that you also print the following reports:

  • “Book to Book Reconciliation”

    To print the “Book to Book Reconciliation” report, point to Fixed Assets on the Reports menu, and then click Comparison.

  • “Book to Book YTD Depreciation Comparison”

    To print the “Book to Book YTD Comparison” report, point to Fixed Assets on the Reports menu, click Comparison, and then click Book to Book YTD Depreciation Comparison in the Reports list.

Step 6: Guarantee that the Fixed Assets calendar is built correctly (This step is optional.)

  1. Use the appropriate method:
    • In Microsoft Dynamics GP 10.0 or Microsoft Dynamics GP 2010, point to Tools on the Microsoft Dynamics GP menu, point to Utilities, point to Fixed Assets, and then click Build Calendar.
    • In Microsoft Dynamics GP 9.0, point to Utilities on the Tools menu, point to Fixed Assets, and then click Build Calendar.
  2. Click Inquire, and then click Verify. When you are prompted to verify the periods, click OK.
  3. In the Report Destination window, click Screen, and then click OK.

Step 7: Verify that the quarters are set up correctly for all the fiscal years

  1. Use the appropriate method:
    • In Microsoft Dynamics GP 10.0 or Microsoft Dynamics GP 2010, point to Tools on the Microsoft Dynamics GP menu, point to Setup, point to Fixed Assets, and then click Quarter.
    • In Microsoft Dynamics GP 9.0, point to Setup on the Tools menu, point to Fixed Assets, and then click Quarter.
  2. Make sure that the following boxes are not empty:
    • Start Date
    • Mid Date
    • End Date

    Note These boxes must exist for each quarter. If any box is empty, type the appropriate date in that box.


Step 8: Create a backup

This backup should be stored off-site together with the rest of the year-end documentation. This backup gives you a permanent record of the company’s financial position at the end of the year. Additionally, this backup can be restored later if it is required. Making a backup guarantees that you can quickly recover if a power fluctuation or other problem occurs during the year-end closing procedures.

To create a backup in Microsoft Dynamics GP, follow these steps:

  1. Use the appropriate method:
    • In Microsoft Dynamics GP 10.0 or Microsoft Dynamics GP 2010, point to Maintenance on the Microsoft Dynamics GP menu, and then click Backup.
    • In Microsoft Dynamics GP 9.0, click Backup on the File
      menu.
  2. In the Company Name list, click the company name.
  3. Change the path of the backup if you must, and then click OK.

Step 9: Perform the fixed assets year-end closing routine

  1. Use the appropriate method:
    • In Microsoft Dynamics GP 10.0 or Microsoft Dynamics GP 2010, point to Tools on the Microsoft Dynamics GP menu, point to Routines, point to Fixed Assets, and then click Year End.
    • In Microsoft Dynamics GP 9.0, point to Routines on the Tools menu, point to Fixed Assets, and then click Year End.
  2. Verify that the fiscal year that is displayed for each book is the current fiscal year. (The current fiscal year is the year that you are closing.)

    Note If the fiscal year that is displayed for a book is not the current fiscal year, see question 1 in the “Frequently asked questions (FAQ)” section.

  3. Click a book that you want to close, and then click Insert. Repeat this step until all the books that you want to close have been inserted.

Note Microsoft Dynamics performs the following procedures during the year-end closing routine:

  • In the Asset General Information window, the Quantity field is copied to the Begin Quantity field of the Expand Quantity window.
  • In the Expand Last Maintenance window, the YTD Maintenance amount is cleared.
  • In the Asset Book window, the YTD Depreciation Amount is cleared.
  • The following procedures are performed:
    • The Cost Basis field is copied to the Begin Year Cost field.
    • The LTD Depreciation field is copied to the Begin Reserve field.
    • The Salvage Value field is copied to the Begin Salvage field.
  • In the Book Setup window, the Current Fiscal Year field is increased by one.

Note A report is not generated during the fixed assets year-end closing routine.

Frequently asked questions (FAQ)

Q1: The fiscal year that is displayed for my book in the Asset Year End window is not 2012. I closed 2011 last year, and I have not yet closed 2012. What should I do?

A1: See the answer for question 4.

Q2: I have closed General Ledger in Microsoft Dynamics GP, and I now realize that I have not yet closed Fixed Asset Management. Can I perform the fixed assets year-end closing routine at this point?

A2: We recommend that you close General Ledger last, after all the subsidiary modules have been closed. However, Fixed Asset Management can be closed after General Ledger is closed. The GL Posting (GL Interface) process can be performed, and then the transaction or transactions can be posted to the closed year or to the historical year in the general ledger. For more information about the GL Posting (GL Interface) process, see step 4 in the “Year-end checklist” section.

To post transactions to the historical year in the general ledger, make sure that the following options are selected in the General Ledger Setup window:

  • Allow Posting to History
  • Maintain History Accounts
  • Maintain History Transactions

Notes

  • To access the General Ledger Setup window in Microsoft Dynamics GP 10.0 or Microsoft Dynamics GP 2010, point to Tools on the Microsoft Dynamics GP menu, point to Setup, point to Financial, and then click General Ledger.
  • To access the General Ledger Setup window in Microsoft Dynamics GP 9.0, point to Setup on the Tools menu, point to Financial, and then click General Ledger.

The posted transaction will update the historical year, and it will roll forward as a beginning balance to the open year. If any expense accounts or any revenue accounts were included in the transaction, they will automatically close out to the Retained Earnings account or accounts.

Q3: I ran the year-end routine in Fixed Asset Management, and then I ran depreciation in the new year. I see that the depreciation is highly overstated and that some assets have a negative number in the “Net Book Value” field. Why is the system calculating so much depreciation?

A3: This problem occurs if the following conditions are true:

  • The year was closed.
  • The assets were not depreciated through the last day of the fiscal year.

Consider the following example:

  • The fiscal year is a calendar year (January 1 through December 31).
  • The assets were depreciated through December 28 when the year was closed.

In this example, depreciation will be incorrect the next time that depreciation is run. The system does not recalculate the yearly rate when the year-end closing routine is performed. Therefore, fixed assets take a full year of depreciation in the last few days that remain in the previous year (December 29 through December 31). The rate of depreciation is the yearly rate currently on each asset. Additionally, if there are assets that are near the end of their original life, the Net Book Value field may become negative.

There are two workarounds for this problem:

  • Recommended workaround
    Restore the data from a backup, run depreciation through the last day of the year, and then perform the year-end closing procedures.
  • Alternative workaround
    Reset life on all the assets.

Note If amounts on the assets have ever been entered for the YTD Depreciation field or for the LTD Depreciation field, resetting life on the assets will change these amounts, and the result may be different. If you change the YTD Depreciation field or the LTD Depreciation field by resetting life on the asset, you will cause inconsistencies between Fixed Asset Management and General Ledger. These inconsistencies must be explained.

Q4: Instead of completing the year-end routine for Fixed Asset Management, I manually changed the “Current Fiscal Year” field in the Book Setup window to the next year. Do I have to go back and run the year-end closing routine, or can I continue to process activity in Fixed Asset Management for the new year?

A4: If no activity, such as additions, changes, transfers, retirements, or depreciation, has been run for the new year, the Current Fiscal Year field in the Book Setup window can be changed back to the previous year, and then the year-end closing routine can be processed.

If any activity, such as additions, changes, transfers, retirements, or depreciation, has been run for the new year, restore the data from a backup, and then continue with the year-end closing routine.

In either situation, the year-end closing routine must be run. If the year-end closing routine is not completed, the amount in the YTD Depreciation field will be overstated on any report that includes assets that were retired or that were fully depreciated in the previous year. If the year-end closing routine is not performed, the amounts in the YTD Depreciation field will not be cleared. The amounts in the YTD Depreciation field will not be zeroed out. Therefore, these amounts will be incorrectly included in the reports for the new year.

Continue Reading:
The year-end closing procedures for the Fixed Asset Management module in Microsoft Dynamics GP

Year-end closing procedures for the Canadian Payroll module in Microsoft Dynamics GP

2012 payroll year-end update and 2013 payroll tax update

This article discusses the payroll year-end update and the payroll tax update. When the payroll year-end update for the year 2012 and the payroll tax update for the year 2013 are released, you may download the file from Partnersource or Customersource. (See the links that are listed in the ‘Install the 2012 Canadian year-end update’ section.) Until the payroll year-end update and the payroll tax update are released, use this article for information and for preparation purposes only.

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.

This document outlines the recommended year-end closing procedures for the Microsoft Dynamics GP integrated Canadian Payroll module. The “More Information” section contains the following:

  • A detailed checklist of the steps that you must follow to complete the year-end closing procedures
  • Detailed information for each step in the checklist
Read this whole article before you perform any one of the
steps. If you have any questions, contact Microsoft Dynamics Technical Support.
More information about the Canadian Payroll module is typically included in the
year-end update documentation.

Payroll year-end checklist

  1. Complete all the pay runs for the current year.
  2. Complete any necessary 2012 payroll reports.
  3. Make a backup of the data.
  4. Install the 2012 Canadian Payroll Year-End Update.
  5. Complete the “Year End File Reset” process.
  6. Make a backup of the data.
  7. Create the T4, T4A, and RL-1 statements, and print the T4, T4A, and RL1 reports.
  8. Edit the T4, T4A, and RL-1 records as
    necessary.
  9. Create T4, T4A, and RL-1 Summary records.
  10. Print the T4, T4A, RL-1 reports and create T4, T4A and RL-1
    XML files, if appropriate.
  11. Verify that pay periods for 2013 are set correctly.

Payroll year-end details

Note The 2012 Payroll Year-End Update and the 2013 Payroll Tax Update (Round 1) will be available for Microsoft Dynamics GP 10.0. Please note that Microsoft Dynamics GP 9.0 and earlier versions are no longer supported. 

Complete all the pay runs for the current year.

Note Any batch that has a value of 2013 in the
Cheque Date field should be processed after you perform the year-end reset. If the cheque date of your final pay period for 2012 is in the year 2013, the 2013 tax tables must be used per the statement in the Canada Customs and Revenue Agency document T4001. To download a copy of this document, visit the following Web site:For example, a weekly payroll that has a cutoff date of January 1, 2013, is processed by using the 2013 tax calculations. This payroll will be included in the 2013 history.

Make a backup of the data.

Create a backup, and then put this backup into safe,
permanent storage. By creating a backup, you make sure that you have a
permanent record of the company’s financial position at the end of the year.
You can restore the backup to quickly recover data if a power fluctuation or
other problem occurs during the year-end closing procedure. To create a back up
from Microsoft Dynamics GP, follow these steps:

  1. Use the appropriate method:

    • In Microsoft Dynamics GP 10.0 or Microsoft Dynamics GP 2010, click  Maintenance on the Microsoft Dynamics GP
      menu, and then click Backup.
    • In Microsoft Dynamics GP 9.0, click
      Backup on the File menu. The Back Up Company
      window opens.
  2. In the Company Name list, click the
    company name.
  3. Change the path of the backup file if this action is
    required, and then click OK.

    Note We recommend that you name this backup “2012 Pre Year-End Tax Update” to differentiate it from your other backups.

Install the 2012 Canadian Year-End Update.

Install the update from one of the following locations,
depending on whether you are a partner or a customer:

Complete the “Year End File Reset” process.

To perform a year-end file reset, follow these steps:

  1. Have all users close all Canadian Payroll windows. Users
    can continue to work in other Microsoft Dynamics GP modules.
  2. Use the appropriate method:
    • In Microsoft Dynamics GP 10.0 or Microsoft Dynamics GP 2010, point to
      Tools on the Microsoft Dynamics GP menu,
      point to Routines, point to Payroll – Canada,
      and then click Year End File Reset.
    • In Microsoft Dynamics GP 9.0, point to
      Routines on the Tools menu, point to
      Payroll – Canada, and then click Year End File
      Reset
      .
  3. In the Payroll Reset Files window, click Copy Files
    to History
    . This step creates the required data to view inquiries from
    the previous year in Canadian Payroll. To access the inquiries from the
    previous year in Canadian Payroll, point to Payroll Canada on
    the Inquiry menu, and then click Employee Last Year
    Information
    .

    Note In this step, you receive a message that warns you to check
    available disk space. You must have at least two times as much available disk
    space as the amount that is currently occupied by all the files that are in the
    Data/Project directory.

  4. Click Tax Credit Indexation Factors.
  5. In the Tax Credit Indexation Factors window, verify the
    basic personal factor (Cost of Living Factor) from the Canada Customs and
    Revenue Agency document T4127. Verify the numbers, and then click
    OK.

    Notes

    • When the employee masters are reset, the TD1 Basic
      Personal amounts will be adjusted by the multiplier that you enter.
    • These TD1 Basic Personal amounts should be
      automatically updated after you install the Canadian Payroll Year-End Update
      file.
  6. Click Reset Employee Master.

    Note You must run this process before you process any pay runs for the
    new year.

  7. Click Yes or No when you
    are prompted to reset the Employee User Numeric fields,
    depending on your preference.
  8. On the Cards menu, point to
    Payroll-Canada, and then click Employee to
    view the Employee User Numeric fields.
  9. In the Employee ID field, type an employee
    ID, click Miscellaneous, and then click User
    Data
    .

Make a backup of the data.

Create a backup, and then put this backup into safe,
permanent storage. By creating a backup, you make sure that you have a
permanent record of the company’s financial position at the end of the year.
You can restore the backup to quickly recover data if a power fluctuation or
other problem occurs during the year-end closing procedure. To create a back
up, follow these steps:

  1. Use the appropriate method:

    • In Microsoft Dynamics GP 10.0 or Microsoft Dynamics GP 2010, click
      Maintenance on the Microsoft Dynamics GP
      menu, and then click Backup.
    • In Microsoft Dynamics GP 9.0, click
      Backup on the File menu. The Back Up Company
      window opens.
  2. In the Company Name list, click your
    company name.
  3. Change the path of the backup file if this action is
    required, and then click OK.

    Note We recommend that you name this backup “2012 Post Year-End Tax Update” to differentiate it from your other backups.

Create the T4, T4A, and RL-1 statements, and print the T4, T4A, and RL-1 reports.

Note This step can be performed any time after you complete the
previous step, “Perform a year-end file reset.” For example, you may complete
pay runs for the new year before you create and print any reports.

Create and print the T4 reports and the RL-1 reports

To do this, follow these steps:

  1. Use the appropriate method:

    • In Microsoft Dynamics GP 10.0 or Microsoft Dynamics GP 2010, point to
      Tools on the Microsoft Dynamics GP menu, point to
      Routines, point to Payroll – Canada, and then
      click T4 and R1 Creation.
    • In Microsoft Dynamics GP 9.0, point to
      Routines on the Tools menu, point to
      Payroll – Canada, and then click T4 and R1
      Creation
      .
  2. Click Create T4′s
  3. Click Create R1′s.
  4. To print the T4 Verification Report, click Print
    T4 Report
    .
  5. To print the R1 Verification Report, click
    Print R1 Report.
  6. Click OK to exit.
  7. Print the T4 Edit List. To do this, point to
    Payroll-Canada
    on the Reports menu, click
    Routines, click Routines Reports, and then
    click T4 Edit Report.
Create and print the T4A reports

To do this, follow these steps:

  1. Use the appropriate method:

    • In Microsoft Dynamics GP 10.0 or Microsoft Dynamics GP 2010, point to
      Tools on the Microsoft Dynamics GP menu,
      point to Routines, point to Payroll – Canada,
      point to T4A Routines, and then click T4A
      Setup
      .
    • In Microsoft Dynamics GP 9.0, point to
      Routines on the Tools menu, point to
      Payroll – Canada, point to T4A Routines, and
      then click T4A Setup.
  2. Click Create T4A’s.
  3. Click Print T4A Report to print the T4A
    Verification Report.

Edit the T4, T4A, and RL-1 records as necessary.

Modify the T4 statements

To do this, use the appropriate method:

  • In Microsoft Dynamics GP 10.0 or Microsoft Dynamics GP 2010, point to
    Tools on the Microsoft Dynamics GP menu,
    point to Routines, point to Payroll – Canada,
    and then click T4 Edit.
  • In Microsoft Dynamics GP 9.0, point to
    Routines on the Tools menu, point to
    Payroll – Canada, and then click T4 Edit.
Modify the T4A statements

To do this, use the appropriate method:

  • In Microsoft Dynamics GP 10.0 or Microsoft Dynamics GP 2010, point to
    Tools on the Microsoft Dynamics GP menu,
    point to Routines, point to Payroll – Canada,
    point to T4A Routines, and then click T4A Record
    Edit
    .
  • In Microsoft Dynamics GP 9.0, point to
    Routines on the Tools menu, point to
    Payroll – Canada, point to T4A Routines, and
    then click T4A Record Edit.
Modify the R1 amounts based on the edit list in the R1 Edit window

To do this, use the appropriate method:

  • In Microsoft Dynamics GP 10.0 or Microsoft Dynamics GP 2010, point to
    Tools on the Microsoft Dynamics GP menu,
    point to Routines, point to Payroll – Canada,
    and then click R1 Edit.
  • In Microsoft Dynamics GP 9.0, point to
    Routines on the Tools menu, point to
    Payroll – Canada, and then click R1 Edit.

Create T4, T4A, and RL-1 Summary records.

Create the summary information for the T4 reports and for the RL-1 reports

To do this, follow these steps:

  1. Use the appropriate method:

    • In Microsoft Dynamics GP 10.0 or Microsoft Dynamics GP 2010, point to
      Tools on the Microsoft Dynamics GP menu,
      point to Routines, point to Payroll – Canada,
      and then click T4 and R1 Summary.
    • In Microsoft Dynamics GP 9.0, point to
      Routines on the Tools menu, point to
      Payroll – Canada, and then click T4 and R1
      Summary
      .
  2. Click Create T4 Summary Records.
  3. Click Create R1 Summary Records.
Create the summary information for the T4A reports

To do this, follow these steps:

  1. Use the appropriate method:

    • In Microsoft Dynamics GP 10.0 or Microsoft Dynamics GP 2010, point to
      Tools on the Microsoft Dynamics GP menu,
      point to Routines, point to Payroll – Canada,
      point to T4A Routines, and then click T4A
      Summary
      .
    • In Microsoft Dynamics GP 9.0, point to
      Routines on the Tools menu, point to
      Payroll – Canada, point to T4A Routines, and
      then click T4A Summary.
  2. Click Create T4A Summary Records.

Print the T4, T4A, RL-1 reports and
create T4, T4A and RL-1 XML files, if appropriate.

Print the final T4 reports

To do this, follow these steps:

  1. Use the appropriate method:

    • In Microsoft Dynamics GP 10.0 or Microsoft Dynamics GP 2010, point to
      Tools on the Microsoft Dynamics GP menu,
      point to Routines, point to Payroll – Canada,
      and then click T4 and R1 Print.
    • In Microsoft Dynamics GP 9.0, point to
      Routines on the Tools menu, point to
      Payroll – Canada, and then click T4 and R1
      Print
      .
  2. In the Employer Number field, select the
    appropriate employer number.
  3. Click T4 Slip Type to select the
    appropriate form.
  4. To print the T4 Statements, click T4
    Slips
    . Follow the prompts and select if you want to test the form
    alignment by printing a test record.
  5. Click T4 Summary and T4
    Segment
    .

    Note These reports are not designed to print on to a pre-printed form.

  6. To generate the electronic T4 file, click
    Electronic T4’s. Complete the Payroll Electronic Transfer T4
    window and then click either Verify Only or Verify and
    Generate
    .
Print the RL-1 reports

To do this, follow these steps:

  1. Use the appropriate method:

    • In Microsoft Dynamics GP 10.0 or Microsoft Dynamics GP 2010, point to
      Tools on the Microsoft Dynamics GP menu,
      point to Routines, point to Payroll – Canada,
      and then click T4 and R1 Print.
    • In Microsoft Dynamics GP 9.0, point to
      Routines on the Tools menu, point to
      Payroll – Canada, and then click T4 and R1
      Print
      .
  2. In the Employer Number field, select the
    appropriate employer number.
  3. Click R1 Slip Type to choose either
    Laser or Continuous.
  4. In the Starting R1 Number field, enter
    the starting R1 number.
  5. To print the R1 statements, click R1
    Slips
    .
  6. To print the R1 Summary report, click R1
    Summary
    .

    Note This report is not designed to print on to a pre-printed
    form.

  7. To generate the electronic RL-1 file, click
    Electronic R1′s. Complete the Payroll Electronic Transfer R1
    window and then click either Verify Only or Verify and
    Generate
    .
Print the T4A reports

To do this, follow these steps:

  1. Use the appropriate method:

    • In Microsoft Dynamics GP 10.0 or Microsoft Dynamics GP 2010, point to
      Tools on the Microsoft Dynamics GP menu,
      point to Routines, point to Payroll – Canada,
      point to T4A Routines, and then click T4A
      Print
      .
    • In Microsoft Dynamics GP 9.0, point to
      Routines on the Tools menu, point to
      Payroll – Canada, point to T4A Routines, and
      then click T4A Print.
  2. In the Employer Number field, select the
    appropriate employer number.
  3. Click T4A Slip Type to choose either
    Laser Employee or Laser CCRA.
  4. To print the T4A statements, click T4A
    Slips
    .
  5. To print the reports, click T4A Segment
    and T4A Summary.
  6. To generate the electronic T4A’s, click Electronic
    T4A’s
    . Complete the Payroll Electronic Transfer T4A window and then
    click either Verify Only or Verify and
    Generate
    .

Verify that the pay periods are set correctly for 2013

To verify that the pay periods are set correctly for 2013, use the appropriate method:  

  • In Microsoft Dynamics GP 10.0 or Microsoft Dynamics GP 2010, point to
    Tools on the Microsoft Dynamics GP menu,
    point to Setup, point to Payroll – Canada,
    point to Control, and then click
    Frequency.
  • In Microsoft Dynamics GP 9.0, point to
    Setup on the Tools menu, point to
    Payroll – Canada, point to Control, and then
    click Frequency.

Article ID: 861806 – Last Review: October 9, 2012 – Revision: 13.2


Applies to
  • Microsoft Dynamics GP 2010
  • Microsoft Dynamics GP 10.0
  • Microsoft Dynamics GP 9.0, when used with:
kbexpertiseinter kbexpertisebeginner kbinfo atdownload kbmbspayrolltaxupdate kbmbsmigrate KB861806

Other Support Sites

Community

Get Help Now

Article Translations

See more here:
Year-end closing procedures for the Canadian Payroll module in Microsoft Dynamics GP

Year-end closing procedures for the Payables Management module in Microsoft Dynamics GP

This article describes the recommended year-end closing procedures for the Payables Management module in Microsoft Dynamics GP. The “More Information” section contains the following information:

  • A checklist of the steps that you must follow to complete the calendar year-end closing procedures.
  • A checklist of the steps that you must follow to complete the fiscal year-end closing procedures.
  • Detailed information about each step in the checklists.
  • A list of frequently asked questions.
Read this whole article before you perform the steps. If you have questions, contact Microsoft Dynamics Technical Support.

Payables Management master year-end closing checklist

Note Use this checklist if you are closing your fiscal year and your calendar year at the same time.

  1. Post all transactions for the year.
  2. Print the Aged Trial Balance with Options report.
  3. Print the Vendor Period Analysis Report.
  4. Install the Payroll year-end update (optional)
  5. Make a backup that is named “Pre-1099 Edits.”
  6. Verify the 1099 information and edit it if it is required.
  7. Print the 1099 statements.
  8. Make a backup that is named “Pre Year-End.”
  9. Close the year.
  10. Close the fiscal periods.
  11. Close the tax year.
  12. Make a backup that is named “Post Year-End.”

Payables Management calendar year-end closing checklist

Note Although the Payables Management module is date-sensitive, the SmartList objects, the Payables Management summary reports, and the Amounts Since Last Close view of the Vendor Yearly Summary window are updated based on the closing of the Payables Management module. Therefore, we recommend that you follow these steps so that the SmartList objects, the Payables Management summary reports, and the Amounts Since Last Close view of the Vendor Yearly Summary window are correct.

  1. Post all transactions for the calendar year.
  2. Print the Aged Trial Balance with Options report.
  3. Make a backup that is named “Pre-1099 Edits.”
  4. Verify the 1099 information and edit it if it is required.
  5. Print the 1099 statements.
  6. Make a backup that is named “Pre Year-End.”
  7. Close the calendar year.
  8. Close the fiscal periods.
  9. Close the tax year.
  10. Make a backup that is named “Post Year-End.”

Payables Management fiscal year-end closing checklist

  1. Post all transactions for the fiscal year.
  2. Print the Vendor Period Analysis Report.
  3. Make a backup that is named “Pre Year-End.”
  4. Close the fiscal year.
  5. Close the fiscal periods.
  6. Make a backup that is named “Post Year-End.”

Detailed information for each step in the year-end checklist

Step 1: Post all transactions for the year

Post all transactions for the year before you close the year. If you want to enter future period transactions before you close the year, create a new batch for the future period transactions. Save the future period transactions in the new batch, but do not post the new batch until after the year has been closed.

The following areas of Microsoft Dynamics GP are not date-sensitive:

  • The Amounts Since Last Close view of the Vendor Yearly Summary window
  • SmartList objects
  • Vendor Summary reports

 These areas of Microsoft Dynamics GP will be incorrect if you do not close the payables year after you enter all 2012 transactions and before you enter all 2013 transactions. However, the Amounts Since Last Close view of the Vendor Yearly Summary window is editable. Therefore, you can update the information in the Amounts Since Last Close view of the Vendor Yearly Summary window if it is required.

To access the Amounts Since Last Close view of the Vendor Yearly Summary window, follow these steps:

  1. On the Cards menu, point to Purchasing, and then click Summary.
  2. In the Vendor Credit Summary window, type a vendor ID in the Vendor ID field, and then click Yearly.
  3. In the Summary View list, click Amounts Since Last Close.

To view the SmartList columns that are affected, follow these steps:

  1. Open SmartList. To do this, use the appropriate step:
    • In Microsoft Dynamics GP 10.0 or Microsoft Dynamics GP 2010, click SmartList on the Microsoft Dynamics GP menu.
    • In Microsoft Dynamics GP 9.0, click SmartList on the View menu.
  2. Use the appropriate step:
    • In Microsoft Dynamics GP 10.0 or Microsoft Dynamics GP 2010, expand the Purchasing node, and then click Vendors.
    • In Microsoft Dynamics GP 9.0, click Vendors.
  3. Click Columns.
  4. Click Add.
  5. Click the following fields in the Available Columns list.
    Note The items flagged with an asterisk are affected by the calendar year-end close. All other items are affected by the fiscal year-end close.
    • *1099 Amount YTD
    • *1099 Amount LYR
    • Amount Billed YTD
    • Amount Billed LYR
    • Amount Paid YTD
    • Amount Paid LYR
    • Average Days To Pay – Year
    • Discount Available LYR
    • Discount Available YTD
    • Discount Lost LYR
    • Discount Lost YTD
    • Discount Taken LYR
    • Discount Taken YTD
    • Finance Charge LYR
    • Finance Chare YTD
    • Number of Finance Charges LYR
    • Number of Finance Charges YTD
    • Number of Invoice LYR
    • Number of Invoice YTD
    • Number of Paid Invoice YTD
    • Returns LYR
    • Returns YTD
    • Trade Discounts Taken LYR
    • Trade Discounts Taken YTD
    • Withholding LYR
    • Withholding YTD
    • Write Offs LYR
    • Write Offs YTD
  6. Click OK.
  7. Click OK.

To view the Vendor Summary reports, follow these steps:

  1. On the Reports menu, point to Purchasing, and then click Analysis.
  2. In the Reports list, click Calendar Year.
  3. In the Options list, click an option, and then click Print.

Step 2: Print the Aged Trial Balance with Options report

We recommend that you print a paper copy of the Aged Trial Balance with Options report to keep with your year-end permanent financial records. To do this, follow these steps:

  1. On the Reports menu, point to Purchasing, and then click Trial Balance.
  2. In the Reports list, click Aged Trial Balance with Options.

Step 3: Print the Vendor Period Analysis report

We recommend that you print a paper copy of the Vendor Period Analysis report to keep with your year-end permanent financial records. To do this, follow these steps

  1. On the Reports menu, point to Purchasing, and then click Analysis.
  2. In the Reports list, click Period.


Step 4: Install the Payroll year-end update (optional)

If there are compliance changes for Payables Management, such as 1099 form changes, install the Payroll year-end update. If there are no changes or compliance issues for the tax year for Payables Management, you may skip this step.

Review the changes that are included in the Payroll year-end update. To do this, visit the appropriate Microsoft Web site:

Step 5: Make a backup that is named “Pre-1099 Edits”

Create a backup, and then put the backup in safe, permanent storage. A backup gives you a permanent record of the company’s financial position at the end of the year, and this backup can be restored later if it is required. A backup lets you recover data quickly if a power fluctuation or other problem occurs during the year-end closing procedure.

To create a backup in Microsoft Dynamics GP, follow these steps:

  1. Use the appropriate step:
    • In Microsoft Dynamics GP 10.0 or Microsoft Dynamics GP 2010, point to Maintenance on the Microsoft Dynamics GP menu, and then click Backup.
    • In Microsoft Dynamics GP 9.0, click Backup on the File menu.
  2. In the Company Name list, click your company name.
  3. Change the path of the backup file if it is required, and then click OK.
    Note We recommend that you name this backup “Pre-1099 Edits” to differentiate it from your other backups.

Step 6: Verify the 1099 information and edit it if it is required

To print the 1099 edit list, follow these steps:

  1. Use the appropriate step:
    • In Microsoft Dynamics GP 10.0 or Microsoft Dynamics GP 2010, point to Tools on the Microsoft Dynamics GP menu, point to Routines, point to Purchasing, and then click Print 1099.
    • In Microsoft Dynamics GP 9.0, point to Routines on the Tools menu, point to Purchasing, and then click Print 1099.
  2. On the File menu, click Print.

To edit the 1099 information for a vendor, follow these steps.

Microsoft Dynamics GP 10.0 or Microsoft Dynamics GP 2010
To open the “1099 Details” window, use one of the following methods.
Method 1

  1. On the Cards menu, point to Purchasing, and then click 1099 Details.
  2. In the Vendor ID list, click a vendor ID.
  3. In the Tax Type list, select one of the following:
    • Dividend
    • Interest
    • Miscellaneous
  4. In the Display area, click Month or Year, and then type 2012 in the Year field.
  5. In the Amount column, type the correct 1099 amount.
  6. Click Save.

Method 2

  1. On the Cards menu, point to Purchasing, and then click Summary.
  2. In the
    Vendor ID list, click a vendor ID, and then click Period.
  3. In the Year field, type 2012.
  4. In the Month/Period field, select the appropriate month or period.
  5. Click the “1099 Details” button that appears next to the 1099 Amount field.
  6. In the Amount column, type the correct 1099 amount.

Microsoft Dynamics GP 9.0

  1. On the Cards menu, point to Purchasing, and then click Summary.
  2. In the Vendor ID field, type the ID of the vendor whose 1099 amounts you must edit, and then click Period.
  3. In the Year field, type 2012.
  4. In the Month/Period field, type the number of the period that you must edit.
  5. In the 1099 Amount field, type the correct 1099 amount.
  6. Click Save.

Step 7: Print the 1099 statements

Note You can do this at any time.

To print the 1099 statements, follow these steps:

  1. Use the appropriate step:
    • In Microsoft Dynamics GP 10.0 or Microsoft Dynamics GP 2010, point to Tools on the Microsoft Dynamics GP menu, point to Routines, point to Purchasing, and then click Print 1099.
    • In Microsoft Dynamics GP 9.0, point to Routines on the Tools menu, point to Purchasing, and then click Print 1099.
  2. In the 1099 Year field, type 2011.
  3. Each of your 1099 report types must be printed separately. In the Print 1099 window, click the options that you want in the 1099 Type field and in the 1099 Box Number field, and then click Print.

The following table provides additional information about the fields on the 1099 form and where this information can be located in Microsoft Dynamics GP.

Collapse this tableExpand this table

Field window where data is located
Payers name, street address, city, state, and ZIP Code/Postal Code Print 1099 window
Payers Federal Identification number Print 1099 window
Recipients name, address, and Zip Code/Postal Code Primary Address of the Vendor Maintenance window
Recipients identification number Tax ID field of the Vendor Maintenance Options window
Amounts for boxes 1-9 on the Dividend Form or 1-16 on the Miscellaneous Form 1099 Amount field in the Vendor Yearly Summary window

Currently, Microsoft Dynamics GP does not handle magnetic media filing of state 1099s. The following Microsoft Dynamics Partner does offer compatible State W-2 and 1099 magnetic media products. For more information, contact:

Greenshades Accounting Software, Inc.

7800 Belfort Parkway
Suite 220

Jacksonville, FL 32207

General: 1-800-209-9793 (Toll-Free)

Sales: 1-800-209-9793×2 (Toll-Free)

sales@greenshades.com

http://www.greenshades.com

(http://www.greenshades.com)

Step 8: Make a backup that is named “Pre Year-End”

Create a backup, and then put the backup in safe, permanent storage. A backup gives you a permanent record of the company’s financial position at the end of the year, and this backup can be restored later if it is required. A backup lets you recover data quickly if a power fluctuation or other problem occurs during the year-end closing procedure.

To create a backup in Microsoft Dynamics GP, follow these steps:

  1. Use the appropriate step:
    • In Microsoft Dynamics GP 10.0 or Microsoft Dynamics GP 2010, point to Maintenance on the Microsoft Dynamics GP menu, and then click Backup.
    • In Microsoft Dynamics GP 9.0, click Backup on the File menu.
  2. In the Company Name list, click your company name.
  3. Change the path of the backup file if it is required, and then click OK.
    Note We recommend that you name this backup “Pre Year-End” to differentiate it from your other backups.

Step 9: Close the year

To close the year, follow these steps:

  1. Use the appropriate step:
    • In Microsoft Dynamics GP 10.0 or Microsoft Dynamics GP 2010, point to Tools on the Microsoft Dynamics GP menu, point to Routines, point to Purchasing, and then click Year-End Close.
    • In Microsoft Dynamics GP 9.0, point to Routines on the Tools menu, point to Purchasing, and then click Year-End Close.
  2. If you are closing both your fiscal and calendar year at the same time, click All. If you are just closing your calendar year, click Calendar. If you are just closing your fiscal year, click Fiscal.
  3. Click to select the Print Report check box, and then click Close Year.
    Note We recommend that you keep a paper copy of the year-end report together with your permanent year-end audit records.

To view the Vendor Yearly Summary window, follow these steps:

  1. On the Cards menu, point to Purchasing, and then click Summary.
  2. In the Vendor ID field, type a vendor ID to view, and then click Yearly.

The calendar year details
The calendar year-end process in Microsoft Dynamics GP will clear the 1099 Amount Year to Date field and then transfer the amount to the 1099 Amount Last Year field for the Amounts Since Last Close view of the Vendor Yearly Summary window.

The fiscal year details
The fiscal year-end process in Microsoft Dynamics GP will clear the following fields:

  • Amount Billed YTD
  • Amount Paid YTD
  • Average Days To Pay – Year
  • Discount Available YTD
  • Discount Lost YTD
  • Discount Taken YTD
  • Finance Charge YTD
  • Number of Finance Charges YTD
  • Number of Invoice YTD
  • Number of Paid Invoice YTD
  • Returns YTD
  • Trade Discounts Taken YTD
  • Withholding YTD
  • Write Offs YTD

The amounts in these fields will also be updated in the Amounts Since Last Close view of the Vendor Yearly Summary window:

  • Amount Billed LYR
  • Amount Paid LYR
  • Discount Available LYR
  • Discount Lost LYR
  • Discount Taken LYR
  • Finance Charge LYR
  • Number of Finance Charges LYR
  • Number of Invoice LYR
  • Returns LYR
  • Trade Discounts Taken LYR
  • Withholding LYR
  • Write Offs LYR

Step 10: Close the fiscal periods

You can use the Fiscal Periods Setup window to close any fiscal periods that are still open for the year. This prevents users from accidentally posting transactions to the wrong period or year. Verify that you have posted all transactions for the period and the year for all modules before closing fiscal periods. If you must later post transactions to a fiscal period that you have already closed, you can return to the Fiscal Periods Setup window to reopen the period before you can post a transaction.

To close a fiscal period, follow these steps:

  1. Use the appropriate step:
    • In Microsoft Dynamics GP 10.0 or Microsoft Dynamics GP 2010, point to Tools on the Microsoft Dynamics GP menu, point to Setup, point to Company, and then click Fiscal Periods.
    • In Microsoft Dynamics GP 9.0, point to Setup on the Tools menu, point to Company, and then click Fiscal Periods.
  2. Click to select the Purchasing check box for the Period that you must close.

Step 11: Close the tax year

Note This procedure should only be completed after you have completed the year-end closing procedures for all sales and purchasing modules.

To close the tax year, follow these steps:

  1. Use the appropriate step:
    • In Microsoft Dynamics GP 10.0 or Microsoft Dynamics GP 2010, point to Tools on the Microsoft Dynamics GP menu, point to Routines, point to Company, and then click Tax Year-End Close.
    • In Microsoft Dynamic GP 9.0, point to Routines on the Tools menu, point to Company, and then click Tax Year-End Close.
  2. Click to select the Close Year check box and the Print Report check box.
  3. Click Process. When you are prompted to continue with the year-end close. Click Yes.
    Note We recommend that you keep a paper copy of the year-end report together with your permanent year-end audit records.

Step 12: Make a backup that is named “Post Year-End”

Create a backup, and then put the backup in safe, permanent storage. A backup gives you a permanent record of the company’s financial position at the end of the year, and this backup can be restored later if it is required. A backup lets you recover data quickly if a power fluctuation or other problem occurs during the year-end closing procedure.

To create a backup in Microsoft Dynamics GP, follow these steps:

  1. Use the appropriate step:
    • In Microsoft Dynamics GP 10.0 or Microsoft Dynamics GP 2010, point to Maintenance on the Microsoft Dynamics GP menu, and then click Backup.
    • In Microsoft Dynamics GP 9.0, click Backup on the File menu.
  2. In the Company Name list, click your company name.
  3. Change the path of the backup file if it is required, and then click OK.
    Note We recommend that you name this backup “Post Year-End” to differentiate it from your other backups.

Frequently asked questions

Q1: Are inactive vendor records cleared during year-end closing? If not, how can inactive vendor records be removed?

A1: No, inactive vendor records are not automatically removed. To remove an inactive vendor record, the following conditions must be true:

  • No current year 1099 amounts exist for the vendor
  • The vendor has no documents in work or history.

To delete all inactive vendor records that fit these criteria, follow these steps:

  1. Use the appropriate step:
    • In Microsoft Dynamics GP 10.0 or Microsoft Dynamics GP 2010, point to Tools on the Microsoft Dynamics GP menu, point to Utilities, point to Purchasing, and then click Mass Vendor Delete.
    • In Microsoft Dynamics GP 9.0, point to Utilities on the Tools menu, point to Purchasing, and then click Mass Vendor Delete.
  2. In the Range list, click by Vendor Status.
  3. In the From list, click Inactive.
  4. In the To list, click Inactive.
  5. Click Process.

Q2: What should I do if I must issue a check on January 1, 2013 but I am not ready to close 2012 yet?

A2: Print the checks, but post them after you process your year-end closing. If you must post the checks immediately, change the Amount Paid fields in the Amounts Since Last Close view of the Vendor Yearly Summary window.

See the original post:
Year-end closing procedures for the Payables Management module in Microsoft Dynamics GP

Employee Level Security in Canadian Payroll for Microsoft Dynamics GP

SUMMARY

The purpose of this document is to provide you with information on the Employee Level Security feature in Canadian Payroll and how you can set this up.

MORE INFORMATION

Follow these steps to set up and use Employee Level Security in Canadian Payroll:

1. Start Canadian Payroll.

2. For Microsoft Dynamics GP 10.0 and later versions, click on Tools under Microsoft Dynamics GP, point to Setup, point to Payroll – Canada, click Control (click OK if prompted) and then select the Control Button.

For Microsoft Dynamics GP 9.0 and earlier versions, click Routines, click Payroll – Canada, click Setup Palette, click Control, and then select the Control button.

3. Click on the No next to Enable Employee Level Security field so the field value shows Yes. After this selection, you will be prompted with a message that “Employee Level Security is Enabled. Please review user security setup for correct access to payroll”. Click OK to clear this message.

4. Click
OK to exit the
Payroll Control Variables – Canada window, and click
Save to exit the
Payroll Control Setup – Canada window.

5. From the
Shortcuts menu, click
Add, and then click
Other Window.

6. Click
Add, click to expand the
Canadian Payroll folder, and then click to expand the
Project folder.

7. From the available windows, click to select the Payroll User Security Group Master – Canada option, and then click
Add.

8. From the available windows, click to select the Payroll User Employee Security Setup- Canada option, and then click
Add.

9. Click Done to close the Add Window Shortcut window.

10. Under Shortcuts, click the Payroll User Security Group Master- Canada option.

11. Create a name and description for the Security Group.

12. Select the appropriate Employer Number, Department, Employee Class, and Employee Payment Method from the lookups. Set up all the security group combinations needed. (You must also set up an ALL group to assign to powerusers. Just click in each field on the word Specific to have it automatically change it to ALL.) Click Save once the setup is complete. Exit from the
Payroll User Security Group Master – Canada window.

13. Click the
Payroll User Employee Security Setup – Canada option from the Shortcuts menu.

14. Select a
User ID from the lookup and select a
Security Group ID from the lookup that the User ID should be assigned to. Click
Save. Exit the
Payroll User Employee Security Setup – Canada window once you have assigned all users to a security group.

NOTE: Also assign security to powerusers.

You can now have users log into Great Plains Canadian Payroll and test the security setup.

NOTE:
This security feature will limit security to the Payroll Employee Setup – Canada window only (click Cards, click Payroll – Canada, click Employee). The users can still access data, such as pay rate, by printing any of the Cards Reports (click Cards, click Payroll – Canada and then click Cards Reports). The user can still access data through Smartlists if they have access to it. 

This article was TechKnowledge Document ID: 34947

Article ID: 862642 – Last Review: October 5, 2012 – Revision: 2.1


Applies to
  • Microsoft Dynamics GP 2010
  • Microsoft Dynamics GP 10.0
  • Microsoft Dynamics GP 9.0, when used with:

Continued here:
Employee Level Security in Canadian Payroll for Microsoft Dynamics GP

SDP 3c2b1b42a-e9f8-48a4-9053-a2ca9e21608d Microsoft Dynamics CRM Claims and IFD Collector

The Microsoft Dynamics CRM Claims and IFD Collector was designed to collect information to be used to troubleshoot issues related to setup and configuration of Claims and Internet Facing Deployment for Microsoft Dynamics CRM.
This article offers an overview of the information that may be collected by the Microsoft Dynamics CRM Claims and IFD Collector.

Notes:

·          This collector is run on the server hosting the Active Directory Federation Service 2.0 service

·          This collector creates two report files.  Both files are prefaced with the ComputerName on which the Microsoft Support Diagnostic Tool is run. 

·          In the event that the ADFS service and CRM Server are on separate machines, the user will be prompted to enter the hostname of the CRM Server.  This feature does not support connections to CRM servers in different domains.

Information Collected

Operating System Information

Collapse this tableExpand this table

Description File Name
Operating System Version Information Computername_ADFSReport_DateRan.htm

Computername_CRMClaimsReport_DateRan.htm

Application Logs

Collapse this tableExpand this table

Description File Name
Event Log – All ADFS 2.0 events in the last seven days

Event Log – All system events in the last seven days

Computername_ADFSReport_DateRan.htm

Federation Service Properties

Collapse this tableExpand this table

Description File Name
Details from the AD FS 2.0 service using the Microsoft.Adfs.Powershell snapin Computername_ADFSReport_DateRan.htm

IIS URL ACL Information

Collapse this tableExpand this table

Description File Name
Provides the output from the Netsh Http Show UrlAcl command line utility Computername_ADFSReport_DateRan.htm

AD FS 2.0 Endpoint Information

Collapse this tableExpand this table

Description File Name
Listing of the configured endpoints in AD FS 2.0 using the Microsoft.Adfs.Powershell snapin Computername_ADFSReport_DateRan.htm

AD FS 2.0 Relying Party Trust Information

Collapse this tableExpand this table

Description File Name
Details the relying party trusts that have been configured in AD FS 2.0 using the Microsoft.Adfs.Powershell snapin Computername_ADFSReport_DateRan.htm

AD FS 2.0 Claims Provider Trust Information

Collapse this tableExpand this table

Description File Name
Details the Claims provider trusts that have been configured in AD FS 2.0 using the Microsoft.Adfs.Powershell snapin Computername_ADFSReport_DateRan.htm

AD FS 2.0 Certificate Information

Collapse this tableExpand this table

Description File Name
Detailed listing of the certificates used for the AD FS Service Communication, Token Signing, and Token Decryption Computername_ADFSReport_DateRan.htm

IIS Application Pool Settings

Collapse this tableExpand this table

Description File Name
Detailed list of all application pools that are present on the server that is running IIS and the AD FS 2.0 service Computername_ADFSReport_DateRan.htm

IIS Applications Running Under AD FS Application Pool

Collapse this tableExpand this table

Description File Name
Listing of the applications that have configured to run under the context of the AD FS 2.0 Application Pool Computername_ADFSReport_DateRan.htm

IIS Authentication Information

Collapse this tableExpand this table

Description File Name
Detailed listing of the authentication settings for the AD FS web site and its application.  The sites include:

‘Default Web Site’

‘Default Web Site’/adfs

‘Default Web Site’/adfs/

Computername_ADFSReport_DateRan.htm

IIS Application Pool Settings For CRM Server

Collapse this tableExpand this table

Description File Name
Detailed listing of all application pools that are present on the server that is running IIS and the CRM Server. Computername_CRMClaimsReport_DateRan.htm

Microsoft Dynamics CRM Server Certificate Information

Collapse this tableExpand this table

Description File Name
Provides information related to the certificate that is assigned to the Microsoft CRM website Computername_CRMClaimsReport_DateRan.htm

Microsoft Dynamics CRM Federation Provider Information

Collapse this tableExpand this table

Description File Name
Listing of the details for the configured Microsoft Dynamics CRM Federation Provider that is stored in the MSCRM_Config.FederationProvider table Computername_CRMClaimsReport_DateRan.htm

Microsoft Dynamics CRM Web Address Information

Collapse this tableExpand this table

Description File Name
Detailed listing of the web addresses that have been used to configure Microsoft Dynamics CRM 2011 for Claims based authentication. Computername_CRMClaimsReport_DateRan.htm

Microsoft Dynamics CRM Internet Facing Deployment (IFD) Information

Collapse this tableExpand this table

Description File Name
Listing of properties from the MSCRM_Config.Deployment table that are used to configure Microsoft Dynamics CRM as an Internet Facing Deployment. Computername_CRMClaimsReport_DateRan.htm

Microsoft Dynamics CRM IIS URL ACL Information

Collapse this tableExpand this table

Description File Name
Provides the output from the Netsh Http Show UrlAcl command line utility {Computername_CRMClaimsReport_DateRan.htm

Additional Information

This collector has a notifications area at the top of the diagnostic report detailing items that may be important to make note of.  These are items that aren’t at the root cause of an issue but are worth noting as they may affect the performance or usability of Microsoft Dynamics CRM.  For this reason, they are called out at the top of the report to give them visibility. 

1.     Virtualization Check – This is notification that CRM is being run with a virtual server and may experience performance issues.

2.     IsDisableLoopbackCheckEnabled – Warnings that this key from the HKLMSYSTEMCurrentControlSetControlLsa registry hive is or is not set.  This key does impact the performance of the Microsoft Dynamics CRM server.

3.     IsBackConnectionHostNames – Similar warning to the IsDisableLoopbackCheckEnabled registry key check.  This can have performance implications as well.

4.     CustomPluginPresenceCheck – Just notifies the customer or engineer to the presence of custom CRM Plugins in the deployment.

5.     Power Plan Settings Notification – Having the CRM server’s power plan settings set to something other than High Performance may have performance implications to Microsoft CRM.  This displays what the power plan is set to.

References                                                                                                                           

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

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

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

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

for other considerations.

Article ID: 2764416 – Last Review: October 5, 2012 – Revision: 1.0


Applies to
  • Microsoft Dynamics CRM 2011
kbmbsmigrate kbsurveynew KB2764416

Taken from:
SDP 3c2b1b42a-e9f8-48a4-9053-a2ca9e21608d Microsoft Dynamics CRM Claims and IFD Collector

Integration between Microsoft Dynamics CRM Online and SharePoint Online

How to integrate Microsoft SharePoint Online with Microsoft Dynamics CRM Online 2011
Integration between SharePoint Online Subscription to work with Microsoft Dynamics CRM 2011 Online
A working SharePoint Subscription and Workplace should be created for 2007 (BPOS) or 2010 (O365). Please follow the below steps in the CRM application to complete the integation steps with SharePoint

1. In Microsoft Dynamics CRM, click on Settings in the navigation pane

2. Click on Document Managment

3. Click On New

4. Click on Sharepoint Sites

5. Enter the Display Name and the Description

6. Under URL Options select Absoloute URL

7. Enter the Absolute URL (Example: http://orgname.sharepoint.microsoftonline.com)

8. Click on Save & Close

9. Under Document Managment, click on SharePoint Document Locations

10. Enter the Display name and description of the the location

11. Under the URL Options select Absolute URL

12. Enter the Absolute URL. (This has to be the location of the folder in your SharePoint site, if you are not sure navigate to your SharePoint site, click on the folder, and copy the location in the address bar)

13. Click on Save & Close

14. Under Document Managment click on Document Managment Settings

15. Select the entity that would use SharePoint to store docs. (Keep the URL Box Empty) 
 

To confirm point to WorkPlace, click on Accounts, and select an Account (assuming the Accounts entity is chosen to use SharePoint in the Document Managment Settings wizard) Click on Documents and the interface would prompt for login credentialss. Use the SharePoint Online credentials. Once Authenticated the user would have access to the SharePoint Site.
Note This is a “FAST PUBLISH” article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use

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

for other considerations.

Article ID: 2517202 – Last Review: October 5, 2012 – Revision: 8.0


Applies to
  • Microsoft Dynamics CRM 2011
kbmbsmigrate kbsurveynew KB2517202

See the original article here:
Integration between Microsoft Dynamics CRM Online and SharePoint Online

Supportability is available for Office Communications Server 2007 R2 member server role on a Windows Server 2008 R2 operating system

This article describes the supportability for the Microsoft Office Communications Server 2007 R2
member server role on a server that has a Windows Server 2008 R2 operating
system installed. However,
the following scenarios are currently not supported
on a Windows Server 2008 R2 operating system:
  • Upgrading the operating system to Windows Server 2008 R2 for an existing installation of Office Communications Server 2007 R2 is not supported.
  • Office Communications Server 2007 R2 administration tools will only install in native 32-bit or native 64-bit mode. Because of an application compatibility issue with Windows Server 2008 R2, installing 32-bit Office Communications Server 2007 R2 administration tools on 64-bit Windows 2008 R2 operating system is not supported.
  • Development with Speech Server (2007) Developer Edition and deployment of the Speech Server 2007 role are not supported on Windows Server 2008 R2.
  • The Office Communications Server 2007 R2 XMPP Gateway role is not supported on Windows Server 2008 R2.
  • The Communicator Web Access 2007 R2 role is not supported on Windows Server 2008 R2         
Take
the following steps to install Office Communications Server 2007 R2 on a server
that is running a Windows Server 2008 R2 operating system:
  1. Install.NET Framework 3.5.1 by using Roles wizard from
    Server Manager. You can do this by selecting the Windows-based application server
    role to make sure completeness. This is a manual step. You must have
    .NET Framework 3.5 SP1 on a Windows Server 2008 R2 operating system before you
    install a version of Office Communications Server 2007 R2 that only includes
    .NET Framework 3.5.
  2. Install the Desktop Experience Features by using Add
    Features wizard from Server Manager. This is required for Media format runtime.
    The name of the media format runtime package depends on the operating system
    and the Office Communications Server 2007 R2 setup that refers to the Windows
    Server 2008 or to the Windows Server 2003 Media format runtime installation
    package.
  3. Install the Hotfix that is described in KB 975858 for
    Windows Server 2008 R2.
    975858

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

    An application or service that
    calls the InitializeSecurityContext function together with the
    ISC_REQ_EXTENDED_ERROR flag may encounter a TLS/SSL negotiation failure on a
    computer that is running Windows Server 2008 R2 or Windows 7 operating system

  4. Install Office Communications Server 2007 R2 Server
    Roles
  5. For Office Communications Server 2007 R2, Standard Edition,
    or Enterprise Edition, or Edge Server role, when KB 974571 is installed,
    Activation of the Office Communications Server 2007 R2 server role fails. To
    fix this problem, follow these steps:

    1. Apply the OCSASNFix.exe file. To download the
      Ocsasnfix.exe file, visit the following Microsoft Web site:
    2. Rerun Office Communications Server 2007 R2
      Activation

    Note This is not specific to Windows Server 2008 R2 operating system.
    For more information, visit the following Microsoft Web site:

  6. Install updates for Office Communications Server 2007 R2
    that are dated October 2009 (3.5.6907.56), or install later versions. To
    download the updates for Office Communications Server 2007 R2, visit the
    following Microsoft Web site:
    For more information about how to install the Office
    Communications Server 2007 R2 updates, click the following article number to
    view the article in the Microsoft Knowledge Base:
    968802

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

    Updates for Communications Server 2007 R2

  7. Install updates for Office Communications Server 2007 R2, Group Chat Server, Office Communications Server 2007 R2, Group Chat Admin Tool and Office Communications Server 2007 R2, Group Chat Client that are dated May 2010 (3.5.6907.200), or install later versions.

    Note You will experience the issue that is described in Microsoft Knowledge Base article 982129

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

    if you do not apply the the update that is mentioned in the previous step.

    To download the updates for Office Communications Server 2007 R2, Group Chat Server, visit the following Microsoft website:

    To download the updates for Office Communications Server 2007 R2 Group Chat Administration Tool, visit the following Microsoft website:

    To download the updates for Office Communications Server 2007 R2 Group Chat Client, visit the following Microsoft website:

  8. The default security setting on Windows Server 2008 R2
    operating system for NTLM SSP requires 128-bit encryption. Depending on the
    client operating system mix in the enterprise, you may have to reduce this
    setting on a Windows Server 2008 R2 operating system that is running Office
    Communications Server 2007 R2 as a down level operating system. The key is set
    to “No requirement.”

    1. For any down level operating system, such as Windows XP
      or for Windows Vista, the default value is set to “No Minimum.”
    2. For a Windows 7 operating system, the default value is
      set to “Requires 128-bit encryption.”

For more information about the “Changes in NTLM
Authentication” as it applies to Windows 2008 R2 and Windows 7 operating
systems, please visit the following Microsoft Web site:
If you want to change the NTLM setting, follow these steps:

  1. Start secpol.msc on a Windows Server 2008 R2 operating
    system server.
  2. Click to select Local Policies and then
    click Security Options node.
  3. Make sure that the following values of the policies are
    set to “No Minimum.”

    • Network Security: Minimum session security for NTLM SSP
      based (including secure RPC)
    • Network Security: Minimum session security for NTLM SSP
      based (including secure RPC) servers

For more information about the operating systems that are
currently supported for Office Communications Server 2007 R2, visit the
following Microsoft Web site:
For more information about Office
Communications 2007 R2 running in Windows 2008 R2 Domain and Forest, click the
following article number to view the article in the Microsoft Knowledge Base:

982020

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

Office Communications Server 2007
R2, Office Communications Server 2007 or Live Communications Server 2005 does
not work correctly after you upgrade a domain controller to Windows Server 2008
R2 operating system

Article ID: 982021 – Last Review: October 4, 2012 – Revision: 6.0


Applies to
  • Microsoft Office Communications Server 2007 R2 Enterprise Edition
  • Microsoft Office Communications Server 2007 R2 Standard Edition
kbexpertiseinter kbinfo kbtshoot kbsurveynew KB982021

Continued here:
Supportability is available for Office Communications Server 2007 R2 member server role on a Windows Server 2008 R2 operating system

Page 323 of 754« First...102030...321322323324325...330340350...Last »

Recent Comments

    Archives

    Categories