• You are here:  
  • Home
  • Q&A
  • Q&A
  • InfoMaker
  • Infomaker Error Connecting to SQL Server

Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (4)

Resolved Infomaker Error Connecting to SQL Server

  1. Advice
0
Votes
Undo
  1. Keeley Stalnaker
    Keeley Stalnaker
  2. InfoMaker
  3. Wednesday, 12 August 2020 18:13 PM UTC

Hi,

I have a couple Infomaker reports that I've converted from Oracle to SQL Server. I am using SNC SQL Native Client as the connection type for both and have deployed the EXEs to my users' machines. The EXEs both work fine for me on my computer and when I remote in to the user computer. However, only one works when the users try to run it themselves. The other gives the error:


******

Database connect failed. Application cannot be run. Error: 18456 

SQLSTATE = 28000 

Microsoft SQL Server Native Client 11.0 

Login failed for user 'TheUserName'

*********

Again, both are using the same connection which includes a master username and password, so I am confused as to why the error message references the individual's username, and why one EXE works and one gives that error. Any input would be greatly appreciated; thank you!

  1. Error
  2. InfoMaker
  3. SQL Server
Infomaker 2017R2-1769 login problems
Error - Invalid DataWindow row/column specified
Responses (4)
Keeley Stalnaker
Keeley Stalnaker Accepted Answer Pending Moderation
  1. Thursday, 13 August 2020 20:32 PM UTC
  2. InfoMaker
  3. # 1

Thanks, ya'll; the lesson for the day is that when you are absolutely convinced there is nothing different between your two sets of code, there usually is! :-)

I opened my two ini files, saw they had slightly different connections, so copied and pasted the text of the one that was working into the other and problem solved!

Comment
Armeen Mazda @Appeon
  1. Armeen Mazda @Appeon
  2. Thursday, 13 August 2020 20:55 PM UTC
Thanks for sharing the solution!
  1. Helpful
There are no comments made yet.
Olan Knight
Olan Knight Accepted Answer Pending Moderation
  1. Thursday, 13 August 2020 16:32 PM UTC
  2. InfoMaker
  3. # 2

It >>> APPEARS <<< that the failed connection attempt is using the name of the person currently logged on to attempt to connect to the database.

Walk through the connection attempt in DEBUG mode and examine the components of the transaction object being used.


Good Luck,

Olan

Comment
There are no comments made yet.
Keeley Stalnaker
Keeley Stalnaker Accepted Answer Pending Moderation
  1. Wednesday, 12 August 2020 18:50 PM UTC
  2. InfoMaker
  3. # 3

Thanks for your response. The PBSNC is deployed and the client is installed on user machines, but one of the EXEs still throws that error.

Comment
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Wednesday, 12 August 2020 20:08 PM UTC
Hi Keeley;

IM only builds 32bit EXE's, so make sure that the installed SS DB Client is also of the 32bit nature.

Regards ... Chris
  1. Helpful
There are no comments made yet.
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 12 August 2020 18:42 PM UTC
  2. InfoMaker
  3. # 4

Hi Keeley;

  Sounds like you need to:

1) make sure that you deploy the I'm runtime - including the SS driver PBSNCnnn.dll (nnn = IM version).

2) install the SS DB client from Microsoft. This software would normally come from your DBA team.

HTH

Regards .... Chris

Comment
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.