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

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Finance | Project Operations, Human Resources, ...
Unanswered

Dynamics SL 2018 - The user name or password provided is incorrect. 2

(0) ShareShare
ReportReport
Posted on by

Good Day,

I have just setup an SL 2018 system, and when i try to log in, i get the below message:

The user name or password provided is incorrect.2
I know I am typing the correct credentials

I have the same question (0)
  • Sandhya nallamotu Profile Picture
    on at

    Hi,

    I am also facing the same issue. Do you have any update on the resolution.

    Thank you,

    Sandhya N.

  • Community Member Profile Picture
    on at

    I did a quick search for this error in Google and came up with this from SL 2015. May be completely unrelated, but thought I'd pass it on.

    community.dynamics.com/.../447887

  • MARC_ Profile Picture
    626 on at

    Hello Kumar and Sandhya,

    Unfortunately, I'm not certain what's going on in each of your scenarios...  Are you using the 'stock' build or have you customized and built your own?  Which release are you trying to deploy?  Are you using Windows Auth? If so, are you prepending with the domain\?  or are you using SL Authentication?  

    I'm assuming you entered the trusted windows user into the SL screen and these are the credentials entered into the app pool(s)?  Granted proper rights to all web service methods?  I would again try redeploying both web apps and web service.  Rerun the App and Sys SQL scripts.  Restart IIS.

    If you continue to get this message, hopefully someone from MSFT can help you.  Short of that, you may need to get the source code, build your own version, deploy it and debug.  To debug, you attach to the IIS worker process (w3wp) and you must have a 'debug' build deployed that matches the code to which you are trying to debug.  Your particular errors are happening in the Microsoft.Dynamics.SL.Timecard.Mobile project and then 'HomeController'

    Put stops on the <Post> Index function and I would also put on the UIHelper.impersonateValidUser

    Good Luck!

    Marc

  • WebApps Profile Picture
    on at

    Hi Marc,

    Thank You for your inputs. After changing the Logging Level key value as 4 in the web.config , we are experiencing the different error.

    Below is the error description

    16302 - Fatal SQL Error(-> Procedure or function WebserviceAccess_Insert has too many arguments specified.)

  • WebApps Profile Picture
    on at

    Hi Stuart,

    Thank You for your inputs. We followed the article which you shared already ,  but no luck. We are suspecting here the version mismatch.

  • MARC_ Profile Picture
    626 on at

    Well, that's good - you are getting closer. 

    What does that stored procedure look like in your SYS database? 

  • MARC_ Profile Picture
    626 on at

    I would also check the structure of that table (WebServiceAccess ) while you are there

  • WebApps Profile Picture
    on at

    ALTER Proc  [dbo].[WebServiceAccess_Insert] @Duration smallint, @Company varchar (10), @UserId varchar (47), @WindowsUserId varchar (85), @OnBehalfOf varchar(47), @SecToken uniqueidentifier, @Culture varchar (30), @SessionEncoding varchar(1) as

          INSERT INTO [WebServiceAccess] ([LastActivity],[TimeoutDuration],[CompanyID],[UserId],[WindowsUserId],[OnBehalfOf],[ID],[Locale],[Encoding])

          VALUES(CURRENT_TIMESTAMP, @Duration, @Company, @UserId, @WindowsUserId, @OnBehalfOf, @SecToken, @Culture, @SessionEncoding)

    =================================================

    SET QUOTED_IDENTIFIER ON

    GO

    CREATE TABLE [dbo].[WebServiceAccess](

    [LastActivity] [datetime] NOT NULL,

    [TimeoutDuration] [smallint] NOT NULL,

    [CompanyID] [char](10) NOT NULL,

    [UserId] [char](47) NOT NULL,

    [WindowsUserId] [char](85) NOT NULL,

    [OnBehalfOf] [char](85) NOT NULL,

    [ID] [uniqueidentifier] NOT NULL,

    [Locale] [char](30) NOT NULL,

    [Encoding] [char](1) NOT NULL,

    [tstamp] [timestamp] NOT NULL,

    [BusinessDate] [smalldatetime] NOT NULL,

    [CustomizationLevel] [smallint] NOT NULL,

    [CustomGrpID] [char](30) NOT NULL,

    [InitializationMode] [char](1) NOT NULL,

    [UserrecID] [char](47) NOT NULL,

    CONSTRAINT [WebServiceAccess0] PRIMARY KEY CLUSTERED

    (

    [ID] ASC

    )WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON, OPTIMIZE_FOR_SEQUENTIAL_KEY = OFF) ON [PRIMARY]

    ) ON [PRIMARY]

    GO

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

    We are migrating from 2015 to 2018 version

  • MARC_ Profile Picture
    626 on at

    You are sure you reran the SYS script that comes with web apps?  that should have updated it (although, I'm pretty sure this proc is the same in 2015 as it is in 2018 - were you using web apps in 2015?)

    the proc should look like this (the sys script alters it); try altering it, but if this is off, I would worry there are other objects that are not correct, too.

    ALTER PROC [dbo].[WebServiceAccess_Insert]

    @Duration smallint,

    @Company varchar (10),

    @UserId varchar (47),

    @WindowsUserId varchar (85),

    @OnBehalfOf varchar(47),

    @SecToken uniqueidentifier,

    @Culture varchar (30),

    @SessionEncoding varchar(1),

    @BusinessDate smalldatetime,

    @CustomizationLevel smallint,

    @CustomGrpID varchar(30),

    @InitializationMode varchar(1),

    @UserrecID varchar(47)

    AS

          INSERT INTO [WebServiceAccess] ([LastActivity],[TimeoutDuration],[CompanyID],[UserId],[WindowsUserId],[OnBehalfOf],[ID],[Locale],[Encoding],[BusinessDate],[CustomizationLevel],[CustomGrpID],[InitializationMode],[UserrecID])

          VALUES(CURRENT_TIMESTAMP, @Duration, @Company, @UserId, @WindowsUserId, @OnBehalfOf, @SecToken, @Culture, @SessionEncoding, @BusinessDate, @CustomizationLevel, @CustomGrpID, @InitializationMode, @UserrecID)

    go

  • Sandhya nallamotu Profile Picture
    on at

    Hi Marc,

    Thanks for the reply.

    we have ran WebApps2.01_Sys.sql scripts again which fixed the issue.

    Now we are facing the below error

    The database you are trying to log into does not support Web Apps

    1. Port 135 and Ports 5000-5020 are allowed through firewall

    2. Both servers are able to identified by its name - able to ping both servers.

    and in cliconfg we have made necessary changes still facing MSDTC error.

    Dynamics SL Message 15914: ~~~~ -> Communication with the underlying transaction manager has failed. -> The MSDTC transaction manager was unable to pull the transaction from the source transaction manager due to communication problems. Possible causes are: a firewall is present and it doesn't have an exception for the MSDTC process, the two machines cannot find each other by their NetBIOS names, or the support for network transactions is not enabled for one of the two transaction managers. (Exception from HRESULT: 0x8004D02B) (Consumer: fe80::d9bf:ab28:793e:fc84%2)

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

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

#1
Martin Dráb Profile Picture

Martin Dráb 551 Most Valuable Professional

#2
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 450 Super User 2025 Season 2

#3
BillurSamdancioglu Profile Picture

BillurSamdancioglu 278 Most Valuable Professional

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans