Dynamics GP 2010 Web Services Installation – The Security ID structure is invalid. (Exception from HRESULT:0x80070539)

 

I been trying to install the web services for one of my clients, they are running a complicated environment, clustered SQL Server environment over three servers and clustered Hyper-V server to manage virtualized web applications like Workflow and Business Portal.

We have installed the SharePoint Server Farm and configured the Load Balancer to manage the load balancing between servers and created web applications for both Workflow and Business Portal and then moved to the web services installation which was already installed on the production environment, unfortunately the installation never succeeded with the above error message.

I tried everything, reinstalled it more that 100 times with no luck, searched every where with no result where I realized that the web services cannot be installed on a multiple server environment which does not make sense.

Finally I have decided to select the same Web Services database of the production environment and it worked! Looks like the Web Services cannot be installed with more that security database which is logically right due to the complication of the security roles and tasks on the web services entities.

Next time do not waste your time and directly select one name for web services database!


Regards,

Mohammad R. Daoud MVP – MCT
MCP, MCBMSP, MCTS, MCBMSS
+962 – 79 – 999 65 85
me@mohdaoud.com
www.mohdaoud.com

Advertisements

Dynamics GP Workflow–Task Approval Page redirects to local server URL even if the used URL was published!!

 

Looks like the folk at Microsoft forgot to remove the local URL when redirecting from Task Approval page to the actual document behind “This workflow task applied to:”:

image

So if your workflow was published over the internet and you users tries to open a document, the system will redirect them to the local server and not to the website as shown below:

image

To workaround this, I had to use SharePoint Designer or any available scripting tool to change the redirection of the below hyperlink in (C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\LAYOUTS\Dynamics.Workflow.TaskApprovalPage.aspx):

<a href=”<%=this.DocumentUrl%>” id=”A1″ target=”_blank”
     title=”<%=this.WindowLinkTitle%>”>
     <%=this.DocumentUrlText%></a>.

Into the below modified one:    

<a href=”Dynamics.Workflow.GP.PurchaseOrderViewer.aspx?org=1&workflow=f01d80eb-d355-460c-8cb6-b2a2162a078b&PoNumber=<%=this.DocumentUrlText%>” id=”A1″ target=”_blank”
     title=”<%=this.WindowLinkTitle%>”>
     <%=this.DocumentUrlText%></a>.

And it worked Smile Hope that this helps.


Regards,

Mohammad R. Daoud MVP – MCT
MCP, MCBMSP, MCTS, MCBMSS
+962 – 79 – 999 65 85
me@mohdaoud.com
www.mohdaoud.com

Dynamics GP Workflow – Workflow is incorrectly activated

 

Looks like it is the Workflows week! I been in a situation with one of my clients who also had an issue with the workflow, their “Vendors” been suddenly start requesting for approvals once they creates a new vendor and the below message shown on the left panel:

“Unable to Connect to Remote Server”

During the investigation I noticed that the vendor workflow was not activated in the workflow system! Which was very wired situation.

While digging into this I found that the setup they had for the Workflow is incorrect, they had the Microsoft Dynamics Workflow Location is different that the Office Server Location which made this error:

image

Fixing this miss resolved our issue!

Regards,

Mohammad R. Daoud MVP – MCT
MCP, MCBMSP, MCTS, MCBMSS
+962 – 79 – 999 65 85
me@mohdaoud.com
www.mohdaoud.com

Dynamics GP Workflow Backup

 

It has been a very tough month, me and all my team which now are 12 consultants in Dynamics Innovations are overloaded with tasks and projects assignments, I am travelling to Jeddah – KSA the upcoming couple of hours and wanted to post some articles before it leave my remaining rooms of my mind!

I been in a situation the last couple of days were one of my customers had a failure in their portals server that holds the Workflow and the Business Portal, after performing the reinstallation and making sure that all systems are up and running, I realized that the workflow I have created for this clients is a tree with 7 levels in depth and 900 lines of conditions that checks the cost center for each purchase order line and redirect the purchase order for the concerned department manager for first line approval! In addition, imagine the documents that will be lost during the maintenance procedure and the documents that will be stuck between the workflow and Dynamics GP!

I been lucky having a planned backup performed on daily basis, where I been able to restore the backup and proceed with the production environment smoothly.

Worth to mention that when I used the backup set I had for the Workflow database it failed to launch the applications! I had to restore the entire web application from the SharePoint Central Administration portal to get this done.

I wanted to share the script I used to schedule the daily backup, it is basically a batch file that will be called by Windows Scheduler daily and will command the STSADM to perform a backup to specific folder, that will be automatically created based on the backup date, replace “<servername>” with your actual server name and “<port>” with your actual port:

@ECHO OFF
@SET STSADM=”c:\program files\common files\microsoft shared\web server extensions\12\bin\stsadm.exe”
for /F “tokens=1-4 delims=/- ” %%A in (‘date/T’) do set DATE=%%B%%C%%D
for /F “tokens=1-4 delims=:., ” %%a in (‘time/T’) do set TIME=%%a%%b%%c

echo Workflow Backup Operation Started….

%STSADM% -o backup -url http://<servername>:<port>/sites/DynamicsGPworkflow -filename “C:\WSS Backups\Daily Backups\Workflow\Workflow_%DATE%_%TIME%.dat”

echo Business Portal Backup Operation Started….

%STSADM% -o backup -url http://<servername>:<port> -filename “C:\WSS Backups\Daily Backups\Business Portal\BP_%DATE%_%TIME%.dat”

echo Farm Backup Operation Started….

MD “C:\WSS Backups\Daily Backups\Farm\FARM_%DATE%_%TIME%”
%STSADM% -o backup -directory “C:\WSS Backups\Daily Backups\Farm\FARM_%DATE%_%TIME%” -backupmethod full

:End

Paste this into NOTEPAD and save it with “.CMD” extension to be an executable package and schedule the run periodically.

Enjoy!

Regards,

Mohammad R. Daoud MVP – MCT
MCP, MCBMSP, MCTS, MCBMSS
+962 – 79 – 999 65 85
me@mohdaoud.com
www.mohdaoud.com

Dynamics GP Workflow Installation – The selected website is not a SharePoint site

 

I been in a situation yesterday with one of my clients, they had a problem in their portals server and been getting the above message during the uninstallation of the Workflow of Dynamics GP.

The exact message was: “The selected website is not a SharePoint site”, but if you open the SharePoint Central Administration you finds the web application that holds the Workflow and it is indeed your Workflow web application.

While digging deeply into this, I noticed that the web applications for Workflows are being identified by unique identifier instead of using the web application name, so the mentioned case might became due to an operation that you have deleted the SharePoint web application from SharePoint Central Administration which workflow installed, and re-added the web application with the same name and same configuration, even with the same data as I have restored the web application from a SharePoint backup I had earlier.

The only way to resolve this is by forcing the workflows to be uninstalled without validating the SharePoint, to do this you will need to download Windows Installer Cleanup Utility which could be downloaded from here, and uninstall the workflow application by clicking on uninstall, this will remove the information of the workflow from your system but will not delete workflow files, normally workflow files will be replaced after doing the reinstallation, but the only thing that will have to be removed manually is the registered workflows and features that was deployed over SharePoint, this will need to be done by running following commands in CMD:

cd C:\Program Files\Common files\Microsoft shared\Web server extensions\12\Bin\         
stsadm -o deactivatefeature -name DynamicsApproval -url <DynamicsGPWorkflow URL> –force
stsadm -o deactivatefeature -name DynamicsWorkflowForms -url <DynamicsGPWorkflow URL> -force
stsadm -o deactivatefeature -name DynamicsWorkflow -url <DynamicsGPWorkflow URL> -force
stsadm -o uninstallfeature -name DynamicsApproval -force
stsadm -o uninstallfeature -name DynamicsWorkflowForms -force
stsadm -o uninstallfeature -name DynamicsWorkflow -force

Replace the <DynamicsGPWorkflow URL> placeholder with the path of the DynamicsGPWorkflow site collection. For example, replace the placeholder with the following path:

http:// Server_name /Sites/DynamicsGPWorkflow

Finally you’ll be able to reinstall the workflow with no issues.

Enjoy!

Regards,

Mohammad R. Daoud MVP – MCT
MCP, MCBMSP, MCTS, MCBMSS
+962 – 79 – 999 65 85
me@mohdaoud.com
www.mohdaoud.com