GP 2013R2 Upgrade stuck in loop "Budiness Intelligence reports were not deployed"

This error occurs when you previously deployed the Excel Reports but have moved servers or the location where you originally installed them is no longer in place.


If you are just doing a test upgrade you can just exit GP Utilities.

GP would have been upgraded already. You can always re-deploy the reports within GP.

Re-open Closed Fiscal Period

Scenario

• Closed February and March accidentally in AP.
• Only February should have been closed in AP.

 

Resolution:

• Have users log out of SL
• Execute the below SQL statement on Test Company first. (Assuming March is the third period for Fiscal Year 2018)
• update apsetup set CurrPerNbr = 201803, PerNbr = 201803
• Test entering transaction for March 2018. Confirm all is well.
• Complete same steps on live company.

Moving and Upgrading Integration Manager

Moving from server running GP2013  to a new server with GP2016.

Process for moving integrations to the new server:

Integration Manager can be migrated to a new location by moving the Integration Manager database. The location of the database file can be found by viewing the options menu window in the Default Integration Manager Database field on Integration Manager.

After this file has been moved to the new server, you should use the Convert Database tool in Integration Manager to convert the database to the newest version, matching the installation of Integration Manager.

All paths in the integration will not change automatically. This part will have to be done manually.

An error occurred while loading or initializing an addin. Ask your administrator to check the Windows event log for more details. Dynamics will now close.

So you are trying to upgrade GP 2013 to GP 2013R2.

You launch GP and get the message as per subject.

When you check event viewer you get 'An exception occurred while trying to load or initialize the add in located at Excel Builder'


Reason for issue:
Your client gives you a mismatched database to GP folder.


To Resolve:
- Ensure the SLB from eone is installed
-Remove the excel related add ins from the Add In Folder in GP.
- Manually add the SLB module in the add remove of GP
-Launch GP. You will be fine.

SQL Database in Recovery Pending Mode

So you have done a restore of your virtual machine.
Sign in to SQL and boom! Your database is in recovery pending mode!
What the hell is that?

To fix:
- Go to the folder where the ldf and mdf is stored, grant access to 'everyone'
-Sign back in to SQL, restart the service
-Run the following script and you are good to go!
ALTER DATABASE dbnamehere SET ONLINE

And voila! Problem resolved!

Dynamics SL ROI

Ever wondered what ROI stands for in Dynamics SL?

Well have no fear, you are in the right place sir/ma'am!

ROI stands for - Report Operations Interpreter

What is it - it is the screen you see immediately before running any SL Crystal Report. The purpose of the screen is to filter or group the report the way you want it to show at run time.

The remote server returned an error: (407) Proxy Authentication Required.

So you are installing Management Reporter Application and Process Service in the environment. Clean install. No reports or anything else exists. Then.... you get the above error! It looks like everything was installed though. :s

What next?
- Remove the Application and Process Service.
-Delete the Management Reporter database in SQL that was just made by the process.
-Go into Internet Explorer and turn off the Proxy Service.
-Re-run the install for the Application and Process Service.
-Voila!