Microsoft Support

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

You experience decreased report performance in Microsoft FRx

When you use Microsoft Business Solutions – FRx, you experience decreased report performance.
This problem may occur because you are not using indexes for the Microsoft Business Solutions – Great Plains tables on a computer that is running Microsoft SQL Server. This problem may also occur because the duplex settings on the network adapters are incorrect.
To resolve this problem, follow these steps:
  1. Verify that you are using indexes for the Microsoft Great Plains tables on the computer that is running SQL Server:
    1. Click Start, point to All Programs, point to Microsoft SQL Server, and then click Enterprise Manager.
    2. Double-click Microsoft SQL Servers, double-click SQL Server Group, double-click Databases, double-click the name of the company database, and then double-click Tables.
    3. Locate the GL00100 table in the list of tables.
    4. Right-click GL00100, select All Tasks, and then click Manage Indexes.
    5. In the Manage Indexes dialog box, verify that the indexes exist. You will need the indexes for SQL Server to perform optimally with Microsoft FRx.
  2. Verify the duplex settings on the network adapters:
    1. Click Start, click Control Panel, double-click Administrative Tools, double-click Computer Management, and then click Device Manager.
    2. Double-click Network adapters, right-click the name of the network adapter, and then click Properties.
    3. Click the Advanced tab, and then select Duplex.
    4. Verify the selection in the Value box. If Auto is selected, you must adjust the setting to match the network bandwidth.
    5. Click OK.

Article ID: 912970 – Last Review: January 17, 2015 – Revision: 3.0


Applies to
  • Microsoft Business Solutions for Analytics–FRx 6.7 Desktop
  • Microsoft Dynamics GP 9.0
  • Microsoft Business Solutions–Great Plains 8.0
  • Microsoft Business Solutions–Great Plains 7.5, when used with:
    • Microsoft Business Solutions for Analytics–FRx 6.7 Desktop
kbnosurvey kbarchive kbgreatplainsfrx kbmbsmigrate kbprb KB912970

Continue reading here:
You experience decreased report performance in Microsoft FRx

Error message when you print an edit list in Sales Order Processing in Microsoft Dynamics GP: "Distribution accounts are missing or invalid"

When you print an edit list in Sales Order Processing in Microsoft Dynamics GP or in Microsoft Business Solutions – Great Plains, you receive the following error message:

Distribution accounts are missing or invalid.

This problem occurs because the distribution account is missing on the line item detail.
To resolve this problem, update the table to include the distribution account.

To do this, follow these steps:

  1. Have all users exit Microsoft Dynamics GP.
  2. In SQL Query Analyzer, run the following statement against the company database.
    UPDATE SOP10200 SET XXX = YYY WHERE SOPNUMBE=ZZZ

    Notes

    • Replace XXX with one of the following field names for the index field:
      • INVINDX
      • CSLSINDX
      • SLSINDX
      • MKDNINDX
      • RTNSINDX
      • INUSINDX
      • INSRINDX
      • DMGDINDX
    • Replace YYY with the account index number in the GL00100 table.
    • Replace
      ZZZ with the invoice document number.

Article ID: 859406 – Last Review: January 17, 2015 – Revision: 4.0


Applies to
  • Microsoft Dynamics GP 2010
  • Sales Order Processing
kbnosurvey kbarchive kberrmsg kbexpertisebeginner kbtshoot kbprb kbexpertiseinter kbmbsmigrate KB859406

See original article:
Error message when you print an edit list in Sales Order Processing in Microsoft Dynamics GP: "Distribution accounts are missing or invalid"

Error 9060 when emailing Excel files to multiple users

Issue Summary:

Error 9060 when emailing Excel files to multiple users

Issue Detail:

Quality Report Description:

When email reports to Excel and using email addresses in the tree, you will get an error 9060, Error in FRxXML Module during ParseXML procedure. The error will occur depending on where in the tree the email address is. If it is placed on a unit in the middle of the tree, the error occurs.

Reported in Version: 6.5.184

Steps to Recreate:

1. Create a row and column layout.

2. Create a tree layout by going to Edit | Add Reporting Units.

3. Place an email address on a unit in the middle of the tree.

4. Create a catalog using the about layouts.

5. Set the output to Excel 5 or above (via OLE).

6. Enable email and mark to Use Tree.

7. Generate the report.

Expected Results:

The report will send an email to the recipient listed in the tree.

Actual Results:

Error 9060, Error in FRxXML Module during ParseXML procedure.

Workaround:

If all the units in the tree have an email address, the report will generate. However, if you enter multiple email addresses on one unit, you will get the 9060 error message.

You can also put an email address on the first unit or the last unit and it will work.
You can also put the email address on the first or last unit and then add to units consecutively and the report will generate.

Status of Resolution:

This problem report has been corrected with service pack 6 (FRx 6.5.199).

This article was TechKnowledge Document ID: 5207

Article ID: 865164 – Last Review: January 17, 2015 – Revision: 3.0


Applies to
  • FRx Financial Reporter 6.5
  • Microsoft Business Solutions–Great Plains 7.5
  • Microsoft Dynamics AX 3.0
kbnosurvey kbarchive kbSolomonFRx kbSmallBusinessFinancialsFRx kbGreatPlainsFRx kbAxaptaFRx kbMBSMigrate KB865164

Excerpt from:
Error 9060 when emailing Excel files to multiple users

"Object does not support this property or method: Hcalc32.Reset" in FRx Forecaster

SYMPTOMS

“Object does not support this property or method: Hcalc32.Reset.” occurs on Windows NT and 2000 machines after being asked to auto-download in FRx Forecaster.

CAUSE

FRx Forecaster components are not installed or there is a newer version of the Hcalc control available.

RESOLUTION


Close your Internet Explorer browser, and then re-open it.

1. If the Error on Page still exists, on the Tools menu, click Internet Options. Select the General tab, click the Settings button, and then click the View Objects button. If the Hcalc32 control exists, then right-click on it and select Update.

2. If the error still persists, open Windows Explorer. Search for all instances of Hcalc32.ocx and delete the files.

3. Log into FRx Forecaster and you will be prompted to auto-download. Select Yes. Close the browser and re-open it.

This article was TechKnowledge Document ID: 31339

Article ID: 860231 – Last Review: January 17, 2015 – Revision: 4.0


Applies to
  • Microsoft Business Solutions for AnalyticsForecaster 6.7
  • Microsoft Dynamics GP 9.0
  • Microsoft Business Solutions–Great Plains 8.0
  • Microsoft Business Solutions–Great Plains 7.5
  • Microsoft Business Solutions–Solomon 6.0
  • Microsoft Dynamics AX 3.0
kbnosurvey kbarchive kbsolomonfrx kbgreatplainsfrx kbaxaptafrx kbmbsmigrate KB860231

See original article:
"Object does not support this property or method: Hcalc32.Reset" in FRx Forecaster

How to Import and Export a Row, Column, Tree or Catalog in FRx to restore a single damaged Row, Column, Tree or Catalog

SUMMARY

This article describes how to Import and Export a Row, Column, Tree or Catalog in FRx to restore a single damaged Row, Column, Tree or Catalog without restoring everything.

MORE INFORMATION

To restore a damaged Row Format in FRx without restoring everything, follow these steps:

1. Make a backup of your SYSDATA folder.

2. Identify the Specification Set that contains the Row Format, and the *.f32 file that contains the Specification Set. (Ex. Row Format INCSTMT is in DYNDEMO Specification Set.)

3. Right-click the *.f32 file in the SYSDATA folder that contains the Specification Set, click Rename, and then type a new name. (Ex. DYNDEMO Specification Set is in FRXRPTS.f32.)

4. Right-click the same *.f32 file from the Backup SYSDATA folder, click Copy, click the existing SYSDATA folder (not the backup), right-click and then click Paste to copy the Backup *.f32 file.

5. Start FRx and click Company, and then click Specification Sets.

6. Select the Specification Set that contains the Row Format, and then click Export.

7. In the Export Selection window, click the Row tab, select the Row Format, and then click Export.

8. In the Create Export File window, accept the default of FRXEXP.tdb and then click OK. This will create a temporary database file containing the Row Format you have chosen. It will be located in the IO_Data folder as the default.

9. Exit FRx. Right-click the current *.f32 file in the SYSDATA folder, click Rename, and then type the new name. Right click the .f32 file from Step 3, click Rename and type the original name of this .f32 file (rename it back to its original name).

10. Start FRx. Click the affected Row Format, click save, and then type a new name to save it with a new name. Click File, click Delete, click Row, and then select the affected Row Format to delete it with the old name.

11. Click Company, click Specification Sets, select the Specification Set that contained the Row Format, and then click Import.

12. In the Select Import File window, accept the default of FRXEXP.tdb, and then click OK. FRx will import the Row Format into the Specification Set. These steps apply to any Row, Column, Tree, or Catalog in the Specification Set.

This article was TechKnowledge Document ID: 5760

Article ID: 865606 – Last Review: January 17, 2015 – Revision: 3.0


Applies to
  • Microsoft Business Solutions for Analytics–FRx 6.7 Desktop
  • Microsoft Dynamics GP 9.0
  • Microsoft Business Solutions–Great Plains 8.0
  • Microsoft Business Solutions–Great Plains 7.5
  • Microsoft Dynamics SL 6.5
  • Microsoft Business Solutions–Solomon 6.0
  • Microsoft Dynamics AX 4.0
  • Microsoft Dynamics AX 3.0
  • Microsoft Dynamics NAV 4.0
  • Microsoft Business Solutions–Navision 3.70
  • FRx Financial Reporter 6.5
kbnosurvey kbarchive kbnavisionfrx kbsolomonfrx kbsmallbusinessfinancialsfrx kbgreatplainsfrx kbaxaptafrx kbmbsmigrate KB865606

More here:
How to Import and Export a Row, Column, Tree or Catalog in FRx to restore a single damaged Row, Column, Tree or Catalog

Error message when you try to import a customization to another Microsoft Dynamics CRM 4.0 server: "Invalid name prefix"

Consider the following scenario. You upgrade an installation of Microsoft Dynamics CRM 3.0 that has Update Rollup 2 to Microsoft Dynamics CRM 4.0. Then, you export a customization from this upgraded Microsoft Dynamics CRM 4.0 server. Next, you try to import the customization to another Microsoft Dynamics CRM 4.0 server. In this scenario, you receive the following error message:
This problem is fixed in the latest cumulative update rollup for Microsoft Dynamics CRM 4.0. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

949256

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

Microsoft Dynamics CRM 4.0 updates and hotfixes

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the “Applies to” section.
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684

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

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

For more information about Microsoft Dynamics CRM software hotfix and update package terminology, click the following article number to view the article in the Microsoft Knowledge Base:

887283

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

Microsoft Business Solutions CRM software hotfix and update package naming standards

Article ID: 951909 – Last Review: January 17, 2015 – Revision: 3.0


Applies to
  • Microsoft Dynamics CRM 4.0
kbnosurvey kbarchive kberrmsg kbfix kbautohotfix kbexpertiseinter kbsurveynew kbmbsmigrate kbqfe kbhotfixserver KB951909

See the original post:
Error message when you try to import a customization to another Microsoft Dynamics CRM 4.0 server: "Invalid name prefix"

Event IDs 8239 and 8206 are logged when you schedule and then cancel a meeting in Communicator 2007

You use Microsoft Office Communicator 2007 and Microsoft Exchange Server 2003. You schedule a meeting and then cancel the meeting in Communicator 2007. When you do this, the following events may be logged in the Exchange Server 2003 event log:

Event ID : 8239

Category : General

Source : EXCDO

Type : Error

Message : An appointment with the subject “” was saved to mailbox mailbox_address. The start time is missing, so the calendaring agent cannot publish the free/busy information for this appointment. To correct this, please delete the appointment and recreate it.

Event ID : 8206

Category : General

Source : EXCDO

Type : Error

Message : Calendaring agent failed with error code 0x8004010f while saving appointment.

To resolve this problem, install update 951662.

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

951662

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

Description of the update for Communicator 2007: April 30, 2008

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

Article ID: 951870 – Last Review: January 17, 2015 – Revision: 2.0


Applies to
  • Microsoft Office Communicator 2007
kbnosurvey kbarchive kboffice2007presp2fix kbprb kbqfe kbexpertiseinter kbfix KB951870

More:
Event IDs 8239 and 8206 are logged when you schedule and then cancel a meeting in Communicator 2007

You are looped in the sign-in page when you try to run the Data Migration Manager Wizard in Microsoft Dynamics CRM 4.0

Process:Microsoft.Crm.Tools.DMWizard |Organization:00000000-0000-0000-0000-000000000000 |Thread: 3 |Category: Exception |User: 00000000-0000-0000-0000-000000000000 |Level: Error | CrmException..ctor

at CrmException..ctor(String message, Exception innerException, Int32 errorCode, Boolean isFlowControlException, Boolean enableTrace)

at CrmException..ctor(String message, Exception innerException, Int32 errorCode, Boolean isFlowControlException)

at CrmException..ctor(String message, Int32 errorCode)

at LocalizedLabelService.CheckForPossibleDuplicates(MetadataBusinessEntity metadataEntity, ISqlExecutionContext sqlContext)

at LocalizedLabelService.ValidateForCreate(MetadataBusinessEntity metadataEntity, ISqlExecutionContext context)

at MetadataProcessObject.Create(MetadataBusinessEntity metadataEntity, ISqlExecutionContext sqlContext, OperationContext operationContext)

at LocalizedLabelCreateAction.MetabaseOperation()

at EntityCreateAction.MetabaseOperation()

at MetadataHelper.ProcessQueue()

at DiffBuilder.PropagateChangesToClient()

at SyncData.DoSchemaChanges()

at SyncData.Sync(ITransferDataProvider transferDataProvider, Int32 callPriority)

at SyncData.Sync(ITransferDataProvider transferDataProvider)

at InitClass.SyncDMW()

at InitClass.DoInit(Object sender, DoWorkEventArgs dwe)

at BackgroundWorker.OnDoWork(DoWorkEventArgs e)

at BackgroundWorker.WorkerThreadStart(Object argument)

at StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)

at StackBuilderSink.PrivateProcessMessage(RuntimeMethodHandle md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)

at StackBuilderSink.AsyncProcessMessage(IMessage msg, IMessageSink replySink)

at AgileAsyncWorkerItem.ThreadPoolCallBack(Object o)

at _ThreadPoolWaitCallback.WaitCallback_Context(Object state)

at ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)

at _ThreadPoolWaitCallback.PerformWaitCallback(Object state)

>Crm Exception: Message: Entity with id dc6574cb-92ce-446c-a5d6-885a75107d52 already has the label Lead for column LocalizedName and language 1033 – update entity with id 21ea87ab-98ef-dc11-a41b-000d56f1ca2d cannot have the same label, ErrorCode: -2147192815

Continue Reading:
You are looped in the sign-in page when you try to run the Data Migration Manager Wizard in Microsoft Dynamics CRM 4.0

How to use multiple string formats in a scrolling window by using Dexterity in Microsoft Dynamics GP

When you use Dexterity in Microsoft Dynamics GP and in Microsoft Business Solutions – Great Plains, you can assign more than one FormatString property to a string format. Then, you can use an integer field that is linked to the string field by using the Link Format Selector tool while you work on a window layout. When you change the value of the integer field, you can select the different FormatString properties.

This feature does not work when the string field and the linked integer field are in a scrolling window. This is a known issue. This issue is documented in Microsoft Knowledge Base article 869310.
For more information, see the “References” section. This article describes how to use multiple string formats in a scrolling window by using Dexterity in Microsoft Dynamics GP and in Microsoft Business Solutions – Great Plains.

As a workaround to Microsoft Knowledge Base article 869310, you can produce a very similar result so that the string field is formatted correctly in the scrolling window. To do this, follow these steps and use the example code:
  1. Create a new local string field of a keyable length that is large enough to fit the longest format.

  2. Put this local string field in the scrolling window, and then hide the original string field.
  3. Create a series of messages that have an ID that is larger than 22,000 and that contains the formats in the same order as they are listed in the format string list. If you begin at message 22,201, the base number will be 22,200.
  4. Create a Format_String function that resembles the following.
    	function returns string OUT_String;
    	in string IN_String;
    	in string IN_Format;
    
    	local integer i, j;
    	local string l_string;
    
    	clear l_string, j;
    	for i = 1 to length(IN_Format) do
    		if substring(IN_Format,i,1) = CH_X then
    			increment j;
    			l_string = l_string + substring(IN_String,j,1);
    		else
    			l_string = l_string + substring(IN_Format,i,1);
    		end if;
    	end for;
    	OUT_String = l_string;

  5. In the Scrolling Window Fill script, set the local string field by using the Format_String function.
    	'(L) Dummy String' of window Scrolling_Window =
    		Format_String('String' from table Table, getmsg(Base + 'Format' from table Table);
    

    Note You must use the fields from the table buffer because the window fields are populated after the fill script is completed.

    This will format the local string field as if the multiple formats were working.

    If the local string field must be editable, you can use the field PRE script and the POST script to strip out the format, and then add it back later. This would make the local string field behave in a similar manner to how date fields work.

For more information about format fields for strings in scrolling windows, click the following article number to view the article in the Microsoft Knowledge Base:

869310

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

Can’t link format fields for strings in scrolling windows

Article ID: 949623 – Last Review: January 17, 2015 – Revision: 4.0


Applies to
  • Microsoft Dynamics GP 10.0
  • Microsoft Dynamics GP 9.0
  • Microsoft Business Solutions–Great Plains 8.0
  • Dexterity
kbnosurvey kbarchive kbexpertiseadvanced kbexpertisebeginner kbmbsmigrate kbhowto kbexpertiseinter KB949623

Link:
How to use multiple string formats in a scrolling window by using Dexterity in Microsoft Dynamics GP

Error message when you try to upgrade an existing organization from Microsoft Dynamics CRM 3.0 to Microsoft Dynamics CRM 4.0: "Action Microsoft.Crm.Setup.Server.CreateCrmGroupsAction failed. General access denied error"

Consider the following scenario. You install Microsoft Dynamics CRM 4.0. The user account that you use to install Microsoft Dynamics CRM 4.0 does not have Create rights in the organizational unit (OU) in the Active Directory directory service. When you run the Environment Diagnostics Wizard, no error occurs. You try to upgrade an existing organization from Microsoft Dynamics CRM 3.0 to Microsoft Dynamics CRM 4.0. In this scenario, you receive the following error message:

Action Microsoft.Crm.Setup.Server.CreateCrmGroupsAction failed.
General access denied error.

This problem occurs because the Microsoft Dynamics CRM upgrade code performs a check against the PrivUserGroup group and against the UserGroup Active Directory group. However, the code does not perform a check against the existing OU to verify that you have the rights to create groups in the OU.
When you upgrade an organization, the upgrade process has to create new groups for Microsoft Dynamics CRM 4.0. However, you do not have the Create right to create the groups.
This problem is fixed in the latest cumulative update rollup for Microsoft Dynamics CRM 4.0. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

949256

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

Microsoft Dynamics CRM 4.0 updates and hotfixes

Article ID: 949598 – Last Review: January 17, 2015 – Revision: 3.0


Applies to
  • Microsoft Dynamics CRM 4.0
kbnosurvey kbarchive kbexpertiseinter kberrmsg kbfix kbmbsupgrade kbmbsadministration kbmbsmigrate kbqfe kbHotfixServer KB949598

Read More:
Error message when you try to upgrade an existing organization from Microsoft Dynamics CRM 3.0 to Microsoft Dynamics CRM 4.0: "Action Microsoft.Crm.Setup.Server.CreateCrmGroupsAction failed. General access denied error"

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

Recent Comments

    Archives

    Categories