• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 33
  • Last Modified:

Getting error: Getting error: Cannot create a connection to data source Data source 1 SOME USERS

My client is reporting an errror

Getting error: Cannot create a connection to data source Data source 1 when they try to view reports in report manager.

Interesting though this is only happening to SOME USERS. Other users can see reports without any issues.
0
vbnetcoder
Asked:
vbnetcoder
  • 18
  • 14
1 Solution
 
Vitor MontalvãoMSSQL Senior EngineerCommented:
Check their ODBC. Something must be different or missing in the complaining users machines.
0
 
vbnetcoderAuthor Commented:
A bit hard to do because it is a remote clients machine. Where would i go to check this?
0
 
vbnetcoderAuthor Commented:
Actually, i believe 2 users are getting this error and for one it is working
0
Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

 
Vitor MontalvãoMSSQL Senior EngineerCommented:
You need to have access to their machine. Or ask them to send you a print screen of their ODBC DSN configuration.
They can check it in Control Panel / Administrative Tools / Data Sources (ODBC) / System DSN.
0
 
vbnetcoderAuthor Commented:
What should they see .... when i look at the one on my local box i don't see anything
0
 
vbnetcoderAuthor Commented:
This is mine.  I am able to connect to reports on my local machine
0
 
vbnetcoderAuthor Commented:
0
 
Vitor MontalvãoMSSQL Senior EngineerCommented:
By the error message I had the impression that they were using Data Source Names (DSN).
So, if they aren't using an ODBC connection means that they are connecting directly with SQL Server Native Client (SNAC) maybe.
I don't have any clues by now.
0
 
vbnetcoderAuthor Commented:
Let me know if you have any ideas of what i can check ....

the screenshot was from my computer but the same is on their server where i am able to run reports
0
 
vbnetcoderAuthor Commented:
is it possible that they don't have drivers installed under drivers in the Data Sources (ODBC)?
0
 
Vitor MontalvãoMSSQL Senior EngineerCommented:
You check if they have the SNAC installed. That's a good idea.
0
 
vbnetcoderAuthor Commented:
How do i do that? sorry i am a complete newbie
0
 
Vitor MontalvãoMSSQL Senior EngineerCommented:
You can check in ODBC for SQL Server drivers and also in the Add/Remove Programs for SQL Server Native Client (SNAC).
0
 
vbnetcoderAuthor Commented:
I assume we are talking about what i am pointing to in the screenshot.  Where should they go to download it if they don't?
Capture.JPG
0
 
Vitor MontalvãoMSSQL Senior EngineerCommented:
You can download it from Microsoft download center. This is the full Feature Pack and you just need to download the ENU\x64\sqlncli.msi (for 64bit) or ENU\x86\sqlncli.msi (for 32bit). It's a msi file (windows installer) so just double-click on it to get it installed.
0
 
vbnetcoderAuthor Commented:
ok i should only do this if i don't see what i highlighted in the screen shot above correct?
0
 
Vitor MontalvãoMSSQL Senior EngineerCommented:
I can't confirm that. I don't know how is configured the report connections.
0
 
vbnetcoderAuthor Commented:
if it's not on their computer it wouldn't hurt to download it though right?
0
 
Vitor MontalvãoMSSQL Senior EngineerCommented:
No, not at all but you should check what the user that has no issues have different on his machine from the others.
0
 
vbnetcoderAuthor Commented:
True will do that first.
0
 
vbnetcoderAuthor Commented:
To do that should i go through all the tabs in the Data Sources (ODBC)?
0
 
Vitor MontalvãoMSSQL Senior EngineerCommented:
I'm not talking only about ODBC. You should see everything. Applications, drivers, user permissions and anything do you remember.
0
 
vbnetcoderAuthor Commented:
hmmm not sure what i all need to check then
0
 
Vitor MontalvãoMSSQL Senior EngineerCommented:
I would start to check if the users have access to the SQL Server database.
0
 
vbnetcoderAuthor Commented:
How would i do that?
0
 
Vitor MontalvãoMSSQL Senior EngineerCommented:
You need to connect to the database and check if the users are created there.
I would also review the report connections.
0
 
vbnetcoderAuthor Commented:
I am looking at the error logs and the message is Login Failed for user (followed by the user)
0
 
Vitor MontalvãoMSSQL Senior EngineerCommented:
Ok, that's a more clear error message. That user doesn't have access to SQL Server. Or if he have the password is wrong.
0
 
vbnetcoderAuthor Commented:
What would  i need to do to resolve it?  I don't see the user that work in SQL server either
0
 
Vitor MontalvãoMSSQL Senior EngineerCommented:
You need to create it. I think I already told you how yesterday in one of your SSRS questions.
0
 
Vitor MontalvãoMSSQL Senior EngineerCommented:
Yes, I did. Check it here.
0
 
vbnetcoderAuthor Commented:
ty
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

  • 18
  • 14
Tackle projects and never again get stuck behind a technical roadblock.
Join Now