Showing posts with label edition. Show all posts
Showing posts with label edition. Show all posts

Friday, March 30, 2012

Network error.

Hi,
I am facing a weird network problem. I am running a SQL 2000 SP2
enterprise edition over a Windows 2003 enterprise edition machine.
I am getting the network error messages (see below) while trying to
connect to the server. However if i am connected to the server before
the problem occurs i can continue running queries from the query
analyzer but cannot use the object browser to view the tables/ views
etc.
The problem is temporarily fixed if i restart the sql server service
but reappears after some times.
Seems to me it is is not a network problem otherwise the connection
would have broken.
Error 1:
[ODBC SQL Server Driver][DBNETLIB]General network error. Check your
network documentation.
Error 2:
[ODBC SQL Server Driver][DBNETLIB]ConnectionRead (recv()).
Any idea why this is happening?
Thanks in advance
Taw.
Consider applying SP4, or at least SP3a, to your SQL 2000 instance.
Hope this helps.
Dan Guzman
SQL Server MVP
"Taw" <tawfiq.choudhury@.grameenphone.com> wrote in message
news:1185800793.766706.9030@.l70g2000hse.googlegrou ps.com...
> Hi,
> I am facing a weird network problem. I am running a SQL 2000 SP2
> enterprise edition over a Windows 2003 enterprise edition machine.
> I am getting the network error messages (see below) while trying to
> connect to the server. However if i am connected to the server before
> the problem occurs i can continue running queries from the query
> analyzer but cannot use the object browser to view the tables/ views
> etc.
> The problem is temporarily fixed if i restart the sql server service
> but reappears after some times.
> Seems to me it is is not a network problem otherwise the connection
> would have broken.
> Error 1:
> [ODBC SQL Server Driver][DBNETLIB]General network error. Check your
> network documentation.
> Error 2:
> [ODBC SQL Server Driver][DBNETLIB]ConnectionRead (recv()).
> Any idea why this is happening?
> Thanks in advance
> Taw.
>

Network error.

Hi,
I am facing a weird network problem. I am running a SQL 2000 SP2
enterprise edition over a Windows 2003 enterprise edition machine.
I am getting the network error messages (see below) while trying to
connect to the server. However if i am connected to the server before
the problem occurs i can continue running queries from the query
analyzer but cannot use the object browser to view the tables/ views
etc.
The problem is temporarily fixed if i restart the sql server service
but reappears after some times.
Seems to me it is is not a network problem otherwise the connection
would have broken.
Error 1:
[ODBC SQL Server Driver][DBNETLIB]General network error. Check your
network documentation.
Error 2:
[ODBC SQL Server Driver][DBNETLIB]ConnectionRead (recv()).
Any idea why this is happening?
Thanks in advance
Taw.Consider applying SP4, or at least SP3a, to your SQL 2000 instance.
Hope this helps.
Dan Guzman
SQL Server MVP
"Taw" <tawfiq.choudhury@.grameenphone.com> wrote in message
news:1185800793.766706.9030@.l70g2000hse.googlegroups.com...
> Hi,
> I am facing a weird network problem. I am running a SQL 2000 SP2
> enterprise edition over a Windows 2003 enterprise edition machine.
> I am getting the network error messages (see below) while trying to
> connect to the server. However if i am connected to the server before
> the problem occurs i can continue running queries from the query
> analyzer but cannot use the object browser to view the tables/ views
> etc.
> The problem is temporarily fixed if i restart the sql server service
> but reappears after some times.
> Seems to me it is is not a network problem otherwise the connection
> would have broken.
> Error 1:
> [ODBC SQL Server Driver][DBNETLIB]General network error. Check you
r
> network documentation.
> Error 2:
> [ODBC SQL Server Driver][DBNETLIB]ConnectionRead (recv()).
> Any idea why this is happening?
> Thanks in advance
> Taw.
>

Network error.

Hi,
I am facing a weird network problem. I am running a SQL 2000 SP2
enterprise edition over a Windows 2003 enterprise edition machine.
I am getting the network error messages (see below) while trying to
connect to the server. However if i am connected to the server before
the problem occurs i can continue running queries from the query
analyzer but cannot use the object browser to view the tables/ views
etc.
The problem is temporarily fixed if i restart the sql server service
but reappears after some times.
Seems to me it is is not a network problem otherwise the connection
would have broken.
Error 1:
[ODBC SQL Server Driver][DBNETLIB]General network error. Check your
network documentation.
Error 2:
[ODBC SQL Server Driver][DBNETLIB]ConnectionRead (recv()).
Any idea why this is happening?
Thanks in advance
Taw.Consider applying SP4, or at least SP3a, to your SQL 2000 instance.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Taw" <tawfiq.choudhury@.grameenphone.com> wrote in message
news:1185800793.766706.9030@.l70g2000hse.googlegroups.com...
> Hi,
> I am facing a weird network problem. I am running a SQL 2000 SP2
> enterprise edition over a Windows 2003 enterprise edition machine.
> I am getting the network error messages (see below) while trying to
> connect to the server. However if i am connected to the server before
> the problem occurs i can continue running queries from the query
> analyzer but cannot use the object browser to view the tables/ views
> etc.
> The problem is temporarily fixed if i restart the sql server service
> but reappears after some times.
> Seems to me it is is not a network problem otherwise the connection
> would have broken.
> Error 1:
> [ODBC SQL Server Driver][DBNETLIB]General network error. Check your
> network documentation.
> Error 2:
> [ODBC SQL Server Driver][DBNETLIB]ConnectionRead (recv()).
> Any idea why this is happening?
> Thanks in advance
> Taw.
>

Wednesday, March 28, 2012

Network

We are developing with SQL 7 Developer Edition and planning to install
MSDE with the VB application. We received the following question from
the IT dept. of our client:
"Does your version of SQLServer database work well across a frame
relay wide area network?"
Should there be any problems regarding speed, etc.?
Thanks!
Ernie Adsett"Ernie Adsett" <ernie@.amt.nb.ca> wrote in message
news:JhAPb.69757$IF6.1700023@.ursa-nb00s0.nbnet.nb.ca...
quote:

> We are developing with SQL 7 Developer Edition and planning to install
> MSDE with the VB application. We received the following question from
> the IT dept. of our client:
> "Does your version of SQLServer database work well across a frame
> relay wide area network?"
> Should there be any problems regarding speed, etc.?
> Thanks!
> Ernie Adsett
>

If your application is written to avoid unnecessary network traffic (use
stored procedures, avoid returning unnecessary rows in result sets etc.),
then there shouldn't be any special considerations. But to get a definite
answer, you would need to test it, of course.
Simon|||"Ernie Adsett" <ernie@.amt.nb.ca> wrote in message
news:JhAPb.69757$IF6.1700023@.ursa-nb00s0.nbnet.nb.ca...
quote:

> We are developing with SQL 7 Developer Edition and planning to install
> MSDE with the VB application. We received the following question from
> the IT dept. of our client:
> "Does your version of SQLServer database work well across a frame
> relay wide area network?"
> Should there be any problems regarding speed, etc.?

Depends entirely on your design and how good it is.
quote:

> Thanks!
> Ernie Adsett
>
sql

Network

We are developing with SQL 7 Developer Edition and planning to install
MSDE with the VB application. We received the following question from
the IT dept. of our client:
"Does your version of SQLServer database work well across a frame
relay wide area network?"
Should there be any problems regarding speed, etc.?

Thanks!

Ernie Adsett"Ernie Adsett" <ernie@.amt.nb.ca> wrote in message
news:JhAPb.69757$IF6.1700023@.ursa-nb00s0.nbnet.nb.ca...
> We are developing with SQL 7 Developer Edition and planning to install
> MSDE with the VB application. We received the following question from
> the IT dept. of our client:
> "Does your version of SQLServer database work well across a frame
> relay wide area network?"
> Should there be any problems regarding speed, etc.?
> Thanks!
> Ernie Adsett

If your application is written to avoid unnecessary network traffic (use
stored procedures, avoid returning unnecessary rows in result sets etc.),
then there shouldn't be any special considerations. But to get a definite
answer, you would need to test it, of course.

Simon|||"Ernie Adsett" <ernie@.amt.nb.ca> wrote in message
news:JhAPb.69757$IF6.1700023@.ursa-nb00s0.nbnet.nb.ca...
> We are developing with SQL 7 Developer Edition and planning to install
> MSDE with the VB application. We received the following question from
> the IT dept. of our client:
> "Does your version of SQLServer database work well across a frame
> relay wide area network?"
> Should there be any problems regarding speed, etc.?

Depends entirely on your design and how good it is.

> Thanks!
> Ernie Adsett

Monday, March 26, 2012

Net Send Failure

On a Windows 2000 Server in MYDomain I can do the following
successfully:

Net Send JoeUser "test"

However on a Windows Server 2003 (Standard Edition) in MyDomain I get:

An error occurred while sending a message to JoeUser.
The message alias could not be found on the network.
More help is available by typing NET HELPMSG 2273.

If I enter: net send /DOMAIN:MyDomain joeuser "test"
net send comes back with:

The message was successfully sent to domain MyDomain

BUT... no popups are received.

Is there something common to a Windows Server 2003 server that I need
to configure to get this to work?

How does this relate to SQL Server 2000? I figure that if I can get it
to work via a command prompt that it will work for notification as well
-- which at this point it doesn't.

Thanks for any help.

RBollingerIn article <1114705456.439354.148620@.o13g2000cwo.googlegroups. com>, "robboll" <robboll@.hotmail.com> wrote:
>On a Windows 2000 Server in MYDomain I can do the following
>successfully:
>Net Send JoeUser "test"
>However on a Windows Server 2003 (Standard Edition) in MyDomain I get:
>An error occurred while sending a message to JoeUser.
>The message alias could not be found on the network.
>More help is available by typing NET HELPMSG 2273.

Most likely the messenger service is not enabled by default in Windows 2003.
This is a good thing; there is no authentication with the messenger service,
so that anyone at all can send those "popup" messages to you claiming to be
anyone they want. I rejoiced when I saw SP2 for XP turned that service off.

If you have to use this, you'll need to enable the messager service. It's
probably set to "disabled", so you'll need a reboot once you've set it to
"automatic" for it to start.

>How does this relate to SQL Server 2000? I figure that if I can get it
>to work via a command prompt that it will work for notification as well
>-- which at this point it doesn't.

Hmm. I think the same logic would apply to fixing an SQL server that doesn't
boot because the hard-drive failed; that too would prevent you from using SQL.

But I figured I'd be nice and answer it, anyway :)|||Enabling the "Messenger" service under the Services Applet corrected
the problem. No reboot was necessary. Yes it seems that a lot of the
services previously available by default in previous OS' are locked
down in Windows Server 2003.

It's people like you who make the newsgroups my first source for
finding solutions.

Thank you!

RBollinger

John C. Ring, Jr. wrote:
> In article <1114705456.439354.148620@.o13g2000cwo.googlegroups. com>,
"robboll" <robboll@.hotmail.com> wrote:
> >On a Windows 2000 Server in MYDomain I can do the following
> >successfully:
> >Net Send JoeUser "test"
> >However on a Windows Server 2003 (Standard Edition) in MyDomain I
get:
> >An error occurred while sending a message to JoeUser.
> >The message alias could not be found on the network.
> >More help is available by typing NET HELPMSG 2273.
> Most likely the messenger service is not enabled by default in
Windows 2003.
> This is a good thing; there is no authentication with the messenger
service,
> so that anyone at all can send those "popup" messages to you claiming
to be
> anyone they want. I rejoiced when I saw SP2 for XP turned that
service off.
> If you have to use this, you'll need to enable the messager service.
It's
> probably set to "disabled", so you'll need a reboot once you've set
it to
> "automatic" for it to start.
> >How does this relate to SQL Server 2000? I figure that if I can get
it
> >to work via a command prompt that it will work for notification as
well
> >-- which at this point it doesn't.
> Hmm. I think the same logic would apply to fixing an SQL server that
doesn't
> boot because the hard-drive failed; that too would prevent you from
using SQL.
> But I figured I'd be nice and answer it, anyway :)

Wednesday, March 7, 2012

Needing to run reporting services on SQL Server 2000

Hi
I want to install SQL Server 2000 Enterprise Edition on Windows XP but it isn't installing.
I have installed SQL Server 2000 Personal Edition but Reporting Services are not installing on the server.
PLZ some one help me out.

SQL 2000 Enterprise Edition is not supported on XP. Please see this link for requirements:

http://www.microsoft.com/sql/prodinfo/previousversions/system-requirements.mspx

Thanks,
Sam Lester (MSFT)

Needed: Feature chart by Reporting Services Edition

I will be grateful to anyone who can tell me where to find a clear,
comprehensive explanation of what features of Reporting Services are
available in which edition(s) of Reporting Services.
I'm using Reporting Services 2005.
After much searching/experimenting, I now know 2 things:
--A "scale-out deployment" is not supported in the Standard version
(this also appears to mean that the encryption keys are useless on
any but the original machine -- so disaster recovery is problematic)
--"Click through" reports, via Report Builder type reports, are not available
in the Standard version.
It certainly is a time-drain to discover and verify these things one at a
time.
Assistance would be greatly appreciated (and anticipated from Microsoft).
--Dana Forsberg
P.S. Among other things, I have looked around quite a bit starting from:
ms-help://MS.VSCC.v80/MS.VSIPCC.v80/MS.SQLSVR.v9.en/rptsrvr9/html/b8d18d3d-9db0-43e7-8286-7b46cc3a37ed.htm
That seems a comprehensive "root" to a lot of resources -- but if there's a
feature chart by Edition, it has eluded me so far.I googled: reporting services features
First hit is this:
http://www.microsoft.com/sql/technologies/reporting/default.mspx
On this page is this link:
http://www.microsoft.com/sql/technologies/reporting/rsfeatures.mspx
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Dana Forsberg" <DanaForsberg@.discussions.microsoft.com> wrote in message
news:4CE62965-65E6-41B6-9FE4-CF77EF49A7A2@.microsoft.com...
>I will be grateful to anyone who can tell me where to find a clear,
> comprehensive explanation of what features of Reporting Services are
> available in which edition(s) of Reporting Services.
> I'm using Reporting Services 2005.
> After much searching/experimenting, I now know 2 things:
> --A "scale-out deployment" is not supported in the Standard version
> (this also appears to mean that the encryption keys are useless on
> any but the original machine -- so disaster recovery is problematic)
> --"Click through" reports, via Report Builder type reports, are not
> available
> in the Standard version.
> It certainly is a time-drain to discover and verify these things one at a
> time.
> Assistance would be greatly appreciated (and anticipated from Microsoft).
> --Dana Forsberg
> P.S. Among other things, I have looked around quite a bit starting from:
> ms-help://MS.VSCC.v80/MS.VSIPCC.v80/MS.SQLSVR.v9.en/rptsrvr9/html/b8d18d3d-9db0-43e7-8286-7b46cc3a37ed.htm
> That seems a comprehensive "root" to a lot of resources -- but if there's
> a
> feature chart by Edition, it has eluded me so far.
>|||Thank you for a very timely and on-target reply.
I really appreciate it.
And... is "Infinite Click-through" the same thing as "Click through reports"?
Actually, I just did a search and found out that it is -- but please pass on
a vote for a little "blurb" of explanation on feature charts, rather than the
austere case of only one or two words to guess from, identifying a given
feature.
Again, thanks very much for the reply.
"Bruce L-C [MVP]" wrote:
> I googled: reporting services features
> First hit is this:
> http://www.microsoft.com/sql/technologies/reporting/default.mspx
> On this page is this link:
> http://www.microsoft.com/sql/technologies/reporting/rsfeatures.mspx
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Dana Forsberg" <DanaForsberg@.discussions.microsoft.com> wrote in message
> news:4CE62965-65E6-41B6-9FE4-CF77EF49A7A2@.microsoft.com...
> >I will be grateful to anyone who can tell me where to find a clear,
> > comprehensive explanation of what features of Reporting Services are
> > available in which edition(s) of Reporting Services.
> >
> > I'm using Reporting Services 2005.
> > After much searching/experimenting, I now know 2 things:
> > --A "scale-out deployment" is not supported in the Standard version
> > (this also appears to mean that the encryption keys are useless on
> > any but the original machine -- so disaster recovery is problematic)
> >
> > --"Click through" reports, via Report Builder type reports, are not
> > available
> > in the Standard version.
> >
> > It certainly is a time-drain to discover and verify these things one at a
> > time.
> >
> > Assistance would be greatly appreciated (and anticipated from Microsoft).
> >
> > --Dana Forsberg
> >
> > P.S. Among other things, I have looked around quite a bit starting from:
> > ms-help://MS.VSCC.v80/MS.VSIPCC.v80/MS.SQLSVR.v9.en/rptsrvr9/html/b8d18d3d-9db0-43e7-8286-7b46cc3a37ed.htm
> >
> > That seems a comprehensive "root" to a lot of resources -- but if there's
> > a
> > feature chart by Edition, it has eluded me so far.
> >
>
>

Saturday, February 25, 2012

Need urgent help.. for SQL Server reporting services installation..

hi,

I have SQL Server Express edition installed on my PC , but now I need to use SQL Server reporting service, there is SP1 for express edition contains reporting service with express edition. Here..

http://msdn.microsoft.com/vstudio/express/sql/download/

Do I need to download 213 MB SQL Server 2005 Express Edition Toolkit SP1 ?

or there is any other method to use reporting services ?

Thanks

You will have to download the full install again, there is no way of installing the components seperatly. With SQl 2000 there used to be a seperate DL for Reporting Services, but in the 2005 stream they are all included in the one package.