Announcements
Hi GPManiac,
General forum etiquette is to create a new thread for each new issue. That way other users can find the answers for their issues as well.
I can certainly provide recommendations as I have done here, but if review of any logs or your environment is needed, a Support Case would need to be entered here:
Thanks!
Yes, I am on the same network domain as my test server.
On another note, I am having problems emailing the Vendor Remittance. I saw your exhaustively detailed documentation on troubleshooting email issues in GP. Would you be willing to help me out this issue as well on this ticket? Should I open up another ticket?
Thanks for your help. Much apporeciated.
Hi GPManiac,
A local account will usually work in single domain setups, as it will usually have access to the same domain as the server.
Are you on the same network as the server?
Outside of that, yes, you would need to open the Web Services ports. By default, Web Services uses port numbers 48620 and 48621 to install onto.
Thanks!
Hello!
Just having another windows user submit the Vendor solved the problem. Although the SQL service is still being run by a local account??
But this brings up another issue. When I try to take action on the email to approve or reject, I cannot do it from my local Outlook client. It only works when I do it from the Outlook client physically installed on my test server. I get the message below. Is there a port that needs to be opened on the server that is running GP or something? Thanks!
Yep. I'll test with a different windows user submitting the workflow. If that doesn't work I'll look a the SQL service account. I do know that the account running the SQL service is a local account but I'll try the different user first and respond back.
SELECT DSS.servicename,
DSS.startup_type_desc,
DSS.status_desc,
DSS.last_startup_time,
DSS.service_account,
DSS.is_clustered,
DSS.cluster_nodename,
DSS.filename,
DSS.startup_type,
DSS.status,
DSS.process_id
FROM sys.dm_server_services AS DSS;
Hi GPManiac,
That can play a part, but your settings would run into this first. I would rule out the easy setting before digging into any issue that could be occurring due to the SQL Service Account.
Let us know if a new user gets the same issue, because that would point to AD being unreachable.
Hi Justin.
I thought that might be the issue but I also see a lot of chatter out there regarding the account that runs the SQL service being the cause of this issue. I'll test with another windows user. Thanks!
Hi GPManiac,
The issue here is that you are logged into Windows as the same user who is both the approver and alternate approver, but have the "Allow originator to be approver" checkbox unmarked.
To be very clear here, the GP user does not matter at all within Workflow. All that matters in the land of Workflow is the Window users.
For you to test you would need to mark the checkbox for the "Allow originator to be approver" option, or will need a different Windows user to test with.
Let us know if you have any questions or concerns.
André Arnaud de Cal... 291,359 Super User 2024 Season 2
Martin Dráb 230,370 Most Valuable Professional
nmaenpaa 101,156