Cannot Create System DSN

Hi,
I'm having some difficulty creating a system DSN on a
win2K machine for connecting to a SQL 2000 server. I'm not
sure if this may be a better question for the windows
group, but... Anyway, when I go through the odbc setup in
windows, the DSN does not appear in the list of system
dsn's that are already created. I begin to create it, and
it says it already exists, "overwrite?". (this is because
I have already tried creating it with that name, and am
using the same dsn name. If I use a new name, I don't get
the "already exists" message, but the following problem
still occurs.) I do so, and continue through creating the
dsn and successfully testing the connection. When I
finish the creation, the dsn name still does not appear in
the list of system dsn's. Is this a corrupt odbc database
on the win2K machine? I have no idea!!! PS I am tryiing
to create it with local Administrator priveledges.
Any help would be appreciated.
Thanks
David
Check the permissions on the following registry key:
HKLM\Software\ODBC\ODBC.INI
Rand
This posting is provided "as is" with no warranties and confers no rights.
|||I'm also experiencing the same problem. I've checked the permissions on the related key in the registry, and have given Full Permission to all users, but to no avail. Any other suggestions?
************************************************** ********************
Sent via Fuzzy Software @. http://www.fuzzysoftware.com/
Comprehensive, categorised, searchable collection of links to ASP & ASP.NET resources...

Cannot Create System DSN

Hi,
I'm having some difficulty creating a system DSN on a
win2K machine for connecting to a SQL 2000 server. I'm not
sure if this may be a better question for the windows
group, but... Anyway, when I go through the odbc setup in
windows, the DSN does not appear in the list of system
dsn's that are already created. I begin to create it, and
it says it already exists, "overwrite?". (this is because
I have already tried creating it with that name, and am
using the same dsn name. If I use a new name, I don't get
the "already exists" message, but the following problem
still occurs.) I do so, and continue through creating the
dsn and successfully testing the connection. When I
finish the creation, the dsn name still does not appear in
the list of system dsn's. Is this a corrupt odbc database
on the win2K machine? I have no idea!!! PS I am tryiing
to create it with local Administrator priveledges.
Any help would be appreciated.
Thanks
DavidCheck the permissions on the following registry key:
HKLM\Software\ODBC\ODBC.INI
Rand
This posting is provided "as is" with no warranties and confers no rights.|||I'm also experiencing the same problem. I've checked the permissions on the
related key in the registry, and have given Full Permission to all users, bu
t to no avail. Any other suggestions?
****************************************
******************************
Sent via Fuzzy Software @. http://www.fuzzysoftware.com/
Comprehensive, categorised, searchable collection of links to ASP & ASP.NET
resources...

Cannot create SSIS projects

When i create a new SSIS project, the system alert will popup a window to show 'Constructor on type 'Microsoft.DataTransformationService.wizards.ETLProjectInitializer' not found'

I met this kind of questions more than 3 time.

Reinstall VS2005?

How should i do?

It sounds like something in the system dll's did not get included or was removed.

Probably the best thing would be to reinstall business intelligence which is a part of the SQL Server install

Re Installing Visual Studio would do nothing due to the fact that SSIS is not associated with Visual Studio 2005 other then through Business Intelligence.

Cannot copy : Insufficient system resources

Production Server: Win2k Advanced Server, SQL 2k Advanced Server, Both fully
patched, 4 processors, 5 GB RAM, 320 GB partition, 68 GB DataBase, SAN, 2 2GB
Fiber NICS teamed
Development Server: Win2k Server, SQL 2k Server, two processors, 2 GB RAM,
Raid 5 SCSI controller, 4 100 mb NICS teamed
Both servers have lots of room on the partition.
We've been refreshing the development server with fresh production data
every three months. My method for doing this has been to do a local backup of
the production server, then copy the bak file to the development server. This
has been working for several years. The bak file is now 70 GB. The last time
it worked the bak file was around 65 GB. Last night the copy of the bak file
over the network failed about halfway through with a popup:
"Cannot copy prd. bak : Insufficient system resources exist to complete the
requested service" There are no entries in either server's application or
system event logs. I've read the MSFT KB Article 259837 but that doesn't seem
to apply because (a) the failure occured about one hour into the copy process
and (b) both servers are fully patched.
Developers are beating on me to get this done tonight. I suspect in the long
run, I will have to get something like SQL lite speed. But I would like a
quick fix for tonight. I would prefer not to shut down the production db and
copy the individual files.
Here are my thoughts:
1. Would I have better luck if I backed up with a UNC path to the
development server?
2. Can I compress the bak file with something?
Any suggestions?Personally, I prefer working with UNC paths for backups.
HowTo: Backup to UNC name using Database Maintenance Wizard
http://support.microsoft.com/default.aspx?scid=kb;en-us;555128
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"MangroveGeek" <carl@.tenthousandislands.net(DoNotSpam)> wrote in message
news:130BD949-316B-44F2-9117-B30B9477D24C@.microsoft.com...
> Production Server: Win2k Advanced Server, SQL 2k Advanced Server, Both
> fully
> patched, 4 processors, 5 GB RAM, 320 GB partition, 68 GB DataBase, SAN, 2
> 2GB
> Fiber NICS teamed
> Development Server: Win2k Server, SQL 2k Server, two processors, 2 GB RAM,
> Raid 5 SCSI controller, 4 100 mb NICS teamed
> Both servers have lots of room on the partition.
> We've been refreshing the development server with fresh production data
> every three months. My method for doing this has been to do a local backup
> of
> the production server, then copy the bak file to the development server.
> This
> has been working for several years. The bak file is now 70 GB. The last
> time
> it worked the bak file was around 65 GB. Last night the copy of the bak
> file
> over the network failed about halfway through with a popup:
> "Cannot copy prd. bak : Insufficient system resources exist to complete
> the
> requested service" There are no entries in either server's application or
> system event logs. I've read the MSFT KB Article 259837 but that doesn't
> seem
> to apply because (a) the failure occured about one hour into the copy
> process
> and (b) both servers are fully patched.
> Developers are beating on me to get this done tonight. I suspect in the
> long
> run, I will have to get something like SQL lite speed. But I would like a
> quick fix for tonight. I would prefer not to shut down the production db
> and
> copy the individual files.
> Here are my thoughts:
> 1. Would I have better luck if I backed up with a UNC path to the
> development server?
> 2. Can I compress the bak file with something?
> Any suggestions?

Cannot copy : Insufficient system resources

Production Server: Win2k Advanced Server, SQL 2k Advanced Server, Both fully
patched, 4 processors, 5 GB RAM, 320 GB partition, 68 GB DataBase, SAN, 2 2G
B
Fiber NICS teamed
Development Server: Win2k Server, SQL 2k Server, two processors, 2 GB RAM,
Raid 5 SCSI controller, 4 100 mb NICS teamed
Both servers have lots of room on the partition.
We've been refreshing the development server with fresh production data
every three months. My method for doing this has been to do a local backup o
f
the production server, then copy the bak file to the development server. Thi
s
has been working for several years. The bak file is now 70 GB. The last time
it worked the bak file was around 65 GB. Last night the copy of the bak file
over the network failed about halfway through with a popup:
"Cannot copy prd. bak : Insufficient system resources exist to complete the
requested service" There are no entries in either server's application or
system event logs. I've read the MSFT KB Article 259837 but that doesn't see
m
to apply because (a) the failure occured about one hour into the copy proces
s
and (b) both servers are fully patched.
Developers are beating on me to get this done tonight. I suspect in the long
run, I will have to get something like SQL lite speed. But I would like a
quick fix for tonight. I would prefer not to shut down the production db and
copy the individual files.
Here are my thoughts:
1. Would I have better luck if I backed up with a UNC path to the
development server?
2. Can I compress the bak file with something?
Any suggestions?Personally, I prefer working with UNC paths for backups.
HowTo: Backup to UNC name using Database Maintenance Wizard
http://support.microsoft.com/defaul...kb;en-us;555128
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"MangroveGeek" <carl@.tenthousandislands.net(DoNotSpam)> wrote in message
news:130BD949-316B-44F2-9117-B30B9477D24C@.microsoft.com...
> Production Server: Win2k Advanced Server, SQL 2k Advanced Server, Both
> fully
> patched, 4 processors, 5 GB RAM, 320 GB partition, 68 GB DataBase, SAN, 2
> 2GB
> Fiber NICS teamed
> Development Server: Win2k Server, SQL 2k Server, two processors, 2 GB RAM,
> Raid 5 SCSI controller, 4 100 mb NICS teamed
> Both servers have lots of room on the partition.
> We've been refreshing the development server with fresh production data
> every three months. My method for doing this has been to do a local backup
> of
> the production server, then copy the bak file to the development server.
> This
> has been working for several years. The bak file is now 70 GB. The last
> time
> it worked the bak file was around 65 GB. Last night the copy of the bak
> file
> over the network failed about halfway through with a popup:
> "Cannot copy prd. bak : Insufficient system resources exist to complete
> the
> requested service" There are no entries in either server's application or
> system event logs. I've read the MSFT KB Article 259837 but that doesn't
> seem
> to apply because (a) the failure occured about one hour into the copy
> process
> and (b) both servers are fully patched.
> Developers are beating on me to get this done tonight. I suspect in the
> long
> run, I will have to get something like SQL lite speed. But I would like a
> quick fix for tonight. I would prefer not to shut down the production db
> and
> copy the individual files.
> Here are my thoughts:
> 1. Would I have better luck if I backed up with a UNC path to the
> development server?
> 2. Can I compress the bak file with something?
> Any suggestions?

Cannot copy : Insufficient system resources

Production Server: Win2k Advanced Server, SQL 2k Advanced Server, Both fully
patched, 4 processors, 5 GB RAM, 320 GB partition, 68 GB DataBase, SAN, 2 2GB
Fiber NICS teamed
Development Server: Win2k Server, SQL 2k Server, two processors, 2 GB RAM,
Raid 5 SCSI controller, 4 100 mb NICS teamed
Both servers have lots of room on the partition.
We've been refreshing the development server with fresh production data
every three months. My method for doing this has been to do a local backup of
the production server, then copy the bak file to the development server. This
has been working for several years. The bak file is now 70 GB. The last time
it worked the bak file was around 65 GB. Last night the copy of the bak file
over the network failed about halfway through with a popup:
"Cannot copy prd. bak : Insufficient system resources exist to complete the
requested service" There are no entries in either server's application or
system event logs. I've read the MSFT KB Article 259837 but that doesn't seem
to apply because (a) the failure occured about one hour into the copy process
and (b) both servers are fully patched.
Developers are beating on me to get this done tonight. I suspect in the long
run, I will have to get something like SQL lite speed. But I would like a
quick fix for tonight. I would prefer not to shut down the production db and
copy the individual files.
Here are my thoughts:
1. Would I have better luck if I backed up with a UNC path to the
development server?
2. Can I compress the bak file with something?
Any suggestions?
Personally, I prefer working with UNC paths for backups.
HowTo: Backup to UNC name using Database Maintenance Wizard
http://support.microsoft.com/default...b;en-us;555128
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"MangroveGeek" <carl@.tenthousandislands.net(DoNotSpam)> wrote in message
news:130BD949-316B-44F2-9117-B30B9477D24C@.microsoft.com...
> Production Server: Win2k Advanced Server, SQL 2k Advanced Server, Both
> fully
> patched, 4 processors, 5 GB RAM, 320 GB partition, 68 GB DataBase, SAN, 2
> 2GB
> Fiber NICS teamed
> Development Server: Win2k Server, SQL 2k Server, two processors, 2 GB RAM,
> Raid 5 SCSI controller, 4 100 mb NICS teamed
> Both servers have lots of room on the partition.
> We've been refreshing the development server with fresh production data
> every three months. My method for doing this has been to do a local backup
> of
> the production server, then copy the bak file to the development server.
> This
> has been working for several years. The bak file is now 70 GB. The last
> time
> it worked the bak file was around 65 GB. Last night the copy of the bak
> file
> over the network failed about halfway through with a popup:
> "Cannot copy prd. bak : Insufficient system resources exist to complete
> the
> requested service" There are no entries in either server's application or
> system event logs. I've read the MSFT KB Article 259837 but that doesn't
> seem
> to apply because (a) the failure occured about one hour into the copy
> process
> and (b) both servers are fully patched.
> Developers are beating on me to get this done tonight. I suspect in the
> long
> run, I will have to get something like SQL lite speed. But I would like a
> quick fix for tonight. I would prefer not to shut down the production db
> and
> copy the individual files.
> Here are my thoughts:
> 1. Would I have better luck if I backed up with a UNC path to the
> development server?
> 2. Can I compress the bak file with something?
> Any suggestions?

Cannot connect toMyserver\SQLEXPRESS

Hi,
i installed Sql server 2005 express edition on an Windows XP professionel
sp2 system, which is alos the IIS server..
Of course i first installed .net Framework 2.0.
I installed it with an administrator account and used following options:
local system
services sql server / sql browser
windows authentification
enable user instance
add user to sql server adminsys role
Further i went to Sql server Configuration Manager and did:
protocols for MSSQLSERVER (service): TCP/IP and shared memory enabled
Finaaly, i went to Sql server Surface Area and did: remote connections:
local and remote connections
using TCP/IP only (and later i also tried: using TCP/IP and named pipes)
My problem is:
--
when starting Sql server Management Studio express, everything seems ok: i
see the server name, authentification (windows), user name (the admin
account), but when clicking on "connect" button, after a while, i get the
error:
"Cannot connect to MYSERVER\SQLEXPRESS.
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: SQL Network Interfaces, error: 26 - Error Locating
Server/Instance Specified) (.Net SqlClient Data Provider)".
1) the optiion 'remote connections' is enabled (with tcp/ip)
2) i even don't use remote connections because sql server is installed on
the same server as the IIS server.
I really have no idea what's the problem and how to solve this. I
uninstalled everything twice (.net framework included) but still same error.
Thanks for help.
CasperIs SQL Server Management Express running on the same system as IIS/SQL
Server? If not, it won't connect.
Again, it makes sense to get the Developer Edition ($50 or less) as it does
not have these limitations.
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
----
---
"Casper" <cas@.per.df> wrote in message
news:%237gT%23XJeHHA.4596@.TK2MSFTNGP05.phx.gbl...
> Hi,
> i installed Sql server 2005 express edition on an Windows XP professionel
> sp2 system, which is alos the IIS server..
> Of course i first installed .net Framework 2.0.
> I installed it with an administrator account and used following options:
> local system
> services sql server / sql browser
> windows authentification
> enable user instance
> add user to sql server adminsys role
> Further i went to Sql server Configuration Manager and did:
> protocols for MSSQLSERVER (service): TCP/IP and shared memory enabled
> Finaaly, i went to Sql server Surface Area and did: remote connections:
> local and remote connections
> using TCP/IP only (and later i also tried: using TCP/IP and named pipes)
> My problem is:
> --
> when starting Sql server Management Studio express, everything seems ok: i
> see the server name, authentification (windows), user name (the admin
> account), but when clicking on "connect" button, after a while, i get the
> error:
> "Cannot connect to MYSERVER\SQLEXPRESS.
> 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: SQL Network Interfaces, error: 26 - Error Locating
> Server/Instance Specified) (.Net SqlClient Data Provider)".
> 1) the optiion 'remote connections' is enabled (with tcp/ip)
> 2) i even don't use remote connections because sql server is installed on
> the same server as the IIS server.
> I really have no idea what's the problem and how to solve this. I
> uninstalled everything twice (.net framework included) but still same
> error.
> Thanks for help.
> Casper
>
>|||Thanks for replying.
Yes, it's installed on the same server.
I reinstalled and now i can enter the Management Studio, but when i start an
asp.net application which uses a MDF file, when an aspx file tries to access
the MDF file, i get just the same error.
Even when doing debugging that page in VWD i get that error. This
application ran perfect on another machine.
What did i wrong during installation, where do i have to search? i'm very
confused.
"William (Bill) Vaughn" <billvaRemoveThis@.betav.com> schreef in bericht
news:uunyo6SeHHA.5056@.TK2MSFTNGP02.phx.gbl...
> Is SQL Server Management Express running on the same system as IIS/SQL
> Server? If not, it won't connect.
> Again, it makes sense to get the Developer Edition ($50 or less) as it
> does not have these limitations.
> --
> ____________________________________
> William (Bill) Vaughn
> Author, Mentor, Consultant
> Microsoft MVP
> INETA Speaker
> www.betav.com/blog/billva
> www.betav.com
> Please reply only to the newsgroup so that others can benefit.
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> __________________________________
> Visit www.hitchhikerguides.net to get more information on my latest book:
> Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
> and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
> ----
---
> "Casper" <cas@.per.df> wrote in message
> news:%237gT%23XJeHHA.4596@.TK2MSFTNGP05.phx.gbl...
>|||Let's see your ConnectionString.
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
----
---
"Casper" <ca@.qdq.dfv> wrote in message
news:uMGFqKWeHHA.3632@.TK2MSFTNGP02.phx.gbl...
> Thanks for replying.
> Yes, it's installed on the same server.
> I reinstalled and now i can enter the Management Studio, but when i start
> an asp.net application which uses a MDF file, when an aspx file tries to
> access the MDF file, i get just the same error.
> Even when doing debugging that page in VWD i get that error. This
> application ran perfect on another machine.
> What did i wrong during installation, where do i have to search? i'm very
> confused.
>
> "William (Bill) Vaughn" <billvaRemoveThis@.betav.com> schreef in bericht
> news:uunyo6SeHHA.5056@.TK2MSFTNGP02.phx.gbl...
>|||William, i found it:
i reinstalled sqk server express, but it changed the instance name to
MYSERVER (instead of .\SQLEXPRESS). So the connection strings didn't work
and generated that error which has nothing to do woth remoting connections.
Thanks anyway
"William (Bill) Vaughn" <billvaRemoveThis@.betav.com> schreef in bericht
news:OFIzPAXeHHA.3648@.TK2MSFTNGP05.phx.gbl...
> Let's see your ConnectionString.
> --
> ____________________________________
> William (Bill) Vaughn
> Author, Mentor, Consultant
> Microsoft MVP
> INETA Speaker
> www.betav.com/blog/billva
> www.betav.com
> Please reply only to the newsgroup so that others can benefit.
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> __________________________________
> Visit www.hitchhikerguides.net to get more information on my latest book:
> Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
> and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
> ----
---
> "Casper" <ca@.qdq.dfv> wrote in message
> news:uMGFqKWeHHA.3632@.TK2MSFTNGP02.phx.gbl...
>

Cannot connect toMyserver\SQLEXPRESS

Hi,
i installed Sql server 2005 express edition on an windows xp professionel
sp2 system, which is alos the IIS server..
Of course i first installed .net Framework 2.0.
I installed it with an administrator account and used following options:
local system
services sql server / sql browser
windows authentification
enable user instance
add user to sql server adminsys role
Further i went to Sql server Configuration Manager and did:
protocols for MSSQLSERVER (service): TCP/IP and shared memory enabled
Finaaly, i went to Sql server Surface Area and did: remote connections:
local and remote connections
using TCP/IP only (and later i also tried: using TCP/IP and named pipes)
My problem is:
when starting Sql server Management Studio express, everything seems ok: i
see the server name, authentification (windows), user name (the admin
account), but when clicking on "connect" button, after a while, i get the
error:
"Cannot connect to MYSERVER\SQLEXPRESS.
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: SQL Network Interfaces, error: 26 - Error Locating
Server/Instance Specified) (.Net SqlClient Data Provider)".
1) the optiion 'remote connections' is enabled (with tcp/ip)
2) i even don't use remote connections because sql server is installed on
the same server as the IIS server.
I really have no idea what's the problem and how to solve this. I
uninstalled everything twice (.net framework included) but still same error.
Thanks for help.
Casper
Is SQL Server Management Express running on the same system as IIS/SQL
Server? If not, it won't connect.
Again, it makes sense to get the Developer Edition ($50 or less) as it does
not have these limitations.
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
------
"Casper" <cas@.per.df> wrote in message
news:%237gT%23XJeHHA.4596@.TK2MSFTNGP05.phx.gbl...
> Hi,
> i installed Sql server 2005 express edition on an windows xp professionel
> sp2 system, which is alos the IIS server..
> Of course i first installed .net Framework 2.0.
> I installed it with an administrator account and used following options:
> local system
> services sql server / sql browser
> windows authentification
> enable user instance
> add user to sql server adminsys role
> Further i went to Sql server Configuration Manager and did:
> protocols for MSSQLSERVER (service): TCP/IP and shared memory enabled
> Finaaly, i went to Sql server Surface Area and did: remote connections:
> local and remote connections
> using TCP/IP only (and later i also tried: using TCP/IP and named pipes)
> My problem is:
> --
> when starting Sql server Management Studio express, everything seems ok: i
> see the server name, authentification (windows), user name (the admin
> account), but when clicking on "connect" button, after a while, i get the
> error:
> "Cannot connect to MYSERVER\SQLEXPRESS.
> 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: SQL Network Interfaces, error: 26 - Error Locating
> Server/Instance Specified) (.Net SqlClient Data Provider)".
> 1) the optiion 'remote connections' is enabled (with tcp/ip)
> 2) i even don't use remote connections because sql server is installed on
> the same server as the IIS server.
> I really have no idea what's the problem and how to solve this. I
> uninstalled everything twice (.net framework included) but still same
> error.
> Thanks for help.
> Casper
>
>
|||Thanks for replying.
Yes, it's installed on the same server.
I reinstalled and now i can enter the Management Studio, but when i start an
asp.net application which uses a MDF file, when an aspx file tries to access
the MDF file, i get just the same error.
Even when doing debugging that page in VWD i get that error. This
application ran perfect on another machine.
What did i wrong during installation, where do i have to search? i'm very
confused.
"William (Bill) Vaughn" <billvaRemoveThis@.betav.com> schreef in bericht
news:uunyo6SeHHA.5056@.TK2MSFTNGP02.phx.gbl...
> Is SQL Server Management Express running on the same system as IIS/SQL
> Server? If not, it won't connect.
> Again, it makes sense to get the Developer Edition ($50 or less) as it
> does not have these limitations.
> --
> ____________________________________
> William (Bill) Vaughn
> Author, Mentor, Consultant
> Microsoft MVP
> INETA Speaker
> www.betav.com/blog/billva
> www.betav.com
> Please reply only to the newsgroup so that others can benefit.
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> __________________________________
> Visit www.hitchhikerguides.net to get more information on my latest book:
> Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
> and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
> ------
> "Casper" <cas@.per.df> wrote in message
> news:%237gT%23XJeHHA.4596@.TK2MSFTNGP05.phx.gbl...
>
|||Let's see your ConnectionString.
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
------
"Casper" <ca@.qdq.dfv> wrote in message
news:uMGFqKWeHHA.3632@.TK2MSFTNGP02.phx.gbl...
> Thanks for replying.
> Yes, it's installed on the same server.
> I reinstalled and now i can enter the Management Studio, but when i start
> an asp.net application which uses a MDF file, when an aspx file tries to
> access the MDF file, i get just the same error.
> Even when doing debugging that page in VWD i get that error. This
> application ran perfect on another machine.
> What did i wrong during installation, where do i have to search? i'm very
> confused.
>
> "William (Bill) Vaughn" <billvaRemoveThis@.betav.com> schreef in bericht
> news:uunyo6SeHHA.5056@.TK2MSFTNGP02.phx.gbl...
>
|||William, i found it:
i reinstalled sqk server express, but it changed the instance name to
MYSERVER (instead of .\SQLEXPRESS). So the connection strings didn't work
and generated that error which has nothing to do woth remoting connections.
Thanks anyway
"William (Bill) Vaughn" <billvaRemoveThis@.betav.com> schreef in bericht
news:OFIzPAXeHHA.3648@.TK2MSFTNGP05.phx.gbl...
> Let's see your ConnectionString.
> --
> ____________________________________
> William (Bill) Vaughn
> Author, Mentor, Consultant
> Microsoft MVP
> INETA Speaker
> www.betav.com/blog/billva
> www.betav.com
> Please reply only to the newsgroup so that others can benefit.
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> __________________________________
> Visit www.hitchhikerguides.net to get more information on my latest book:
> Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
> and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
> ------
> "Casper" <ca@.qdq.dfv> wrote in message
> news:uMGFqKWeHHA.3632@.TK2MSFTNGP02.phx.gbl...
>

Cannot connect to Sql Server 2005 Express. Any idea why ?

Hi everybody
I have a system with :
WinXP Pro, MSDE 2000, Framework 2.0 beta. On top of it i installed SqlServer
2005 Beta with Mixed Mode. I am using Query Analyzer and Enterperise Manager
from SQLServer 2000 to connect to it (manual says I can) but with no
success. I tried to log on with windows authentication as well as with Sql
authentication . I tried the following names to connect :
(local)\SQLEXPRESS; COMP_NAME\SQLEXPRESS; SQLEXPRESS; MSSQL$SQLEXPRESS and
so on but never got connected. It always say that the
SQL Server does not exist or Access denied.
I checked in the services where it is set to automatic and is running. I
also stopped and restarted but with no success. What i am missing ?
At the end I uninstalled everything and reinstalled only Framework 2.0 and
Sql Server 2005 Beta but having the same problem.
Anyone know how to fix this ?
Thanks in advance
Raja
hi, Raja,
"Ing. Rajesh Kumar" <iambad(Without This)@.post.cz> ha scritto nel messaggio
news:OFSx33CcEHA.2908@.TK2MSFTNGP10.phx.gbl...
> Hi everybody
> I have a system with :
> WinXP Pro, MSDE 2000, Framework 2.0 beta. On top of it i installed
SqlServer
> 2005 Beta with Mixed Mode. I am using Query Analyzer and Enterperise
Manager
> from SQLServer 2000 to connect to it (manual says I can) but with no
> success. I tried to log on with windows authentication as well as with Sql
> authentication . I tried the following names to connect :
> (local)\SQLEXPRESS; COMP_NAME\SQLEXPRESS; SQLEXPRESS; MSSQL$SQLEXPRESS and
> so on but never got connected. It always say that the
> SQL Server does not exist or Access denied.
> I checked in the services where it is set to automatic and is running. I
> also stopped and restarted but with no success. What i am missing ?
> At the end I uninstalled everything and reinstalled only Framework 2.0 and
> Sql Server 2005 Beta but having the same problem.
frorm microsoft.private.sqlserver2005.express newsgroup:
1. Enable Protocols
a. Launch SQL Computer Manager
b. Expand "Server Network Configuration"
c. Expand Protocols for "SQLEXPRESS"
d. Enable Np (for local access)
e. Enable TCP (for remote access)
2. Restart SQL Express
a. can be done from either SQL Computer Manager, Services applet, or
command line
3. Start SQL Browser service from Service applet or command line
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.8.0 - DbaMgr ver 0.54.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply

Cannot Connect to SQL Server 2000 using Windows XP Pro account login info

When I try to create a System DSN connection to our SQL Server 2000
database that is installed on a Windows 2000 machine, I keep on
getting the following error:
Connection failed:
SQLState: '28000'
SQL Server Error: 18452
[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user
'(null)'. Reason: Not associated with a trusted SQL Server connection.
We do not have IIS or any web server installed on the database server
machine or the Windows XP Professional machine that is trying to
connect to the Windows 2000 machine. The machines can all see each
other, and we are actually have the machines networked via the
Workgroup setting, not using the Domain setting. Anyone have any ideas
as to what can be the issue?
Thanks,
Jay
(patel@.cs.utk.edu)
Hi Patel,
Since you're not in a domain, Windows Authentication works very
differently. Windows Authentication is commonly used while you're in a
domain and the client has been authenticated on the domain. The error
message "null" indicates that we're unable to "impersonate" the client in
order to make a Windows Authenticated connection.
You have two optioins.
1. Duplicate the nt username & password on both machines and Use Named
Pipes to Connect.
2. Use SQL Standard Security instead of using Windows Authentication.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
|||Kevin,
How do I create a named pipe? I am not sure as to how to do that.
-Jay
(patel@.cs.utk.edu)
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
|||Named pipes are not created, but rather enabled - with both the
Client and Server Network Utilities.
For the Client Network Utility, start it by Start>Run>cliconfg.exe.
The left pane shows disabled protocols. The right pane shows enabled
protocols. In the left pane, click on Named Pipes and then use the
Enable button between the two panes.
For the Server Network Utility (at least for an MSDE version) find the
file SVRNETCN.EXE. Double click to start and the perform the same
actions as in the Client Network Utility, but for the server instance
in question. If you have installed the server as the default instance,
it will have no name, so its just the computer name that will appear
in the server name pull-down list.
If you have a firewall installed on the machines in question, please
say so, since there will be rules to create to open ports if you have
not done so already.
You should also see the article:
Potential causes of the "SQL Server does not exist or access denied"
error message
http://support.microsoft.com/default...06&Product=sql
Lou Arnold
Ottawa, Canada.
On Wed, 21 Jul 2004 21:15:32 -0700, Jay Patel <patel@.cs.utk.edu>
wrote:

>Kevin,
> How do I create a named pipe? I am not sure as to how to do that.
>-Jay
>(patel@.cs.utk.edu)
>*** Sent via Developersdex http://www.codecomments.com ***
>Don't just participate in USENET...get rewarded for it!
|||Kevin,
Your option 1 below implies that you need Named pipes if you have no
domain controller and want Windows Authentication mode. Is that
correct? If so, is this requirement documented somewhere?
Lou Arnold
On Thu, 22 Jul 2004 00:31:06 GMT, kevmc@.online.microsoft.com (Kevin
McDonnell [MSFT]) wrote:

>Hi Patel,
> Since you're not in a domain, Windows Authentication works very
>differently. Windows Authentication is commonly used while you're in a
>domain and the client has been authenticated on the domain. The error
>message "null" indicates that we're unable to "impersonate" the client in
>order to make a Windows Authenticated connection.
>You have two optioins.
>1. Duplicate the nt username & password on both machines and Use Named
>Pipes to Connect.
>2. Use SQL Standard Security instead of using Windows Authentication.
>Thanks,
>Kevin McDonnell
>Microsoft Corporation
>This posting is provided AS IS with no warranties, and confers no rights.
>
>
|||Hey There,
When I try to connect using the Named Pipes, I have pipes enabled on
both the client and server end, with the server pipe being
"\\.\pipe\sql\query" and trying to keep the client pipe the same as
above. When I try to connect, I get this error:
Attempting connection
[Microsoft][ODBC SQL Server Driver][Named Pipes]SQL Server does not
exist or access denied.
TESTS FAILED!
I have added the user and password that I am logged into now on XP Pro
onto the Windows 2000 Server machine. What do you think I am missing?
-Jay
(patel@.cs.utk.edu)
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
|||Hey There,
I have tried the procedure that was suggested. I have added the user name
and password that I am logged in as on my Windows XP Pro machine to the
Windows 2000 Server machine that has SQL Server 2000 installed on it. I have
also created the same username and password on SQL Server 2000 as a valid
user. I have enabled pipes on the server and client with the server pipe
being the default pipe: "\\.\pipe\sql\query" and I have set the client pipe
to the same value. Now I get this error when I try to do a test connection:
Attempting connection
[Microsoft][ODBC SQL Server Driver][Named Pipes]SQL Server does not exist or
access denied.
TESTS FAILED!
What else could I be missing?
-Jay
(jay@.doityourself.com)
Lou_Arnold@.nospam.com (Lou Arnold) wrote in message news:<40ff4f17.8220370@.nntp.flfrd.phub.net.cable.r ogers.com>...[vbcol=seagreen]
> Kevin,
> Your option 1 below implies that you need Named pipes if you have no
> domain controller and want Windows Authentication mode. Is that
> correct? If so, is this requirement documented somewhere?
> Lou Arnold
> On Thu, 22 Jul 2004 00:31:06 GMT, kevmc@.online.microsoft.com (Kevin
> McDonnell [MSFT]) wrote:
|||Jay...
I can't help you further with your problem, sorry. However at least
you have an error messge. Perhaps Kevin can help.
I am slowly coming to the conclusion that Windows Authentication
doesn't work unless you operate a domain controller. If your situation
permits, you may want to try connecting those two computers into a
network with a domain controller.
My only other suggestion is that you try this same test with the sql
server in mixed or SQL Server mode (the alternatives to Windows
Authentication) and see what happens . I'm not sure how to change the
mode after installation.
Lou.
PS Whatever happens, please let us know. It would be of great value to
me to have the information.
On Thu, 22 Jul 2004 00:31:06 GMT, kevmc@.online.microsoft.com (Kevin
McDonnell [MSFT]) wrote:

>Hi Patel,
> Since you're not in a domain, Windows Authentication works very
>differently. Windows Authentication is commonly used while you're in a
>domain and the client has been authenticated on the domain. The error
>message "null" indicates that we're unable to "impersonate" the client in
>order to make a Windows Authenticated connection.
>You have two optioins.
>1. Duplicate the nt username & password on both machines and Use Named
>Pipes to Connect.
>2. Use SQL Standard Security instead of using Windows Authentication.
>Thanks,
>Kevin McDonnell
>Microsoft Corporation
>This posting is provided AS IS with no warranties, and confers no rights.
>
>
|||Lou,
Thanks for the advice. The reason I would really like to use Windows
Authentication is that when I use the SQL Server Authentication, with
some of the machines, it will prompt you to input the password every
single time you select a database table, or click a form button. It
seems that every move that is made requires that SQL needs to have the
password input.
-Jay
(patel@.cs.utk.edu)
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
|||Hi Patel,
Let's try to get a better error message. Try to make the Named Pipe
connection using a Test ODBC Data Source.
When you create a new ODBC DSN, the wizard will walk you through and
generate a much better error message if it fails.
What we need is the OS Error number.
Example: OS Error 53 == Network name not found
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.

Cannot Connect to SQL Server 2000 using Windows XP Pro account login info

When I try to create a System DSN connection to our SQL Server 2000
database that is installed on a Windows 2000 machine, I keep on
getting the following error:
Connection failed:
SQLState: '28000'
SQL Server Error: 18452
[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for
user
'(null)'. Reason: Not associated with a trusted SQL Server connection.
We do not have IIS or any web server installed on the database server
machine or the Windows XP Professional machine that is trying to
connect to the Windows 2000 machine. The machines can all see each
other, and we are actually have the machines networked via the
Workgroup setting, not using the Domain setting. Anyone have any ideas
as to what can be the issue?
Thanks,
Jay
(patel@.cs.utk.edu)Hi Patel,
Since you're not in a domain, Windows Authentication works very
differently. Windows Authentication is commonly used while you're in a
domain and the client has been authenticated on the domain. The error
message "null" indicates that we're unable to "impersonate" the client in
order to make a Windows Authenticated connection.
You have two optioins.
1. Duplicate the nt username & password on both machines and Use Named
Pipes to Connect.
2. Use SQL Standard Security instead of using Windows Authentication.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||Kevin,
How do I create a named pipe? I am not sure as to how to do that.
-Jay
(patel@.cs.utk.edu)
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!|||Named pipes are not created, but rather enabled - with both the
Client and Server Network Utilities.
For the Client Network Utility, start it by Start>Run>cliconfg.exe.
The left pane shows disabled protocols. The right pane shows enabled
protocols. In the left pane, click on Named Pipes and then use the
Enable button between the two panes.
For the Server Network Utility (at least for an MSDE version) find the
file SVRNETCN.EXE. Double click to start and the perform the same
actions as in the Client Network Utility, but for the server instance
in question. If you have installed the server as the default instance,
it will have no name, so its just the computer name that will appear
in the server name pull-down list.
If you have a firewall installed on the machines in question, please
say so, since there will be rules to create to open ports if you have
not done so already.
You should also see the article:
Potential causes of the "SQL Server does not exist or access denied"
error message
http://support.microsoft.com/defaul...306&Product=sql
Lou Arnold
Ottawa, Canada.
On Wed, 21 Jul 2004 21:15:32 -0700, Jay Patel <patel@.cs.utk.edu>
wrote:

>Kevin,
> How do I create a named pipe? I am not sure as to how to do that.
>-Jay
>(patel@.cs.utk.edu)
>*** Sent via Developersdex http://www.codecomments.com ***
>Don't just participate in USENET...get rewarded for it!|||Kevin,
Your option 1 below implies that you need Named pipes if you have no
domain controller and want Windows Authentication mode. Is that
correct' If so, is this requirement documented somewhere?
Lou Arnold
On Thu, 22 Jul 2004 00:31:06 GMT, kevmc@.online.microsoft.com (Kevin
McDonnell [MSFT]) wrote:

>Hi Patel,
> Since you're not in a domain, Windows Authentication works very
>differently. Windows Authentication is commonly used while you're in a
>domain and the client has been authenticated on the domain. The error
>message "null" indicates that we're unable to "impersonate" the client in
>order to make a Windows Authenticated connection.
>You have two optioins.
>1. Duplicate the nt username & password on both machines and Use Named
>Pipes to Connect.
>2. Use SQL Standard Security instead of using Windows Authentication.
>Thanks,
>Kevin McDonnell
>Microsoft Corporation
>This posting is provided AS IS with no warranties, and confers no rights.
>
>

Cannot connect to RS instance with SS2005 Mgmt Studio or Browser U

I get the message "Cannot connect to $ServerName\$RS2005InstanceName"
Additional Info:
Unable to connect to the remote server(System)
No connection could be made because the target machine actively
refused it (System)
Config Is;
SS2005 Database server ENT SP1(Named instance) $ServerName/$Instance1
SSRS2005 Reporting Services ENT SP1(Named instance) $ServerName/$Instance1
Where the Instancenames are exactly the same, & both the Database server and
RS instances are installed on the same server.
Also get a similar message/errors when trying to access the RS subwebs using
a browser URL.
regardsI'm having basicly the same issue. I can not connect to Report Services
through Management studio or the web interface. I'm running 2003 domain
controller, Small business edition and sql 2005 standard with sql service
pack 1 installed.
"Graham Smith" wrote:
> I get the message "Cannot connect to $ServerName\$RS2005InstanceName"
> Additional Info:
> Unable to connect to the remote server(System)
> No connection could be made because the target machine actively
> refused it (System)
> Config Is;
> SS2005 Database server ENT SP1(Named instance) $ServerName/$Instance1
> SSRS2005 Reporting Services ENT SP1(Named instance) $ServerName/$Instance1
> Where the Instancenames are exactly the same, & both the Database server and
> RS instances are installed on the same server.
> Also get a similar message/errors when trying to access the RS subwebs using
> a browser URL.
> regards
>
>

Cannot connect to MYSERVER\SQLEXPRESS

Hi,

i installed Sql server 2005 express edition on an windows xp professionel sp2 system, which is also the IIS server..
Of course i first installed .net Framework 2.0.

I installed it with an administrator account and used following options:
local system
services sql server / sql browser
windows authentification
enable user instance
add user to sql server adminsys role

Further i went to Sql server Configuration Manager and did:
protocols for MSSQLSERVER (service): TCP/IP and shared memory enabled

Finaaly, i went to Sql server Surface Area and did: remote connections:
local and remote connections
using TCP/IP only (and later i also tried: using TCP/IP and named pipes)

My problem is:
-----
when starting Sql server Management Studio express, everything seems ok: i see the server name, authentification (windows), user name (the admin
account), but when clicking on "connect" button, after a while, i get the error:
"Cannot connect to MYSERVER\SQLEXPRESS.
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: SQL Network Interfaces, error: 26 - Error Locating
Server/Instance Specified) (.Net SqlClient Data Provider)".

I don't understand because:
1) the optiion 'remote connections' is enabled (with tcp/ip)
2) i even don't use remote connections because sql server is installed on
the same server as the IIS server.

I really have no idea what's the problem and how to solve this. I uninstalled everything twice (.net framework included) but still same error.

Thanks for help.
Tartuffe

check to make sure the service is started.

Start --> Control Panel --> Administrative Tools --> Services

In the "Services" window, make sure the service is started. If it is started, try re-starting it.

|||

Hi there!

I am also having a similar problem, but in my case management studio just does not detect any database engine instance (it is running and I checked it) and the drop-down list for servername is empty! I even tried rebuilding the OS and installed SQL server 2005 again, but in vain. Kindly post a solution if you arrive at it, so will I.

Regards

|||

Hello vraval, try this:

[HOSTNAME]\SQLEXPRESS example: SEAN\SQLEXPRESS

to get the host name, open the sql server configuration manager --> "SQL Server 2005 Services" on the left --> right click and select "properties" on 'SQL Server (SQLEXPRESS) - in the right window. In the properties menu, select the 'service' tab and you can find the Host Name property here. Put the HOSTNAME, followed by \SQLEXPRESS -- HOSTNAME\SQLEXPRESS as the server name when logging in.

|||

Hi Sean!

Many thanks for the reply and solving my problem. I am now able to connect to my database engine.

God knows why Microsoft People do not show these important directions.

Thanks and warm regards.

|||

Hi all,

glad for you Vraval, but i still have that error after restarting the service (which was started anyway).

i tried with shared memory, with tcp/ip, without Zone alarm, with a time-out of 60 sec etc ... still same error.

What can i try more?

|||Hello tartuffe,

Check out the following links, if them do not help .. im out of ideas. Im sure you have searched and most likely have found these post also from the way it sounds, but here they are:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=271795&SiteID=1

http://aspnet.tribe.net/thread/628e81d8-6a77-4687-ac16-085d54a376f2

have you asked your question on the MSDN forums? if not, you should search and ask the question there also :) They are also informative and the forums have a wealth of information.|||Sean, i found it:

i reinstalled sqk server express, but it changed the instance name to
MYSERVER (instead of .\SQLEXPRESS). So the connection strings didn't work
and generated that error which has nothing to do woth remoting connections.

Thanks anyway

cannot connect the sql server

Hi Friends

when i am trying to connect the sql server2005 i got the following error message.

here mw6 is my system name, pls guide me how to rectify this.

TITLE: Connect to Server

Cannot connect to mw6.

ADDITIONAL INFORMATION:

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: 2)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=2&LinkId=20476

BUTTONS:

OK

Hi,

have a look here: http://www.sqlserver2005.de > Screencast Section > Enable Remote Connections

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de