cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

SQLSTATE=28000 Log-on Error

Former Member
0 Likes
2,426

I'm getting the following error message when attempting to run an application from the development mode:

Error Code: 999

Error Message:  SQLSTATE=28000

Microsoft SQL Server Native client 11.0

Invalid authorization specification.

(I've searched prior posts but I can't find one that fits my situation)

I've just migrated a PB12.5 development application on a laptop to PB 16.  The laptop has Windows 8 (administrator) and the DB is MS SQLServer (Express) 2012.  The 'Connect' entry for SQL Server is 'Windows Authentication'.  PB 16 connects ok to the DB.  The PB database profile is:

SQLCA.DBMS = "SNC SQL Native Client (OLE DB)"

SQLCA.ServerName = "TABLET\SQLExpress"

SQLCA.AutoCommit = True

SQLCA.DBParm = "TrustedConnection=1,Database='callrunner_sqlserver',Provider='SQLNCL11''

The relevant registry setting (HKEY LOCAL MACHINE and mirrored in WOW2364) are:

DBParm "TrustedConnection=1,Database='callrunner_sqlserver',Provider='SQLNCL11'"

DBMS           SNC SQL Native Client (OLE DB)

ServerName  TABLET\SQLEXPRESS

There is no entry of relevance in the SQL Server log file.  All variables load from the registry when running/debugging the application.

View Entire Topic
ricardojasso
Participant
0 Likes

William,

Is the DB in the same machine as PB or in a separate machine?

When you use Windows Authentication (Trusted Connection) PB will try to connect using your Windows user account which "SQL Server validates using the Windows principal token in the operating system" (https://msdn.microsoft.com/en-us/library/ms144284.aspx). If both PB and SQL Server are on the same machine you should have no problem connecting using the trusted connection option.

Have you tried switching to SQL Server Authentication instead of Windows Authentication (Trusted Connection)?

Regards,

Ricardo