Error Count not obtain information about Windows NT group/user

We receive an error as the server attempts to create a publication. The user
has permissions on both the server as an administrator and as an sa. This
conflict should not occur. Can anyone help to explain this? It has been
suggested we go to SP4. There are concerns about firmware and blue screening
on the primary server at this time may preclude sp4 as an option.
Regards,
Jamie
Is there a possibility that when an Enterprise 2005 version of SQL encounters
a Standard version 2000, that this error pops up?
Regards,
Jamie
"thejamie" wrote:

> We receive an error as the server attempts to create a publication. The user
> has permissions on both the server as an administrator and as an sa. This
> conflict should not occur. Can anyone help to explain this? It has been
> suggested we go to SP4. There are concerns about firmware and blue screening
> on the primary server at this time may preclude sp4 as an option.
> --
> Regards,
> Jamie

Error connecting to remote server

Hi
I am trying to cerate a System DSN (in ODBC Data Source Administrator) for a
remote SQL Server. I am getting the below error message;
Connection failed:
SQL State: '01000'
SQL Server Error: 14
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Invalid
Instance())
Connection failed:
SQL State: '08001'
SQL Server Error: 14
[Microsoft][ODBC SQL Server Driver][DBNETLIB]Invalid Connection
What is the problem and how can I fix it?
Thanks
RegardsOn Sep 14, 4:57 pm, "John" <J...@.nospam.infovis.co.uk> wrote:
> Hi
> I am trying to cerate a System DSN (in ODBC Data Source Administrator) for a
> remote SQL Server. I am getting the below error message;
> Connection failed:
> SQL State: '01000'
> SQL Server Error: 14
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Invalid
> Instance())
> Connection failed:
> SQL State: '08001'
> SQL Server Error: 14
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]Invalid Connection
> What is the problem and how can I fix it?
> Thanks
> Regards
the remote server isn't running sql as a named instance is it?|||Not sure. It is our web hosts which is an outside company. What should I ask
them to do?
Many Thanks
Regards
"densial" <densial@.gmail.com> wrote in message
news:1189754261.882976.147900@.r34g2000hsd.googlegroups.com...
> On Sep 14, 4:57 pm, "John" <J...@.nospam.infovis.co.uk> wrote:
>> Hi
>> I am trying to cerate a System DSN (in ODBC Data Source Administrator)
>> for a
>> remote SQL Server. I am getting the below error message;
>> Connection failed:
>> SQL State: '01000'
>> SQL Server Error: 14
>> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Invalid
>> Instance())
>> Connection failed:
>> SQL State: '08001'
>> SQL Server Error: 14
>> [Microsoft][ODBC SQL Server Driver][DBNETLIB]Invalid Connection
>> What is the problem and how can I fix it?
>> Thanks
>> Regards
> the remote server isn't running sql as a named instance is it?
>|||We are trying to access the SQL Server from behind an ISA 2004 firewall.
Even though I have created a rule for port 1433 on ISA 2004, I wonder if
there is something still missing at the ISA 2004 that I need to do.
Many Thanks
Regards
"densial" <densial@.gmail.com> wrote in message
news:1189754261.882976.147900@.r34g2000hsd.googlegroups.com...
> On Sep 14, 4:57 pm, "John" <J...@.nospam.infovis.co.uk> wrote:
>> Hi
>> I am trying to cerate a System DSN (in ODBC Data Source Administrator)
>> for a
>> remote SQL Server. I am getting the below error message;
>> Connection failed:
>> SQL State: '01000'
>> SQL Server Error: 14
>> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Invalid
>> Instance())
>> Connection failed:
>> SQL State: '08001'
>> SQL Server Error: 14
>> [Microsoft][ODBC SQL Server Driver][DBNETLIB]Invalid Connection
>> What is the problem and how can I fix it?
>> Thanks
>> Regards
> the remote server isn't running sql as a named instance is it?
>|||On Sep 14, 8:49 pm, "John" <J...@.nospam.infovis.co.uk> wrote:
> We are trying to access the SQL Server from behind an ISA 2004 firewall.
> Even though I have created a rule for port 1433 on ISA 2004, I wonder if
> there is something still missing at the ISA 2004 that I need to do.
> Many Thanks
> Regards
> "densial" <dens...@.gmail.com> wrote in message
> news:1189754261.882976.147900@.r34g2000hsd.googlegroups.com...
> > On Sep 14, 4:57 pm, "John" <J...@.nospam.infovis.co.uk> wrote:
> >> Hi
> >> I am trying to cerate a System DSN (in ODBC Data Source Administrator)
> >> for a
> >> remote SQL Server. I am getting the below error message;
> >> Connection failed:
> >> SQL State: '01000'
> >> SQL Server Error: 14
> >> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Invalid
> >> Instance())
> >> Connection failed:
> >> SQL State: '08001'
> >> SQL Server Error: 14
> >> [Microsoft][ODBC SQL Server Driver][DBNETLIB]Invalid Connection
> >> What is the problem and how can I fix it?
> >> Thanks
> >> Regards
> > the remote server isn't running sql as a named instance is it?
that error msg <snip>Invalid Instance()</snip> makes me think your
providor is using a named instance, just ask them if they are, then
reference your server as "servername\instancename" (check the slash
direction, can't remember off hand if it's forward or backward).
Another issue could be the port number, try either "servername,1433"
or "servername\instancename,1433" as your server address. this is
often a problem if your using load balanced sql server. also there's
somestuff about the server knowing which port to reply on (for
sql2005), but this is a bit more complex and sometimes requires some
server side config in awkward situations, anyways if it's 2k5 your
connecting to read up about sqlbrowser replying to the client on port
1434 instead of 1433.

Error connecting new data source to SQL Server Express

In ODBC Data Source Administrator, I add the SQL Server driver, complete a name and select my local SQL Server instance, select Windows NT authentication (the client configuration is set to TCP/IP, dynamically determine port) and on clicking Next, the following errors occur:

Connection failed:
SQLState: '01000'
SQL Server error: 2
[Microsoft][ODBC SQL Server Driver][Shared Memory][ConnectionOpen (Connect()).
Connection failed:
SQLState: '08001'
SQL Server error: 17
[Microsoft][ODBC SQL Server Driver][Shared Memory]SQL Server does not exist or access denied.

I note that in the Help it says: "The SQL Server system administrator must have associated your Microsoft Windows login with a SQL Server login ID".

Is this the problem? If so, where do I make this association?

Thanking you in anticipation.

In a default installation of SQL Express, every user on a computer can at least connect to the server. The fact that you're connection is failing suggests that something else is wrong. Based on the error, the most likely cause is that you've mis-typed the server name. SQL Express installs to a named instance so you need to provide both the machine name and instance name in your connection, be default, the instance name is SQLEXPRESS, so your server name would be <machinename>\SQLEXPRES. For local connection you can replace <machinename> with "(local)" or "." Note that it's a back slash, people commonly use the forward slash which will cause an error.

If that doesn't help, verify which SQL driver you are using, there are two of them. It looks like you're using the Native Client, which is good, but if you're using the old MDAC driver (just says "SQL Server" in the list) then you'll need to enable the TCP protocol for the Server using the SQL Configuration Manager. MDAC ODBC connection go through TCP, even for local connections.

Mike

|||

Hi,

I would suggest to refer http://support.microsoft.com/kb/322336 & http://support.microsoft.com/kb/328306/en-us

Hemantgiri S. Goswami

Error connecting new data source to SQL Server Express

In ODBC Data Source Administrator, I add the SQL Server driver, complete a name and select my local SQL Server instance, select Windows NT authentication (the client configuration is set to TCP/IP, dynamically determine port) and on clicking Next, the following errors occur:

Connection failed:
SQLState: '01000'
SQL Server error: 2
[Microsoft][ODBC SQL Server Driver][Shared Memory][ConnectionOpen (Connect()).
Connection failed:
SQLState: '08001'
SQL Server error: 17
[Microsoft][ODBC SQL Server Driver][Shared Memory]SQL Server does not exist or access denied.

I note that in the Help it says: "The SQL Server system administrator must have associated your Microsoft Windows login with a SQL Server login ID".

Is this the problem? If so, where do I make this association?

Thanking you in anticipation.

In a default installation of SQL Express, every user on a computer can at least connect to the server. The fact that you're connection is failing suggests that something else is wrong. Based on the error, the most likely cause is that you've mis-typed the server name. SQL Express installs to a named instance so you need to provide both the machine name and instance name in your connection, be default, the instance name is SQLEXPRESS, so your server name would be <machinename>\SQLEXPRES. For local connection you can replace <machinename> with "(local)" or "." Note that it's a back slash, people commonly use the forward slash which will cause an error.

If that doesn't help, verify which SQL driver you are using, there are two of them. It looks like you're using the Native Client, which is good, but if you're using the old MDAC driver (just says "SQL Server" in the list) then you'll need to enable the TCP protocol for the Server using the SQL Configuration Manager. MDAC ODBC connection go through TCP, even for local connections.

Mike

|||

Hi,

I would suggest to refer http://support.microsoft.com/kb/322336 & http://support.microsoft.com/kb/328306/en-us

Hemantgiri S. Goswami