Unable to connect: incorrect log on parameters [Database Vendor Code: 1005]

We have a report that has been in production for some time and ran successfully with no trouble. However, it now keeps failing with this error and the log on parameters are correct. The whole error is:
Error in
File / usr/local/bobje/data/procSched/mrspas051.reportjobserver/~ tmp2f0ea56e4c88a08d6.rpt: Unable to connect: incorrect log on parameters, Details: [Database Vendor Code: 1005].
Can you tell us why a report suddenly fails with this error? Thank you.

We've been having the same issue with scheduled Crystal reports (in BO 3.1). After much testing, we found that even though reports are set to use the custom database logon credentials, if the name of the original data source changes, it causes the error (Error in File ~tmp1d06ed702daa30.rpt: Unable to connect: incorrect log on parameters. Details: [Database Vendor Code: 1005 ] ). For example, I publish a report to a production environment. It has an original data source called "test". I set it to use the custom database logon. A user then creates a recurring schedule and it runs successfully. A developer opens the report in Crystal 2008 and changes the connection to something else, for ex "dev" (in Crystal, this is on the Database menu, select "Set Datasource Location" and pick a different option under My Connections or create a new one), then saves the report to BO. We promote the report to prod and it overwrites the existing file. We make sure it's still set to use the custom database connection to prod but the recurring schedules that were set up when the original data source was called "test" immediately begin to fail. I tried working with support but they didn't really help much. They had me install the Oracle 11G client on our servers since we were connecting to our 11G repository with the 10G client but that did nothing. They finally claimed that since our repository database was Oracle 11G R2 (not just 11G), it wasn't supported and they wouldn't go any further. If anyone's found a solution, I would really appreciate hearing how it was fixed.

Similar Messages

Unable to connect: incorrect log on parameters. Database Vendor Code: 18456

I have imported a report into Info View (that has no parameters), I am able to run the report on Demand in InfoView, and I am also able to run the report within the CMC Preview. I have tried scheduling using the admin account in CMC, through the publishing wizard and also with a authorized users in InfoView. But anytime I try to schedule the report I get this error.
Status: Failed
Printer: The instance is not printed.
External Destination: Mail the instance to " XXX@XXX .com " with a subject of " test ".
Data Refresh Settings: Use the server defaults.
Start Time: 11/18/08 3:02:19 PM
End Time: 11/18/08 3:02:23 PM
Server Used: clr-combr.reportjobserver
Error Message: Error in File C:\Program Files\Business Objects\BusinessObjects Enterprise 11.5\Data\procSched\clr-combr.reportjobserver\~tmp1304574d76168ca.rpt: Unable to connect: incorrect log on parameters. Details: [Database Vendor Code: 18456 ]
I have made sure that the Reportjobobject is enabled and the server for SMTP email is enabled, and I am pretty sure I have the properties set up correctly within there, we created a email account specifically for crystal. And that email account is also set up as a user. I don't know where else to look.
Please help.
Thanks

Hi Ashley
I would like to suggest you following things with the Report:
1) Please log in into CMC, go to Report which you want to schedule.
2) Click on the report and go to Process
3) Click on the tab Database.
4) There will be two option to make the entries for database logon required for the Report.
Please select the appropriate option. Are you able to Preview the report?
What is the database in use? Please also check the odbc driver settings for that database.

Adding a Subreport to existing report and getting this error, "Unable to connect: incorrect log on parameters"

I have taken on an existing vb.net project done in Visual Studio 2008 with crystal reports version Crystal Report XI.
The reports on their own work very well. Problem is I need to add information to my report which is a 'many-to-one' situation where for each Project Id that I am displaying I need to display several attached documents and the report I am working on is for several Project Id's.
I figured this would be a perfect situation for a SubReport. I created a separate report which calls a stored procedure to get all of the Attached Documents for a specific Project Id. I thought if I were to add this new SubReport to the Original Report and link the Project Id's, easy-peazy, I would be done.
This is not the case. I have vb code that loads the Original Report with a stored procedure and when this code runs with the setup I described above it fails when it is creating the final report with the following error:
Logon failed. Details: crdb_adoplus : Object reference not set to an instance of an object. Error in File C:\~\ProjectDescriptionReport {6BA19F79-2A12-4826-B1F6-456EF799963B}.rpt: Unable to connect: incorrect log on parameters.
I have no specific connections in my vb code for the reports. If I do not add the subreport to the main report, it loads correctly, so I know the error is caused by the subreport.
This is the code that creates the original report (sorry for dumping the code here, i just thought it would be easier to see all the code) :
Public Function LoadReport(ByVal inProjectNum As Integer, ByVal strProjectName As String) As DataTable ', ByVal inFiscalYear As Integer, ByVal inCompany As String) As DataTable
        Dim cnn As SqlConnection = Nothing
        Dim cmd As Data.SqlClient.SqlCommand
        Dim obj As New clsDataClass
        Dim dataAdapter As SqlClient.SqlDataAdapter
        Try
            LoadReport = New DataTable("DescriptionReport")
            cmd = New SqlCommand()
            cnn = obj.Create_Connection()
            With cmd
                .CommandType = Data.CommandType.StoredProcedure
                .Connection = cnn
                .CommandTimeout = "60"
                .CommandText = "usp_GetProjectGroupSpecsCR"
                .Parameters.AddWithValue("@ProjectNumber", inProjectNum)
                .Parameters.AddWithValue("@ProjectName", strProjectName)
            End With
            dataAdapter = New System.Data.SqlClient.SqlDataAdapter
            dataAdapter.SelectCommand = cmd
            dataAdapter.Fill(LoadReport)
            Dim oRpt As New ReportDocument()
            oRpt.Load(Server.MapPath("ProjectDescriptionReport.rpt"))
            oRpt.Refresh()
            oRpt.SetDataSource(LoadReport)
            'oRpt.OpenSubreport("AttachmentsReport").SetDataSource(LAR)
            oRpt.SetParameterValue("inProjectNum", inProjectNum)
            oRpt.SetParameterValue("strProjectName", strProjectName)
            oRpt.ExportToHttpResponse(ExportFormatType.PortableDocFormat, Response, True, "Projects_DescriptionReport") 'inCompany & "ProjectsReport_Description" & inFiscalYear) <-- Line where the error occures.
What I need to know is what is the proper way to add a subreport to a vb.net application?
From the ways I have tried it is clearly not working and I am out of ideas. I am fairly new to Crystal Reports and this way of coding it.
Any help for this would be greatly appreciated, I've been stuck on this for a while and am finally reaching out to the Crystal Report Specialists.
Thank you in advance,
Bryan

Hi Bryan,
You may want to check the Connection properties also. I think the MS Data.SqlClient.SqlCommand is using the MDAC driver, or could be modified.
If you are connecting to SQL Server 2008 or above you should be using the SQL Native 10 or 11 Client.
As Dell suggests have a look at the samples and if you can use a DSN ( 32 bit or 64 bit ODBC Admin )
Also search for "CRlogger", you'll find how to enable CR's database logging component and may help show you what part is failing.
Don

Crystal Reports Server :Unable to connect: incorrect log on parameters

Hi there, I am getting the following error in Crystal Reports Server when i try to preview or schedule a Crystal Report on an Access 2000 database.
Unable to connect: incorrect log on parameters
The Access database does not have has not username or password and I have left these blank when publishing it, and the Database properties in the Central Management Console also show the username and password as blank.
All other reports are fine is it just reports on the Access 2000 database that give me this errror.
Anyone any ideas.
Thanks

Hi,
ok now you have to make ure that the user used to run the BOBJ services on your BO server (if you hvae windows then this is the local system account), has access to your AccessDB. Normally local users do not have access to network locations so it is advisable to create a domain user, who is allowed to access the directory with your database and is melber of the local administrators group on the BOBJ server. All you have to do then is to configure your BOBJ services (Use the Central Configuration Management utility to do this) to run under the credentials (Log-on-as) of user you created.
Regards,
Stratos

Unable to connect: incorrect log on parameters. (CR with InfoSet Query)

Hi ,
I have created a crystal report with InfoSet Query in Crystal Report Designer 2011. And it works fine, data extraction also works fine. After that, I have uploaded it into BI Platform 4.0. I can display the CR via clicking View from context menu. But it was still failed once I tried to schedule it in BI launch Pad.
The error message is : Error in File ~tmp314c6a47c20e892.rpt: Unable to connect: incorrect log on parameters.
It's so stranger, since i can view it in Designer and viewing it direct in BI lauch Pad. Do you have met this same issue within BI Platform 4.0. Thanks.
Best Regards,
Simon Shen

Not sure if this will help but I finally had success with running a report with a database connection. Here is what I learned from other posts:
1) Make sure you are using the ODBCAD32.exe located in \windows\syswow64 folder. It's the 32 bit Administrator, the one in the Control Panel is the 64 bit versions and it won't work with a 32 bit app.
2) Make sure you use System DSN, not User DSN.
Other tips...
1) Create a blank report (no parameters, no db connection). Run and get that to work first.
2) Create a basic db report (no parameters, one table, one field). Run and get that to work second.
3) If step two fails, try creating a report with different drivers.
4) If step three fails, try installing the latest service packs and repeat 1-3.
5) If step four fails, throw out the software or computer or both

Unable to connect: incorrect log on parameters - In CMC / CR report

I have a CR report that connects to an AS400 and an Excel file. The Excel file is on a Network Drive, and I've made sure that the drive is mapped on my server that the Crystal Reports Server is on. I can sucessfully run this report on this same server in CR XI. However, when I try to Preview or Run Now from the CMC, it says "Unable to connect: Incorrect log on parameters".
I do not have a password on the Excel file, but this is where the problem seems to be. Any ideas?

In case you use CR Server 2008 you won't find services for cache and page server. These services are integrated and controlled by the SIA (Server Intelligent Agent) service.
Start you CCM (Central Configuration Manager), Select Server Intelligent Agent, Right click and choose properties, Untick System Account and provide a user (domain) account which has sufficient rights to access your folder.
Regards,
Tim

Error in SAP running Crystal rpt-Unable to connect,incorrect log parameters

A user modified and saved an existing crystal report. They said that they didnu2019t change report definitions, or change parameters, They just modified the report and saved it. Now, when in SAP users are getting the message 'Login Failed. Unable to connect,incorrect log parameters'. Does anyone know what needs to be done to correct the issue?

Hi ,
have u nake a new addon with the changes ?, just check the connection string and refresh the database connection in report .
rgds,
Premraj

Logon failed. Detail [Database Vendor Code: 1005]

The application make use of ODBC to connect to Oracle database
The way the reports are produced in the current VB application is by using the following line of codes
cryQueryReport.Connect = ObjAdoConnection.sADOconnectstr
cryQueryReport..SQLQuery = sSQL & sSortString
along the way the application also passes String value to the formular fields defined in the reports by making use of the following line of code
cryQueryReport.Formulas(iFormulanumber) = "TITLE_1 = '" & mrsReportItems("TITLE_1") & "'"
Now the codes have been modified to the following to accommodate the upgrade
If Report2 Then
    'open the report
      Set MyReport = CrystalReport2
Else
      Set MyReport = CrystalReport1
End If
'Crystal Report2 includes fields from 9 different tables
'Crystal Report1 includes fields from 10 different tables
For i = 1 To MyReport.Database.Tables.Count
With MyReport.Database.Tables(i)
        Set ConnectionInfo = .ConnectionProperties
        .DllName = "crdb_odbc.dll"
        ConnectionInfo.DeleteAll
        ConnectionInfo.Add "DSN", "DSN Name"
        ConnectionInfo.Add "User Id", "User ID"
        ConnectionInfo.Add "Password", "Password"
End With
Next i
MyReport.SQLQueryString = sSQL & sSortString
For intCounter = 1 To MyReport.FormulaFields.Count
    If MyReport.FormulaFields(intCounter).FormulaFieldName = "TITLE_1" Then
        MyReport.FormulaFields(intCounter).Text = mrsReportItems("TITLE_1")
    End If
Next intCounter
CrystalActiveXReportViewer1.ReportSource = MyReport
CrystalActiveXReportViewer1.ViewReport
The error message pops up that says Run-time Error '2147189176 (80047e48)'   Logon failed. Detail [Database Vendor Code: 1005]
when Ok is clicked, another error message says Run-time Error '214191854 (800473d2)': The remaining text does not appear to be part of the formula.
Could anyone tell me what is wrong with the way the Logon information is coded?
Thank you for your time

This post is being handled through an open support incident with the Developer Support team.
It appears to be an issue upgrading from an earlier version of Crystal Reports using the old crystl32.ocx to the RDC SDK in Visual Basic 6.0.
Elaine
Edited by: Elaine Dove on Jul 6, 2009 2:47 PM

Error: 536 Error in File report filename Unable to connect: incorrect log

Hi
I am getting the above error on a client's machine when executing the following code
for i := 0 to crpe.Subreports.Count - 1 do
for j:=0 to crpe.Subreports<i>.Tables.Count - 1 do
    crpe.Subreports<i>.Tables[j].Path := path;
crpe.Subreports[0];   {This line points the VCL back to the main Report}
for i := 0 to crpe.Tables.Count - 1 do
crpe.Tables<i>.Path := path;
The path and the tables exist. The above code also fails when connecting to a report with no subreports.
I cannot see why it is given me incorrect log on parameters as they are just Paradox tables. On other machines it works just fine.
I am distributing Crystal Reports 2008 SP3 runtime. I am using Delphi 2007 to run the reports.
Any ideas?

Hi
Thank you for the information.
I was hopeful that we could still get a solid solution using this version of Crystal and it is a pity that SAP has stopped all support of Win 32 API. We really cannot justify rewriting the application in a .NET language as we want to continue with a Win32 solution for the near future.
What is frustrating is the fact that it works on various computers with similar OS.
On the particular computer we are having the problem I could not really see any differences in the files loaded in memory apart from this one entry
icudt30.dll ICU Data DLL IBM Corporation and others 3.0.0.1
The version I have loaded in memory is
icudt30.dll ICU Data DLL IBM Corporation and others 12.3.1.684
This dll is installed by Crystal in
C:\Program Files\Business Objects\BusinessObjects Enterprise 12.0\win32_x86
Do you know anything about this DLL?

Scheduled report failing with "Incorrect log on parameters"

I am having trouble with a report scheduled on our Crystal Enterprise Server. I didn't design this report but am responsible for supporting the server, so I am trying to determine if this is a server issue or not.
The user who designs these reports has designed many others without issue. She uses Crystal Reports XI and publishes them to the server. There is a group of similar reports that she has setup to run on a schedule and all run fine except for one. This one gives the error:
Error Message: Error in File C:\Program Files\Business Objects\BusinessObjects Enterprise 11.5\Data\procSched\REPORTS.reportjobserver\~tmpee06be03474eb18.rpt: Unable to connect: incorrect log on parameters. Details: [Database Vendor Code: 18456 ]
Within CR XI, we have double and triple checked the username, password and database connection info. The report is using OLE DB to connect to a SQL 2005 server. I know the credentials are correct because several other reports use the same credentials and work fine.
One other interesting note, if I log into the Central Management Console, I can run the same report manually without errors. It only throws this error when it runs as scheduled.
Hope someone can offer some suggestions. I'm no Crystal expert so please ask if I didn't provide enough information.

Moved to BOE Admin Forums.
In the Properties of the report in the CMC you can set the log on info as well as any parameters when scheduled.
Check the Admin guide on how to
Don

Server cleanup wizard problem - unable to connect to the WSUS Server Database.

I'm trying to run server cleanup wizard.. it starts to run and then after a while it gives me this error:
The WSUS administration console was unable to connect to the WSUS Server Database.
Verify that SQL server is running on the WSUS Server. If the problem persists, try restarting SQL.
System.Data.SqlClient.SqlException -- Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
The statement has been terminated.
Source
.Net SqlClient Data Provider
Stack Trace:
   at Microsoft.UpdateServices.Internal.BaseApi.SoapExceptionProcessor.DeserializeAndThrow(SoapException soapException)
   at Microsoft.UpdateServices.Internal.DatabaseAccess.AdminDataAccessProxy.ExecuteSPSearchUpdates(String updateScopeXml, String preferredCulture, ExtendedPublicationState publicationState)
   at Microsoft.UpdateServices.Internal.BaseApi.Update.SearchUpdates(UpdateScope searchScope, ExtendedPublicationState publicationState, UpdateServer updateServer)
   at Microsoft.UpdateServices.Internal.BaseApi.UpdateServer.GetUpdates(UpdateScope searchScope)
   at Microsoft.UpdateServices.UI.AdminApiAccess.UpdateManager.GetUpdates(ExtendedUpdateScope filter)
   at Microsoft.UpdateServices.UI.AdminApiAccess.WsusSynchronizationInfo.InitializeDerivedProperties()
   at Microsoft.UpdateServices.UI.AdminApiAccess.WsusSynchronizationInfo.get_NewUpdatesCount()
   at Microsoft.UpdateServices.UI.SnapIn.Pages.SyncResultsListPage.GetSyncInfoRow(WsusSynchronizationInfo syncInfo)
   at Microsoft.UpdateServices.UI.SnapIn.Pages.SyncResultsListPage.GetListRows()
Thanks

Some questions:
Are there any other databases running on this Std Edition SQL service?
[a] Yes there are, we have Kaspersky enterprise DB, Report Server DB and local application DB.
Are there any other services running on this WSUS Server?
[b] Yes there are, we have Active Directory, Kaspersky enterprise, SQL Server 2005, and WSUS all on the same server.
How many days since your WSUS server was first installed?
[c] It's been about a year now.
What is the physical size of the SUSDB.mdf file?
[d] 9,666,752 KB
What is the hardware configuration of this machine, including disk drives?
[e] Intel Xeon 1.86, 2GB Ram, HD C: 39GB - E: 25.2, running Windows Server 2003 R2 SP2.
How many client systems are you servicing from this WSUS Server?
[f] Around 40.
What products/classifications are you synchronizing.
[g] Windows XP-vista, Windows Server 2003, Office 2003-2007, SQL Server 2005.
Okay, for starters, you have an underpowered/overextended machine running Active Directory, ASP.NET, and a database server, all on a sub 2GHz CPU with 2GB RAM, and not enough disk spindles. The machine has had WSUS running for about a year and is 9GB in size.
There's no doubt in my mind that some of your performance issues are directly related to disk and database fragmentation.
There's also no doubt that some of your performance issues are directly related to memory starvation.
I'd suggest the following long-term fixes:
1. Get a second machine. Make it a dedicated database server. Provision it accordingly to support servicing multiple database applications.
2. Lacking #1, this machine needs more memory. It also needs more disk spindles. At a minimum the databases being serviced should be on a dedicated physical drive; ideally there would be two dedicated drives allocated for supporting database services. The
For the short-term fixes, do this:
1. During after-hours time, if you don't already have one, build a temporary machine that can act as a DC/GC, while you take this machine temporarily offline.
1. Shutdown the Update Services service, SQL Server database engine, and any other services dependent on the SQL Server database engine (Kapersky, and other reporting applications). Disconnect from the network to temporarly eliminate DC traffic. (You could also shutdown the AD services, but disconnecting the network cable is ever-so-much easier.) Defragment ALL drives.
2. Restart ONLY the SQL Server service. Obtain this SQL script to Reindex the WSUS Databases.
3. Restart ONLY the Update Services service. Attempt the Server Cleanup Wizard again. Run it in two passes. Pass 1 performing everything except remove unused updates. Pass 2 running only remove unused updates.
4. After completion of the Server Cleanup Wizard, reconnect the machine to the network and resume all other services.
5. If you're able to complete #3, secure the services of a well-qualified DBA to determine if there are any misconfigurations in your SQL Server setup that would account for why your WSUS database is 9GB in size -- such as improperly configured autogrowth parameters. Based on the products you're updating and only forty clients, 9GB is about 3x the maximum size I would expect to see in a WSUS database. It's possible this is simply caused by excess unused updates, it's possible it's caused by fragmentation, it's probable it was caused by unnecessary autogrowth of the database due to insufficient update maintenance. You'll want a DBA to assist you in shrinking that database after you successfully run the Database Maintenance and Server Cleanup Wizard.
Lawrence Garvin, M.S., MCITP(x2), MCTS(x5), MCP(x7), MCBMSP
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)

CR2008 unable to connect to Cisco CCX Historical Database (7.1) Vista PC.

Does anybody already have experiance with CR2800 connection to Cisco Historical Database?
I configured according cisco admin guide, which is based on CR XI.
Client DSN config. using SQL Server <IP address of Unified CCX server>\CRSSQL.
Default Port 1433. Default database: db-cra
Then creating a new connection using MS OLE DB Provider for ODBC Driver
Selecting the before created DSN name.
After clicking Finisth the following error message occurs:
Failed to open connection
Details: ADO Error Code 0x80004005
Source: Microsoft OLE DB Provider for ODBC Drivers
Description: Microsoft ODBC SQL Server Driver TCP/IP Sockets SQL
Server does not exist or access denied
SQL State: 08001
Native Error: 17 Database Vendor Code: 17
Thanks for a feedback

Hi Don
This advice helped me a lot! Thank you for your help!
The CR2008 connection to CCX Database could be done successfull.
It might be a helpfull info for others with a similar problem:
Creating a DSN according "Cisco Unified Contact Center Express Historical Reporting Administrator and Devolper Guide 7.0(1)"
(Wich is based on Crystal Report XI).
With the following exeption:
In Step Creating Custom Reports , Befor you Begin, copy files from Cisco CCX Historical Reports folder on Cisco CCX HR client system to C:\Program Files\Business Objects\Crystal Reports 11 folder has to change to:
copy files from Cisco CCX Historical Reports folder on Cisco CCX HR client system to C:\Program Files\Business Objects\BusinessObjects Enterprise 12.0\win32_x86.
The file crw32.exe resides in this folder and not in the folder explained in the Cisco Guide.
Therefore the shorcut to crw32.exe properties, explained in the Cisco guide, has to be as follows:
"C:\Program Files\Business Objects\BusinessObjects Enterprise 12.0\win32_x86\launchHRC.exe" crw32.exe
(Quotation marks included, blank between launchHRC.exe" and crw32.exe.
With this shortcut CR 2008 will start together with Cisco Historical Report Appl. on CCX server.
Starting only 2008 will result in the following error message:
Login failed.
Details: ADO Error Code: 0x80004005
Source: Microsoft OLE DB Provider for ODBC Drivers
Description: [Microsoft][ODBC SQL Server Driver]Cannot generate SSPI
context
SQL State: S1000
As explained in the Cisco Guide after creating a DNS the test will fail by clicking Test Data Source.

Failed to open the connection. Details: [Database Vendor Code: 53 ]

I'm upgrading one of our applications from Visual Studio 2005 to 2010. In the process I'm also switching our reports to run using Stored Procedures instead of Tables/Views. Everything runs fine on development machines after all the migration work. On the server however, it does not work. And I am getting the error message ""
Server is Windows 2003 Server 32 bit. And yes, I have installed the latest runtimes version 13.0.2000.0 on the server. There have been no other changes on the server other than to switch the target framework on the website in question from .net 2 to .net 4, and then to modify the web.config file to remove references to the older Crystal Reports and replace with references to the newer version.
I've seen many other threads on this "failed to open the connection" errors but none of them are my problem except there is one post that remains unanswered where someone had the same Database Vendor Code 53. I don't know what that error means, spent a considerable amount of time researching that before asking this question.
Lastly, it appears that this error only happens when the report is pulling data from a Stored Procedure rather than Tables/Views. If I re-copy the previous reports, they still work.
The ODBC drivers haven't changed, nor should they. They are fully up to date on that server machine.
I can't think of anything else that would be indicative of anything other than this is a bug. Here is the error text as it shows up in the event log:
Event code: 3005
Event message: An unhandled exception has occurred.
Event time: 12/7/2011 3:49:50 PM
Event time (UTC): 12/7/2011 11:49:50 PM
Event ID: 38ce5b5487984e8aa8d2b84493d859a8
Event sequence: 17
Event occurrence: 1
Event detail code: 0
Application information:
    Application domain: /LM/W3SVC/739252194/Root-1-129677751941252500
    Trust level: Full
    Application Virtual Path: /
    Application Path: D:\Websites\ACE5\Clients\TST\
    Machine name: ACE1
Process information:
    Process ID: 5436
    Process name: w3wp.exe
    Account name: NT AUTHORITY\NETWORK SERVICE
Exception information:
    Exception type: InternalException
    Exception message: Failed to open the connection.
Failed to open the connection.
Details: [Database Vendor Code: 53 ]
Failed to open the connection.
Details: [Database Vendor Code: 53 ]
Failed to open the connection.
PackSlipTST0 {638463B4-2196-492A-BD6E-9D82CB1862D5}.rpt
   at CrystalDecisions.ReportAppServer.ConvertDotNetToErom.ThrowDotNetException(Exception e)
   at CrystalDecisions.ReportSource.EromReportSourceBase.ExportToStream(ExportRequestContext reqContext)
   at CrystalDecisions.CrystalReports.Engine.FormatEngine.ExportToStream(ExportRequestContext reqContext)
   at CrystalDecisions.CrystalReports.Engine.ReportDocument.ExportToStream(ExportOptions options)
   at CrystalDecisions.CrystalReports.Engine.ReportDocument.ExportToHttpResponse(ExportOptions options, HttpResponse response, Boolean asAttachment, String attachmentName)
   at CrystalDecisions.CrystalReports.Engine.ReportDocument.ExportToHttpResponse(ExportFormatType formatType, HttpResponse response, Boolean asAttachment, String attachmentName)
   at Distribution_PackingSlips_default.ExportPackingSlips(String CrystalReportPath, Boolean UseStoredProcedure)
   at Distribution_PackingSlips_default.Page_Load(Object sender, EventArgs e)
   at System.Web.Util.CalliHelper.EventArgFunctionCaller(IntPtr fp, Object o, Object t, EventArgs e)
   at System.Web.Util.CalliEventHandlerDelegateProxy.Callback(Object sender, EventArgs e)
   at System.Web.UI.Control.OnLoad(EventArgs e)
   at System.Web.UI.Control.LoadRecursive()
   at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
Failed to open the connection.
Failed to open the connection.
Details: [Database Vendor Code: 53 ]
Failed to open the connection.
Details: [Database Vendor Code: 53 ]
Failed to open the connection.
PackSlipTST0 {638463B4-2196-492A-BD6E-9D82CB1862D5}.rpt
   at CrystalDecisions.ReportAppServer.Controllers.ReportSourceClass.Export(ExportOptions pExportOptions, RequestContext pRequestContext)
   at CrystalDecisions.ReportSource.EromReportSourceBase.ExportToStream(ExportRequestContext reqContext)

Lots of great info here, except for the database; MS SQL? Oracle? Etc?
Database Vendor Code 53 is an error code that the CR engine simply passes straight from the database it's self. E.g.; look at your database error code and you should be able to find a verbose description of the error.
As a test, what happens if you add the report to your project and run it in the CR design part of the .NET IDE?
- A quick google search of Error 53 (for MS SQL - an assumption) comes up with a number of good hits. E.g.;
http://social.msdn.microsoft.com/Forums/en-AU/sqlgetstarted/thread/27684811-1a59-4273-b7ed-3cc990b4f20a
Ludek
Follow us on Twitter http://twitter.com/SAPCRNetSup
Got Enhancement ideas? Try the [SAP Idea Place|https://ideas.sap.com/community/products_and_solutions/crystalreports]
Edited by: Ludek Uher on Dec 8, 2011 6:31 AM

Failed to open the connection. Details: [Database Vendor Code: 12154].

I have installed Crystal reports server 2008 VI on a Windows 2008 64bit OS. I have added SQL server and Oracle reports through CMC. I then installed Oracle 10g client 32bit on the server and created and tested the required DSNs using ODBC 32bit. All the testings are successfull.
Now when I try to run my Oracle report through CMC it prompts for the parameters and when I enter them and click ok, gives me the following error:
Failed to open the connection. Details: [Database Vendor Code: 12154].
I have the same exact setup on a different server which has a 32 bit windows 2008 server OS and could run the same reports through CMC.
Is there away to fix this in the 64 bit OS?
I did a yahoo search and someone had a similar problem with Crystal RAS and Oracle.
And there is mentions that this is an issue with 32 bit ODBC drivers on 64bit wondows OS.The parentheses in the default file location, C:\Program Files (x86), causes problems with the ODBC driver and the workarouns in re-installing Crystal RAS on a different folder.
Full description is at (http://www.tririga.info/)
Is this the case with Crystal report server 2008 VI? I already got users using the InfoView to run SQL reports and doing this will have to put the application offline atlease for a say.
Any help is greatly appreciated.

Vasana,
Resolution: Failed to Open the Connection.
First:
If the Crystal Report is using 32-bit version of Microsoft ODBC then the Window 2008 server must also have 32-bit version of Microsoft ODBC. The 32- bit version of Odbcad32.exe is located in the %systemdrive%\Windows\SysWoW64 folder.
On the Windows 2008 server, execute Odbcad32.exe by clicking start and run and entering the following: C:\Window\SysWow64\ODBC32.exe.
Then:
The Windows 2008 server ODBC Data Source Administrator must have the same System Data Source Server and Database Names that is used to run the Crystal Report.
e.g. Crystal Report points to server ABC and database EFG (ABC_efg); then the ODBC connections on the Windows 2008 Server must also point to the same server ABC and database EFG (abc_efg) listed.

Outlook is unable to connect to the proxy server.(Error Code 10)

Hi,
I had problems with RPC proxy, I was trying to setup cutover migration.
So I read somewhere that i need to change the certprincipalname with Set-Outlookprovider.
But after this change my outlook was not working anymore
The settings before the change were:
Name Server CertPrincipalName TTL
EXCH
1
EXPR
1
WEB
1
So I set this back to the original (above) but this didn't helped...
Outlook 2013 and Exchange 2013
There is a problem with the proxy server's security certificate. The name on the security certificate is invalid or does not match the name of the target site mail.abc-company.com.
Outlook is unable to connect to the proxy server.(Error Code 10)

Hi,
Please make sure the mail.abc-company.com is included in your Exchange certificate which has been assigned with IIS service.
If possible, please run the following command for double check:
Get-ExchangeCertificate | FL
For Autodiscover service, please run
Test E-mail AutoConfiguration to check if the connection is successful in Log tab and confirm the other services URL can use proper namespace in Results tab for request access.
If the Autodiscover service fails, please create a SRV record with mail.abc-company.com for Autodiscover service to have a try:
http://support2.microsoft.com/kb/940881/en-us
Regards,
Winnie Liang
TechNet Community Support

Unable to connect: incorrect log on parameters [Database Vendor Code: 1005]

Similar Messages

Maybe you are looking for