Thursday 13 December 2012

Forecaster - Input Set Lock

To remove the input set lock, follow these steps.

Before you clear the lock, verify that no other users are logged on to the system. Otherwise, the user who is modifying the input set will lose their changes. To check for other users who are logged on, click View, and then click Current Users List.

  1. Click Tools, and then click Remove Input Lock.
  2. Click to select the input set that is locked, and then click Clear Lock.

Voila!

Wednesday 12 December 2012

GP Budget Import Error

Trying to import budget from excel to GP.

SCENARIO:
Trying to import budget from excel to GP although you have exported the sample from GP and used that as your basis and put your figures in the spreadsheet generated by GP. Then you proceed to import and get an error.

ERROR:
"The number of periods for the budget does not match the number of columns in Excel. Import will not be able to complete."

RESOLUTION:
Change column headers from date type to text by putting apostrophe (') in front the date fields.

Voila!


Thursday 4 October 2012

Creating a New Budget Year in Forecaster

Dynamics GP Land: Breaking It Down- New Budgets in Forecaster: I have to admit, there are a few questions that make me cringe.  They include-- Why does the reports.dic have to be rebuilt so often? Do c...

special thanks to Christina Phillips.

Setting up Forecaster and adding connections on end user machines

I know i have to do this soon, I stumbled across this blogg by Christina Pillips and it will save me the drama next week. See link below.

Dynamics GP Land: Forecaster.ini...or maybe outie?: With a 4 month old in the house, I can't resist a belly button joke :) I wanted to take a moment to share a little shortcut concerning mana...

Tuesday 2 October 2012

VirtualBox – Cannot Register the Hard Drive Because a Hard Drive with UUID Already Exists

Ok so you're trying to create another virtual machine using an existing hard disk file and you get the below error... What do you do? Follow the below guaranteed steps.





Failed to open the hard disk <FilePath>.
Cannot register the hard disk <FilePath><GUID> becuase a hard disk <DifferentFilePath> with UUID <GUID> already exists.
  1. Open the Command Prompt
  2. Change the directory to where VirtualBox is installed (Default: C:\Program Files\Oracle\VirtualBox) (see below on how to change the command prompt directory to another location)
  3. Type the following VBOXMANAGE.EXE internalcommands sethduuid <PathOfNewVHD>
Note that internalcommands and sethduuid need to be lowercase.
Below is the output of me changing the ID of the VHD located at C:\Users\bschacht\VirtualBox VMs\Windows XP (VPN) Copy.vhd





TO CHANGE THE COMMAND PROMPT DIRECTORY DEFAULT PATH:

Type "cd\program files\" etc and then press enter (in the command prompt)
i.e. cd\path and then press enter.

Microsoft Forecaster 7.0 Tip for using Revenue tab


If you are using your Revenue tab in Forecaster as the standard that is setup that is: market, product and rate, there are some things you need to know.

If you want to use a specific set of input lines for the product (for example you want a full listing of your products so users can enter units to be sold for the various periods) then when entering the product setup select a line which would include the relevant details (product listing).

If you want to use the rates feature then you need to leave the lines for the product blank and then enter the rates in the rate tab. When the user is entering the data on the revenue tab they will have to select which rate they want to enter the information against.

Hope I save you some days in trying to figure this out...

Wednesday 12 September 2012

Management Reporter: Clear Queue

To clear the queue of stuck reports in Management Reporter run the below in SQL server management studio.

USE MANAGEMENTREPORTER
DELETE RepositoryMessage

This will clear the queue.

Tuesday 4 September 2012

Unable to complete login process due to delay in opening server connection

You may receive this error when trying to create a new odbc connection to the server for dynamics gp.

To resolve this error:
Go to the server and change the firewall settings. Disable the firewall for the Domain Profile.

Voila!

Wednesday 11 July 2012

Fatal Error: Language database file c:\prog~1\FRXSOF~1\FRX6~1.7\REPORT~2\FRxXML4.dat not found.

Unable to generate FRx reports the above error keeps displaying.

To resolve:
SOLUTION 1: Try the KB article by Microsoft 932318. 


If the KB article doesn't work the below is guaranteed to work.


SOLUTION 2:  Run the FRxReg.exe located in the FRx 6.7 directory and then attempt to run the report again. You should have no issues.


Friday 13 April 2012

How to create a macro to automatically log in and Post a batch

STEP 1: Create macro to sign into GP and post batch.

Click on GP launch file.
When the sign in window appears click 'Alt + F8' to begin the recording of the macro.
Name your macro and the location to be saved to.
Continue the process as if you were going to post the batch.
Therefore, enter userid and password, click ok, select company, etc.
Go to Menu and click Transactions>> Sales>> Series POst (for example). click on batch to post and continue with the steps that the auto proceedure should complete. once finished click 'Alt + F8" to stop recording the macro.


STEP 2: Create Notepad file.

Create a note pad document, in the contents of the document enter the location of the Dynamics exe file, the set file and the location of the macro.
For example: "C:\Program Files\Microsoft Dynamics\GP\DYNAMICS.EXE" "C:\Program Files\Microsoft Dynamics\GP\DYNAMICS.SET" "C:\Program Files\Microsoft Dynamics\GP\DATA\AUTOPOST.MAC"


STEP 3: Change notepad file to batch file.

Right click on the notepad file and change the extention from '.txt' to '.bat'


STEP 4: Run macro.
To run macro just double click on the batch file.

*If you need to edit the batch file - right click on the file and click 'edit'

For more information on Integration manager autoposts see the following link by Mariano Gomez.
http://dynamicsgpblogster.blogspot.com/2009/01/how-to-schedule-dynamics-gp-to.html

Thursday 29 March 2012

Entering Licence Keys for Dynamics NAV

To upload your license file

  1. Open the Classic client.
    Click Start, and then click Microsoft Dynamics NAV 2009 Classic with Microsoft SQL Server
  2. On the Tools menu, click License Information.
  3. In the License Information window, click Upload.
  4. In the Upload License File window, browse to the folder where your Microsoft Dynamics NAV license file is located.
  5. Select the license file, and then click Open to upload it to the SQL Server database.

 

Copying the License File to Classic Database Serverupload your

This procedure assumes that you are using a database on the Database Server instead of running in single-user mode.

To copy your license file to the Classic Database Server

  1. Locate and copy your license file.
  2. On the computer where you have installed the Classic Database Server, navigate to the directory where the Classic Database Server executable, Server.exe, is located.
    The default location is Program Files\Microsoft Dynamics NAV\60\Database Server.
  3. Paste the license file in the server directory.
  4. Rename the file fin.flf if you have not already done so.
  5. Restart the Microsoft Dynamics NAV Database Server service.


http://msdn.microsoft.com/en-us/library/dd338774.aspx

Thursday 15 March 2012

Installing SQL on Windows Server

Please note that contrary to popular belief you CAN install SQL 2005 32 bit on Windows Server 2008R2 64 bit.

The system will not prompt you with any errors and the system will work fine.

Lessons Learnt.

Stock Status Report and Bins

BINS CANNOT BE ADDED TO THE STOCK STATUS REPORT IN REPORT WRITER FOR DYNAMCIS GP.

There is an option in the report options for bin but you cannot even select it because the system will tell you that you cannot use multi bins as a range.

After trying and trying it is now quite clear that bins cannot be added through report writer for this report. However it can be done through Crystal Reports or SRS.

Regards,

R.

Monday 12 March 2012

The stored procedure verify/versioninformation() of form duSQLInstall Pass Through SQL returned the following results: DBMS: 468, Microsoft Dynamics GP: 0.

After installing SQL and restoring GP database backups you sign into GP and get the following error:
The stored procedure verify/versioninformation() of form duSQLInstall Pass Through SQL returned the following results: DBMS: 468, Microsoft Dynamics GP: 0.

This is because of the collations.

To resolve this you need to uninstall SQL and go to control panel and change the location to United States. Restart the machine and ensur that the location remains the same.

Reinstall SQL and ensure you change the collation to: SQL_Latin1_General_CP1_CI_AS

Then run GP Utilites to recreate new company. (this is so the database folder will be present in SQL so you can restore to them) after company has been created restore the SQL backups.

Run script in SQL "sp_helpdb" expand the "status" column and ensure that all databases have the correct collation: SQL_Latin1_General_CP1_CI_AS, SQLSortOrder=52

Thursday 1 March 2012

"The date cannot be part of a different fiscal year".

This error will display if there is another year with the same periods in it. To resolve this go through the years already setup in the Fiscal Periods window and take note of the "culprit" year.

Go to SQL and run the following statements on the database:

delete sy40100
where year1=20**
delete SY40101
where YEAR1=20**
delete sy40102
where year1=20**
delete SY40103
where YEAR1=20**

please repalce 20** with the "culprit" year. The year  I am referring to is the field titled "Year" as seen in the Fiscal Period Setup window screen shot below.

PLEASE DO NOT DELETE IF YOU HAVE TRANSACTIONS POSTED FOR THE PERIODS LISTED UNDER THAT YEAR.


Thursday 23 February 2012

Run Microsoft Virtual PC 2007 SP1 on Windows7 64bit OS

Uninstall Windows Virtual PC from your machine. Go to Control Panel>> Programs and Features>> View installed updates.

Uninstall the Windows Virtual PC and then install Microsoft Virtual PC 2007 SP1.

You will  now be able to run VPCs.

Voila! You may now pass GO! lol...