activeX step never finishes.

I have an activex script which executes a query that never finishes. If I recompile the query in Management Studio before I run this step, then the step will *usually* work fine. This is the last step in a very long update process so the data has changed a great deal when this step executes.

The query always works fine in Management studio btw.

I am using BI studio to run the package.

I have tried placing a step before this that marks the query for recompilation but that doesnt seem to work. Any ideas how to resolve this?

Why ActiveX?|||it loops through the result set and sends out an email for each record. The package was originally a dts 2000 package so I just kept it as is. If theres a better way to do this in SSIS I would love to know.|||Use an Execute SQL task to populate an object-typed variable. Hook the SQL task to a Foreach loop which "shreds" the variable. Inside that foreach loop you could use a Send Mail task.

See if this helps: http://blogs.conchango.com/jamiethomson/archive/2005/07/04/SSIS-Nugget_3A00_-Execute-SQL-Task-into-an-object-variable-_2D00_-Shred-it-with-a-Foreach-loop.aspx

Account Lockout on SQL2005

Hi Champs,
Is there a way to recover from a account lockout in SQL2005?
I cannot connect to "Database Engine" in "SQL Server Management Studio",
error: login failed...18456.
And I also cannot start the "SQL Server agent service"
Any possebility to recover without reinstall?
/Many thanksKurlan wrote:
> Hi Champs,
> Is there a way to recover from a account lockout in SQL2005?
> I cannot connect to "Database Engine" in "SQL Server Management Studio",
> error: login failed...18456.
> And I also cannot start the "SQL Server agent service"
> Any possebility to recover without reinstall?
>
> /Many thanks
Start from here
http://blogs.msdn.com/sql_protocols.../21/536201.aspx
Regards
Amish Shah|||Hi
If your issue is that a windows account has been locked contact the system
administrator to unlock it through the active directory user management
tools. If this is a SQL login then you can uncheck the account locked box on
the status screen under the account details of the security branch in SQL
Management Studio.
You don't give any error messages that come up when you try and start SQL
agent! If you are using a domain account as the service account, then try
switching to local system and see if it will start, you can then switch back
once you have validated that the account you are using is ok.
If this does not work check out the SQL Agent Log File to see if there are
any information there.
John
"Kurlan" wrote:

> Hi Champs,
> Is there a way to recover from a account lockout in SQL2005?
> I cannot connect to "Database Engine" in "SQL Server Management Studio",
> error: login failed...18456.
> And I also cannot start the "SQL Server agent service"
> Any possebility to recover without reinstall?
>
> /Many thanks|||Yes it is the SQL account.
I cannot access SQL Management Studio, so I cannot access the SQL accounts.
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> If your issue is that a windows account has been locked contact the system
> administrator to unlock it through the active directory user management
> tools. If this is a SQL login then you can uncheck the account locked box
on
> the status screen under the account details of the security branch in SQL
> Management Studio.
> You don't give any error messages that come up when you try and start SQL
> agent! If you are using a domain account as the service account, then try
> switching to local system and see if it will start, you can then switch ba
ck
> once you have validated that the account you are using is ok.
> If this does not work check out the SQL Agent Log File to see if there are
> any information there.
> John
> "Kurlan" wrote:
>|||Hi
You can also use the T-SQL command ALTER LOGIN with the UNLOCK option when
setting the password.
John
"Kurlan" wrote:
[vbcol=seagreen]
> Yes it is the SQL account.
> I cannot access SQL Management Studio, so I cannot access the SQL accounts
.
>
> "John Bell" wrote:
>|||in order to run a t-sql, I have to have connection to either the management
consol or via sqlcmd, and I get access denied in both cases.
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> You can also use the T-SQL command ALTER LOGIN with the UNLOCK option when
> setting the password.
> John
> "Kurlan" wrote:
>|||Kurlan wrote:[vbcol=seagreen]
> Yes it is the SQL account.
> I cannot access SQL Management Studio, so I cannot access the SQL accounts.[/vbcol
]
Why do you need Management Studio to change the service account?
Start -> Administrative Tools -> Services, go to the properties for the
MSSQLSERVICE, configure it to run as the Local System account.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Hi
If you log in on the same machine as SQL Server is running as an
administrator you should be able to log in with a trusted connection (-E
option for SQLCMD or OSQL). You should also be able to log into management
studio this way. If not type in NET START at a command prompt to make sure
the SQL Server is running.
John
"Kurlan" wrote:
[vbcol=seagreen]
> in order to run a t-sql, I have to have connection to either the managemen
t
> consol or via sqlcmd, and I get access denied in both cases.
> "John Bell" wrote:
>

Account Lockout on SQL2005

Hi Champs,
Is there a way to recover from a account lockout in SQL2005?
I cannot connect to "Database Engine" in "SQL Server Management Studio",
error: login failed...18456.
And I also cannot start the "SQL Server agent service"
Any possebility to recover without reinstall?
/Many thanksKurlan wrote:
> Hi Champs,
> Is there a way to recover from a account lockout in SQL2005?
> I cannot connect to "Database Engine" in "SQL Server Management Studio",
> error: login failed...18456.
> And I also cannot start the "SQL Server agent service"
> Any possebility to recover without reinstall?
>
> /Many thanks
Start from here
http://blogs.msdn.com/sql_protocols/archive/2006/02/21/536201.aspx
Regards
Amish Shah|||Hi
If your issue is that a windows account has been locked contact the system
administrator to unlock it through the active directory user management
tools. If this is a SQL login then you can uncheck the account locked box on
the status screen under the account details of the security branch in SQL
Management Studio.
You don't give any error messages that come up when you try and start SQL
agent! If you are using a domain account as the service account, then try
switching to local system and see if it will start, you can then switch back
once you have validated that the account you are using is ok.
If this does not work check out the SQL Agent Log File to see if there are
any information there.
John
"Kurlan" wrote:
> Hi Champs,
> Is there a way to recover from a account lockout in SQL2005?
> I cannot connect to "Database Engine" in "SQL Server Management Studio",
> error: login failed...18456.
> And I also cannot start the "SQL Server agent service"
> Any possebility to recover without reinstall?
>
> /Many thanks|||Yes it is the SQL account.
I cannot access SQL Management Studio, so I cannot access the SQL accounts.
"John Bell" wrote:
> Hi
> If your issue is that a windows account has been locked contact the system
> administrator to unlock it through the active directory user management
> tools. If this is a SQL login then you can uncheck the account locked box on
> the status screen under the account details of the security branch in SQL
> Management Studio.
> You don't give any error messages that come up when you try and start SQL
> agent! If you are using a domain account as the service account, then try
> switching to local system and see if it will start, you can then switch back
> once you have validated that the account you are using is ok.
> If this does not work check out the SQL Agent Log File to see if there are
> any information there.
> John
> "Kurlan" wrote:
> > Hi Champs,
> > Is there a way to recover from a account lockout in SQL2005?
> > I cannot connect to "Database Engine" in "SQL Server Management Studio",
> > error: login failed...18456.
> >
> > And I also cannot start the "SQL Server agent service"
> >
> > Any possebility to recover without reinstall?
> >
> >
> > /Many thanks|||Hi
You can also use the T-SQL command ALTER LOGIN with the UNLOCK option when
setting the password.
John
"Kurlan" wrote:
> Yes it is the SQL account.
> I cannot access SQL Management Studio, so I cannot access the SQL accounts.
>
> "John Bell" wrote:
> > Hi
> >
> > If your issue is that a windows account has been locked contact the system
> > administrator to unlock it through the active directory user management
> > tools. If this is a SQL login then you can uncheck the account locked box on
> > the status screen under the account details of the security branch in SQL
> > Management Studio.
> >
> > You don't give any error messages that come up when you try and start SQL
> > agent! If you are using a domain account as the service account, then try
> > switching to local system and see if it will start, you can then switch back
> > once you have validated that the account you are using is ok.
> >
> > If this does not work check out the SQL Agent Log File to see if there are
> > any information there.
> >
> > John
> >
> > "Kurlan" wrote:
> >
> > > Hi Champs,
> > > Is there a way to recover from a account lockout in SQL2005?
> > > I cannot connect to "Database Engine" in "SQL Server Management Studio",
> > > error: login failed...18456.
> > >
> > > And I also cannot start the "SQL Server agent service"
> > >
> > > Any possebility to recover without reinstall?
> > >
> > >
> > > /Many thanks|||in order to run a t-sql, I have to have connection to either the management
consol or via sqlcmd, and I get access denied in both cases.
"John Bell" wrote:
> Hi
> You can also use the T-SQL command ALTER LOGIN with the UNLOCK option when
> setting the password.
> John
> "Kurlan" wrote:
> > Yes it is the SQL account.
> >
> > I cannot access SQL Management Studio, so I cannot access the SQL accounts.
> >
> >
> > "John Bell" wrote:
> >
> > > Hi
> > >
> > > If your issue is that a windows account has been locked contact the system
> > > administrator to unlock it through the active directory user management
> > > tools. If this is a SQL login then you can uncheck the account locked box on
> > > the status screen under the account details of the security branch in SQL
> > > Management Studio.
> > >
> > > You don't give any error messages that come up when you try and start SQL
> > > agent! If you are using a domain account as the service account, then try
> > > switching to local system and see if it will start, you can then switch back
> > > once you have validated that the account you are using is ok.
> > >
> > > If this does not work check out the SQL Agent Log File to see if there are
> > > any information there.
> > >
> > > John
> > >
> > > "Kurlan" wrote:
> > >
> > > > Hi Champs,
> > > > Is there a way to recover from a account lockout in SQL2005?
> > > > I cannot connect to "Database Engine" in "SQL Server Management Studio",
> > > > error: login failed...18456.
> > > >
> > > > And I also cannot start the "SQL Server agent service"
> > > >
> > > > Any possebility to recover without reinstall?
> > > >
> > > >
> > > > /Many thanks|||Kurlan wrote:
> Yes it is the SQL account.
> I cannot access SQL Management Studio, so I cannot access the SQL accounts.
Why do you need Management Studio to change the service account?
Start -> Administrative Tools -> Services, go to the properties for the
MSSQLSERVICE, configure it to run as the Local System account.
--
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Hi
If you log in on the same machine as SQL Server is running as an
administrator you should be able to log in with a trusted connection (-E
option for SQLCMD or OSQL). You should also be able to log into management
studio this way. If not type in NET START at a command prompt to make sure
the SQL Server is running.
John
"Kurlan" wrote:
> in order to run a t-sql, I have to have connection to either the management
> consol or via sqlcmd, and I get access denied in both cases.
> "John Bell" wrote:
> > Hi
> >
> > You can also use the T-SQL command ALTER LOGIN with the UNLOCK option when
> > setting the password.
> >
> > John
> >
> > "Kurlan" wrote:
> >
> > > Yes it is the SQL account.
> > >
> > > I cannot access SQL Management Studio, so I cannot access the SQL accounts.
> > >
> > >
> > > "John Bell" wrote:
> > >
> > > > Hi
> > > >
> > > > If your issue is that a windows account has been locked contact the system
> > > > administrator to unlock it through the active directory user management
> > > > tools. If this is a SQL login then you can uncheck the account locked box on
> > > > the status screen under the account details of the security branch in SQL
> > > > Management Studio.
> > > >
> > > > You don't give any error messages that come up when you try and start SQL
> > > > agent! If you are using a domain account as the service account, then try
> > > > switching to local system and see if it will start, you can then switch back
> > > > once you have validated that the account you are using is ok.
> > > >
> > > > If this does not work check out the SQL Agent Log File to see if there are
> > > > any information there.
> > > >
> > > > John
> > > >
> > > > "Kurlan" wrote:
> > > >
> > > > > Hi Champs,
> > > > > Is there a way to recover from a account lockout in SQL2005?
> > > > > I cannot connect to "Database Engine" in "SQL Server Management Studio",
> > > > > error: login failed...18456.
> > > > >
> > > > > And I also cannot start the "SQL Server agent service"
> > > > >
> > > > > Any possebility to recover without reinstall?
> > > > >
> > > > >
> > > > > /Many thanks

accessing sql express peer to peer on xp home

HI

2 pc's networked on XP home - SQL Express installed on one (on both actually, but that's probably superfluous info)

I've got the CTP studio express installed on both, but can't connect to the instance on the other machine - I've enabled TCPIP and named pipes, restarted the services, the XP filewall is disabled and still no luck - I've got mixed mode authentication...

What else can I try - how do I fix ?

THanks

Bruce

I haven't tried this but instructions at

http://blogs.msdn.com/sqlexpress/archive/2005/05/05/415084.aspx may help.

GS

|||

You can also use the Surface Area Configuration tool to enable remote connections.

Thanks

Laurentiu

Accessing SQL Database created in Visual Studio

I created an SQL database in Visual Studio 2005 Express Edition and would like to edit it in SQL Server Management Studio Express. The only databases listed in the Object Explorer of SQL Server MSE are the system databases (ones that are part of the SQL Server MSE).

If I dig through the directories, I can locate my database under the Visual Studio directory, but I am unable to open it. I get an error message stating, "There is no editor available for [my database]... Make sure the application for the file type (.mdf) is installed."

I'm sure that this is a ridiculously simple rookie mistake that I'm committing somehow, but I'm stumped. Any idea what I'm doing wrong?

What you need to do is "attach" your database in your management studio. This is supprisingly a goofy process, being that this is our newest implementation of a manager for SQL Express, here's some help to get you started.

http://msdn2.microsoft.com/en-us/library/ms190209.aspx

|||

I tried it, and I think that it should have worked, but it didn't. I got a long string of error messages. It's probably just another bug that Microsoft will some day issue a patch for. When I attempted to add my review of the tip to the msdn website my computer locked up. That was kind of a metaphor for the entire experience. I've learned my lesson. Don't make databases in Visual Studio - do it in SQL Studio or MySQL.

|||

I've never had an issue with the Management Studio, or SQL Express databases, I'm not sure what your experiencing, but they arent as unreliable as your making them out to be.

Sorry you couldnt get it fixed.

Accessing SQL 2000 servers from 2005 Management Studio

Hi,
I have seen many post on this problem, but I have not seen a concise
answer.
I have 2 servers running SQL 2000. I have a fresh installation of XP
and SQL 2005 on my laptop (No Firewall). I cannot register the 2000
servers using the SQL 2005 Management studio by Named Pipes or by
TCPIP. Names Pipes throws the error 40 error, and TCP throws the error
0, connection refused error.
the 2000 severs can regsiter each other and a 4th machine with EM on it
can register them, so I know this isn't a firewall or connection issue
on the 2000 servers.
Can anyone shed some light on how to open up my SQL 20005 installation
to allow it to communicate with the 2000 servers.
Thanks
Pepper FlemingHi
Do you configure SQL Server 2005 remote connection to be enabled?
Can you show an exact error you are getting?
<PepperFleming@.gmail.com> wrote in message
news:1150642596.033192.219160@.u72g2000cwu.googlegroups.com...
> Hi,
> I have seen many post on this problem, but I have not seen a concise
> answer.
> I have 2 servers running SQL 2000. I have a fresh installation of XP
> and SQL 2005 on my laptop (No Firewall). I cannot register the 2000
> servers using the SQL 2005 Management studio by Named Pipes or by
> TCPIP. Names Pipes throws the error 40 error, and TCP throws the error
> 0, connection refused error.
> the 2000 severs can regsiter each other and a 4th machine with EM on it
> can register them, so I know this isn't a firewall or connection issue
> on the 2000 servers.
> Can anyone shed some light on how to open up my SQL 20005 installation
> to allow it to communicate with the 2000 servers.
> Thanks
> Pepper Fleming
>|||Hi Uri,
Thanks so much for responding. The message I am getting through the
Management studio when trying to connect to the server running SQL 2000
is:
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) (Microsoft SQL Server, Error: 1326)
I have named pipes enabled on my laptop under the SQL Server
Configuration manager.
The message looks a little misleading to me, because the way I read it,
the studio thinks it is connecting to a SQL Server 2005 instance.
Thanks,
Pepper|||One more piece of information if it helps, I can connect to other SQL
2005 servers remotely, this seems specific to SQL 2000 servers.
Pepper|||These may help. Using portqry you should get similar output as below.
http://www.microsoft.com/downloads/details.aspx?familyid=89811747-C74B-4638-A2D5-AC828BDC6983&displaylang=en
http://support.microsoft.com/default.aspx?scid=kb;en-us;287932
F:\PortQryV2>
*** User Input***
F:\PortQryV2>portqry -i
PortQry Interactive Mode
Type 'help' for a list of commands
Default Node: 127.0.0.1
Current option values:
end port= 80
protocol= TCP
source port= 0 (ephemeral)
*** User Input***
> node 192.168.1.98
Default Node: 192.168.1.98
>
*** User Input***
> q sql
resolving service name using local services file...
TCP port resolved to the 'ms-sql-s' service
IP address resolved to pe1600.dspatrick.local.com
querying...
TCP port 1433 (ms-sql-s service): LISTENING
>
resolving service name using local services file...
UDP port resolved to the 'ms-sql-m' service
IP address resolved to pe1600.dspatrick.local.com
querying...
UDP port 1434 (ms-sql-m service): LISTENING or FILTERED
Sending SQL Server query to UDP port 1434...
Server's response:
ServerName PE1600
InstanceName MSSQLSERVER
IsClustered No
Version 9.00.1399.06
tcp 1433
F
==== End of SQL Server query response ====UDP port 1434 is LISTENING
*** User Input***
> exit
exiting PortQry Interactive Mode...
F:\PortQryV2>
--
Regards,
Dave Patrick ...Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect
<PepperFleming@.gmail.com> wrote:
| One more piece of information if it helps, I can connect to other SQL
| 2005 servers remotely, this seems specific to SQL 2000 servers.
|
| Pepper
||||Thanks Dave,
I will run this, but does anyone know if my problem is unusual or is
this a configuration issue common with a standard SQL Server 2005
installation.
Can you manage SQL 2000 servers from the 2005 Management studio out of
the box?
Pepper|||1.) Yes, unusual.
2.) Yes, you can.
--
Regards,
Dave Patrick ...Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect
<PepperFleming@.gmail.com> wrote:
| Thanks Dave,
|
| I will run this, but does anyone know if my problem is unusual or is
| this a configuration issue common with a standard SQL Server 2005
| installation.
|
| Can you manage SQL 2000 servers from the 2005 Management studio out of
| the box?
|
| Pepper
||||Hey Dave,
Thanks for the link to the tool. That did the trick.
If anyone is interested, I noticed in the event log that the TCP / UDP
protocols had been disabled due to incompatability with windows 2003.
There are 2 things interesting about this. First, the entry wasnt' an
error, nor an alert but an information entry. the second, is that the
server is running SP 4a. A port scan did confirm that 1433 was not
open, and a reinstall of 4a did re-enable the port again.
I can only conclude that something I had done had rolled-back or over
wrote something critical for Windows 2003 to identify the service pack
level of SQL server and cause the ports to be disabled.
Thanks to all that responded, I appreciate the help.
Pepper|||Glad to hear it. You're welcome.
--
Regards,
Dave Patrick ...Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect
<PepperFleming@.gmail.com> wrote:
| Hey Dave,
|
| Thanks for the link to the tool. That did the trick.
|
| If anyone is interested, I noticed in the event log that the TCP / UDP
| protocols had been disabled due to incompatability with windows 2003.
| There are 2 things interesting about this. First, the entry wasnt' an
| error, nor an alert but an information entry. the second, is that the
| server is running SP 4a. A port scan did confirm that 1433 was not
| open, and a reinstall of 4a did re-enable the port again.
|
| I can only conclude that something I had done had rolled-back or over
| wrote something critical for Windows 2003 to identify the service pack
| level of SQL server and cause the ports to be disabled.
|
| Thanks to all that responded, I appreciate the help.
|
| Pepper
|

Accessing SQL 2000 servers from 2005 Management Studio

Hi
Do you configure SQL Server 2005 remote connection to be enabled?
Can you show an exact error you are getting?
<PepperFleming@.gmail.com> wrote in message
news:1150642596.033192.219160@.u72g2000cwu.googlegroups.com...
> Hi,
> I have seen many post on this problem, but I have not seen a concise
> answer.
> I have 2 servers running SQL 2000. I have a fresh installation of XP
> and SQL 2005 on my laptop (No Firewall). I cannot register the 2000
> servers using the SQL 2005 Management studio by Named Pipes or by
> TCPIP. Names Pipes throws the error 40 error, and TCP throws the error
> 0, connection refused error.
> the 2000 severs can regsiter each other and a 4th machine with EM on it
> can register them, so I know this isn't a firewall or connection issue
> on the 2000 servers.
> Can anyone shed some light on how to open up my SQL 20005 installation
> to allow it to communicate with the 2000 servers.
> Thanks
> Pepper Fleming
>Hi Uri,
Thanks so much for responding. The message I am getting through the
Management studio when trying to connect to the server running SQL 2000
is:
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) (Microsoft SQL Server, Error: 1326)
I have named pipes enabled on my laptop under the SQL Server
Configuration manager.
The message looks a little misleading to me, because the way I read it,
the studio thinks it is connecting to a SQL Server 2005 instance.
Thanks,
Pepper|||One more piece of information if it helps, I can connect to other SQL
2005 servers remotely, this seems specific to SQL 2000 servers.
Pepper|||These may help. Using portqry you should get similar output as below.
http://www.microsoft.com/downloads/...&displaylang=en
http://support.microsoft.com/defaul...kb;en-us;287932
F:\PortQryV2>
*** User Input***
F:\PortQryV2>portqry -i
PortQry Interactive Mode
Type 'help' for a list of commands
Default Node: 127.0.0.1
Current option values:
end port= 80
protocol= TCP
source port= 0 (ephemeral)
*** User Input***
> node 192.168.1.98
Default Node: 192.168.1.98
>
*** User Input***
> q sql
resolving service name using local services file...
TCP port resolved to the 'ms-sql-s' service
IP address resolved to pe1600.dspatrick.local.com
querying...
TCP port 1433 (ms-sql-s service): LISTENING
>
resolving service name using local services file...
UDP port resolved to the 'ms-sql-m' service
IP address resolved to pe1600.dspatrick.local.com
querying...
UDP port 1434 (ms-sql-m service): LISTENING or FILTERED
Sending SQL Server query to UDP port 1434...
Server's response:
ServerName PE1600
InstanceName MSSQLSERVER
IsClustered No
Version 9.00.1399.06
tcp 1433
F
==== End of SQL Server query response ====
UDP port 1434 is LISTENING
*** User Input***
> exit
exiting PortQry Interactive Mode...
F:\PortQryV2>
Regards,
Dave Patrick ...Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect
<PepperFleming@.gmail.com> wrote:
| One more piece of information if it helps, I can connect to other SQL
| 2005 servers remotely, this seems specific to SQL 2000 servers.
|
| Pepper
||||Hi,
I have seen many post on this problem, but I have not seen a concise
answer.
I have 2 servers running SQL 2000. I have a fresh installation of XP
and SQL 2005 on my laptop (No Firewall). I cannot register the 2000
servers using the SQL 2005 Management studio by Named Pipes or by
TCPIP. Names Pipes throws the error 40 error, and TCP throws the error
0, connection refused error.
the 2000 severs can regsiter each other and a 4th machine with EM on it
can register them, so I know this isn't a firewall or connection issue
on the 2000 servers.
Can anyone shed some light on how to open up my SQL 20005 installation
to allow it to communicate with the 2000 servers.
Thanks
Pepper Fleming|||Hi
Do you configure SQL Server 2005 remote connection to be enabled?
Can you show an exact error you are getting?
<PepperFleming@.gmail.com> wrote in message
news:1150642596.033192.219160@.u72g2000cwu.googlegroups.com...
> Hi,
> I have seen many post on this problem, but I have not seen a concise
> answer.
> I have 2 servers running SQL 2000. I have a fresh installation of XP
> and SQL 2005 on my laptop (No Firewall). I cannot register the 2000
> servers using the SQL 2005 Management studio by Named Pipes or by
> TCPIP. Names Pipes throws the error 40 error, and TCP throws the error
> 0, connection refused error.
> the 2000 severs can regsiter each other and a 4th machine with EM on it
> can register them, so I know this isn't a firewall or connection issue
> on the 2000 servers.
> Can anyone shed some light on how to open up my SQL 20005 installation
> to allow it to communicate with the 2000 servers.
> Thanks
> Pepper Fleming
>|||Hi Uri,
Thanks so much for responding. The message I am getting through the
Management studio when trying to connect to the server running SQL 2000
is:
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) (Microsoft SQL Server, Error: 1326)
I have named pipes enabled on my laptop under the SQL Server
Configuration manager.
The message looks a little misleading to me, because the way I read it,
the studio thinks it is connecting to a SQL Server 2005 instance.
Thanks,
Pepper|||One more piece of information if it helps, I can connect to other SQL
2005 servers remotely, this seems specific to SQL 2000 servers.
Pepper|||These may help. Using portqry you should get similar output as below.
http://www.microsoft.com/downloads/...&displaylang=en
http://support.microsoft.com/defaul...kb;en-us;287932
F:\PortQryV2>
*** User Input***
F:\PortQryV2>portqry -i
PortQry Interactive Mode
Type 'help' for a list of commands
Default Node: 127.0.0.1
Current option values:
end port= 80
protocol= TCP
source port= 0 (ephemeral)
*** User Input***
> node 192.168.1.98
Default Node: 192.168.1.98
>
*** User Input***
> q sql
resolving service name using local services file...
TCP port resolved to the 'ms-sql-s' service
IP address resolved to pe1600.dspatrick.local.com
querying...
TCP port 1433 (ms-sql-s service): LISTENING
>
resolving service name using local services file...
UDP port resolved to the 'ms-sql-m' service
IP address resolved to pe1600.dspatrick.local.com
querying...
UDP port 1434 (ms-sql-m service): LISTENING or FILTERED
Sending SQL Server query to UDP port 1434...
Server's response:
ServerName PE1600
InstanceName MSSQLSERVER
IsClustered No
Version 9.00.1399.06
tcp 1433
F
==== End of SQL Server query response ====
UDP port 1434 is LISTENING
*** User Input***
> exit
exiting PortQry Interactive Mode...
F:\PortQryV2>
Regards,
Dave Patrick ...Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect
<PepperFleming@.gmail.com> wrote:
| One more piece of information if it helps, I can connect to other SQL
| 2005 servers remotely, this seems specific to SQL 2000 servers.
|
| Pepper
||||Thanks Dave,
I will run this, but does anyone know if my problem is unusual or is
this a configuration issue common with a standard SQL Server 2005
installation.
Can you manage SQL 2000 servers from the 2005 Management studio out of
the box?
Pepper

Accessing Reports via URL

I have configured my report server. I can connect to it via Management
Studio and via http://localhost/reports however when I try to connect via
http://servername/reports I get a Windows style password box. What user is
it expecting? Regards, Chris.Ignore me it seems to be working now
"Fresno Bob" <nospam@.nospam.com> wrote in message
news:u7VfBfz7HHA.2476@.TK2MSFTNGP05.phx.gbl...
>I have configured my report server. I can connect to it via Management
>Studio and via http://localhost/reports however when I try to connect via
>http://servername/reports I get a Windows style password box. What user is
>it expecting? Regards, Chris.
>

Accessing printer settings in the sql reporting services 2000

I am using Visual Studio 2003 and SQL Reporting Services 2000. I am creating a Intranet based application which will be used by our company employees only. I want to know how can I set a printer, paper tray and paper size in the report settings, so that user need not to change the printer settings for each report. In the application some of the reports will be printed on pre-printed paper, some on the plain paper. and i want to print the reports which is not a defaul printer.

I did not find any solution yet... any ideas ... It will be a great help for me..