When trying to send a file attachment using Hotmail, my partner ran into an issue. She was reporting that the email would stop responding and closing the email would report "Attachment Id has bad format".
The problem was due to the fact that the file name had spaces. I renamed my attachment from "my file.docx" to be "myfile.docx" and it was fine
In the UK company car owners are being hit by the HRMC for back tax for incorrect or late company submissons. In addition to have a large company car to impress is no longer an option if the car is a "fuel guzzler". When deciding on your company car please consider the CO2 emissions first followed by the Car Value. Both are factors taken into consideration and can save you paying excessive tax each month.
Problems encountered with Dynamics GP Workflow meant that I had to rebuild the product and in the end uninstalling and then reinstalling. The problem with the rebuild or uninstall of the product was that we receive the error:
“The remote server returned an error (503) server unavailable”.
To get round this I manually uninstalled the product however I received the same issue when I began to install it again.
Cause The issue was down to a registry entry that was point to a different Security Admin Service.
HKLM\SOFTWARE\Microsoft\Business Solutions\Workflow for Dynamics GP\1033\SETUP\
Resolution Manually removed Dynamics GP workflow and cleaning up the registry especially removing the above key
Manually removing Dynamics GP Workflow
1. Verify the Dynamics GP Workflow 10.0 record in the WSInstallStatus table is removed by running the follow SQL command in SQL Management Studio:
select * from DYNAMICS..WSInstallStatus where InstallStep = ‘350DF9B1-F1A1-4859-BBD3-776021116F69’
2. Search the Windows Registry on the server to make sure there isn't any mention of 'Workflow for Microsoft Dynamics GP', 'Workflow for Microsoft Dynamics GP 10.0' or 'Workflow'. Also remove the registry key:
HKLM\SOFTWARE\Microsoft\Business Solutions\Workflow for Dynamics GP\1033\SETUP\
IMPORTANT: Please ensure that you do not remove reference to other products (sharepoint and office) who may be reference the word Workflow. The blog author can not be held responsible for any damage caused by editing the registry directly. 3. If the Dynamics GP Workflow 10.0 site is still available, please run these command from the sharepoint program filder and verify they are successful:
4. Remove the web application through SharePoint that Dynamics GP Workflow 10.0 was installed onto, marking the option to remove the web site in IIS Manager and the content database in SQL Server. Run an IISRESET to complete the changes.
Dynamics GP Workflow New Install
1. Create a new web application in SharePoint again to install Dynamics GP Workflow onto. No need to create a site collection as the Workflow install will create the relevant /sites/DynamicsGPWorkflow site collection.
Management Reporter 2.0 (1664.19) A consolidation report was not working for a report that contained a tree which held three companies. When the report was run the report, it only brought data back for only two companies.
The Account Format in Dynamics GP although were correctly setup the labels were different. We saw the following in the three companies effected.
Company 1 (CMP - NOMINAL - SUB) Company 2 (CMP - NOMINAL - SUB) Company 3 (SEGMENT1 - SEGMENT2 - SEGMENT3)
By changing the labels for the account segment for company 3, we were able to extract data for all companies.
Management Reporter 2.0 (1664.19) In the row setup for a report a number format mask was applied to a line which was dividing one row with another. As a result of generating the report, the percentage did not appear to calculate correctly.
The column number format mask was overriding the number format mask on the row. To correct the issue we removed the number format mask on the column and this allowed the row number format mask to work
When installing Dynamics GP 2010 on a SQL Server the end collation will be based on the Regional Settings that your server is running under.
English (United Kingdom) - Latin1_General_CI_AS English (United States) - SQL_Latin1_General_CP1_CI_AS Both are supported to use as Sort Order 52 for Microsoft Dynamics GP 2010. However you can run a SQL_Latin1_General_CP1_CI_AS company database on a server running Latin1_General_CI_AS
Issue occurred with Requisition Manager. No one could convert approved Requisitions to Purchase Orders in Microsoft Dynamics GP 2010. It reported the following error
The specified Protocol is invalid
The issue was due to a missing Web.config in out installation directory where Business Portal 5.1 had been installed. To correct confirm the precise version of Business Portal and log a call with Microsoft Support. They will send you the web.config for your version.
We received the following error when accessing Purchase Center page after migrtating from Business Portal 3 to 5.1
An unexpected error has occurred. Correlation ID: 8ef07403-e7af-4527-bf2c-ecb5929afbab
The error gave me nothing to go on. However the following steps allowed me to dig deeper and make sense of the issue
Please do the following steps below to get a more descriptive error message:
1. Determine the home directory of your Business Portal site.
a. Open IIS and locate the virtual server hosting your Business Portal site b. Right click on the virtual server and select Properties c. Click the Home Directory tab and note the Local Path file location
2. Browse the directory and locate the web.config file
3. Make a backup of this file
4. Open the file and make the following changes.
Find: CallStack="false" and Change to: CallStack="true"
Find: CustomErrors mode="RemoteOnly" and Change to: CustomErrors mode="Off"
5. Save your changes
6. Go to Start > Run and type in iisreset
7. Launch back into Business Portal and click on the page receiving the error. You should get a more descriptive error message?
8. Also look in the Application Event Viewer, are there any corresponding errors occurring there? In my case there was nothing,
When running SQL Reporting Services Reports deployed for Dynamics GP 2010 we receive the error:
"An error has occurred during report processing. (rsProcessingAborted)
Cannot create a connection to data source 'DataSourceGPCompany'. (rsErrorOpeningConnection)"
Resolution: As the SQL Server Reporting Services service is on a different server to the database server we could not use the Windows authentication for the datasources. To correct amend each datasource (one per company and one for Dynamics database), and mark each to use SQL Server authentication. Use a SQL login to with sufficent rights
193720 No way to remove revenue account from revenue module once data has been associated.
312625 Error displaying capital in detail report when using Allow drilldown to capital detail. 315158 Deleting pay type association from salary grade creates orphaned records
320795 Current users list doesn't work correctly on SQL Server 2005/2008. 321729 The Multi-row tab doesn’t show the lines (rows), if an input set name is longer than 24 characters.
325800 Start Period and End Period can’t be adjusted in HR Master after another field is changed. 344372 Entering capital item into invalid period and deleting causes duplicate/orphan records
362922 Excel Add-in returns no results when the optimization factor is 0. 363919 Single Row Input with 'Suppress Zero Lines on Input' creates difference from Multi-row.
363939 When using Human Resources Annually’ with regular allocations not selected, headcount is not updated for hourly employees. 366414 Reports where lines are the departments show a zero balance
367077 Copy plan wizard for HR Details does not correctly calculate allocation. 368241 System needs to keep deleted employees shaded while changing the “Show Allocation As” option.
368800 Importing HR changes clears existing data in HR master but not in HR input. 370981 Improve CALREV processing performance.
378602 FTE not calculated correctly for employees distributed between multiple departments when specifying different employee options. 381253 Running capital task on input set with historic periods causes results to shift the number of historic periods defined.
383592 When reassigning an employee to a new department, the value in the Increase Period 2 field is not updated in the new department. 390352 Allocation lost when reassigning an employee from two or more departments into one using the reassign window.
403235 Error: “ExpressLink encountered a problem attempting to submit data to Microsoft Forecaster.” This occurs if the user name contains a period. (Ex. Jane.doe) 403641 Decimal values do not appear on the single row tab
404570 Temp tables do not get dropped on SQL Server 2000 when the username is numeric
410614 When prompting for period and using a selection sub-menu in a report, users have to select period twice before the report will display.
415674 If a user defined benefit exceeds 5,000 characters, Forecaster will close unexpectedly when trying to select it. 419972 Enabling Auto-translate causes Forecaster to stop responding when adding employees in HR master.
440395 If many options are created for a user defined benefit, Forecaster may close unexpectedly when trying to select an option in HR input. 453998 The destination account and the contra account can’t be the same when two or more allocations are created and accumulate is used.
465875 When sorting columns in the Multi-row tab, incorrect values can be created if a @LOOKUP calculation is also used. 466855 Enabling Auto-translate causes Forecaster to stop responding when importing employees through HR import.
467705 Forecaster closes unexpectedly. 469946 If an employee from a previous input set salary grade doesn’t exist in a new input set, Forecaster closes expectedly when adding the employee.
470760 Specifying a color for calculated columns doesn’t apply the color. 473830 If Add as FTE is not selected when adding an employee in HR master, Forecaster closes unexpectedly.
How to Create an Application Role in SQL Server 2008 for Forecaster 7.0
By using an application role, users will be unable to log on to a database by using ODBC or another querying tool unless they know the password for the role. This helps prevent unauthorized access to the Forecaster database data. The Microsoft Forecaster 7.0 client will be able to read the application role password and let users log on.
The SharePoint Health Analyser picked up an issue with the configuration of a new SharePoint 2010 installation and found the following two errors:
[MissingWebPart] WebPart class [a7563a72-5661-4571-de0c-b2bc1de8718d] is referenced  times in the database [XXXXXX], but is not installed on the current farm. Please install any feature/solution which contains this web part. One or more web parts are referenced in the database [XXXXXX], but are not installed on the current farm. Please install any feature or solution which contains these web parts.
[MissingWebPart] WebPart class [8d6034c4-a416-e535-281a-6b714894e1aa] is referenced  times in the database [SharePoint_AdminContent_392c3097-c08f-4865-b5bf-2ce1b95b1269], but is not installed on the current farm. Please install any feature/solution which contains this web part. One or more web parts are referenced in the database [SharePoint_AdminContent_392c3097-c08f-4865-b5bf-2ce1b95b1269], but are not installed on the current farm. Please install any feature or solution which contains these web parts.
To correct the entries above go to GENERAL APPLICATION SETTINGS > FARM SEARCH ADMINISTRATION > SEARCH SERVICE ADMINISTRATION. Then afterwards go back to the reported message and click Reanalyse, it should then disappear