You Cannot Print An Unauthorized Purchase Order

● Ian Grieve ●  ● 0 Comments   ● 

Microsoft Dynamics GPThe below error message was reported to me by a user performing UAT (User Acceptance Testing) on an implementation of Purchase Order Processing and Workflow 2.0:

Microsoft Dynamics GP - You cannot print an unauthorized purchase order

Microsoft Dynamics GP

You cannot print an unauthorized purchase order

This error was somewhat surprising as it was produced when trying to print a purchase order (PO) which had been converted from a purchase requisition (PR). There was a workflow process on the PR, which had been final approved and the PO created, but there was not a workflow on the PO.

I double checked to make sure that the old Purchase Order Enhancements (POE) Approvals functionality was disabled (it was) as the customer had previously been using this.

It was when I was checking for POE Approvals, that I realised that, as part of the project, we had enabled the PO Commitments part of POE.

The warning message was being produced as the PO line had exceeded the commitment budget value. Loading the PO, clicking the save button, accepting the override of the commitment budget value, reloading the PO and clicking the Print button successfully printed the PO.

● Categories: Dynamics, GP, Microsoft ● Tags: , , , , , , , , , , ,  ● Permalink ● Shortlink ●

eConnect Incoming Service Won’t Start

● Ian Grieve ●  ● 0 Comments   ● 

Microsoft Dynamics GPeConnect is both a very useful tool for integrating data into Microsoft Dynamics GP, and also hugely frustrating. I assisted a client in creating a new test system recently and had some problems with eConnect. I installed it as normal, but the service didn’t start; when I tried to start the service manually, it started and immediately stopped without showing an error message.

I checked in the Windows Event Viewer for any errors and, again, there were none.

I’ve previously had issues with the eConnect service not starting and I figured it was worth a try.

The post linked above, has step by step screenshots, but the gist of what I tried is as follows:

  1. Make the eConnect service account an admin in Local Users and Groups.
  2. Start the service and note that it started correctly and continued to run.
  3. Stop the service
  4. Remove the eConnect Service from the Admins group.
  5. Start the service and again note that it started and continued to run.

The service has continued to run correctly since then.

● Categories: Dynamics, eConnect, GP, Microsoft ● Tags: , , , , ,  ● Permalink ● Shortlink ●

Dexterity Development ‘Unhandled script exception’ on data area

● Ian Grieve ●  ● 1 Comment   ● 

Microsoft Dynamics GPI’ve been doing some work recently on upgrading some Dexterity code to work with Microsoft Dynamics GP 2016 (both the RTM and R2). After compiling the new dictionary, I started Microsoft Dynamics GP and as the home page was loading got the following error:

MIS_AMS_Ext_160.dic - Unhandled script exception: SCRIPTS - data area. EXCEPTION_CLASS_SCRIPT_MISSING

MIS_AMS_Ext_160.dic

Unhandled script exception:
SCRIPTS - data area

EXCEPTION_CLASS_SCRIPT_MISSING

Continue reading → Dexterity Development ‘Unhandled script exception’ on data area

● Categories: Dexterity, Dynamics, GP, Microsoft ● Tags: , , , , , , ,  ● Permalink ● Shortlink ●

Workflow Email Action Request Error After Approval

● Ian Grieve ●  ● 4 Comments   ● 

Microsoft Dynamics GPA client who had recently upgraded to Microsoft Dynamics GP 2016 reported an error when approving a purchase order via Workflow 2.0 Email Actions. The user would click Approve on the email, enter their comment and click Approve and then received the following message:

Workflow Email Action Request Error

Request Error

The server encountered an error processing the request. See server logs for more details.

The purchase order was showing as approved, so Workflow itself was working correctly from this point of view and I couldn’t find any logs which might explain the issue.

However, while I was having a look at the workflow setup, I noticed that the Purchase Order Approval workflow type, did not have a manager set. There had been a workflow manager defined or the workflow process could not have been activated, but at some point it disappeared.

Adding a manager for the workflow type, saw the error message stop appearing.

The manager’s disappearance could be related to the upgrade, but I’ve upgraded some other clients who were using workflow and not had his same problem.

● Categories: Dynamics, GP, Microsoft, Workflow ● Tags: , , , , ,  ● Permalink ● Shortlink ●

Nothing Happens When Submitting A Purchase Requisition For Approval

● Ian Grieve ●  ● 3 Comments   ● 

Microsoft Dynamics GPI was onsite with a client to start a project implementing Workflow 2.0 for Purchase Requisition Approval and ran into a problem while doing training on how to interact with the workflow.

Everything had been fine until this point, but after creating a simple example approval workflow, I clicked the Submit button on the Purchase Requisition Entry window and nothing happened; I tried again through the navigation list, again without success.

I promised to figure out the issue in the next break and moved onto discussing other ways of interacting and then called the break.

It occurred to me that this might be another manifestation of an issue I have encountered previously, but without the visible error message.

I ran the script against the system database which redeploys the .NET Assemblies used by Workflow:

exec wfDeployClrAssemblies

It took a few minutes to run through, but I was then able to approve the requisition without further problem.

● Categories: Dynamics, GP, Microsoft, Workflow ● Tags: , , , , , , ,  ● Permalink ● Shortlink ●

Integration Manager Sales Order Integration – “The Sales Intrastat Entry window is open”

● Ian Grieve ●  ● 1 Comment   ● 

Microsoft Dynamics GPJust before Christmas I was creating an integration for a client in Integration Manager which would integrate Sales Orders, but unfortunately I was receiving an error message:

Integration Log
Integration: Eriks SO Integration (ID: 8)
Action: None
Start Time: 23/12/2016 11:05:38

  23/12/2016 11:05:38 Source: IIntegrationEngine_Run, Status Code: 0    Opening source query...
  23/12/2016 11:05:38 Source: IIntegrationEngine_Run, Status Code: 0    Initializing Source...
  23/12/2016 11:05:38 Source: IIntegrationEngine_Run, Status Code: 0    Establishing source record count...
  23/12/2016 11:05:38 Source: IIntegrationEngine_Run, Status Code: 0    Beginning integration...
1:  Order  Insert Failed 5. Seconds 
    DOC 1 ERROR: The Sales Intrastat Entry window is open. - The Sales Intrastat Entry window is open.
  23/12/2016 11:05:43 Source: FinishIntegration, Status Code: 3    Integration Failed
  23/12/2016 11:05:43 Source: FinishIntegration, Status Code: 3    Integration Results
    1 documents were read from the source query.
    1 documents were attempted:
        0 integrated without warnings.
        0 integrated with warnings.
        1 failed to integrate.

Finish Time: 23/12/2016 11:05:43

Source Total: 1
Successfully Integrated: 0
Integrated With Warning: 0
Failed: 1

Completion Status: Completed
Integration Status: No Documents Succeeded

Continue reading → Integration Manager Sales Order Integration – “The Sales Intrastat Entry window is open”

● Categories: Dynamics, GP, Intrastat, Microsoft ● Tags: , , , , , , , , ,  ● Permalink ● Shortlink ●

Hyper-V Error Creating Virtual Machines

● Ian Grieve ●  ● 0 Comments   ● 

Hyper-VA while ago I was having problems with Hyper-V whenever I tried to start a VM after my laptop had been to sleep or after it was first started up.

That problem went away recently after I upgraded to Windows 10 by rebuilding the laptop. However, it seems the problem has migrated to whenever I try to create a new virtual machine:

The server encountered an error while creatng

New Virtual Machine Wizard

The server encountered an error while creating {server name}.

The operation failed.

An unexpected error occurred: Logon failure: the user has not been granted the requested logon type at this computer. (0x80070569).

The operation failed.

The Hyper-V Virtual Machine Management server encountered an under unexpected error: Logon failure: the user has not been granted the requested logon type at this computer. (0x80070569).

This is a lot less disruptive than the originally problem as I started VMs a lot more often than I create them. And fortunately, the fix is the same as last time, so the batch file I created can still be used.

Run the batch file and the VM can be created; and even better is that I can keep the New Virtual Machine Wizard open with all of the settings configured when I run the batch file. So if I forget to run the batch file before starting to create the VM, I don’t lose any work.

● Categories: Hyper-V, Microsoft ● Tags: , , ,  ● Permalink ● Shortlink ●

Workflow 2.0 Tasks Not Escalating

● Ian Grieve ●  ● 2 Comments   ● 

Microsoft Dynamics GPI probably spent longer pondering over this one than I should have done.

We created a new Payables Transaction approval workflow for a client last week and during UAT they reported that tasks were not escalating when they went overdue.

I verified the workflow and did some testing and was able to confirm that tasks were not escalating correctly.

This was not something I had seen before so I spent a little time doing other things to divert my mind before the realisation struck that a scheduled process has to be checking for tasks to escalate. So off to SQL Server Agent I went.

Or at least tried to. The client does not have SQL Server Agent installed; rather they use an alternate third party tool (I don’t know why).

We passed details of the jobs through to them which are usually created in SQL Server Agent (Scan For Overdue Workflow Tasks For All Companies and Scan For Invalid AD Users and Expired Delegations For All Companies) so that they could create them in the third party tool.

The additional thought which occurred is that Dynamics GP is supported on Microsoft SQL Server Express which does not contain SQL Server Agent, so users on this SQL Server platform cannot use escalations in Workflow 2.0 (unless they use a third party equivalent of SQL Server Agent).

● Categories: Dynamics, GP, Microsoft, Workflow ● Tags: , , , , , , ,  ● Permalink ● Shortlink ●

Weird Duplicate PO Issue

● Ian Grieve ●  ● 3 Comments   ● 

Microsoft Dynamics GPThis is going to be a more wordy post than usual as I have no screenshots of the issue or resolution.

When I returned to the office on Wednesday after being away at reIMAGINE for a few days and then being on holiday in Kentucky, I was asked for assistance by Jason on our service desk.

A client had logged an issue with a PO; lets say the PO Number was PO34791 for the sake of argument (I don’t actually recall what it was).

When the PO Documents Enquiry (Inquiry) window was used, the PO looked fine; the creditor (vendor) was the correct one and all other values were okay and the PO showed as received.

However, the PO was also showing in PO Entry with a different creditor id.

Jason showed me two SQL queries;

  • The first, was a select on POP10100 WHERE PONUMBER = ‘PO34791’ and showed the correct PO.
  • The second, was a select on POP10100 WHERE VENDORID = ‘1ST001’ AND DOCAMNT = ‘791.50’ and this showed the other PO which the PO Entry window was loading. This query could be run for any information unique to the PO and it would return this PO instead of the correct one; ibncluding the PONUMBER field in the select would cause it to return nothing.

All very unusual.

I ran another query against POP10100 WHERE PONUMBER LIKE ‘PO34791%’ and this returned two lines of information both showing a PONUMBER field of PO34791.

in SQL Server Management Studio I dragged the values from the recordset into the query window to compare them; one was shorter than the other. The cause was that one of them (the one for the Vendor ID 1st001) contained a control character which is why it appeared shorter.

We’re not sure what the user had done, but the second, incorrect, PO was entered with a PO Number containing a control character; they’d been able to successfully enter the PO, but GP was then becoming confused about which one should be loaded when the user typed, or did a lookup, for PO34791.

We copied the live company into test and deleted the second PO (for vendor 1st001) from all tables (it had lines and tax and so on) and then verified the data with a Check Links and Reconcile and asked the user to double check.

This process would then be repeated on live with the PO being re-keyed (it was only a single line).

● Categories: Dynamics, GP, Microsoft ● Tags: , , , , ,  ● Permalink ● Shortlink ●

Error Submitting Batch For Workflow 2.0 Approval

● Ian Grieve ●  ● 3 Comments   ● 

Microsoft Dynamics GPWhile preparing earlier today for a client demo on Workflow 2.0, I encountered an error while trying to submit a batch for approval.

Workflow Error

[Microsoft][SQL Server Native Client 11.0][SQL Server][A .NET Framework error occurred during execution of user-defined routine or aggregate "Get "GetAssignedUsers".
System.IO.FileLoadException: Could not load file or assembly 'System.DirectoryServices, Vers[

Continue reading → Error Submitting Batch For Workflow 2.0 Approval

● Categories: Dynamics, GP, Microsoft, Workflow ● Tags: , , , , ,  ● Permalink ● Shortlink ●