Logon failed. Details: ADO Error Code: 0x Source: Microsoft OLE DB Provider

[Former Member]

I have been trying for 2 days now to move a report from my development machine to our webserver. But it simply won't work. I've gotten these to work before but they were always dealing with an SQL data base and in this instance I am trying to connect to some older Visual FoxPro tables (dbfs not .DBCs).

Like I said this works perfectly on my development PC but not on the webserver.

I am developing in ASP.NET 2.0 VS 2005 using Visual Basic.

Here is the last bit of code that I tried that still didn't work along with the error I'm receiving.

Dim fname As String = ""

fname = Request.PhysicalApplicationPath & "clubadmin\Club Backlog Report.rpt"

Me.CrystalReportSource1.ReportDocument.Load(fname)

Me.CrystalReportViewer1.ParameterFieldInfo.Clear()

Dim ParamFields As ParameterFields = Me.CrystalReportViewer1.ParameterFieldInfo

Dim p_SalesRep As New ParameterField

p_SalesRep.Name = "SalesRep"

Dim p_SalesRep_Value As New ParameterDiscreteValue

p_SalesRep_Value.Value = Session("RepCode")

p_SalesRep.CurrentValues.Add(p_SalesRep_Value)

ParamFields.Add(p_SalesRep)

Dim myConnectionInfo As New ConnectionInfo

myConnectionInfo.ServerName = "
sbt-server\sbt\pro50\01"

myConnectionInfo.UserID = "administrator"

myConnectionInfo.Password = "112233"

NOTE: administrator has full permissions on all servers.

Here is the error I'm getting. Any help would be greatly appreciated.

Logon failed. Details: ADO Error Code: 0x Source: Microsoft OLE DB Provider for Visual FoxPro Description: Invalid path or file name. Native Error: Error in File C:\DOCUME_{1\WEBSERV\ASPNET\LOCALS}1\Temp\Club Backlog Report {8B57478B-2CE4-4BD2-B3D4-9F34927902B6}.rpt: Unable to connect: incorrect log on parameters

[Former Member · Accepted solution]

Hi, Tom;

I would start by looking at permissions. You said the Administrator account has full permissions, but which account is running the IIS process? Try changing the application pool to run as System, or the Administrator account. Also, ensure the account that is running the IIS process to the Temp folder that is mentioned in the error.

Regards,

Jonathan