BCA won't refresh document

i keep getting this error message when i submit a document to be refreshed.:
(109)Connection or SQL sentence error:(DA0005):[[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user’jbloggs’.18456]The following data providers have not been successfully refreshed:Query one with Wldtg. (DMA0007):[]
Document is from full client 6.1a
Broadcast agent 6.1a running om windows server 2000
Database is sql server2000

anyone out there know what it might be?
i checked the odbc on the server and it looks ok, i also ran this report manually on the business objects server and it refreshed ok.


mrf (BOB member since 2004-08-02)

Welcome to B :mrgreen: B

That sure sounds like an ODBC connection problem.
Triple check the connection (yea, i know you already double checked it)
There’s a TEST CONNECTION dialogue at the end of the SQL Server ODBC Config, Successful?

One other thought, is the connection correct on your actual BCA server? If you’re running multiple servers, I would make sure it’s configured correctly on every cluster and node in your environment, especially the BCA server.


Chris Pohl :us: (BOB member since 2002-06-18)

thx Chris, good to finally find a decent bus objects forum,i was getting a bit fustrated with bus. objects own site.
sadly no joy with this though, i go through the odbc connection and do the test and get the test successful! message but still get the same error when i try to do the scheduled refresh.
this is the connection on the server bca is running on.
:confused:


mrf (BOB member since 2004-08-02)

Are you using pass thru login by chance?
(where you pass your bobj login id to the database)

is the jbloggs id your business objects id or the id you setup in the odbc connection?


Chris Pohl :us: (BOB member since 2002-06-18)

the jbloggs login is the business objects login of the user who created the report, which is also a login for the sql server database.
a different sql server login(with sysadmin rights) is used for the odbc connection on the bca server.


mrf (BOB member since 2004-08-02)

So the jbloggs login is somehow overriding the “other” sysadmin login … hmmm

Let’s check the ODBC Connection on the BCA Server …

On the 2nd screen in the configuration wizard … which do you have selected for “How should SQL Server verify the authenticity of the login ID”

  1. With Windows NT authentication using the network login ID
  2. With SQL Server authentication usinng a login ID …
    (I usually use the 2nd)

Then, do you have the checkbox checked for “Connect to SQL Server to obtain default settings for the additional configuration options” (I usually do)

And finally, do you have a valid userid and password supplied on this screen?

At the end of the configuation wizard (same screen where you TEST CONNECTION) … can you copy/paste in the diagnostic info given?


Chris Pohl :us: (BOB member since 2002-06-18)

to both your questions yes,these are the same settings i have on the bca server.
on the test connection screen:
Microsoft SQL Server ODBC Driver Version 03.70.1146

Data Source Name: BO6_Repo
Data Source Description: BO6_Repo
Server: XXX123
Database: BO6_Repo
Language: (Default)
Translate Character Data: Yes
Log Long Running Queries: No
Log Driver Statistics: No
Use Integrated Security: No
Use Regional Settings: No
Prepared Statements Option: Drop temporary procedures on disconnect
Use Failover Server: No
Use ANSI Quoted Identifiers: Yes
Use ANSI Null, Paddings and Warnings: Yes


mrf (BOB member since 2004-08-02)

Everything looks the same except for the driver (we’re using 03.81.9042)
So there’s probably a later driver you can try, but i doubt that’s the problem here.

Your connection is called BO6_Repo … Is your repository on SQL Server?
Are you looking at the SystemDSN for your data source or for your repository?
Maybe double check the universe connection and see where exactly it’s pointed.


Chris Pohl :us: (BOB member since 2002-06-18)

oops yes, i’m probably confusing the issue.
both the repository & data are on sql server - different databases though.
the dsn for the data gives:
Microsoft SQL Server ODBC Driver Version 03.70.1146

Data Source Name: RP_User
Data Source Description: RP_User
Server: XXX123
Database: (Default)
Language: (Default)
Translate Character Data: Yes
Log Long Running Queries: No
Log Driver Statistics: No
Use Integrated Security: No
Use Regional Settings: No
Prepared Statements Option: Drop temporary procedures on disconnect
Use Failover Server: No
Use ANSI Quoted Identifiers: Yes
Use ANSI Null, Paddings and Warnings: Yes


mrf (BOB member since 2004-08-02)

Do you need to specify a database?
(the ODBC configuration screen after you specify the userid/password)


Chris Pohl :us: (BOB member since 2002-06-18)

yes, i did not have the change ‘default database’ set to the correct database, but now that i have it still doesn’t work. :confused:


mrf (BOB member since 2004-08-02)

What’s the error message?
Also: Did you check your universe to ensure it’s using the correct SqlServer SystemDNS?


Chris Pohl :us: (BOB member since 2002-06-18)

same error as i first posted.
i am even able to manually run the report from business objects on the bca server itself.
i checked the systen dsn the universe is using & it’s the same as on the bca server.
it’s weird becuase we have a seperate bca server/repository/database in the US but it’s basically set up in exactly the same way as this euro one & scheduled reports refresh on it ok.


mrf (BOB member since 2004-08-02)

performing an upgrade to 6.1.3 seems to have fixed the problem completely :smiley:


mrf (BOB member since 2004-08-02)