Hi,You must have read this thread:To detail the steps, please do as I describe:ImportantThis 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 theregistry before you modify it.
Bad Memory, invalid bits or physically bad memory. Bad computer memory is also a common cause for fatal exception errors. If you have recently added memory to the computer, it is recommended that it first be removed to verify that you are not experiencing conflicts with the recently installed memory.
Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry,To open the Registry Editor, please press Win + R, type regedit in the blank box, pressEnter. / Or we can type regedit.exe in Windows 8.1 Search, you'll find it easily.Now the Registry Editor is open.Then we see the pane on left, expand the following path:HKEYCURRENTUSERSoftwareMicrosoftWindowsCurrentVersionExplorerUser Shell FoldersThen we can see a list on right, find Cache, right click on it, clickModify., under Value data, change the value to something likeC:WindowsTemp, click OK.Exit Registry Editor.As for 'You might also right click on the file with file explorer, choose Properties, then General tab and click on the Unblock button.' Just find the file, right click on it, chooseProperties, under General tab, if you see aUnblock button, click on it.' Some of our customers found it sometimes a permission problem.cmd = dcomcnfg' Do the following:Press Win + R, type in cmd in the blank box, pressEnter.In the new black-background window, type in dcomcnfg, pressEnter.Then the Component Services window will pop up, on the left pane, expandComponent services - Computes -My Computer - Dcom config - and selectMicrosoft Excel Application, right click on it - Properties -Identity tab - Select The interactive user -OK.I hope I've explained the steps clearly.Good luck.Regards,Melon ChenTechNet Community Support. Hi,You must have read this thread:To detail the steps, please do as I describe:ImportantThis 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 theregistry 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,To open the Registry Editor, please press Win + R, type regedit in the blank box, pressEnter. / Or we can type regedit.exe in Windows 8.1 Search, you'll find it easily.Now the Registry Editor is open.Then we see the pane on left, expand the following path:HKEYCURRENTUSERSoftwareMicrosoftWindowsCurrentVersionExplorerUser Shell FoldersThen we can see a list on right, find Cache, right click on it, clickModify., under Value data, change the value to something likeC:WindowsTemp, click OK.Exit Registry Editor.As for 'You might also right click on the file with file explorer, choose Properties, then General tab and click on the Unblock button.' Just find the file, right click on it, chooseProperties, under General tab, if you see aUnblock button, click on it.' Some of our customers found it sometimes a permission problem.cmd = dcomcnfg' Do the following:Press Win + R, type in cmd in the blank box, pressEnter.In the new black-background window, type in dcomcnfg, pressEnter.Then the Component Services window will pop up, on the left pane, expandComponent services - Computes -My Computer - Dcom config - and selectMicrosoft Excel Application, right click on it - Properties -Identity tab - Select The interactive user -OK.I hope I've explained the steps clearly.Good luck.Regards,Melon ChenTechNet Community Support.
![Not Not](/uploads/1/2/5/5/125508301/574648577.jpg)
Changes in Product Update 1.Sage 300 ERP 2012 Product Update 1 Release NotesProduct Update 1 contains a modified version of one or more Sage 300 ERP program components. It is not a full upgrade or a product replacement. It is valid only until we release the next product update or the next version of Sage 300 ERP.
Updating ProgramsImportant! This product update contains database changes for Project and Job Costing. After installing the update, you will need to reactivate your data for this program for version 2012.Important!
This update includes changes to the Sage 300 ERP Portal. If you have installed the portal, the installation program will need to stop and restart Internet Information Services (IIS) and the Sage 300 ERP Tomcat service.Note: After installing this update, you should clear your browser’s cache. (Some fixes included in the update will not take effect until you do.) Upgrading to Later VersionsImportant!
If you upgrade to a later version of Sage 300 ERP, you must install all released product updates for that version before activating your data to avoid possible data corruption issues. Compatibility with Sage ProgramsSage 300 ERP is now compatible with Sage Fixed Assets 2013.For a complete list of compatible programs, database platforms, and operating systems, see the on the Sage Customer Portal.
SAP Crystal Reports® Runtime EngineAs described in the 2012 Release Notes, reports in the Sage 300 ERP Desktop are now printed using the SAP Crystal Reports® runtime engine for.NET Framework 4, which is installed with Sage 300 ERP. Potential issues when reporting via macros. The COM API for SAP Crystal Reports® is no longer supported by SAP, and is not included in the SAP Crystal Reports® runtime engine for.NET Framework 4, which is installed with Sage 300 ERP. ( SAP Crystal Reports® now supports only.NET and Java interfaces.)If you use any macros that write to the SAP Crystal Reports® COM API, you must modify these programs to use the.NET interface or the Sage 300 ERP COM API.
![Enough Enough](http://www.agiletechbusiness.com/wp-content/uploads/2017/09/Unable-to-Determine-Security-Privileges.jpg)
For developer documentation on using the Sage 300 ERP COM API, visit the Sage 300 ERP Development Partner Wiki at. For more information about reporting via macros, including a sample macro to print O/E quotes, see. Slower performance when printing reports. We are continuing to work with SAP to resolve the issue of slower performance when printing reports using the updated SAP Crystal Reports® runtime engine for.NET Framework 4.
The previous version of the runtime engine is no longer supported by SAP, so this change is required to ensure continued support for all reporting features.Errors and Omissions in Release DocumentationSage makes every effort to provide accurate product documentation, and we apologize for any inconvenience caused by the following errors and omissions in the release documentation for Sage 300 ERP 2012. In the 2012 Release Notes, we neglected to mention that if you use Pervasive PSQL, Sage 300 ERP 2012 only supports Pervasive PSQL version 11.2 and later. Older versions of Pervasive PSQL (version 11.0 and earlier) are not supported.
To learn more about supported platforms and system requirements for Sage 300 ERP 2012, please review the. In the 2012 Release Notes, we noted that reports in the Sage 300 ERP Desktop are now printed using the SAP Crystal Reports® runtime engine for.NET Framework 4, which is installed with Sage 300 ERP. The text that followed this note implied that you require the 2011 version of SAP Crystal Reports® to create and customize reports and forms for Sage 300 ERP. This is not the case. Note:. This feature is available only in programs created using the Sage 300 ERP Software Development Kit (SDK).
If you use Options products ( Ops Inquiry and Sales Analysis), Number Changers, or other integrated programs that were not created using the Sage 300 ERP SDK, company colors will not appear in screens for those programs. This feature is available for web-deployed systems.
However, before you can view company colors on a workstation using an existing web-deployed system, you must install the new Sage 300 ERP.NET library from Webcabs, and then delete all files matching a4w. from C:WindowsDownloaded Program Files. Note:. To use the new inventory item lookup feature, you must install the new version of Sage 300 ERP Integration for Sage CRM (the Sage CRM-side integration component) included with this product update. For more information, see 'Upgrading Sage CRM 7.1 Integrated with Sage 300 ERP 2012 to Support Sage 300 ERP Product Update 1' in the Sage CRM Integration Upgrade Guide. The Item Inventory button appears on the Company Summary screen only if a company is a Sage 300 ERP customer. It does not appear when viewing other company types such as vendors, or when viewing non-integrated companies.Before you can create a new quote or new order for an item from the Sage CRM Item Inventory screen, default values must be specified in Sage 300 ERP for the following O/E Order Entry fields:.
Price List. Location. Any automatically inserted optional fields (if you use Transaction Analysis and Optional Field Creator)For more information, see the Sage CRM Integration Guide.Sage 300 ERP SDKThe AccpacReport COM object now supports exporting reports to Microsoft Excel.xls and.xlsx formats. For more information, see the and.Product Update 1 Program FixesThe following sections describe program fixes included in Product Update 1. System Manager.
Restored the ability to select an export format and destination after clicking the Export button in the print preview window for a report. (This feature was available in previous versions, but was not available in the 2012 release due to changes in the SAP Crystal Reports® runtime engine for.NET Framework 4, which is installed with Sage 300 ERP 2012.)In the 2012 release, clicking the Export button opened a Save As window, which allowed you to save the exported report as a file. Now, clicking the Export button opens an Export window, which you can use to select a format and destination for the exported report. Available destinations are Application, Disk File, and Microsoft Mail. Available formats include Microsoft Excel and Word (multiple formats), plus PDF, HTML, XML, CSV, RTF, TTX, and TXT.For more information, see Knowledgebase article 2. Fixed a problem that prevented printing certain reports to a printer. When you tried to print a report that required you to enter report parameters, the parameter screen did not appear if the print destination was set to Printer.Changes to the SAP Crystal Reports®.NET SDK prevented the parameter screen from appearing.
Now, a new parameter screen appears when print destination is set to Printer. For more information, see Knowledgebase article 2.
Fixed a problem that caused the License Manager to incorrectly display Unauthorized as the status for some licenses. When activating licenses with a seven-digit Client ID, the Status column on the Licenses tab incorrectly displayed Unauthorized instead of Current. For more information, see Knowledgebase article 2. Fixed a problem that caused third-party programs created using the XAPI to consume an additional LanPak license. When the problem occurred, the LanPak Users screen incorrectly displayed an additional current user, even if the program signed in with the user ID of a user who had already signed in to Sage 300 ERP.
For more information, see Knowledgebase article 2. Fixed a problem that could prevent you from starting third-party programs created using the XAPI. The problem occurred if you tried to open multiple companies with the program. Even if you had enough IAP licenses, the program displayed the error message: “there are no IAP Licenses left at this time.” For more information, see Knowledgebase article 2.Bank Services. Fixed a problem that could cause the Reconcile Statements Summary to be out of balance. Previously, you could use the Reverse Transactions screen to select and reverse a bank entry that was reconciled and cleared. Now, you cannot select a bank entry on the Reverse Transactions screen if it has been cleared.
To reverse the bank entry, you must first use the Reconcile Statements screen to change its status to Outstanding.Accounts Payable. Fixed a problem that could occur when using the A/P Print Checks screen to print checks. If you selected a large number of checks, a 'UI container' error message appeared when printing or previewing, and the program stopped responding. For more information, see Knowledgebase article 2.Accounts Receivable. Fixed a problem that could cause inquiry screens to stop responding. The problem occurred only if you tried to use a custom screen to open the Customer Inquiry screen or the Document Inquiry screen multiple times.
Improved the performance of the A/R Statements/Letters/Labels screen. When reprinting A/R statements, the program now produces the report faster. Fixed a problem that allowed users to enter a negative miscellaneous receipt amount on the A/R Receipt Entry screen, which created an incorrect balance in Bank Services. For more information, see Knowledgebase article 2. Fixed a problem that could cause the A/R Customer Inquiry screen or A/R Document Inquiry screen to stop responding. The problem occurred if you opened these screens from a screen developed by a third-party. For more information, see Knowledgebase article 2 or 210-32204.General Ledger.
Fixed a problem that could cause information to be excluded incorrectly from the posting journals report. If a posting sequence included any entries to which you did not have access, the whole posting sequence was excluded from the report. For more information, see Knowledgebase article 2.Inventory Control.
Fixed a performance issue that occurred when using the I/C Update Item Pricing screen to update item pricing for databases with large numbers of items. Previously, if you selected Item Number on the Select by list, the program searched all item records within the range of price list codes you specified, regardless of the range of item numbers you specified. Now, the program only searches and updates item pricing for records within the range of price list codes and item numbers you specify. For more information, see Knowledgebase article 2.
Fixed a problem that occurred after deleting an inactive Bill of Material (BOM). When printing the I/C Item Valuation report, the deleted BOM appeared in the report, and displayed the item number and description from the item listed above it in the report. Fixed a problem that caused an 'Error Code 5' error message to appear when trying to open Inventory Control reports. If you used the UI Profile Maintenance screen to create a custom profile ID for the I/C Stock Transactions Report, users to whom you assigned this profile ID received the error message when opening other Inventory Control reports. For more information, see Knowledgebase article 2. Fixed a problem that could cause a 'Fractional quantities are not allowed' error message to appear when generating an inventory worksheet.
Important!. To implement the program fixes described in this section, you must install the new version of Sage 300 ERP Integration for Sage CRM (the Sage CRM-side integration component) included with this product update. For more information, see 'Upgrading Sage CRM 7.1 Integrated with Sage 300 ERP 2012 to Support Sage 300 ERP Product Update 1' in the Sage CRM Integration Upgrade Guide. If you have installed Sage CRM and Sage 300 ERP on separate servers, see 'Setting up Sage CRM and Sage 300 ERP on Separate Servers' in Chapter 4 of the Sage CRM Integration Guide for important information about changes to server configuration. You must follow the revised integration procedures described in this section to enable multi-browser support in a two-server setup.The following program fixes for Sage CRM are included with this product update:.
Fixed a problem that could cause performance issues in Sage CRM, and in some cases, caused error messages to appear, or caused the program to stop responding. The problem occurred because the integrated Quotes and Orders pages in Sage CRM reused session IDs for multiple processes. Now, the integrated pages use IIS to generate unique session IDs. For more information, see Knowledgebase article 2. Fixed a problem that allowed a Sage CRM user to delete an opportunity in Sage CRM for which there are outstanding amounts in Sage 300 ERP. Now, if there are outstanding amounts for an opportunity, an error message appears when a Sage CRM user attempts to delete the opportunity. For more information, see Knowledgebase article 2.
If Sage CRM and Sage 300 ERP are installed on separate servers, the integrated Quotes and Orders screens are now supported in Internet Explorer, Firefox, Chrome, and Safari. For more information, see Knowledgebase article 2. Improved performance when promoting a customer to Sage 300 ERP, if your Sage 300 ERP database includes a large number of O/E transactions (shipments, invoices, credit notes, or debit notes). For more information, see Knowledgebase article 2.Ops Inquiry. Fixed a problem that prevented Ops Inquiry from saving changes to column order on the Stock Card-Detail tab of the IC Item Inquiry screen.
For more information, see Knowledgebase article 2. Fixed a problem on the I/C Item Inquiry screen that could cause incorrect information to appear in the Total Quantity and Total Available fields.
The problem occurred when viewing an item for which there was inventory at more than 20 locations. For more information, see Knowledgebase article 2.Sales Analysis. Fixed a problem that prevented Sales Analysis screens from appearing if the Client ID on the Sales Analysis license was greater than. For more information, see Knowledgebase article 2.Account Code Change. Fixed a problem that caused the following error message to appear when combining allocation accounts:'G/L Acct Alloc Instructions: Internal Error: field number is out of range.' Note: After combining allocation accounts, Account Code Change does not automatically update the percent allocated to the account. To set allocation to 100%, open the G/L Accounts screen, and on the Allocation tab, change the amount(s) in the Percent column so that the Total Percent field displays 100.For more information, see Knowledgebase article 2.