web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics GP (Archived) / GP 2013 users can'...
Microsoft Dynamics GP (Archived)

GP 2013 users can't sign in.

(0) ShareShare
ReportReport
Posted on by ShawnO 165

I have installed GP web client in Windows Azure. I created a test account in GP and in AD adding it to the users group I created before installing the web client. The web client works great as the administrator account I used to install it all with. When I try to log in with a plain user I get,

Unexpected Error

An unexpected error has occurred. Press the Sign-in button to reconnect to the application.
Correlation ID: 41dbc617-a889-432c-9922-a6a32a548dca

 

The user account can log into GP with no problems and when I add the user as a member of the domain admin group in AD it can then log into the Web Client with no problems. What rights is the user group missing so that they can get to the GP log in through the web client?

 

c042475d-7df7-4436-bbba-bd9762afb02f:An unexpected error has occurred.  Press the Sign-in button to reconnect to the application.:http://SVADC:48650/SessionService:System.Web.HttpUnhandledException (0x80004005): Exception of type 'System.Web.HttpUnhandledException' was thrown. ---> System.ServiceModel.FaultException`1[System.ServiceModel.ExceptionDetail]: Logon failure: the user has not been granted the requested logon type at this computer (Fault Detail is equal to An ExceptionDetail, likely created by IncludeExceptionDetailInFaults=true, whose value is:

System.ComponentModel.Win32Exception: Logon failure: the user has not been granted the requested logon type at this computer

   at System.Diagnostics.Process.StartWithCreateProcess(ProcessStartInfo startInfo)

   at Microsoft.Dynamics.GP.Web.Services.Session.SessionProcess.StartableSessionProcess.TryToStartProcess()

   at Microsoft.Dynamics.GP.Web.Services.Session.SessionProcess.StartableSessionProcess.Start()

   at Microsoft.Dynamics.GP.Web.Services.Session.Service.SessionCreator.CreateSession(SessionCreationContext creationContext, Uri runtimeServiceBaseAddress, SessionUserInfo sessionUserInfo)

   at Microsoft.Dynamics.GP.Web.Services.Session.Service.SessionService.CreateSession(SessionCreationContext creationProperties, Guid authenticationToken)

   at SyncInvokeCreateSession(Object , Object[] , Object[] )

   at System.ServiceModel.Dispatcher.SyncMethodInvoker.Invoke(Object instance, Object[] inputs, Object[]&...).

   at System.Web.UI.Page.HandleError(Exception e)

   at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

   at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

   at System.Web.UI.Page.ProcessRequest()

   at System.Web.UI.Page.ProcessRequest(HttpContext context)

   at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()

   at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)

 

I have granted the group read\write permissions on the folder structure where the web Client is installed on the Web server but that did not help.

*This post is locked for comments

I have the same question (0)
  • Suggested answer
    KirkLivermont Profile Picture
    KirkLivermont 5,985 on at

    I haven't used the web client yet but my first guess is that it is because the user password is passed to the server encrypted in a manner that is partially based on the server name used when creating the ODBC connection.

  • Verified answer
    Community Member Profile Picture
    Community Member on at

    Sorry for the late answer, just ran across this thread.

    Sounds like you're loading this onto a Domain Controller. It's not a supported configuration but sometimes hard (impossible) to avoid.

    I ran across this in my test environment, here's how I fixed it:

    Start->run gpmc.msc

    Open your domain

    Open "Group Policy Objects"

    Right-click "default domain controllers policy"

    Choose Edit.

    Computer Configurations-><Policies->Windows Settings->Security Settings->Local Policies->User Rights Assignment

    Right click "Allow log on locally" and click Properties.  Add the group you created for the GP Web Users.

    Run gpupdate ; you should see "user policy update has completed successfully" when complete.

    Or you could just make everyone a member of the "Domain Admins" group :-)

  • MG-16101311-0 Profile Picture
    MG-16101311-0 26,225 on at

    I guess the main question is, can you describe your Azure VM infrastructure. Are you deploying all WC components onto one provisioned VM server? Is this VM server an AD DC as well? If so, Kirk is correct and you will need at least 2 servers, one of which will be an AD domain controller. The second server could be running all your GP and GP Web components.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the March Top 10 Community Leaders

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans