Home Server

Connection Timeout

edited March 2010 in Server
Hi

On my Windows 2003 server, which is giving the AV in ntdll.dll, my report
now consistently fails to run and ends with a Connection Timeout error.

Previously there was a 50-50 chance of it running and displaying the .pdf
report, or failing with the ntdll.dll AV. Apart from changing the printer
so that a real printer is the default device (it was set to some pdf
printer), I do not perceive anything has changed on the server.

In the cache folder various sub folders have been created, including a
report.pdf of size 1kb which appears to be empty.

The Server and webTier are both running on the same machine and I attach the
logs file from both below.

There is no firewall running on the machine to block the port 1333. I have
tried increasing the web tier connection time out but this only just delays
the inevitable.

I am running report Builder 10.07.

Any thoughts as to where the problem may lie? Unfortunately dumping the
server in the Ocean is not a valid option.

I know RB works and I have run the Server report many times before so it
must be something machine specific.

Regards to all

Philip L Jackson



2010-03-07T21:48:06.885Connection timed
out.weException1{10BA2E33-4525-4135-8EDD-21953CA8DC74}




Server Log

2010-03-07T21:47:06.698Validate session
parameters
requestseServiceRequest877ValidateSessionParametersSession
Service
2010-03-07T21:47:06.698Validate session
parameters
response: -1seServiceResponse901ValidateSessionParametersSession
Service
2010-03-07T21:47:06.698Session
StartseInformation0{6F6D536C-65DF-4772-BA43-CC1D7B702EBC}
2010-03-07T21:47:06.698Request
AutoSearch parameters:
reportFiles\reportfiles\AdsPDAIntruderseServiceRequest1004GetAutoSearchParametersReport
Publishing{6F6D536C-65DF-4772-BA43-CC1D7B702EBC}
2010-03-07T21:47:06.854Send AutoSearch
parameters:
reportFiles\reportfiles\AdsPDAIntruderseServiceResponse1001GetAutoSearchParametersReport
Publishing{6F6D536C-65DF-4772-BA43-CC1D7B702EBC}
2010-03-07T21:47:06.870Validate session
parameters
requestseServiceRequest877ValidateSessionParametersSession
Service
2010-03-07T21:47:06.870Validate session
parameters
response: -1seServiceResponse901ValidateSessionParametersSession
Service
2010-03-07T21:47:06.870Session
StartseInformation0{81042F69-2339-44CF-9D09-179027153160}
2010-03-07T21:47:06.870Request page 1:
reportFiles\reportfiles\AdsPDAIntruderseServiceRequest1142PublishReportReport
Publishing{81042F69-2339-44CF-9D09-179027153160}

Comments

  • edited March 2010

    Try testing whether the error happens with every report or just one or some.

    As a test, try using the Demos\Clients\Client Explorer project to connect to
    the server and generate a PDF via the ClientReport.

    Before testing, reboot the machine.

    If you think it is a printer driver issue, try modifying the report to use
    printer name 'Screen'


    This rbWiki a 'How To' shows how to write to the server log, you could
    perhaps add code to the server to write some custom messages to trouble
    shoot.

    http://www.digital-metaphors.com/rbWiki/Server/Report_Server/How_To...Write_to_the_Server_Log




    --
    Nard Moseley
    Digital Metaphors
    www.digital-metaphors.com



    Best regards,

    Nard Moseley
    Digital Metaphors
    www.digital-metaphors.com
This discussion has been closed.