connection issue from our developer

Hi,
SQL 2005 EE is installed on W2k3 box and firewall is off in this server.
From my client machine, my window account and that developer window account
all can login into this server with ODBC, sql client, telent to 1433 or VS
connection. But, this developer can't login to SQL server from him machine
with any appliction. He is in the same domain as server and my machine. I
don't know what's the reason to cause this issue now.
Please advise. Thank you.
Lynn
Best Regards,
Lynn
What is the exact error message and error number he gets
when he tries to log into SQL Server?
-Sue
On Thu, 22 Mar 2007 10:33:45 -0700, Lynn
<Lynn@.discussions.microsoft.com> wrote:

>Hi,
>SQL 2005 EE is installed on W2k3 box and firewall is off in this server.
>From my client machine, my window account and that developer window account
>all can login into this server with ODBC, sql client, telent to 1433 or VS
>connection. But, this developer can't login to SQL server from him machine
>with any appliction. He is in the same domain as server and my machine. I
>don't know what's the reason to cause this issue now.
>Please advise. Thank you.
>Lynn
|||We only enable Shared Memory and TCP/IP protocal in server side. And, those
are the error they are getting.
osql -- SQL server doesn't exist or access denied
Query Analyzer -- General network error. Check your network documentation
VS 2005 -- (without specifing TCP protocal in connection) A connection was
succssfully established with the server, but then an error occured during the
pre-login handshake. When connecting ....(provider: Named Pipes provider,
error: 0 - No process is on the ther end of the pipe)
VS 2005 -- (specify TCP protocal in connection) 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 ...
(provider: TCP provider: 0 -- A connection attempt failed because the
connected party didn't not properly respond after a period of tiem, or
established connection failed because connected host has failed to respond.)
Again, this developer is able to login by using my machine with his WIN
account.
After I enable Named Pipes in server. This developer is able to connect to
server on his machine by using Named Pipe.
Firewall is off in the server, so I can't think of the issue for TCP
connection on developer's machine.
Please advise. Thank you.
Best Regards,
Lynn
"Sue Hoegemeier" wrote:

> What is the exact error message and error number he gets
> when he tries to log into SQL Server?
> -Sue
> On Thu, 22 Mar 2007 10:33:45 -0700, Lynn
> <Lynn@.discussions.microsoft.com> wrote:
>
>
|||Check the following article in Books Online:
http://msdn2.microsoft.com/en-us/library/ms175496.aspx
-Sue
On Fri, 23 Mar 2007 09:15:08 -0700, Lynn
<Lynn@.discussions.microsoft.com> wrote:

>We only enable Shared Memory and TCP/IP protocal in server side. And, those
>are the error they are getting.
>osql -- SQL server doesn't exist or access denied
>Query Analyzer -- General network error. Check your network documentation
>VS 2005 -- (without specifing TCP protocal in connection) A connection was
>succssfully established with the server, but then an error occured during the
>pre-login handshake. When connecting ....(provider: Named Pipes provider,
>error: 0 - No process is on the ther end of the pipe)
>VS 2005 -- (specify TCP protocal in connection) 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 ...
>(provider: TCP provider: 0 -- A connection attempt failed because the
>connected party didn't not properly respond after a period of tiem, or
>established connection failed because connected host has failed to respond.)
>Again, this developer is able to login by using my machine with his WIN
>account.
>After I enable Named Pipes in server. This developer is able to connect to
>server on his machine by using Named Pipe.
>Firewall is off in the server, so I can't think of the issue for TCP
>connection on developer's machine.
>Please advise. Thank you.
|||Sue,
The developer's client protocol order is TCP and NP. We didn't enable Named
Pipe in server at the beginning, that's why the first message is NP message
due to client will try to connect in the protocol order in the client. As I
menetioned, after I turn on Named Pipes in server, user's machine is able to
connect to server. But, the issue our developers had is that they couldn't
connect with TCP protocol from their machine. (I can connect by TCP protocol
from my machine. The developer login to my machine and his win account can
connect to the server as well). His machine is able to connect to our SQL
2000 with TCP protocol, but just can't connect to 2005 with TCP protocol. I
was thinging is firewall in server to caused this issue, but firewall didn't
enable in the server at all. So, I don't know what cause the issue.
Please advise.
Best Regards,
Lynn
"Sue Hoegemeier" wrote:

> Check the following article in Books Online:
> http://msdn2.microsoft.com/en-us/library/ms175496.aspx
> -Sue
> On Fri, 23 Mar 2007 09:15:08 -0700, Lynn
> <Lynn@.discussions.microsoft.com> wrote:
>
>
|||When you get symptoms like this where it only affects the
user on a particular PC then you need to look at that PC.
You'd probably start by testing basic connectivity to the
server from the PC: Can the user ping the server by name,
can the user ping the server by IP, what network related
issues are found in the Event logs on the PC, can the user
connect to the server using sqlcmd, etc. Also, have you
tried logging in from that users PC?
If you find that the issue is comes up only with Management
Studio, have the user increase the connect timeout in SSMS:
When logging on, click on the options button in the Connect
to Server window and increase the connection timeout to
something greater than the 15 second default.
It would also be worth checking the users MDAC installation
using the component checker. You can download this from:
http://msdn2.microsoft.com/en-us/data/aa937730.aspx
You may also want to look at applying the latest SQL Server
service pack to the client on that PC having problems.
-Sue
On Thu, 29 Mar 2007 15:38:05 -0700, Lynn
<Lynn@.discussions.microsoft.com> wrote:

>Sue,
>The developer's client protocol order is TCP and NP. We didn't enable Named
>Pipe in server at the beginning, that's why the first message is NP message
>due to client will try to connect in the protocol order in the client. As I
>menetioned, after I turn on Named Pipes in server, user's machine is able to
>connect to server. But, the issue our developers had is that they couldn't
>connect with TCP protocol from their machine. (I can connect by TCP protocol
>from my machine. The developer login to my machine and his win account can
>connect to the server as well). His machine is able to connect to our SQL
>2000 with TCP protocol, but just can't connect to 2005 with TCP protocol. I
>was thinging is firewall in server to caused this issue, but firewall didn't
>enable in the server at all. So, I don't know what cause the issue.
>Please advise.
|||Sue,
Thank you again. Definitely, we already checked the network connect from
those developers machine. The connection issue happens to all related
developers. The developers were able to ping the server by name and IP from
their machine. But, the issue only happened on connecting to SQL 2005 with
TCP protocol. We tested through ODBC (with TCP/IP), osql, telnet to 1433
port, VS, but all connection were failed.
One developer already reinstall SQL 2005 client, but the problem is still
resisted. Will ask them to update to sp2 and go from there.
Best Regards,
Lynn
"Sue Hoegemeier" wrote:

> When you get symptoms like this where it only affects the
> user on a particular PC then you need to look at that PC.
> You'd probably start by testing basic connectivity to the
> server from the PC: Can the user ping the server by name,
> can the user ping the server by IP, what network related
> issues are found in the Event logs on the PC, can the user
> connect to the server using sqlcmd, etc. Also, have you
> tried logging in from that users PC?
> If you find that the issue is comes up only with Management
> Studio, have the user increase the connect timeout in SSMS:
> When logging on, click on the options button in the Connect
> to Server window and increase the connection timeout to
> something greater than the 15 second default.
> It would also be worth checking the users MDAC installation
> using the component checker. You can download this from:
> http://msdn2.microsoft.com/en-us/data/aa937730.aspx
> You may also want to look at applying the latest SQL Server
> service pack to the client on that PC having problems.
> -Sue

Connection error to As 2000 cube data source

Here is my setup: I have Reporting Service and SQL Server 2000 in one box
(Box A), and IIS and Analysis Service in another box (Box B), which has
couple of cubes based on the database in Box A, using SQL Authentication and
Allow save password. Create AS2000 data source at Reporting Project, then
create a report, I can preview the report fine in VS.2003. But I got the
following error after deploying the report to the reportserver and browse the
report:
Cannot create a connection to data source 'Cube'. (rsErrorOpeningConnection)
Get Online Help
Database 'Cube' does not exist.
Do I miss anything?
Thanks
DonAre the cubes on the same domain with your report server?
If not, it won't connect.
"Don" <Don@.discussions.microsoft.com> wrote in message
news:26BEED36-14C5-48A1-87DA-E751CB391888@.microsoft.com...
> Here is my setup: I have Reporting Service and SQL Server 2000 in one box
> (Box A), and IIS and Analysis Service in another box (Box B), which has
> couple of cubes based on the database in Box A, using SQL Authentication
> and
> Allow save password. Create AS2000 data source at Reporting Project, then
> create a report, I can preview the report fine in VS.2003. But I got the
> following error after deploying the report to the reportserver and browse
> the
> report:
> Cannot create a connection to data source 'Cube'.
> (rsErrorOpeningConnection)
> Get Online Help
> Database 'Cube' does not exist.
> Do I miss anything?
> Thanks
> Don
>|||Chris,
Thanks for the quick response. Yes, my OLAP server and Report Server on the
same domain, and my domain user account on both boxes.
"Chris" wrote:
> Are the cubes on the same domain with your report server?
> If not, it won't connect.
> "Don" <Don@.discussions.microsoft.com> wrote in message
> news:26BEED36-14C5-48A1-87DA-E751CB391888@.microsoft.com...
> > Here is my setup: I have Reporting Service and SQL Server 2000 in one box
> > (Box A), and IIS and Analysis Service in another box (Box B), which has
> > couple of cubes based on the database in Box A, using SQL Authentication
> > and
> > Allow save password. Create AS2000 data source at Reporting Project, then
> > create a report, I can preview the report fine in VS.2003. But I got the
> > following error after deploying the report to the reportserver and browse
> > the
> > report:
> >
> > Cannot create a connection to data source 'Cube'.
> > (rsErrorOpeningConnection)
> > Get Online Help
> > Database 'Cube' does not exist.
> > Do I miss anything?
> >
> > Thanks
> >
> > Don
> >
>
>

connecting using a trusted connection

Hello,

I appologize if this is in the wrong spot, but it seemed like the appropriate place.

We have IIS installed on one box and SQL on another. We use a trusted connection to connect.

When we try an connect to our DB, we don't get an error, the page just refreshes. From what i have gathered, it looks like we are not being authenticated. We have the ASPNET domain user on both boxes and its configured with the correct permissions, but we still can't connect.

Do i need to set up or give permissions to another account i dont know about, or is there some file that needs access?

Have you checked SQL logs, or IIS logs? Event logs? If it's a securtiy issue it should be logged. Also make sure you really are using the ASP.NET account when you access the box, it could be an authenticated user's credentials that are passed. And keep in mind that by defualt the ASp.NET process account is not a domain account, it's local.

Jeff

|||There are two permissions in SQL Server, the server permissions in the management section of Enterprise Manager or Management Studio and the database permissions are in the database under permissions and in SQL Server 2005 under security in the database. You may have created one and not the other. Hope this helps.

Connecting to SSIS in Management Studio.

Hi:

I have 4 named instances of SQL 2005 running on one of our sales server (dont ask me why I have 4 instances.Its a beefy box btw). All the instances have SSIS Packages (around 6-7 in each instance) saved to the SQL server and not to the file system. The issue is every time i need to look at the packages or export the packages from SSMS I have to edit the MsDtsSrvr.ini.xml and type in the named instance name within the <ServerName></ServerName> tag . I then have to restart my SSIS. I dont see an easier approach to this method.

This is causing me a lot of unnecessary time waste. is there anyway this can be automated where in i can pass the instance name dynamically to the ini file or even more best, can I have all the instance names in the ini file and some how look at the packages in each Instance. I am not sure how having all the instance names in the ini file woud resolve the issue though.

I know I can use BIDS which is much more flexible and a recommended approach but need a solution for looking at SSIS packages through SSMS in all of the 4 instances. I look forward to recommendations from anyone who have better ideas and suggestions.

Thank you

AK

you could create a console app that edits the xml file and re-starts ssis.|||

Thanks Duane. Do you happen to have an example code sample on how to do that?. I can build looking from that.

Thanks again

AK

|||

Ankith wrote:

Thanks Duane. Do you happen to have an example code sample on how to do that?. I can build looking from that.

Thanks again

AK

unfortunately, i don't have a code example to share with you. however, writing such an application should be fairly straightforward (provided that you know .NET). the .NET system.xml namespace provides a number of classes to manipulate xml data. also, the system.serviceprocess namespace provides classes to manipulate windows services.

i hope this helps.

|||

Hi Duane:

I got this working. I am posting the code snippet for the benefit of others. I have created a SQL Agent job that changes the server name in the XML ini file and restarts SSIS. Restarting I do it through the Job step. Works great.

if (File.Exists(xmlFile))
{
XmlDocument doc = new XmlDocument();
doc.Load(xmlFile);

XmlNode node = doc.SelectSingleNode(@."//*[local-name()='ServerName']");

if (node == null)
{
Console.Write("Node does not exist");
}
else
{
node.InnerText = value;
}

node = null;

doc.Save(xmlFile);

Thanks again for your help.

AK

|||Instead of switching between the servers, you can simply add them all to the SSIS service config file! Simply copy the <FOLDER> tag (till the end - </FOLDER>) as many times as you have SQL instances, give each one unique <NAME>, save config file and restart the SSIS service:

...
<TopLevelFolders>
<Folder xsi:type="SqlServerFolder">
<Name>Sql1</Name>
<ServerName>.\Instance1</ServerName>
</Folder>
<Folder xsi:type="SqlServerFolder">
<Name>Sql2</Name>
<ServerName>.\Instance2</ServerName>
</Folder>
<Folder xsi:type="SqlServerFolder">
<Name>Sql3</Name>
<ServerName>.\Instance3</ServerName>
</Folder>
</TopLevelFolders>
...|||

WOW!!!. Thats cool. Thanks Michael.I used your solution and it works great and I dont need my code anymore. DBAs who dont have much experience with C# will find your method really helpful.

Thanks for posting it.

Best Regards

AK

Connecting to SSIS in Management Studio.

Hi:

I have 4 named instances of SQL 2005 running on one of our sales server (dont ask me why I have 4 instances.Its a beefy box btw). All the instances have SSIS Packages (around 6-7 in each instance) saved to the SQL server and not to the file system. The issue is every time i need to look at the packages or export the packages from SSMS I have to edit the MsDtsSrvr.ini.xml and type in the named instance name within the <ServerName></ServerName> tag . I then have to restart my SSIS. I dont see an easier approach to this method.

This is causing me a lot of unnecessary time waste. is there anyway this can be automated where in i can pass the instance name dynamically to the ini file or even more best, can I have all the instance names in the ini file and some how look at the packages in each Instance. I am not sure how having all the instance names in the ini file woud resolve the issue though.

I know I can use BIDS which is much more flexible and a recommended approach but need a solution for looking at SSIS packages through SSMS in all of the 4 instances. I look forward to recommendations from anyone who have better ideas and suggestions.

Thank you

AK

you could create a console app that edits the xml file and re-starts ssis.|||

Thanks Duane. Do you happen to have an example code sample on how to do that?. I can build looking from that.

Thanks again

AK

|||

Ankith wrote:

Thanks Duane. Do you happen to have an example code sample on how to do that?. I can build looking from that.

Thanks again

AK

unfortunately, i don't have a code example to share with you. however, writing such an application should be fairly straightforward (provided that you know .NET). the .NET system.xml namespace provides a number of classes to manipulate xml data. also, the system.serviceprocess namespace provides classes to manipulate windows services.

i hope this helps.

|||

Hi Duane:

I got this working. I am posting the code snippet for the benefit of others. I have created a SQL Agent job that changes the server name in the XML ini file and restarts SSIS. Restarting I do it through the Job step. Works great.

if (File.Exists(xmlFile))
{
XmlDocument doc = new XmlDocument();
doc.Load(xmlFile);

XmlNode node = doc.SelectSingleNode(@."//*[local-name()='ServerName']");

if (node == null)
{
Console.Write("Node does not exist");
}
else
{
node.InnerText = value;
}

node = null;

doc.Save(xmlFile);

Thanks again for your help.

AK

|||Instead of switching between the servers, you can simply add them all to the SSIS service config file! Simply copy the <FOLDER> tag (till the end - </FOLDER>) as many times as you have SQL instances, give each one unique <NAME>, save config file and restart the SSIS service:

...
<TopLevelFolders>
<Folder xsi:type="SqlServerFolder">
<Name>Sql1</Name>
<ServerName>.\Instance1</ServerName>
</Folder>
<Folder xsi:type="SqlServerFolder">
<Name>Sql2</Name>
<ServerName>.\Instance2</ServerName>
</Folder>
<Folder xsi:type="SqlServerFolder">
<Name>Sql3</Name>
<ServerName>.\Instance3</ServerName>
</Folder>
</TopLevelFolders>
...|||

WOW!!!. Thats cool. Thanks Michael.I used your solution and it works great and I dont need my code anymore. DBAs who dont have much experience with C# will find your method really helpful.

Thanks for posting it.

Best Regards

AK

connecting to SQL Server with PHP issue

Hi all,

I've tried googling this.

I'm attempting to connect to a DB on SQL Server on a MS 2003 server box. The DB is for a different application that the office uses, and I'm not the owner of it. I'm attempting to connect without making any changes to the server side of things.

The sql server I'm attempting to connect to is set up with: "with Windows NT Authentication using the Network Login ID"

On my Linux box in PHP, I've tried using a valid Network Login ID and it's not working. I can connect to other data sources that use other login types on the same box.

I can from other boxes use MS Access and connect to the data.

Is there something special I need to do in PHP to connect to the DB?

here's some of my php code:

$con = mssql_connect('192.168.111.2', 'xxxxxxx', 'yyyyyyy');
$result = mssql_query ('select * from policyregister');
while ($row=mssql_fetch_array($result))
{ print $row[1]; }
mssql_close($numero);I think you are going to need to use SQL Server authentication for web apps. When I code ASP that is how I always do it. Which means the SQL Server might have to changed to mixed mode. Windows Authentication may not work off of the LAN. I am not 100% on this.

Hi all,

I've tried googling this.

I'm attempting to connect to a DB on SQL Server on a MS 2003 server box. The DB is for a different application that the office uses, and I'm not the owner of it. I'm attempting to connect without making any changes to the server side of things.

The sql server I'm attempting to connect to is set up with: "with Windows NT Authentication using the Network Login ID"

On my Linux box in PHP, I've tried using a valid Network Login ID and it's not working. I can connect to other data sources that use other login types on the same box.

I can from other boxes use MS Access and connect to the data.

Is there something special I need to do in PHP to connect to the DB?

here's some of my php code:

$con = mssql_connect('192.168.111.2', 'xxxxxxx', 'yyyyyyy');
$result = mssql_query ('select * from policyregister');
while ($row=mssql_fetch_array($result))
{ print $row[1]; }
mssql_close($numero);|||ahhh OK. thanks. I have a windows program that works that does a "backup" of the sql server data to mysql. Maybe I just cron job that to run once a minute since my data isnt that critical. :)

I didnt see any stuff on for PHP on SQL Server authentication for web apps.

thanks. you confirmed what I was dreading. heheh