Problem with Sql Server 2000 error

I am using VWD with Sql Server 2000. My application was running smoothly till I rebooted both my local box and the Machine where sql Server 2000 resides and now I am getting this error:

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)

like I said before I am using Sql Server 2000 and not 2005. I don't really understand the problem. The application was running smoothly before rebooting it, so I know there is nothing wrong with the code. Maybe I need to start some service within IIS or something.

If anyone has any idea please let me know.

Thanks in advance for your help

Hi,

I do not have an idea why you catch this error while working with a SQL2K database.

But to enable remote connections, open the SQL Server Surface Area Configuration tool. Then drill down the Services and Connections, open the Database Engine. Then enable remote connections from this configuration tool.

eralper

http://www.kodyaz.com

|||

Could be a number of issues.

First, I rarely let SQL Server use named pipes. I hate them, I force SQL Server to TCP/IP always, unless it's a local connection then shared memory.

A firewall blocking the connection could do it.

Putting in the wrong server name could do it.

Configuring SQL Server to deny remote connections could do it (That is what the error message is saying).

There was a problem with SP2 and SQL Server 2000. Check the SP readme.txt to make sure you've configured it correctly for use with XP SP2.

Problem with SQL 2005 Beta 2 Reporting Services

I've just installed SQL 2005 Beta 2 onto a Windows Server 2003 SP1 box.
I've installed all the components, including Reporting Services.
When I try to connect to the web site I get the message
The request failed with HTTP status 407: Proxy Authentication Required.
Anonymous access to the web site is allowed.
Any thoughts?
Thanks
Laurence
--
Laurence Sharp
Senior Systems Engineer
TNS UKOn Thu, 7 Apr 2005 07:09:05 -0700, "Laurence Sharp"
<LaurenceSharp@.discussions.microsoft.com> wrote:
>I've just installed SQL 2005 Beta 2 onto a Windows Server 2003 SP1 box.
>I've installed all the components, including Reporting Services.
>When I try to connect to the web site I get the message
>The request failed with HTTP status 407: Proxy Authentication Required.
>Anonymous access to the web site is allowed.
>Any thoughts?
>Thanks
>Laurence
Hi Laurence,
Questions about RS2005 should probably go to the
microsoft.private.sqlserver2005.reportingsvcs. Despite the name it's a
public newsgroup intended for the RS2005 beta and CTPs.
Are you really using Beta 2 from June/July last year? Beta 2 has
functionality similar to RS2000 with little new.
If you are, then you should probably update BUT be sure to read
carefully CTPNotes.mht about uninstall order before upgrading.
The February CTP has new functionality and has fewer configuration
problems than earlier builds.
Andrew Watt
MVP - InfoPath

Problem with saving Chinese.

Hi.. I'm trying to save text into SQL 2000 database.

When user enter text in text box , the text save into variable , and show it in confirm page , after save the text to database, all the text turned into "??"

I try to view the data in SQL enterprise Manager / Web Matrix / ASP web page gridview , all of them showing the text fields in "??"

Then I try to add record which come with SQL 2000 enterprise Manager.After save the record , the chinese also turned into "??"

Is there something I need to set for database or server?

Is your datatype VARCHAR, TEXT or CHAR as the datatype on the table columns?

If VARCHAR change to NVARCHAR. If TEXT change to NTEXT. If CHAR change to NCHAR.

If you are using stored procedures (and you should be), you will to amend the parameter declaration on them.

You might want to change the collating sequence on your database to one more appropriate to Chinese (if collating sequence is meaningful for that language), but otherwise you should not need to change anything at the database level.

If this reply provides the anser to your question, please mark as such.

|||all the text are stored in varchar... I'll try to change it to nvarchar|||

yea... it works when I change all the text field type to nnvarchar..

Problem with printing database diagrams

When I print a database diagram directly, I get the top left corner obsrured on the printout by what looks like an empty popup box. This means the columns names are blanked out for the first 5-6 rows. I have tried this with a variety of printers and the effectis the same on all. The problem appears to be specific to SQL2005 as one of the servers has both SQL2000 and SQL2005. The disagrams from the SQL2000 print perfectly, the ones from SQL2005 do not.

SQL2005 has been patched to SP2.

I have circumvented the problem by writing an SSRS package to print the output of a stored procedure that emulates the database diagram. Also there is an option in SQL2005 database diagrams to get an image of the diagram. I have printed this in Word and it prints flawlessly that way.

I believe this is an unique problem you are facing and I think nothing much done from SQL dev. team.

See thsi http://www.codeproject.com/dotnet/ScriptDiagram2005.asp is any help and you can report the same to MS Connect website http://connect.microsoft.com/

|||Regrettably I still have the problem with diagram on SQL2005 (but SQL2000)
|||

This is not a unique problem.

I've been encountering it for a month or two.

It's intermittent. Sometimes the diagrams are okay, sometimes these boxes obscure fields.

My only work-around is to PRINT SCREEN and then copy it into Word and print it.

|||We are having this same problem. If you copy to Word it will print. Has there been a solution found yet?|||Copying to Word is a good work-around, but is not a solution. It did happen with all the printers I could try at that site.