I have an Access front-end connected to a SQL Server database. A report that
used to work fine still opens fine in Preview mode, but when you go to print,
after a long delay it finally generates the error:
Connection failed:
SQLState: '01000'
SQL Server Error: 10060
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen
{PreLoginHandshake()}.
Connection Failed:
SQL State: '08001'
SQL Server Error: 11
[Microsoft][ODBC SQL Server Driver][DBNETLIB]General network error.Check
your network documentation.
and hangs up the server (the users have been restarting it to get back up
and running).
Would appreciate any ideas to help me resolve this. I have copied the
database and app to another system and did not have any problems there, so I
suspect the problem is with SQL Server on the first system.
Carole
Hello Carole,
Because the issue does not occur when previewing, it seems to be related to
printer driver. I suggest that you use the printer "Microsoft Office
document image writer" as default printer. Does the issue occurs at this
time?
Also, please install the latest MDAC 2.8 sp1 on the cleint to test the
sitaution.
If you copy the database to a different client, can you reproduce the
issue? Have a great day!
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
Business-Critical Phone Support (BCPS) provides you with technical phone
support at no charge during critical LAN outages or "business down"
situations. This benefit is available 24 hours a day, 7 days a week to all
Microsoft technology partners in the United States and Canada.
This and other support options are available here:
BCPS:
https://partner.microsoft.com/US/tec...rview/40010469
Others: https://partner.microsoft.com/US/tec...pportoverview/
If you are outside the United States, please visit our International
Support page:
http://support.microsoft.com/default...national.aspx.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
| Thread-Topic: Error 10060
| thread-index: AcWdB9WyA+PsIdd4R12C2kKVL3Rfsg==
| X-WBNR-Posting-Host: 66.119.205.215
| From: "=?Utf-8?B?Q0R1dHRsaW5nZXI=?=" <h2oPower@.newsgroup.nospam>
| Subject: Error 10060
| Date: Tue, 9 Aug 2005 10:29:02 -0700
| Lines: 23
| Message-ID: <4F683860-86FB-4FF9-83E5-5FD0D6277F3E@.microsoft.com>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
| Newsgroups: microsoft.public.sqlserver.odbc
| NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
| Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA02.phx.gbl!TK2MSF TNGXA03.phx.gbl
| Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.odbc:2571
| X-Tomcat-NG: microsoft.public.sqlserver.odbc
|
| I have an Access front-end connected to a SQL Server database. A report
that
| used to work fine still opens fine in Preview mode, but when you go to
print,
| after a long delay it finally generates the error:
|
| Connection failed:
| SQLState: '01000'
| SQL Server Error: 10060
| [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen
| {PreLoginHandshake()}.
| Connection Failed:
| SQL State: '08001'
| SQL Server Error: 11
| [Microsoft][ODBC SQL Server Driver][DBNETLIB]General network error.Check
| your network documentation.
|
| and hangs up the server (the users have been restarting it to get back up
| and running).
|
| Would appreciate any ideas to help me resolve this. I have copied the
| database and app to another system and did not have any problems there,
so I
| suspect the problem is with SQL Server on the first system.
| --
| Carole
|
|||This print job has to go to a specific printer, which is also used for
numerous other reports that don't lock up SQL Server. If I use the image
writer as my default printer, won't that just create a file on disk -- that
isn't a viable solution.
I cannot reproduce the error on another server, though it happens fairly
consistently from all the clients on the problem server.
Carole
"Peter Yang [MSFT]" wrote:
> Hello Carole,
> Because the issue does not occur when previewing, it seems to be related to
> printer driver. I suggest that you use the printer "Microsoft Office
> document image writer" as default printer. Does the issue occurs at this
> time?
> Also, please install the latest MDAC 2.8 sp1 on the cleint to test the
> sitaution.
> If you copy the database to a different client, can you reproduce the
> issue? Have a great day!
> Best Regards,
> Peter Yang
> MCSE2000/2003, MCSA, MCDBA
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ================================================== ===
> Business-Critical Phone Support (BCPS) provides you with technical phone
> support at no charge during critical LAN outages or "business down"
> situations. This benefit is available 24 hours a day, 7 days a week to all
> Microsoft technology partners in the United States and Canada.
> This and other support options are available here:
> BCPS:
> https://partner.microsoft.com/US/tec...rview/40010469
> Others: https://partner.microsoft.com/US/tec...pportoverview/
> If you are outside the United States, please visit our International
> Support page:
> http://support.microsoft.com/default...national.aspx.
> ================================================== ===
> This posting is provided "AS IS" with no warranties, and confers no rights.
> --
> | Thread-Topic: Error 10060
> | thread-index: AcWdB9WyA+PsIdd4R12C2kKVL3Rfsg==
> | X-WBNR-Posting-Host: 66.119.205.215
> | From: "=?Utf-8?B?Q0R1dHRsaW5nZXI=?=" <h2oPower@.newsgroup.nospam>
> | Subject: Error 10060
> | Date: Tue, 9 Aug 2005 10:29:02 -0700
> | Lines: 23
> | Message-ID: <4F683860-86FB-4FF9-83E5-5FD0D6277F3E@.microsoft.com>
> | MIME-Version: 1.0
> | Content-Type: text/plain;
> | charset="Utf-8"
> | Content-Transfer-Encoding: 7bit
> | X-Newsreader: Microsoft CDO for Windows 2000
> | Content-Class: urn:content-classes:message
> | Importance: normal
> | Priority: normal
> | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
> | Newsgroups: microsoft.public.sqlserver.odbc
> | NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
> | Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA02.phx.gbl!TK2MSF TNGXA03.phx.gbl
> | Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.odbc:2571
> | X-Tomcat-NG: microsoft.public.sqlserver.odbc
> |
> | I have an Access front-end connected to a SQL Server database. A report
> that
> | used to work fine still opens fine in Preview mode, but when you go to
> print,
> | after a long delay it finally generates the error:
> |
> | Connection failed:
> | SQLState: '01000'
> | SQL Server Error: 10060
> | [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen
> | {PreLoginHandshake()}.
> | Connection Failed:
> | SQL State: '08001'
> | SQL Server Error: 11
> | [Microsoft][ODBC SQL Server Driver][DBNETLIB]General network error.Check
> | your network documentation.
> |
> | and hangs up the server (the users have been restarting it to get back up
> | and running).
> |
> | Would appreciate any ideas to help me resolve this. I have copied the
> | database and app to another system and did not have any problems there,
> so I
> | suspect the problem is with SQL Server on the first system.
> | --
> | Carole
> |
>
|||Hello Carole,
I'd like to explain the suggestions I provided is just to narrow down the
issue, other than a permanet solution. If the "Microsoft Office document
image writer" works. We shall take some actions to reolve the printer
driver or related issue on this machine. Or, we shall find other possible
cause.
To check if the issue is relate to user profile, I suggest that you create
a new user on this machine with admin rights and log on as this new user to
test the situation.
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
| Thread-Topic: Error 10060
| thread-index: AcWd3YxRa9b6SiYZRW+JwZSYJajkQg==
| X-WBNR-Posting-Host: 66.119.205.215
| From: "=?Utf-8?B?Q0R1dHRsaW5nZXI=?=" <h2oPower@.newsgroup.nospam>
| References: <4F683860-86FB-4FF9-83E5-5FD0D6277F3E@.microsoft.com>
<WzR0VIXnFHA.3472@.TK2MSFTNGXA01.phx.gbl>
| Subject: RE: Error 10060
| Date: Wed, 10 Aug 2005 11:58:51 -0700
| Lines: 110
| Message-ID: <86B3C55F-3647-4E4B-9414-B6137D3AD6CE@.microsoft.com>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
| Newsgroups: microsoft.public.sqlserver.odbc
| NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
| Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
| Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.odbc:2577
| X-Tomcat-NG: microsoft.public.sqlserver.odbc
|
| This print job has to go to a specific printer, which is also used for
| numerous other reports that don't lock up SQL Server. If I use the image
| writer as my default printer, won't that just create a file on disk --
that
| isn't a viable solution.
|
| I cannot reproduce the error on another server, though it happens fairly
| consistently from all the clients on the problem server.
| --
| Carole
|
|
| "Peter Yang [MSFT]" wrote:
|
| > Hello Carole,
| >
| > Because the issue does not occur when previewing, it seems to be
related to
| > printer driver. I suggest that you use the printer "Microsoft Office
| > document image writer" as default printer. Does the issue occurs at
this
| > time?
| >
| > Also, please install the latest MDAC 2.8 sp1 on the cleint to test the
| > sitaution.
| >
| > If you copy the database to a different client, can you reproduce the
| > issue? Have a great day!
| >
| > Best Regards,
| >
| > Peter Yang
| > MCSE2000/2003, MCSA, MCDBA
| > Microsoft Online Partner Support
| >
| > When responding to posts, please "Reply to Group" via your newsreader
so
| > that others may learn and benefit from your issue.
| >
| > ================================================== ===
| >
| > Business-Critical Phone Support (BCPS) provides you with technical
phone
| > support at no charge during critical LAN outages or "business down"
| > situations. This benefit is available 24 hours a day, 7 days a week to
all
| > Microsoft technology partners in the United States and Canada.
| >
| > This and other support options are available here:
| >
| > BCPS:
| >
https://partner.microsoft.com/US/tec...rview/40010469
| >
| > Others:
https://partner.microsoft.com/US/tec...pportoverview/
| >
| > If you are outside the United States, please visit our International
| > Support page:
| > http://support.microsoft.com/default...national.aspx.
| >
| > ================================================== ===
| >
| > This posting is provided "AS IS" with no warranties, and confers no
rights.
| >
| > --
| > | Thread-Topic: Error 10060
| > | thread-index: AcWdB9WyA+PsIdd4R12C2kKVL3Rfsg==
| > | X-WBNR-Posting-Host: 66.119.205.215
| > | From: "=?Utf-8?B?Q0R1dHRsaW5nZXI=?=" <h2oPower@.newsgroup.nospam>
| > | Subject: Error 10060
| > | Date: Tue, 9 Aug 2005 10:29:02 -0700
| > | Lines: 23
| > | Message-ID: <4F683860-86FB-4FF9-83E5-5FD0D6277F3E@.microsoft.com>
| > | MIME-Version: 1.0
| > | Content-Type: text/plain;
| > | charset="Utf-8"
| > | Content-Transfer-Encoding: 7bit
| > | X-Newsreader: Microsoft CDO for Windows 2000
| > | Content-Class: urn:content-classes:message
| > | Importance: normal
| > | Priority: normal
| > | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
| > | Newsgroups: microsoft.public.sqlserver.odbc
| > | NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
| > | Path:
TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA02.phx.gbl!TK2MSF TNGXA03.phx.gbl
| > | Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.odbc:2571
| > | X-Tomcat-NG: microsoft.public.sqlserver.odbc
| > |
| > | I have an Access front-end connected to a SQL Server database. A
report
| > that
| > | used to work fine still opens fine in Preview mode, but when you go
to
| > print,
| > | after a long delay it finally generates the error:
| > |
| > | Connection failed:
| > | SQLState: '01000'
| > | SQL Server Error: 10060
| > | [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen
| > | {PreLoginHandshake()}.
| > | Connection Failed:
| > | SQL State: '08001'
| > | SQL Server Error: 11
| > | [Microsoft][ODBC SQL Server Driver][DBNETLIB]General network
error.Check
| > | your network documentation.
| > |
| > | and hangs up the server (the users have been restarting it to get
back up
| > | and running).
| > |
| > | Would appreciate any ideas to help me resolve this. I have copied the
| > | database and app to another system and did not have any problems
there,
| > so I
| > | suspect the problem is with SQL Server on the first system.
| > | --
| > | Carole
| > |
| >
| >
|
No comments:
Post a Comment