ISQL query fails after reboot

Good morning we are having a wierd issue with our Windows 2003 server and SQ
L
2000 sp4 server. From the client side we use isql queries. When we reboot
the server the isql queries that are larger then 512 bytes will fail from
both the client or from the sql server itself smaller ones will work. Query
analyzer works perfectly. The strange part is if we run any query in either
query analyzer or using isql then restart the services everything works. We
also have another server which appears to be identical and everything works
with no issues. If anyone can point me in the right direction to
troubleshoot this issue it would be greatly appreciated.
Richard TracyHave you tried using OSQL instead of ISQL?
In terms of why you are having problems, that's hard to say
without knowing what error message you receive when running
the queries that fail. As a guess, it sounds like you could
be running into issues related to ISQL and the packet size.
Try using the -a switch and increase the default packet
size.
-Sue
On Wed, 12 Apr 2006 07:50:02 -0700, Richard Tracy
<RichardTracy@.discussions.microsoft.com> wrote:

>Good morning we are having a wierd issue with our Windows 2003 server and S
QL
>2000 sp4 server. From the client side we use isql queries. When we reboot
>the server the isql queries that are larger then 512 bytes will fail from
>both the client or from the sql server itself smaller ones will work. Quer
y
>analyzer works perfectly. The strange part is if we run any query in eithe
r
>query analyzer or using isql then restart the services everything works. W
e
>also have another server which appears to be identical and everything works
>with no issues. If anyone can point me in the right direction to
>troubleshoot this issue it would be greatly appreciated.
>Richard Tracy|||We have tried using the -a with no success the error we get is a network
error even if we run it on the localhost. We have also uninstalled sql
server and tried it on a plain vanilla sql server with no success. Any idea
s
of how to troubleshoot this would be greatly appreciated
Thank you
"Sue Hoegemeier" wrote:

> Have you tried using OSQL instead of ISQL?
> In terms of why you are having problems, that's hard to say
> without knowing what error message you receive when running
> the queries that fail. As a guess, it sounds like you could
> be running into issues related to ISQL and the packet size.
> Try using the -a switch and increase the default packet
> size.
> -Sue
> On Wed, 12 Apr 2006 07:50:02 -0700, Richard Tracy
> <RichardTracy@.discussions.microsoft.com> wrote:
>
>|||You really have to look at the exact full error messages and
the error number. You can try googling on those or try
posting with the full information. Connectivity issues are
generally difficult to troubleshoot via newsgroups. If you
want to do that, you need to post a lot of details, full
error messages, configurations, exact steps to reproduce,
etc. Even then, it can be difficult via newsgroups.
-Sue
On Thu, 13 Apr 2006 23:18:02 -0700, Richard Tracy
<RichardTracy@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>We have tried using the -a with no success the error we get is a network
>error even if we run it on the localhost. We have also uninstalled sql
>server and tried it on a plain vanilla sql server with no success. Any ide
as
>of how to troubleshoot this would be greatly appreciated
>Thank you
>"Sue Hoegemeier" wrote:
>|||Thank you for your help Sue. We found what the issue was, we found it was
being caused by an application called NCS (Native Command Substitution. It
is installed with lightspeed which was created by imceda software which has
been bought by quest software. We removed this software and it has worked
without an issue. Again thak you very much for your help
"Sue Hoegemeier" wrote:

> You really have to look at the exact full error messages and
> the error number. You can try googling on those or try
> posting with the full information. Connectivity issues are
> generally difficult to troubleshoot via newsgroups. If you
> want to do that, you need to post a lot of details, full
> error messages, configurations, exact steps to reproduce,
> etc. Even then, it can be difficult via newsgroups.
> -Sue
> On Thu, 13 Apr 2006 23:18:02 -0700, Richard Tracy
> <RichardTracy@.discussions.microsoft.com> wrote:
>
>|||That's interesting one ...thanks for posting back.
-Sue
On Sun, 16 Apr 2006 14:01:02 -0700, Richard Tracy
<RichardTracy@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Thank you for your help Sue. We found what the issue was, we found it was
>being caused by an application called NCS (Native Command Substitution. It
>is installed with lightspeed which was created by imceda software which has
>been bought by quest software. We removed this software and it has worked
>without an issue. Again thak you very much for your help
>"Sue Hoegemeier" wrote:
>