Dynamics GP Business Portal: Folder Executive– [CompanyName] does not exist.

I ran into the below error this morning while installing business portal for Dynamics GP 2013:

-----------------------------------------------------------------------

Feature Id:  538b415a-89eb-4de6-a93c-9fea1d565363

      Location:  C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\FEATURES\BPGPReportsCenter

        Action:  Activate

     Exception:  Folder Executive – [Company Name] does not exist.

   Stack Trace:     at Microsoft.Dynamics.SharePoint.Helper.ValidateFolder(SPList pageLibraryList, String folder)

   at Microsoft.Dynamics.SharePoint.Helper.AddFolderPermission(String siteRelativePath, String pageLibrary, String folder, String group, String permissionLevel)

   at Microsoft.Dynamics.GP.BusinessPortal.GPReportsCenter.CenterActivateProcess(String urlCenterLibrary, String quickLunchTitle, String groupName, String groupDesc, String folderName, String pageLibraryName)

   at Microsoft.Dynamics.GP.BusinessPortal.GPReportsCenter.FeatureActivated(SPFeatureReceiverProperties properties)

   at Microsoft.SharePoint.SPFeature.DoActivationCallout(Boolean fActivate, Boolean fForce)

   at Microsoft.SharePoint.SPFeature.Activate(SPSite siteParent, SPWeb webParent, SPFeaturePropertyCollection props, Boolean fForce)

   at Microsoft.SharePoint.SPFeatureCollection.AddInternal(SPFeatureDefinition featdef, Version version, SPFeaturePropertyCollection properties, Boolean force, Boolean fMarkOnly)

   at Microsoft.SharePoint.SPFeatureCollection.AddInternalWithName(Guid featureId, String featureName, Version version, SPFeaturePropertyCollection properties, Boolean force, Boolean fMarkOnly, SPFeatureDefinitionScope featdefScope)

   at Microsoft.SharePoint.SPFeatureCollection.Add(Guid featureId)

   at Microsoft.Dynamics.GP.Deployment.SharePoint.Office14.FeatureAdapter.Activate(Guid id, FeatureScope scope, String siteCollection, String relativeUrl)

   at Microsoft.Dynamics.GP.Deployment.WindowsInstaller.SharePoint.SharePointActivateFeature.OnPerform(IFeature spFeature, SharePointFeatureInformation spFeatureInfo)

   at Microsoft.Dynamics.GP.Deployment.WindowsInstaller.SharePoint.SharePointFeatureDeploymentProcessor.Process(IFeature featureInterface, SharePointFeatureCustomActionData data)

-----------------------------------------------------------------------

After searching everything on the internet and investigated all possibilities I found finally that one of my companies contains “-“ and “*”, removing these from this company resolved my issue!

---

Regards,

--
Mohammad R. Daoud MVP - MCT
MCP, MCBMSP, MCTS, MCBMSS
+962 - 79 - 999 65 85
me@mohdaoud.com
http://www.di.jo

Update SQL Server Collation for a Clustered Installation

I been in a situation with one of my clients where I been implementing and Active/Active clustering setup over SQL Server 2008 R2 as my customer is still using GP 10.0, after finalizing and testing everything I noticed that the code page I must use is 1256 while I have used 1250!!!

Thanks god for having a utilities to update the collation without having to destroy the cluster! I have followed the steps below and it worked like a charm:

1. Backup your objects! As this process will drop logins, linked servers, jobs, and anything related to the instant itself plus will de-attach your database.

2. Make sure that your current server is online and carrying your SQL Instant.

3. Make sure that SQL Services is offline.

4. Run the following command:

"E:\SQL\setup.exe" /QUIET /ACTION=REBUILDDATABASE /INSTANCENAME=MSSQLSERVER /SAPWD=P@ssW0rd /SQLCOLLATION=Arabic_CI_AI /SQLSYSADMINACCOUNTS="DAOUD-PC\DAOUD"

E:\SQL\setup.exe will need to be replaced with the locations of the SQL Server 2008 R2 setup.exe path.

MSSQLSERVER represents the default instance, if you have a named instance this must be changed to hold the instance name.

P@ssW0rd: is the new SA user password, it must be strong password or otherwise the repair will fail.

Arabic_CI_AI: is the new collation name.

DAOUD-PC\DAOUD need to be replaced with the local administrator of the server or PC you are installing the SQL on.

Paste above command into CMD and wait for 3-4 minutes, you will have your SQL Collation changed.

Warning: this operation will recreate your master database, were all existing setting will be reset, if you had databases attached it will be de-attached and will be found in the database folder.

---

Regards,

--
Mohammad R. Daoud MVP - MCT
MCP, MCBMSP, MCTS, MCBMSS
+962 - 79 - 999 65 85
me@mohdaoud.com
http://www.di.jo