Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
samuelshaju
Starting Member
4 Posts |
 Posted - 2005-04-12 : 19:30:03
|
| Hi Friends,I have a problem when generating report in Crystal reports.the client is using SQL 6.5 and they have an existing program fromwhich they generate a report.But from some machines, this report cannot be generated. It gives an ODBC error .I tried running the ODBC trace and got the following info.DIAG [08004] [Microsoft][ODBC SQL Server Driver][SQL Server]Server user id 41 is not a valid user in database 'CompassV3' But the user have been created in SQL server and has been added to a group which have access to the tables. To confirm thisanother person in the same Group is able to print the report. So i assume that when a user is added to a group all the permissionsrelated or given to the group will be inherited by the new user added to it as well.i have tried lot of options but to no succeess, can anyone help me out if they have come across this stutation ??Help me please !!!RgdsSam |
|
|
TG
Master Smack Fu Yak Hacker
6065 Posts |
Posted - 2005-04-12 : 21:30:22
|
| Well, its been a long time for me with ODBC, Crystal and 6.5 but a couple of (obvious) things. * Can you successfully "test connection" from the ODBC datasource administrator window? * Is the ODBC datasource a User DSN or a Machine DSN? (should be machine). Make sure you don't have a similar named DSN as a User DSN. That one burned me good once. I set up a machine dsn but pointed the report to a user dsn that was already on the machine.* Is it only that report or all reports that use that DSN that is having trouble?Be One with the OptimizerTG |
 |
|
|
samuelshaju
Starting Member
4 Posts |
Posted - 2005-04-13 : 01:59:58
|
| TG ur information was valuable, but still have probs, i found that i had DSN created in the System as well as one under File DSN. Now the problem what i feel is that, The SQL server is in a Domain say 'A' and the users that log in is in Domain 'B'. so normally when user logs in from domain 'B' it will recognize as 'B_User1' rt ??SO is there any way to trick the SQL server ?? |
|
|
|
TG
Master Smack Fu Yak Hacker
6065 Posts |
Posted - 2005-04-13 : 07:52:19
|
| What was the answer to the first question (above)? If what you suspect is true, the answer should be that they can not successfully "test the connection". If you can change the (or create a new) DSN that uses Sql Authentication instead of Windows authentication, and successfully connect and run the report, then it sounds like you are correct. It would be a system access issue and your network admin people should be able to solve your problem. It may be that the person having trouble connecting just needs to be added directly (or to a security group) to the sql server box.Be One with the OptimizerTG |
|
|
|
samuelshaju
Starting Member
4 Posts |
Posted - 2005-04-13 : 18:39:03
|
| The answer to the first Qn is YES I can connect and i get a "Test Completed Successful Message"Now this was Using SQL_Authentication, I then Tried creating the DSN using Windows Authentication. But that doesnt allows to connect to the Database. Now that gives me a error message that "Login Failed, <DomainName>\<UserName> not defined as a valid User of Trusted SQl Server Connection.So I tried creating a user as <DomainName>\<UserName> in SQL Server. But that too gives an error (obviously) as it doesnt accepts the "\". Says its not in a Valid format. |
|
|
|
samuelshaju
Starting Member
4 Posts |
Posted - 2005-04-13 : 21:28:57
|
| Ok I have overcome the problem and this is how i did it, though it may be not the correct way to do it, for me it was a matter of time. I created a new user in SQL and then aliased it with the User who is having rights for that particular report and for whom it was working. any how that worked fine. thankx TG for your comments. appreciated.. |
|
|
|
|
|
|
|
|
SQL ODBC Problem