Management Reporter 2012 Rocks!

 

It’s time to put FRx out to pasture and welcome Management Reporter with open arms!

Heretofore I have not been carrying the flag for Management Reporter, but I just saw some stuff today that blows the doors off of what it can do. Management Reporter has come of age!

I’ll be sharing more details as soon as I find out which ones I can share, but there are more features coming that have not been advertised. Stay tuned, Management Reporter 2012 is a must.

It’s so good that it would be worth it to go to Convergence just to learn about Management Reporter 2012. Since its targeted release date is date Q1 2012 – that puts it in prime time for Convergence.

More to come, but just know that so many things you wanted it to do it WILL!

Until next post!

Leslie

2012 Tax tables re-released!

Round 1 of the 2012 tax tables have been re-released to reflect the changes made by congress to extend the 2% tax holiday.  Make sure you have the new tables or you will be buying yourself a lot of heartache.

Get the new tax tables from PartnerSource: 2012 Tax Tables from PartnerSource

Until next post!

Leslie

Federal W-2 electronic file couldn’t be created

If you have ever been lucky enough to receive this error, it can be difficult to track down a solution. Fortunately, one solution is easy – an ‘additional information’ button would have been nice though.



In my world this error message is presented because the path indicated in the File Name field does not exist, or you do not have ‘write’ permission to it.



Some of the newer operating systems, like Windows 7, will not let you create files in what they deem to be ‘protected folders’. So what worked last year might not work this year.

Good luck with year-end!

Until next post!

Leslie

Beware the 2012 Tax Tables!

The first batch of 2012 tax tables issued by GP are WRONG.

DO NOT USE THEM!

The FICA withholding is set to 6.2% instead of 4.2%. I know how much fun we had last year with this problem, let's not do it again. GP will be issuing new tables this week - those should be correct.

If you have imported the 2012 tables, you can simply change the FICAS tax table to reflect the correct 4.2% rate.

Here's how to change the percentage:


Microsoft Dynamics GP > Setup > System > Payroll Tax

1. Tax Code = FICAS

2. Select the 'Filing Status' button

Payroll Tax Setup window

On next window:

3. Filing Status = NA

4. Select the 'Tables' button

Payroll Tax Setup window

Type in the new Tax Rate where indicated. You can also update the limit. In the window below, the FICA limit is 106,800. The limit goes up for the 2012 tax year to $110,100.

Payroll Tax Tables window

We are all rushing to the finish line this time of year - don't forget to have fun!  I hope this will help someone.

Until next post!

Leslie

Internal Error 2738

Have you ever started to install a product, think it’s about to install, and then been greeted with:

This happened to me recently (today) while installing the GP2010 version of AvaTax. Specifically AvaTax 11.0.0.0.1.05.

Well, I’ve seen this error many times and have solved it by registering the vbscript.dll. To register the DLL, do the following:
For a 32-bit machine

1. First, be sure to close the Windows installer.
2. Click Start > All Programs > Accessories
3. Right-click on Command Prompt and select Run as Administrator.
4. Type cd C:\Windows\System32 and then press Enter.
5. Type regsvr32 C:\Windows\System32\vbscript.dll and then press Enter.
6. You will hopefully receive the following dialog:
   Click OK
7. Close the command prompt window.
8. Restart your computer.

For a 64-bit machine

1. First, be sure to close the Windows installer.
2. Click Start > All Programs > Accessories
3. Right-click on Command Prompt and select Run as Administrator.
4. Type cd C:\Windows\SysWOW64 and then press Enter.
5. Type regsvr32 C:\Windows\SysWOW64\vbscript.dll and then press Enter.
6. You will hopefully receive the following dialog:
   Click OK
7. Close the command prompt window.
8. Restart your computer.

Normally, that’s all you need to do. But what if things go wrong???

If Things Go Wrong:
If this doesn’t work, you’ll need to take more aggressive action. After searching the MSDN site and blogs, I found the solution. If you want to read the original article, go to: article on 2738 errors.  As it turns out, script-based custom action failures are behind many 2738 (and 2739) errors. If you are a programmer (are you listening Avalara?) it would be best not to use script-based custom actions in an MSI. If you do, you are opening up your users to problems.
The problem is that re-registering the DLL from a regular command prompt writes the registration to  HKEY_CURRENT_USER instead of HKEY_CURRENT_MACHINE. Starting with Vista, the Windows Installer will not load and use scripting engines if the registration is written to HKEY_CURRENT_USER. Consequently, re-registering the DLL from a normal user cmd prompt, will not help fix this type of error.
To see if you have this problem – MAKE A BACKUP OF YOUR REGISTRY-  and then check for the existence of the key below, and unregister it if it exists in HKEY_CURRENT_USER.

• For a 32-bit machine: HKCU\SOFTWARE\Classes\CLSID\{ B54F3741-5B07-11CF-A4B0-00AA004A55E8}
• For a 64-bit machine: HKCU\SOFTWARE\Classes\Wow6432Node\CLSID\{B54F3741-5B07-11CF-A4B0-00AA004A55E8}

To unregister the vbscript.dll from HKEY_CURRENT_USER:

1. First, be sure to close the Windows installer, and then MAKE A BACKUP OF YOUR REGISTRY. After the backup is complete, continue the listed steps.
2. Click Start > All Programs > Accessories
3. Right-click on Command Prompt and select Run as Administrator.
4. For a 32-bit machine type in the following command:
   reg delete "HKCU\SOFTWARE\Classes\CLSID\{B54F3741-5B07-11CF-A4B0-00AA004A55E8}" /f
5. For a 64-bit machine type in the following command:
   reg delete "HKCU\SOFTWARE\Classes\Wow6432Node\CLSID\{B54F3741-5B07-11CF-A4B0-00AA004A55E8}" /f

After removing the HKCU key, my software – Avalara’s AvaTax – installed perfectly.
I hope this helps someone with this delightful dialog:

Until next post!
Leslie