There isn't a valid login record on the server for the user id and password you entered.

(0) Share

Report

Posted on by Bullsai

I have a client that had a server go down. They have it back up and running and have SQL Server 2000 installed, as well as SBF v9.

They can login as sa. They can create new users and login with those. They cannot login with any of the old users; they receive the following error:

"There isn't a valid login record on the server for the user id and password you entered."

Can someone help out with this ASAP? They have payroll to run today.

Thanks,

Todd M Bowlsby

*This post is locked for comments

I have the same question (0)

All responses (4)

Answers (0)

Community Member on at

Like (0)

Report

Are the uses set up in MSSQL?

Did they re-install MSSQL from scratch when the server went down? If so, they probably re-installed GP and then just restored their Dynamics and company databases from backups.

If so, then their old users would exist in the Dynamics database, but would not be set up in SQL.

There is script that creates users in SQL based on records in the dynamics database. I don't have it...but I know a lad who does!! - I'll see can I get it. Or you could manually set them up in SQL yourself. Remember to add them to the DYNGRP.

Look on partnersource for a techknowledge in relation to this issue.

Was this reply helpful? Yes No
MG-16101311-0 26,225 on at

Like (0)

Report

Since the issue seems you are missing your SQL Server logins for your Dynamics GP users, here is what you can do:

1. Identify all the missing SQL Server logins for the Dynamics GP users. The following script should get you this information.

USE DYNAMICS
go
SELECT USERID FROM SY01400 WHERE USERID NOT IN (SELECT [name] FROM master..syslogins)

2. With the above list, you can run the following to add your users one by one.

use master
go
sp_droplogin missingLoginHere
go
sp_addlogin @loginame=missingLoginHere, @passwd=someDefaultPasswordHere, @encryptopt=skip_encryption
go
USE DYNAMICS
go
EXEC sp_grantdbaccess 'missingLoginHere'
EXEC sp_addrolemember 'public', 'missingLoginHere'
EXEC sp_addrolemember 'DYNGRP', 'missingLoginHere'
go

Good luck,

Was this reply helpful? Yes No
Bullsai on at

Like (0)

Report

Thank you to both Ian and Mariano. This has resolved the issue. You guys are the best!

Todd M Bowlsby

Was this reply helpful? Yes No
Bill Campbell 12 on at

Like (0)

Report

Mario, I know this is really old - but it fits my problem

I can see all the user ID is both the database Security and the SQL Security

I have changed the SA password to complex - I can now connect to the ODBC

I can not login in GP with the SA or any user password - from any workstation or the Server

The Server Crashed on the cleint and when it was turned on this morning - this error has been generated for every user that connects.

Was this reply helpful? Yes No