Details: [Database Vendor Code: 18456 ]

[jmd0252]

From the look of this error,, It says it cannot run this report, because the database will not let me logon. This is a brand new installation, NO,, I do not know if everything has been installed correctly. I know that I have setup the login thru the web, to use windows AD,, and that does work. Above that,, ask your questions..

 

[Turkbear]

Hi,
OK, questions:

What database?( looks like SqlServer)
Does that database support AD logins or does it need its own login stuff ( most do)

Is the database local to the BOE server or a remote one?

Try here:

http://blogs.msdn.com/sql_protocols/archive/2006/02/21/536201.aspx

To Paraphrase:"The Help you get is proportional to the Help you give.."

 

[jmd0252]

The server is local,,actually they are both VM-machines. It is an 2005 SQL server. I wondered about the logins, The software we use off of the sql server, has it's own login. I have the crystal developers edition on my local machine, designed and saved a report (runs fine on my machine). Took the saved file(rpt), and moved to the crystal machine, went thru the "publication wizard", and published the report. Signed on crystal thru the web interface, and then I wanted to run the report. Cannot find anything, except where I can schdule the report to run, tried that,, and that is when I get the above error. My password, is the same for both the crystal and the sql machine. I am kind of stuck, with what to do next. Ideas, suggestions, brand of liquor to buy, byb I drink scotch, FYI. Thanks in advance..

 

[hilfy]

Do you want each user to have the report log in to the database using their own ID and password? Or would it work to have a common reporting id for the database that all of the reports would use? (This is what we do...)

If you have a common reporting ID, you can set the database logon information in the CMC.

-Dell

A computer only does what you actually told it to do - not what you thought you told it to do.

 

[jmd0252]

I appreiciate the reply,, I went into the SQL server,, thinking I had to setup a user/password, for the request coming from the crystal machine. I structured everything around the common password,, but I still cannot schedule and run the report. I get the same error. Ideas, comments??