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

OFFXP: Office Shortcut Tab Is Unavailable

When you view the Shortcut tab in the Properties dialog box for any of the Office shortcuts on the Programs menu, the entire tab may be unavailable.

NOTE: On Microsoft Windows 2000 and Microsoft Windows Millennium Edition (Me), only the Target box is unavailable on the Shortcut tab of the Properties dialog box.

The items on the Shortcut tab are unavailable if you install Office and you are using one of the following versions of Windows:

  • Microsoft Windows 98
    -or-
  • Microsoft Windows NT version 4.0 with Internet Explorer
    4.01, at least Service Pack 1, and Windows Desktop Update installed
    -or-
  • Microsoft Windows 2000
    -or-
  • Microsoft Windows Millennium Edition (Me)

Office XP shortcuts installed on these versions of Windows are Windows Installer shortcuts. Windows Installer shortcuts do not directly reference the path of the shortcut target. Instead, they contain a token that the Windows Installer resolves to the path of the shortcut target.

If you want to customize the Office shortcuts on the Programs menu, use one of the following methods.

Method 1: Create Your Own Shortcuts

You can create your own shortcuts to the Office programs and replace the ones installed by Office with the ones that you create.

NOTE: Any shortcuts that you create by using this method are not Windows Installer shortcuts and do not take advantage of the features offered by the Windows Installer. See the “More Information” section of this article.

For example, to replace the shortcut for Microsoft Word, follow these steps.

NOTE: Because there are several versions of Microsoft Windows, the following steps may be different on your computer. If they are, see your product documentation to complete these steps.

  1. Click Start, point to Programs, and then click Windows Explorer.
  2. In Windows Explorer, open the WindowsStart MenuPrograms folder, and then delete the shortcut for Word.
  3. In Windows Explorer, open the Program FilesMicrosoft OfficeOffice10 folder, and then right-click Winword.exe.
  4. Click Create Shortcut on the shortcut menu.
  5. Right-click the shortcut that you just created, and then click Properties. Modify the necessary fields on the Shortcut tab, and then click OK.
  6. Move this shortcut to the WindowsStart MenuPrograms folder.

NOTE: Your custom shortcut may be replaced by a Windows Installer shortcut if you name the shortcut Microsoft Word, and if either of the following is true:

  • You use the Detect and Repair feature in Office, and the Restore my shortcuts while repairing check box is selected.
    -or-
  • You select the Repair Office option in Maintenance Mode Setup, click Next, click the Detect and Repair errors in my Office installation option, and then select the Restore My Start Menu Shortcuts check box.

In this situation, you must recreate your custom, non-Windows Installer shortcuts.

Method 2: Customize Shortcuts with the Custom Installation Wizard

The Custom Installation Wizard (CIW) is a tool available in the Microsoft Office Resource Kit (ORK). (To obtain, see the “More Information” section of this article.) The advantage of using the CIW is that the custom shortcuts you create this way are Windows Installer shortcuts that take advantage of the features offered by the Windows Installer.

To create custom shortcuts by using the CIW, follow these steps:

  1. Start the Custom Installation Wizard.
  2. In page 2 of the CIW, locate and select the .msi file from your installation source. For example, select Proplus.msi if you are using Microsoft Office Professional with FrontPage.

    NOTE: You can only use the CIW with Enterprise editions of Office XP. If the .msi file that you are using contains “ret” (for example, Proret.msi) in the file name, you are using a non-Enterprise edition of Office.

  3. Provide a path and name for the transform file (.mst) in page 4 of the CIW.
  4. In the Add, Modify, or Remove Shortcuts dialog box of the CIW, select the shortcut that you want to customize, and then click Modify.
  5. In the Add/Modify Shortcut Entry dialog box, specify any or all of the following items:
    • Target
    • Location
    • Name
    • Start in (location)
    • Shortcut key
    • Run (window state)
    • Icon
  6. Make the changes to the shortcut properties, and then click OK.
  7. Repeat steps 4 through 6 for each of the shortcuts that you want to customize.
  8. Click Finish.
    The last page in the CIW provides the command-line switches for running Office Setup by using the transform file created by the CIW.

    NOTE: The /qb+ switch on the end of the example command line is optional.

  9. Run Office Setup using the command line provided by the CIW. For example, your command line may be similar to the following

    pathSetup.exe Transforms=drive:MyShortcuts.mst

    where path is the path to Setup.exe, and drive:MyShortcuts is the path and name of the transform file (.mst).

Windows Installer shortcuts offer the following added benefits over standard shortcuts:

  • Windows Installer shortcuts allow programs on the Programs menu to be set to Installed on First Use.
  • Windows Installer shortcuts allow the Windows Installer to autorepair programs when started.

For more information about the Microsoft Office XP Resource Kit, please browse to the following Microsoft Web site:

Article ID: 290379 – Last Review: November 6, 2012 – Revision: 4.0


Applies to
  • Microsoft Excel 2002 Standard Edition
  • Microsoft Outlook 2002 Standard Edition
  • Microsoft PowerPoint 2002 Standard Edition
  • Microsoft Word 2002

View original post here:
OFFXP: Office Shortcut Tab Is Unavailable

Description of the Excel 2000 SR-1 update: June 19, 2002

Microsoft has released an update to Microsoft Excel 2000.
This update includes several security updates and other issues that are
corrected.

This article describes how to download and install Excel
2000 Update: June 19, 2002.

Important Before you install Excel 2000 Update: June 19, 2002, Microsoft
Office 2000 Service Release 1a (SR-1a) must already be installed on your
computer.

For additional information about the latest
service pack for Microsoft Office 2000, click the following article number to view the article in the Microsoft Knowledge Base:

276367

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

OFF2000: How to obtain the latest Office 2000 service pack

How to Download and Install the Update

Administrative Update

If you installed Microsoft Excel 2000 from a server location, the
server administrator must update the server location with the administrative
public update and deploy that update to your computer.

If you are the
server administrator, follow these steps:

  1. Visit the following Microsoft Web site:
  2. Download the file to your desktop.
  3. In Microsoft Windows Explorer, double-click the Exc0901a.exe file.
  4. Click Yes to accept the License Agreement.
  5. In the Please type the location where you want to
    place the extracted files
    box, type
    C:exc0901a, and then click OK.
  6. Click Yes when you are prompted to create the folder.
  7. Click Start, and then click Run. Type the following command in the Open box:

    start msiexec /p pathname of update
    MSP file /a pathname of MSI file SHORTFILENAMES=TRUE /qb /L*v pathname of
    log file

  8. To deploy the update to the client workstations, click Start, and then click Run. Type the following command in the Open box:

    start msiexec /i path to updated .msi
    file on the administrative image REINSTALL=EXCELFiles REINSTALLMODE=vomus
    /q

For additional information about how to update
your administrative installation and deploy to client
workstations, click the following article number to view the article in the Microsoft Knowledge Base:

304165

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

How to download and install an update to an administrative installation of Office 2000

This article contains
standard instructions for installing an administrative public
update.

Alternatively, see the following article in the Microsoft
Office XP Resource Kit:

How to Determine Whether the Public Update Is Installed

The Excel 2000 Update: June 19, 2002 affects the Excel.exe file.
Excel 2000 Update: June 19, 2002 updates the version of Microsoft Excel 2000 to
version 9.0.6508. To determine the version of Microsoft Excel installed on your
computer, follow these steps:

  1. Search for Excel.exe
  2. Right-click the Excel.exe file, and then click Properties on the shortcut menu.
  3. View the Version tab to determine the version of Excel that is on your
    computer.

Note If Excel 2000 Update: June 19, 2002 is already applied to your
computer, you will receive the following message when you try to install the
Excel 2000 Update: June 19, 2002:

This update has already been applied or is included in an update that has already been applied.

Issues Fixed by the Update

The update fixes the issues described in the following Knowledge
Base articles:

305694

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

XL2000: ALT+TAB Does Not Trigger Workbook_WindowActivate Event

289629

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

XL2000: “An Unexpected Error Has Occurred” When You Update Links from Web Browser

316479

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

XL2000: Contents of PivotTable Disappear When Data Is Updated in a Different Language Version of Excel

272189

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

XL2000: JPN: Nested Group Objects in Excel 95 Workbook Are Displayed in Different Location

278679

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

OFF2000: “This Workbook (Document) Has Been Password Protected” When You Open Workbook or Document

300523

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

PPT2000: Embedded Excel Worksheets Shrink When You Edit Them

304442

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

FIX: Excel 2000 May Fault in MSO9.DLL When Calling an XLL Function that Takes an Array

303809

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

XL2000: Drawing Objects on Charts Move After You Save and Reopen

305949

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

XL2000: CPU Usage Spikes at 100 Percent When Excel Is Running in the Background

297883

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

XL2000: You Can See Other Users’ Printers in a Terminal Server Session

307809

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

XL: Excel Stops Responding When You Drag an Item in the PivotTable Layout Wizard

311749

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

XL2000: Combo Box Control on a Worksheet Returns to Its Original Value After Refresh

307609

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

XL2000: Borders of AutoShape on Embedded Excel Chart Change Thickness When Printed

291110

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

XL2000: Cannot Use Keyboard Shortcuts to Select Ranges in RefEdit Control

316399

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

XL2000: Error Message: No RETURN() or HALT() Function Found on Macro Sheet

316070

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

PPT: Borders Are Lost When You Print Inserted Excel Objects at Printer Resolution

318063

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

XL2000: Cannot Set the Orientation Property of a Pivot Field

317850

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

XL2000: Excel Stops Responding When You Run VBA Macro Code That Displays a User Form

320520

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

XL2000: Excel Quits Unexpectedly When You Switch Between Tab Strip and Chart on Worksheet

Additionally, the following issues have been fixed in this
update but were previously not documented in the Microsoft Knowledge Base.

XL2000: Security Update: Change in Binary Format Can Bypass Macro Security

If a file is changed at the binary level, the file may
bypass Excel macro security settings.

OFF2000: Security Update: Office Programs Do Not Warn When You Open Infected Documents That Have Been Flagged or Scanned by Antivirus Software.

When you open an Excel file that has been flagged by
antivirus software as infected, Excel may not warn you that the file contains
macros that may damage to your system.

XL2000: Security Update: Embedded Macro Command Object Can Bypass High Security Settings

When you click an embedded object, a macro that can
bypass Excel security settings may be run.

OFF: 100% CPU Usage When You Hold Left Mouse Button Down

When you use any of the Office programs on a Microsoft
Windows 2000-based computer, the CPU usage reaches 100% if you hold the left
mouse button down for more then a few seconds.

XL2000: PivotTable Operation with a Macro Causes Error

In Microsoft Excel Version 2000, when you run a Visual
Basic for Applications macro that creates and format a series of PivotTables
several times, you may receive the error message:

Run-time error: -2147417848 (80010108) ‘Position’ method failed: ‘PivotField’
object”.

XL2000: Transition Navigation Keys Setting Is Not Retained

When you use the Multilanguage Pack for Office 2000,
the Transition navigation keys setting is lost when you quit Excel.

(To view the Transition navigation keys check box, click Options on the Tools menu, and then click the Transition tab.)

XL2000: When You Save File with Chart as Excel 5.0/95 Format, Excel Quits Unexpectedly

In Excel 2000, when you open an Excel 95 file that
contains a chart, and then save the file in Excel 5.0/95 format, Excel may quit
unexpectedly.

XL2000: Embedded Charts with Custom Colors Lose Colors When Saved As HTML

Embedded charts on a worksheet do not retain custom
colors if you save the workbook as HTML and then open it in Microsoft Internet
Explorer. If you open the same HTML file in Excel 2000, the custom colors are
displayed as expected.

XL2000: Chart Resized After You Embed It in Word

If you set a chart to a custom size in Excel, copy the
chart, and then embed it in a Word document, the chart in the original file may
be resized to the Excel window.

XL2000: JPN: Macro Causes Error After Using AutoComplete

After you insert an AutoComplete entry, when you run a
macro, you may receive the following error message:

Run-time error ’1004′: Method ‘Visible’ of object ‘_Worksheet’
failed”.

XL2000: Custom Chart Resized After Editing in Word

When you edit a custom size Excel chart in-place in
Word, the chart may lose its custom size.

XL2000: JPN: Bad Redraw with Freeze Panes Used with Outline Group

After you group a series of cells, and then click Freeze Panes while you are working with a Zoom value of less than 100%, the
freeze pane may move to the left and some column text may be deleted.

XL2000: Cannot Follow a Path to Further Analysis in PivotTable

In Excel 2000, you cannot follow a path to to further
analysis in a PivotTable unless the Save data with table layout option is selected.

XL2000: JPN: Excel Quits Scrolling Mouse Horizontally

In print preview, when you try to scroll horizontally
by using a touch pad, Excel may generate an application error, and then quit
unexpectedly.

XL2000: JPN: Excel Quits Unexpectedly Inserting a Calculated Field

When you use Excel 2000 with a program that uses
Windows Messaging, if you add a calculated field with a double-byte character
set (DBCS) field name to a PivotTable, there may be an access violation in
Excel.

XL2000: Error Message When User Name Is Longer Than Nine Characters

If you change your user name in Excel to a name that is
more than nine characters long, and you then switch between multiple Excel
worksheets, Excel stops responding (hangs) when you quit Excel.

XL2000: Error Message States That File Locked by Another User

When you open an Excel file with a URL longer than 255
characters, you may receive the following error message:

File name is locked for editing by
user name‘.

XL2000: Excel Quits Unexpectedly When You Save File That Contains Charts

If you try to save a workbook that contains charts in
Microsoft Excel 2000 SR-1, Excel may stop responding or quit unexpectedly.
After this problem occurs, Excel quits unexpectedly again when you try to
reopen the workbook.

XL2000: Adding Data Fields to a Pivot Table From Macro Can Cause Error

If you use an Excel worksheet that contains a macro to
create and format a series of PivotTables, you may receive the following error
message:

Run-time error ‘-2147417848 (80010108)’: Method
“Orientation’ of object “PivotField” failed.

XL2000: Application Error When You Quit Excel on a SharePoint Portal Server Client

On a Microsoft SharePoint Portal Server Client, if you
quit Excel after you open an .xls file that includes a Microsoft Outlook
Express envelope, there may be an application error and Excel may quit.

XL2000: Radar Chart Shrinks After Print Preview

After you print preview a worksheet that contains a
radar chart, the radar chart dimensions shrink dramatically.

Excerpt from:
Description of the Excel 2000 SR-1 update: June 19, 2002

Error message when you try to perform the year-end closing process in General Ledger in Microsoft Dynamics GP: "Retained Earnings account not found"

When you try to perform the year-end closing process in General Ledger in Microsoft Dynamics GP, you receive the following error message:

Retained Earnings account not found.

This problem occurs if you click to select the Close to Divisional Account Segments check box in the General Ledger Setup window.

Additionally, the error message may occur because of one of the following causes:

Cause 1

Only one Retained Earnings account is set up. However, the Close to Divisional Account Segments check box is selected in the General Ledger Setup window. See .

Cause 2

Retained Earnings accounts are set up without a common segment to close to. See Resolution 2.

Cause 3

The Close to Divisional Account Segments check box is selected. However, the Retained Earnings account is not set up for each segment division. See Resolution 3.

Cause 4

The Retained Earnings accounts have blank spaces in them. See Resolution 4.

Cause 5

The GL00105 Account Index table has a damaged record. See Resolution 5.

Before you perform any of these resolutions, make sure that you have all other users log out of Microsoft Dynamics GP or Microsoft Business Solutions – Great Plains. Also make sure that you create a restorable backup of the company database.

Resolution 1

To resolve this problem, clear the Close to Divisional Account Segments check box in the General Ledger Setup window. To do this, follow these steps:

  1. Open the General Ledger Setup window. To do this, follow these steps:
    • Microsoft Dynamics GP 10.0 or Microsoft Dynamics GP 2010:

      On the Microsoft Dynamics GP menu, point to Tools, point to Setup, point to Financial, and then click General Ledger.

  2. In the General Ledger Setup window, click to clear the Close to Divisional Account Segments check box.
  3. Click OK to save the changes.


Resolution 2

To resolve this problem, close to only one segment of the different Retained Earnings account numbers. You cannot close to more than one segment of the account numbers.

Example

In this example, the following Retained Earnings account numbers exist:

  • A-000-3030-00
  • B-100-3030-00
  • C-200-3030-00

In this example, you cannot close by using the second segment of the account numbers. The second segments are 000, 100, and 200. After you decide on that segment that you want to close by, the rest of the segments must be the same. Therefore, in this example, you have the following options:

  • If you want to close by using the second segment, you must change the first segment (the letter) so that it is the same for all accounts. For example, to close by using the second segment and by using the divisional retained earnings, change the first segments as follows:
    • A-000-3030-00
    • A-100-3030-00
    • A-200-3030-00
  • If you want to close by using the first segment, you must change the second segment so that it is the same for all accounts. You can change the second segment by using one of the following options:
    • A-000-3030-00, B-000-3030-00, C-000-3030-00
    • A-100-3030-00, B-100-3030-00, C-100-3030-00
    • A-200-3030-00, B-200-3030-00, C-200-3030-00


Resolution 3

Verify that no segment division has a Retained Earnings account that was created for it. To do this, follow these steps:

  1. Open the Account Segment Setup window. To do this, follow these steps:
    • Microsoft Dynamics GP 10.0 or Microsoft Dynamics GP 2010:

      On the Microsoft Dynamics GP menu, point to Tools, point to Setup, point to Financial, and then click Segment.

  2. Click the lookup button next to the Segment field, and then note the account segment that is assigned in the General Ledger Setup window.
  3. Use the lookup button next to the Number field.
  4. Note the segment numbers that you can view by using the segment lookup button.
  5. Open the Account Maintenance window. To do this, click Cards, point to Financial, and then click Account.
  6. Make sure that all segments noted in step 4 have corresponding Retained Earnings accounts set up.

    Example

    The following conditions are true:

    • You have a Retained Earnings account number of 000-3030-00.
    • The first segment of the account number is set up as the divisional account segment.
    • You noted that the first segment has these numbers set up: 000, 100, 200, 300, and 400.

    In this example, you have to verify that the following Retained Earnings account numbers are also set up:

    100-3030-00
    200-3030-00
    300-3030-00
    400-3030-00

  7. If all segments are not set up, set them up now in the Account Maintenance window. To do this, click Cards, point to Financial, and then click Account.


Resolution 4

To resolve this problem, determine whether the Retained Earnings account numbers have blank spaces in them. To do this, follow these steps:

  1. Open the Account Maintenance window. To do this, click Cards, point to Financial and then click Account.
  2. Select one of the Retained Earnings accounts, and then examine the account number to make sure that it has no spaces in it.

    Example

    • You have a Retained Earnings account number of 000-3030-00.
    • The first segment of the account number is set up as the divisional account segment.
    • You noted that the first segment has these numbers set up: 000, 100, 200, 300, and 400.

    In this example, you have to verify that the following Retained Earnings account numbers are also set up:

    100-3030-10
    200-3030-20
    300-3030-30
    400-3030-40

    However, you may have unintentionally increased the segment length of the first segment to four characters, and Microsoft Dynamics GP will not recognize the Retained Earnings accounts that you originally created. If you increase the first segment, the account numbers would resemble the following:

    100X-3030-10
    200X-3030-20
    300X-3030-30
    400X-3030-40

    Note In these numbers, X represents a blank space.

    If there are spaces in the account numbers, continue with the following steps.

  3. Open the Reconcile window. To do this, follow these steps: 
    • Microsoft Dynamics GP 10.0 or Microsoft Dynamics GP 2010:

      On the Microsoft Dynamics GP menu, point to Tools, point to Utilities, point to System, and then click Reconcile.

    Note The Reconcile command reverts the account segment format to the original segment lengths. The reconciliation works only if no accounts that have an actual first segment length of four characters,excluding spaces. That is, no accounts that have a first segment such as 1000 as in the example, 1000-1100-00. If this is the case, the segment lengths revert to three characters.

  4. Select Account Format Setup, and then click Insert.
  5. Click Reconcile, and then print the error log to the screen.

    Note The Account Index Master (GL00105) table would probably still contain the accounts that use the account length of four characters. Therefore, you have to rebuild the table by using SQL Maintenance.

  6. Open the SQL Maintenance window. To do this, follow these steps: 
  7. Select the company database, and then select Microsoft Dynamics GP under Product.
  8. Select the Account Index Master table under Financial Series.
  9. Click to select all the check boxes, and then click Process.

    Note After the GL00105 table is re-created, you have to restore the data by using Check Links.

  10. Open the Check Links window. To do this, follow these steps: 
  11. Select Financial as the Series, and then insert the Account Master logical tables.
  12. Click OK to start the process.

    Note The information found in the Account Master (GL00100) table should now populate the GL00105 table.

Resolution 5

1. Open SQL Server Management Studio.
2. In a query window, run this script against the company database:
3. Open Microsoft Dynamics GP. On the Microsoft Dynamics GP menu, point to Maintenance, and then click Check Links.

4. Select Financial series.

5. In the Logical Tables list, click to select Account Master. Click Insert.

6. Then click OK to run check links. Print the Error Log to the screen.

7. Test again.

Article ID: 850741 – Last Review: November 6, 2012 – Revision: 12.0


Applies to
  • Microsoft Dynamics GP 2010
  • Microsoft Dynamics GP 10.0
  • Microsoft Dynamics GP 9.0
  • Microsoft Business Solutions–Great Plains 8.0, when used with:
kberrmsg kbtshoot kbprb kbexpertiseinter kbexpertisebeginner kbmbsmigrate KB850741

See more here:
Error message when you try to perform the year-end closing process in General Ledger in Microsoft Dynamics GP: "Retained Earnings account not found"

Image is not updated immediately when the Application. ScreenUpdating property is set to False in Excel 2010

Assume that the Application.ScreenUpdating property is set to False in Microsoft Excel 2010. When you capture an image by using the Camera tool, the text in the image is not immediately updated.

Note This issue occurs after you apply update 2405840 or a later version of the Excel 2010 hotfix package that fixes the issues that are described in update 2405840.

To resolve this issue, apply the following hotfix package:
2687559

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

Description of the Excel 2010 hotfix package (Excel-x-none.msp): October 30, 2012

Registry key information

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

After you install the hotfix package, follow these steps to enable the hotfix:

  1. Click Start, click Run, type regedit in the Open box, and then click OK.
  2. Locate and then select the following registry subkey:

    HKEY_CURRENT_USERSoftwareMicrosoftOffice14.0ExcelOptions

  3. On the Edit menu, point to New, and then click DWORD (32-bit) Value.
  4. Type UpdateCameraOnButtonClick, and then press Enter.
  5. In the Details pane, right-click UpdateCameraOnButtonClick, and then click Modify.
  6. In the Value data box, type 1, and then click OK.
  7. Exit Registry Editor.
Microsoft
has confirmed that this is a problem in the Microsoft products that are listed
in the “Applies to” section.

Article ID: 2760378 – Last Review: November 6, 2012 – Revision: 3.0

kbqfe kbsurveynew kbexpertisebeginner KB2760378

Read this article:
Image is not updated immediately when the Application. ScreenUpdating property is set to False in Excel 2010

Data provider framework error in Microsoft Management Reporter 2012 for Dynamics GP 2010

You may receive the following error in Management Reporter Report Designer when opening a row definition or column definition:

The operation could not be completed due to a problem in the data provider framework

The following error will also be in the Event Viewer:

Microsoft.Dynamics.Performance.DataProvider.Core.RequestException: The source system request did not complete successfully. —> System.ArgumentException: An item with the same key has already been added.
   at System.ThrowHelper.ThrowArgumentException(ExceptionResource resource)
   at System.Collections.Generic.Dictionary`2.Insert(TKey key, TValue value, Boolean add)
   at System.Collections.ObjectModel.KeyedCollection`2.AddKey(TKey key, TItem item)
   at System.Collections.ObjectModel.KeyedCollection`2.InsertItem(Int32 index, TItem item)
   at Microsoft.Dynamics.Performance.DataProvider.Collections.LockableKeyedCollection`2.InsertItem(Int32 index, TItem item)
   at System.Collections.ObjectModel.Collection`1.Add(T item)
   at Microsoft.Dynamics.Performance.DataProvider.GeneralLedger.GP.Data.AttributeElementCollection.CreateAttributeElementCollection(ChartElementCollection elementCollection, SourceSystemRepository repository)
   at Microsoft.Dynamics.Performance.DataProvider.GeneralLedger.GP.GLProvider.EnsureAttributeElementsPopulated()
   at Microsoft.Dynamics.Performance.DataProvider.GeneralLedger.GP.GLProvider.GetAttributes(GLAttributeRequest request)

This is caused if the same name existing in one of the three groups that are listed here:

1. User-Defined field names (Tools | Setup | Financial | General Ledger)

2. AA Dimensions with a type of Boolean, Numeric, or Date.

3. List of reserved attributes names:

Account Category
Audit Trail Code
Batch ID
Currency ID
Customer ID
Distribution Reference
Employee
Exchange Rate
Item ID
Journal Entry
Originating Audit Trail Code
Originating Document Number
Originating Master Record ID
Originating Master Record Name
Originating Transaction Type
Reference
Reporting Ledger
Site ID
Source Document
Transaction Date
Vendor ID
Voided
Series


Examples that will cause the error:

Example 1: If a User-Defined field is named “Reference”

Example 2: If a User-Defined field is named “Customer” and an AA Dimension (Boolean) exists with a name “Customer”.

The duplicated name must be changed in Microsoft Dynamics GP so that the name is unique across the 3 groups.
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: 2776705 – Last Review: November 5, 2012 – Revision: 1.0


Applies to
  • Microsoft Management Reporter 2012
  • Microsoft Dynamics GP 2010
  • Microsoft Dynamics GP 2010 R2
  • Microsoft Dynamics GP 2010 Service Pack 1
  • Microsoft Dynamics GP 2010 Service Pack 2
  • Microsoft Dynamics GP 2010 Service Pack 3
kbmbsmigrate kbsurveynew KB2776705

Excerpt from:
Data provider framework error in Microsoft Management Reporter 2012 for Dynamics GP 2010

"System Resource Exceeded" error message when you perform a query in Access 2010

Assume that you apply the hotfix package that is described in Knowledge Base (KB) article 2553447 to Access 2010. However, when you perform a complex query that applies to many records, you receive the following error message:
Note For more information about hotfix 2553447, click the following article number to view the article in the Microsoft Knowledge Base:
2553447

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

MS12-046: Description of the security update for Office 2010: July 10, 2012

To resolve this issue, apply the following update:
2760394

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

Description of the Access 2010 hotfix package (ace-x-none.msp): October 30, 2012

Registry key information

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

After you install the hotfix package, follow these steps to enable the hotfix:

  1. Click Start, click Run, type regedit in the Open box, and then click OK.
  2. Locate and then select the following registry subkey:

    HKEY_LOCAL_MACHINESOFTWAREMicrosoftOffice14.0Access Connectivity EngineEngines

  3. On the Edit menu, point to New, and then click DWORD (32-bit) Value.
  4. Type WorkingSetSleepValue, and then press Enter.
  5. In the Details pane, right-click WorkingSetSleepValue, and then click Modify.
  6. In the Value data box, type 1, and then click OK.
  7. Exit Registry Editor.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the “Applies to” section.

Article ID: 2726928 – Last Review: November 5, 2012 – Revision: 1.0

kbqfe kbsurveynew kbexpertisebeginner KB2726928

Continued here:
"System Resource Exceeded" error message when you perform a query in Access 2010

2007 Office system cumulative update for October 2012

The cumulative update packages for October 2012 contain the latest hotfixes for the 2007 Microsoft Office system and for 2007 Office servers.

We recommend that you test hotfixes before you deploy them in a production environment. Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous update package. We recommend that you consider applying the most recent fix release that contains the hotfix that you need.

How to obtain the October 2012 cumulative update packages

A set of supported cumulative update packages are now available from Microsoft. However, each package is intended to correct only the applications that are listed in this article. Apply the packages only to systems that are experiencing these specific problems. If you are not severely affected by any of these problems, we recommend that you wait for the next update package that contains the hotfixes in these cumulative update packages.

Note If additional issues occur or any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for a specific cumulative update package. To create a separate service request, visit the following Microsoft website:

Packages that are included in the October 2012 cumulative update

A link to a Microsoft Knowledge Base article that discusses each hotfix will be released as the article becomes available. To obtain a specific hotfix, please contact support and ask for the hotfix by referencing the Knowledge Base article number.

For more information about the 2007 Office system issues that are fixed in this cumulative update, click the following article numbers to view the articles in the Knowledge Base.

2007 Office system client updates

Collapse this tableExpand this table

Hotfix package name Knowledge Base article number Product
Xlconv-x-none.msp; Oartconv-x-none.msp; Oart-x-none.msp; Graph-x-none.msp; Excel-x-none.msp
2687605

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

Description of the Excel 2007 hotfix package (Xlconv-x-none.msp; Oartconv-x-none.msp; Oart-x-none.msp; Graph-x-none.msp; Excel-x-none.msp): October 30, 2012

Excel 2007
Xlconv-x-none.msp; Graph-x-none.msp; Excel-x-none.msp
2687538

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

Description of the Excel 2007 hotfix package (Xlconv-x-none.msp; Graph-x-none.msp; Excel-x-none.msp): October 30, 2012

Excel 2007
mso-x-none.msp
2760380

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

Description of the 2007 Office system hotfix package (mso-x-none.msp): October 30, 2012

2007 Office system
Oartconv-x-none.msp, Oart-x-none.msp
2687539

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

Description of the 2007 Office system hotfix package (Oartconv-x-none.msp, Oart-x-none.msp): October 30, 2012

2007 Office system
Ipeditor-x-none.msp
2760382

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

Description of the Office InfoPath 2007 hotfix package (Ipeditor-x-none.msp): October 30, 2012

Office InfoPath 2007
Outlook-x-none.msp
2687540

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

Description of the Outlook 2007 hotfix package (Outlook-x-none.msp): October 30, 2012

Outlook 2007
Pptconv-x-none.msp, Powerpoint-x-none.msp
2687542

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

Description of the PowerPoint 2007 hotfix package (Pptconv-x-none.msp, Powerpoint-x-none.msp): October 30, 2012

PowerPoint 2007
Wordconv-x-none.msp, Word-x-none.msp
2687537

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

Description of the Word 2007 hotfix package (Wordconv-x-none.msp, Word-x-none.msp): October 30, 2012

Word 2007

2007 Office server rollup update for Windows SharePoint Services (WSS) Servers

Collapse this tableExpand this table

Hotfix package name Knowledge Base article number Product
WSS server-package
2687535

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

Description of the Windows SharePoint Services 3.0 cumulative update server hotfix package (WSS server-package): October 30, 2012

Windows SharePoint Services 3.0

2007 Office individual server updates

Collapse this tableExpand this table

Hotfix package name Knowledge Base article number Product
Xlsrvapp-x-none.msp
2687531

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

Description of the Excel Services in SharePoint Server 2007 hotfix package (Xlsrvapp-x-none.msp): October 30, 2012

Excel Services in SharePoint Server 2007
Coreserver-x-none.msp
2760381

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

Description of the SharePoint Server 2007 hotfix package (Coreserver-x-none.msp): October 30, 2012

SharePoint Server 2007

Prerequisites

Prerequisites are listed in the KB articles for the individual packages.

Article ID: 2757116 – Last Review: November 5, 2012 – Revision: 1.0


Applies to
  • Microsoft Office Excel 2007
  • Microsoft Office Outlook 2007
  • Microsoft Office InfoPath 2007
  • Microsoft Office PowerPoint 2007
  • Microsoft Office Word 2007
  • Microsoft Office Basic 2007
  • Microsoft Office Home and Student 2007
  • Microsoft Office Standard 2007
  • Microsoft Office Enterprise 2007
  • Microsoft Office Project Server 2007
  • Microsoft Office SharePoint Server 2007
  • Excel Services in Microsoft Office SharePoint Server 2007
kbsurveynew kbexpertiseinter KB2757116

See the original post:
2007 Office system cumulative update for October 2012

Description of the Access 2010 hotfix package (ace-x-none.msp): October 30, 2012

This article describes the issue that is fixed in the Microsoft Access 2010 hotfix package that is dated November 2, 2012.

Issue that this hotfix package fixes

Assume that you apply the update that is described in Knowledge Base (KB) article 2553447 to Access 2010. In this situation, you receive the following error message when you perform a complex query that refers to many records:Note For more information about update 2553447, click the following article number to view the article in the Microsoft Knowledge Base:

2553447

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

MS12-046: Description of the security update for Office 2010: July 10, 2012

Hotfix information

A
supported hotfix is available from Microsoft. However, this hotfix is intended
to resolve only the problem that is described in this article. Apply this
hotfix only to systems that are experiencing the problem described in this
article. This hotfix might receive additional testing. Therefore, if you are
not severely affected by this problem, we recommend that you wait for the next
software update that contains this hotfix.

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

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

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

Prerequisites

To apply this hotfix package, you must have the Office 2010 Service Pack 1 (SP1) installed.

Restart requirement

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

Hotfix replacement information

This hotfix does not replace a previously released
hotfix.

Registry key information

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

After you install the hotfix package, follow these steps to enable the hotfix:

  1. Click Start, click Run, type regedit in the Open box, and then click OK.
  2. Locate and then select the following registry subkey:

    HKEY_LOCAL_MACHINESOFTWAREMicrosoftOffice14.0Access Connectivity EngineEngines

  3. On the Edit menu, point to New, and then click DWORD (32-bit) Value.
  4. Type WorkingSetSleepValue, and then press Enter.
  5. In the Details pane, right-click WorkingSetSleepValue, and then click Modify.
  6. In the Value data box, type 1, and then click OK.
  7. Exit Registry Editor.

File information

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

The
global version of this hotfix package uses a Microsoft Windows Installer
package to install the hotfix package. The dates and the times for these files
are listed in Coordinated Universal Time (UTC) in the following table. When you
view the file information, the date is converted to local time. To find the
difference between UTC and local time, use the Time Zone tab
in the Date and Time item in Control Panel.

x64

Download information

Collapse this tableExpand this table

File name File version File size Date Time
Office2010-kb2760394-fullfile-x64-glb.exe 14.0.6129.5000 2,774,096 21-Oct-12 5:36

Microsoft Windows Installer .msp file information

Collapse this tableExpand this table

File name File version File size Date Time
Ace-x-none.msp Not applicable 1,699,840 20-Oct-12 20:29

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

Collapse this tableExpand this table

File name File version File size Date Time
Acecore.dll 14.0.6129.5000 2,639,464 20-Oct-12 12:52
Aceexcl.dll 14.0.6129.5000 902,264 20-Oct-12 12:52
Acetxt.dll 14.0.6125.5000 298,128 28-Aug-12 17:53
Vbajet32.dll 6.0.1.1627 50,760 15-May-12 11:16

x86

Download information

Collapse this tableExpand this table

File name File version File size Date Time
Office2010-kb2760394-fullfile-x86-glb.exe 14.0.6129.5000 2,643,456 21-Oct-12 8:56

Microsoft Windows Installer .msp file information

Collapse this tableExpand this table

File name File version File size Date Time
Ace-x-none.msp Not applicable 1,581,568 20-Oct-12 20:25

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

Collapse this tableExpand this table

File name File version File size Date Time
Acecore.dll 14.0.6129.5000 2,195,560 20-Oct-12 12:52
Aceexcl.dll 14.0.6129.5000 647,288 20-Oct-12 12:52
Acetxt.dll 14.0.6125.5000 221,328 28-Aug-12 17:53
Vbajet32.dll 6.0.1.1627 50,248 15-May-12 11:17
For more information about
software update terminology, click the following article number to view the
article in the Microsoft Knowledge Base:
824684

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

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

Article ID: 2760394 – Last Review: November 5, 2012 – Revision: 1.0

kbqfe kbsurveynew kbexpertiseinter kbhotfixrollup kbhotfixserver kbautohotfix kbhotfixallversions KB2760394

Continue reading here:
Description of the Access 2010 hotfix package (ace-x-none.msp): October 30, 2012

Description of the Access 2010 hotfix package (Stislist-x-none.msp): October 30, 2012

This article describes the issues that are fixed in the Microsoft Access 2010 hotfix package that is dated October 30, 2012.

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problems that are described in this article. Apply this hotfix only to systems that are experiencing the problems described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

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

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

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

Prerequisites

To install this hotfix, you must have Access 2010 Service Pack 1 (SP1) installed.

Restart requirement

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

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

Registry information

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

File information

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

The global version of this hotfix package uses a Microsoft Windows Installer package to install the hotfix package. The dates and the times for these files are listed in Coordinated Universal Time (UTC) in the following table. When you view the file information, the date is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

x86 versions

Download information

Collapse this tableExpand this table

File name File version File size Date Time
Office2010-kb2760390-fullfile-x86-glb.exe 14.0.6129.5000 2,416,912 21-Oct-12 8:56

Microsoft Windows Installer .msp file information

Collapse this tableExpand this table

File name File version File size Date Time
Stslist-x-none.msp Not applicable 1,297,920 20-Oct-12 20:18

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

Stislist-x-none.msp file information

Collapse this tableExpand this table

File name File version File size Date Time
Stslist.dll 14.0.6129.5000 2,833,016 20-Oct-12 12:52

x64 versions

Download information

Collapse this tableExpand this table

File name File version File size Date Time
Office2010-kb2760390-fullfile-x64-glb.exe 14.0.6129.5000 2,686,056 21-Oct-12 5:36

Microsoft Windows Installer .msp file information

Collapse this tableExpand this table

File name File version File size Date Time
Stslist-x-none.msp Not applicable 1,554,432 20-Oct-12 20:22

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

Stislist-x-none.msp file information

Collapse this tableExpand this table

File name File version File size Date Time
Stslist.dll 14.0.6129.5000 3,913,336 20-Oct-12 12:56
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

824684

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

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

Article ID: 2760390 – Last Review: November 5, 2012 – Revision: 1.0

kbqfe kbsurveynew kbexpertiseinter kbhotfixserver kbhotfixrollup kbautohotfix kbhotfixallversions KB2760390

See the original post:
Description of the Access 2010 hotfix package (Stislist-x-none.msp): October 30, 2012

You receive a "One or more users need an assigned license in order to retain an Exchange Online mailbox or archive" message on the Users page of the Office 365 portal

When you view the Users page of the Office 365 portal in Microsoft Office 365, you receive the following message:

One or more users need an assigned license in order to retain an Exchange Online mailbox. Create a new view and select “Users with mailboxes and no licenses.” Select all users in the list, and then click “Edit” to assign licenses.

This occurs when the user mailboxes are created in the Exchange Control Panel, and the users are not yet assigned a license.
Create a view in the Office 365 portal to display a list of users who have mailboxes but who do not have a license. To do this, follow these steps:
  1. Sign in to the Office 365 portal.
  2. In the left navigation pane, under Management, click Users.
  3. On the Users page, click New view in the View drop-down list.
  4. On the “New view” page, follow these steps:
    1. In the Name your view box, type Users with no mailboxes and no licenses.
    2. Under Select an account status to further restrict the view, click to select the Users with mailboxes and no licenses check box.
    3. Click Save.
  5. On the Users page, click Users with mailboxes and no licenses in the View drop-down list to view the list of users who have mailboxes but who are not yet assigned a license.

Note To assign a license to a user, click to select the check box next to the name of the user, and then click Edit. On the “Assign licenses” page, click to select the check boxes next to the items that you want to assign, and then click Save.

Users must be assigned a license, or the mailbox is deleted. From the time that the user mailbox is created in Exchange Control Panel, administrators have 60 days to assign the user a license in the Office 365 portal.

Article ID: 2506570 – Last Review: November 5, 2012 – Revision: 11.0


Applies to
  • Microsoft Office 365 for enterprises
  • Microsoft Office 365 for small businesses
  • Microsoft Office 365 for education
  • Microsoft Exchange Online
vkbportal231 o365 vkbportal237 KB2506570

Visit site:
You receive a "One or more users need an assigned license in order to retain an Exchange Online mailbox or archive" message on the Users page of the Office 365 portal

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

Recent Comments

    Archives

    Categories