Crystal Report Viewer. Logon Failed Details: [Database Vendor Code:18456}

I am running Sage Accpac version 5.5 on a 64 Bit windows 2008 Virtual server.
The database is SQL 2005 and reside on a different physical server. I created various customized reports using Crystal Reports XI. These reports were created by linking to views that was created in the SQL database. I link to the database with a ODBC (RDO) connection for all the reports. I can run all the reports from the Crystal Reports designer. However when I want to run them from the Accpac desktop I get the following error when running some of them

Logon Failed Details: [Database Vendor Code:18456]

Strangely enough the reports are all linked to the database in exactly the same way (ODBC) the only difference is that use different views.

Advice on this issue will be much appreciated.
malcolmaddisonAsked:
Who is Participating?
 
malcolmaddisonAuthor Commented:
Thanks guys
The issue was that although I had the views in both the main and sub-reports the visible views in the reports referred to other SQL views that was not directly in the reports.

Thanks for all the replies. This issue is now resolved.
0
 
JayConverseCommented:
Are the views in the main report or a subreport?  The latter is probably necessary, Accpac has issues with views in the main report.
0
 
Accpac_AttackCommented:
Alternatively, you can create a DSN for reporting which uses a trusted connection.  Ensure that the users have read access to the database and you should be good to go.
0
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

 
mlmccCommented:
CR XI doesn't support 64-bit Windows.

Do you have the 32-bit ODBC drivers loaded?

mlmcc
0
 
Scott_SchreinerCommented:
This relates to security within the report.  You must select "use trusted connection" within the report when creating the connection, and the connection needs to match the Accpac database connection configuration.
0
 
JayConverseCommented:
@scott -

Accpac doesn't use trusted connections, it uses SQL authentication.  Its Crystal wrapper replaces database login info, but only for tables in its data dictionary, hence the problem with views that it doesn't know about.
0
 
Scott_SchreinerCommented:
thanks, Jay, you're right, of course :)
0
 
malcolmaddisonAuthor Commented:
Issue Resolved
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.

All Courses

From novice to tech pro — start learning today.