Crystal Reports Server 2008 TRIAL version: Error returned from Windows Sockets API: 0 (also 10054)

[Former Member]

We are upgrading our development environment from XP and Visual Studio 2008 with Crystal Reports Server XI SP2, to Windows 7 64-bit and Visual Studio 2010 with Crystal Reports Server 2008. I keep getting an error when trying to load a report via RAS: "Failed to connect to server xxx. Error returned from Windows Sockets API: 0" Looks like it's in clientdoc.dll.

Crystal Reports Server 2008 TRIAL Version Error received when trying to load a ReportDoccument object without specifying a port:

"Failed to connect to server "XYZ" Error returned from Windows Sockets API : 0."

  System.Collections.ListDictionaryInternal

  &H80041015

  Nothing

  &H80041015

  Nothing

  False

  "clientdoc.dll"

  at
CrystalDecisions.ReportAppServer.ClientDoc.ReportClientDocumentClass.Open(Object&
DocumentPath, Int32 Options) at
CrystalDecisions.ReportAppServer.ReportClientDocumentWrapper.Open(Object& DocumentPath,
Int32 Options) at
CrystalDecisions.ReportAppServer.ReportClientDocumentWrapper.EnsureDocumentIsOpened()

***************************************************

If I change the Report Application Server to use a specific port and specify that port with the servername on the load, then the error received when trying to load a ReportDoccument object becomes:

"Failed to receive reply from server: Error returned from Windows Sockets API : recv (buffer) 10054

***************************************************

NOTE:

Using “Modules in Memory Viewer” I see the following two versions of clientdoc.dll are loaded when the error occurs:

crystalras.exe from Crystal Reports Server 2008 Trial Version loads clientdoc.dll (12.3.0.601) from c:\program files
(x86)\business objects\business objects enterprise 12.0\win32_x86\clientdoc.dll

and

w3wp.exe (our IIS app running in 32-bit mode built with Visual Studio 2010) loads clientdoc.dll (13.0.3.612) from c:\program
files (x86)\sap business objects\crystal reports for .net framework 4.0\common\sap business objects enterprise xi 4.0\win32x86\clientdoc.dll.

***************************************************

Can anyone please help?

Thank you.

Tom

[Former Member]

Replying for Tom Broderick

We logged a "Customer Message" or support incident and we were able to fix our issue as follows:

Using the Central Management Console,

1. enable "Guest" account and set to concurrent user.

2. add -ipport "1566" to Command Line Parameters for Report Application Server

3. add -reportdirectory "C:/OurReports" to Command Line Parameters for Report Application Server.

That's it. Note that we are using unmanged RAS.

Thanks for the help.

David

[Former Member]

One more important thing: we also removed CR for Visual Studio 2010 and went back to using Visual Studio 2008.

David

[former_member183750]

What RAS and CR assemblies are you referencing, and what are their versions?

- Ludek

Follow us on Twitter

Got Enhancement ideas? Try the SAP Idea Place

Share Your Knowledge in SCN Topic Spaces

[Former Member]

Ludek,

We are referencing the following:

CrystalDecisions.CrystalReports.Engine version 13.0.3.612 (13.0.2000.0)

CrystalDecisions.Shared 13.0.3.612 (13.0.2000.0)

CrystalDecisions.Web 13.0.3.612 (13.0.2000.0)

We are using the ReportDocument object, not the ReportClientDocument object, as we always have in the past with CRS XI.

Thank you.

Tom.

[Former Member]

Ludek,

One other important thing: we are using out-of-process session state as we always have with CRS XI.

If I use in-process session state then I can open our reports as follows:

crReport.Load("rassdk://" & ConfigurationSettings.AppSettings("ReportLocation") & m_sCrystalReport & ".rpt", OpenReportMethod.OpenReportByTempCopy)

where crReport is a ReportDocument object.

Tom.

[Adam_Stone]

Your modules shows that two versions of Crystal Reports are being loaded, so that should be the first clue.  Second clue is the many posts already on here that says you cannot use the Crystal Reports for Visual Studio 2010 to connect to an Enterprise Server (RAS) to run reports.  Lastly, Crystal Reports Server 2008 does not support development in VS2010, you should be using VS2008.

[Former Member]

Adam,

Thank you for your suggestions. I will investigate this right now and post my results here.

Tom.