Connection Managers are recognized after migrating to another server

Hi,

My database admin just migrated my packages from development to user testing server.

My packages configured to read the connection manager properties from the .dtsconfig.

But I am getting "The connection "CRPRDNMSQEZ.CIReporting2" is not found"

CRPRDNMSQEZ.CIReporting2 is being my connection manager.

I did find and replace server name in the dtsconfig but I guess it didn't work.

Any help is appreciated.

At a guess your connection manager name contained the orginal server name. The connection manager's connection string property ( you may have used other properties such as ServerName) would also have included the server name. When you did the find and replace you change both the connection name and the property values. The connection name should not have changed as that is the object in the package that you are trying to address.

For example take this config file snippet -

<Configuration ConfiguredType="Property" Path="\Package.Connections[ConnName].Properties[ConnectionString]" ValueType="String">
<ConfiguredValue>Data Source=MachineNameInstance;User ID=FunnyName;Password=somethingsecure;</ConfiguredValue>
</Configuration>

ConnName is the connection name, what you see in the Connections tray in the package.

MachineNameInstance is the bit to change. It is probably if you just accepted the defaults the designer gave you that your config file looked a bit like this-

<Configuration ConfiguredType="Property" Path="\Package.Connections[CRPRDNMSQEZ.CIReporting2].Properties[ConnectionString]" ValueType="String">
<ConfiguredValue>Data Source=CRPRDNMSQEZ;Initial Catalog=CIReporting2</ConfiguredValue>
</Configuration>

Doing a find and replace on CRPRDNMSQEZ would have found two hits, one of them being incorrect from your point of view. I strongly recomend when building packages you name things such as connections with functional or logical names, not physical names. It means the name continues to sensible over entire the package lifetime, e.g.

<Configuration ConfiguredType="Property" Path="\Package.Connections[DWReportServer].Properties[ConnectionString]" ValueType="String">
<ConfiguredValue>Data Source=CRPRDNMSQEZ;Initial Catalog=CIReporting2</ConfiguredValue>
</Configuration>

|||Sounds like the name of the connection manager in the .dtsconfig file does not match the name of a connection manager inside the package. Double check that it does.

Connection Managers are NOT recognized after migrating to another server

Hi,

My database admin just migrated my packages from development to user testing server.

My packages configured to read the connection manager properties from the .dtsconfig.

But I am getting "The connection "CRPRDNMSQEZ.CIReporting2" is not found"

CRPRDNMSQEZ.CIReporting2 is being my connection manager.

I did find and replace server name in the dtsconfig but I guess it didn't work.

Any help is appreciated.

At a guess your connection manager name contained the orginal server name. The connection manager's connection string property ( you may have used other properties such as ServerName) would also have included the server name. When you did the find and replace you change both the connection name and the property values. The connection name should not have changed as that is the object in the package that you are trying to address.

For example take this config file snippet -

<Configuration ConfiguredType="Property" Path="\Package.Connections[ConnName].Properties[ConnectionString]" ValueType="String">
<ConfiguredValue>Data Source=MachineNameInstance;User ID=FunnyName;Password=somethingsecure;</ConfiguredValue>
</Configuration>

ConnName is the connection name, what you see in the Connections tray in the package.

MachineNameInstance is the bit to change. It is probably if you just accepted the defaults the designer gave you that your config file looked a bit like this-

<Configuration ConfiguredType="Property" Path="\Package.Connections[CRPRDNMSQEZ.CIReporting2].Properties[ConnectionString]" ValueType="String">
<ConfiguredValue>Data Source=CRPRDNMSQEZ;Initial Catalog=CIReporting2</ConfiguredValue>
</Configuration>

Doing a find and replace on CRPRDNMSQEZ would have found two hits, one of them being incorrect from your point of view. I strongly recomend when building packages you name things such as connections with functional or logical names, not physical names. It means the name continues to sensible over entire the package lifetime, e.g.

<Configuration ConfiguredType="Property" Path="\Package.Connections[DWReportServer].Properties[ConnectionString]" ValueType="String">
<ConfiguredValue>Data Source=CRPRDNMSQEZ;Initial Catalog=CIReporting2</ConfiguredValue>
</Configuration>

|||Sounds like the name of the connection manager in the .dtsconfig file does not match the name of a connection manager inside the package. Double check that it does.sqlsql

Connection issue - Even Admin in the Server Machine

I am having administrative previlages in the SQL Server Machine, but I am
not able to connect to the SQL Server instance. Can you please help. I am
using windows authendication.
Thanks...SafeerI tried telnet ipaddress 1433, its not connecting thru the port.
I am connected to the server directly and then checked the port using server
utility and its 1433.
"Safeer" <safeerm@.gmail.com> wrote in message
news:e1jmNjrVHHA.4028@.TK2MSFTNGP04.phx.gbl...
> I am having administrative previlages in the SQL Server Machine, but I am
> not able to connect to the SQL Server instance. Can you please help. I am
> using windows authendication.
> Thanks...Safeer
>|||I tried telnet ipaddress 1433, its not connecting thru the port.
I am connected to the server directly and then checked the port using server
utility and its 1433.
"Safeer" <safeerm@.gmail.com> wrote in message
news:e1jmNjrVHHA.4028@.TK2MSFTNGP04.phx.gbl...
> I am having administrative previlages in the SQL Server Machine, but I am
> not able to connect to the SQL Server instance. Can you please help. I am
> using windows authendication.
> Thanks...Safeer
>|||We need more info.
- What version and edition of SQL Server are you using?
- What version of the Windows are you using?
It sounds like you are connecting from a client on another computer. If you
are using SQL Server 2005, use the Surface Area Configuration tool to
confirm that your SQL Server instance is listening for remote connections.
Also, a firewall could be blocking 1433. This is common with Windows XP
service pack 2.
If SQL Server is running on Vista, you have other issues.
For SQL Server 2005, there is a short tutorial that will help. See
http://msdn2.microsoft.com/en-us/library/ms345318.aspx
--
Rick Byham (MSFT)
This posting is provided "AS IS" with no warranties, and confers no rights.
"Safeer" <safeerm@.gmail.com> wrote in message
news:eu1sb1rVHHA.1016@.TK2MSFTNGP04.phx.gbl...
>I tried telnet ipaddress 1433, its not connecting thru the port.
> I am connected to the server directly and then checked the port using
> server
> utility and its 1433.
>
> "Safeer" <safeerm@.gmail.com> wrote in message
> news:e1jmNjrVHHA.4028@.TK2MSFTNGP04.phx.gbl...
>|||Hi,
Windows: - Windows NT 5.2 (Build 3790: Service Pack 1)
SQL:- Microsoft SQL Server 2000 - 8.00.194 (Intel X86) Standard Edition
My workstation is Windows 2000. I am connecting to the server using MSTSC.
My sql server log shows the following.
"SQL server listening on Shared Memory, Named Pipes."
Actually TCP/IP/1433 is enabled in the server.
& I am not able to telnet the machine with port 1433 from the server itself.
NB: No one is using this machine now and I need to setup and install service
packs. Its a new box with installed SQL 2K and nobody know the SA password.
Thanks...Safeer
"Rick Byham, (MSFT)" <rickbyh@.REDMOND.CORP.MICROSOFT.COM> wrote in message
news:08EB12C9-D906-4977-A40E-0F050C837E1E@.microsoft.com...
> We need more info.
> - What version and edition of SQL Server are you using?
> - What version of the Windows are you using?
> It sounds like you are connecting from a client on another computer. If
you
> are using SQL Server 2005, use the Surface Area Configuration tool to
> confirm that your SQL Server instance is listening for remote connections.
> Also, a firewall could be blocking 1433. This is common with Windows XP
> service pack 2.
> If SQL Server is running on Vista, you have other issues.
> For SQL Server 2005, there is a short tutorial that will help. See
> http://msdn2.microsoft.com/en-us/library/ms345318.aspx
> --
> Rick Byham (MSFT)
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> "Safeer" <safeerm@.gmail.com> wrote in message
> news:eu1sb1rVHHA.1016@.TK2MSFTNGP04.phx.gbl...
am[vbcol=seagreen]
am[vbcol=seagreen]
>|||It looks like your SQL Server is listening on shared memory (which is a
local pipe) and named pipes, but is not listening on TCP/IP. So if you want
to connect using TCP/IP and port 1433, you will have to enable TCP/IP and
restart SQL Server. You use the Server Network Utility for that.
--
Rick Byham (MSFT)
This posting is provided "AS IS" with no warranties, and confers no rights.
"Safeer" <safeerm@.gmail.com> wrote in message
news:uCxeUt5VHHA.868@.TK2MSFTNGP05.phx.gbl...
> Hi,
> Windows: - Windows NT 5.2 (Build 3790: Service Pack 1)
> SQL:- Microsoft SQL Server 2000 - 8.00.194 (Intel X86) Standard Edition
> My workstation is Windows 2000. I am connecting to the server using MSTSC.
> My sql server log shows the following.
> "SQL server listening on Shared Memory, Named Pipes."
> Actually TCP/IP/1433 is enabled in the server.
> & I am not able to telnet the machine with port 1433 from the server
> itself.
> NB: No one is using this machine now and I need to setup and install
> service
> packs. Its a new box with installed SQL 2K and nobody know the SA
> password.
> Thanks...Safeer
>
> "Rick Byham, (MSFT)" <rickbyh@.REDMOND.CORP.MICROSOFT.COM> wrote in message
> news:08EB12C9-D906-4977-A40E-0F050C837E1E@.microsoft.com...
> you
> rights.
> am
> am
>|||Hi Rick,
I've already did that. Now I did it again and restarted the server. In the
Server Netwrok Utility, its showing tcp/ip. But the log is not showing
TCP/IP.
Thanks...Safeer
"Rick Byham, (MSFT)" <rickbyh@.REDMOND.CORP.MICROSOFT.COM> wrote in message
news:53642094-FE1C-4BFB-85BF-E114587DDB0F@.microsoft.com...
> It looks like your SQL Server is listening on shared memory (which is a
> local pipe) and named pipes, but is not listening on TCP/IP. So if you
want
> to connect using TCP/IP and port 1433, you will have to enable TCP/IP and
> restart SQL Server. You use the Server Network Utility for that.
> --
> Rick Byham (MSFT)
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> "Safeer" <safeerm@.gmail.com> wrote in message
> news:uCxeUt5VHHA.868@.TK2MSFTNGP05.phx.gbl...
Edition[vbcol=seagreen]
MSTSC.[vbcol=seagreen]
message[vbcol=seagreen]
I[vbcol=seagreen]
I[vbcol=seagreen]
>|||Is the SQL Server Browser service started?
____________________________________
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)
----
---
"Safeer" <safeerm@.gmail.com> wrote in message
news:e%23n1O5eWHHA.4668@.TK2MSFTNGP04.phx.gbl...
> Hi Rick,
> I've already did that. Now I did it again and restarted the server. In the
> Server Netwrok Utility, its showing tcp/ip. But the log is not showing
> TCP/IP.
> Thanks...Safeer
>
> "Rick Byham, (MSFT)" <rickbyh@.REDMOND.CORP.MICROSOFT.COM> wrote in message
> news:53642094-FE1C-4BFB-85BF-E114587DDB0F@.microsoft.com...
> want
> rights.
> Edition
> MSTSC.
> message
> I
> I
>|||Its SQL Server 2000.
"William (Bill) Vaughn" <billvaRemoveThis@.nwlink.com> wrote in message
news:uPPE4YgWHHA.4384@.TK2MSFTNGP02.phx.gbl...
> Is the SQL Server Browser service started?
> --
> ____________________________________
> 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)
> ----
---
> "Safeer" <safeerm@.gmail.com> wrote in message
> news:e%23n1O5eWHHA.4668@.TK2MSFTNGP04.phx.gbl...
the[vbcol=seagreen]
message[vbcol=seagreen]
and[vbcol=seagreen]
to[vbcol=seagreen]
>|||Okay, did you follow the checklist shown in:
http://betav.com/blog/billva/2006/0..._connected.html ?
____________________________________
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)
----
---
"Safeer" <safeerm@.gmail.com> wrote in message
news:eR6kqFsWHHA.3332@.TK2MSFTNGP04.phx.gbl...
> Its SQL Server 2000.
>
> "William (Bill) Vaughn" <billvaRemoveThis@.nwlink.com> wrote in message
> news:uPPE4YgWHHA.4384@.TK2MSFTNGP02.phx.gbl...
> rights.
> ---
> the
> message
> and
> to
>

Connection issue - Even Admin in the Server Machine

I am having administrative previlages in the SQL Server Machine, but I am
not able to connect to the SQL Server instance. Can you please help. I am
using windows authendication.
Thanks...Safeer
I tried telnet ipaddress 1433, its not connecting thru the port.
I am connected to the server directly and then checked the port using server
utility and its 1433.
"Safeer" <safeerm@.gmail.com> wrote in message
news:e1jmNjrVHHA.4028@.TK2MSFTNGP04.phx.gbl...
> I am having administrative previlages in the SQL Server Machine, but I am
> not able to connect to the SQL Server instance. Can you please help. I am
> using windows authendication.
> Thanks...Safeer
>
|||I tried telnet ipaddress 1433, its not connecting thru the port.
I am connected to the server directly and then checked the port using server
utility and its 1433.
"Safeer" <safeerm@.gmail.com> wrote in message
news:e1jmNjrVHHA.4028@.TK2MSFTNGP04.phx.gbl...
> I am having administrative previlages in the SQL Server Machine, but I am
> not able to connect to the SQL Server instance. Can you please help. I am
> using windows authendication.
> Thanks...Safeer
>
|||We need more info.
- What version and edition of SQL Server are you using?
- What version of the Windows are you using?
It sounds like you are connecting from a client on another computer. If you
are using SQL Server 2005, use the Surface Area Configuration tool to
confirm that your SQL Server instance is listening for remote connections.
Also, a firewall could be blocking 1433. This is common with Windows XP
service pack 2.
If SQL Server is running on Vista, you have other issues.
For SQL Server 2005, there is a short tutorial that will help. See
http://msdn2.microsoft.com/en-us/library/ms345318.aspx
Rick Byham (MSFT)
This posting is provided "AS IS" with no warranties, and confers no rights.
"Safeer" <safeerm@.gmail.com> wrote in message
news:eu1sb1rVHHA.1016@.TK2MSFTNGP04.phx.gbl...
>I tried telnet ipaddress 1433, its not connecting thru the port.
> I am connected to the server directly and then checked the port using
> server
> utility and its 1433.
>
> "Safeer" <safeerm@.gmail.com> wrote in message
> news:e1jmNjrVHHA.4028@.TK2MSFTNGP04.phx.gbl...
>
|||Hi,
Windows: - Windows NT 5.2 (Build 3790: Service Pack 1)
SQL:- Microsoft SQL Server 2000 - 8.00.194 (Intel X86) Standard Edition
My workstation is Windows 2000. I am connecting to the server using MSTSC.
My sql server log shows the following.
"SQL server listening on Shared Memory, Named Pipes."
Actually TCP/IP/1433 is enabled in the server.
& I am not able to telnet the machine with port 1433 from the server itself.
NB: No one is using this machine now and I need to setup and install service
packs. Its a new box with installed SQL 2K and nobody know the SA password.
Thanks...Safeer
"Rick Byham, (MSFT)" <rickbyh@.REDMOND.CORP.MICROSOFT.COM> wrote in message
news:08EB12C9-D906-4977-A40E-0F050C837E1E@.microsoft.com...
> We need more info.
> - What version and edition of SQL Server are you using?
> - What version of the Windows are you using?
> It sounds like you are connecting from a client on another computer. If
you
> are using SQL Server 2005, use the Surface Area Configuration tool to
> confirm that your SQL Server instance is listening for remote connections.
> Also, a firewall could be blocking 1433. This is common with Windows XP
> service pack 2.
> If SQL Server is running on Vista, you have other issues.
> For SQL Server 2005, there is a short tutorial that will help. See
> http://msdn2.microsoft.com/en-us/library/ms345318.aspx
> --
> Rick Byham (MSFT)
> This posting is provided "AS IS" with no warranties, and confers no
rights.[vbcol=seagreen]
> "Safeer" <safeerm@.gmail.com> wrote in message
> news:eu1sb1rVHHA.1016@.TK2MSFTNGP04.phx.gbl...
am[vbcol=seagreen]
am
>
|||It looks like your SQL Server is listening on shared memory (which is a
local pipe) and named pipes, but is not listening on TCP/IP. So if you want
to connect using TCP/IP and port 1433, you will have to enable TCP/IP and
restart SQL Server. You use the Server Network Utility for that.
Rick Byham (MSFT)
This posting is provided "AS IS" with no warranties, and confers no rights.
"Safeer" <safeerm@.gmail.com> wrote in message
news:uCxeUt5VHHA.868@.TK2MSFTNGP05.phx.gbl...
> Hi,
> Windows: - Windows NT 5.2 (Build 3790: Service Pack 1)
> SQL:- Microsoft SQL Server 2000 - 8.00.194 (Intel X86) Standard Edition
> My workstation is Windows 2000. I am connecting to the server using MSTSC.
> My sql server log shows the following.
> "SQL server listening on Shared Memory, Named Pipes."
> Actually TCP/IP/1433 is enabled in the server.
> & I am not able to telnet the machine with port 1433 from the server
> itself.
> NB: No one is using this machine now and I need to setup and install
> service
> packs. Its a new box with installed SQL 2K and nobody know the SA
> password.
> Thanks...Safeer
>
> "Rick Byham, (MSFT)" <rickbyh@.REDMOND.CORP.MICROSOFT.COM> wrote in message
> news:08EB12C9-D906-4977-A40E-0F050C837E1E@.microsoft.com...
> you
> rights.
> am
> am
>
|||Hi Rick,
I've already did that. Now I did it again and restarted the server. In the
Server Netwrok Utility, its showing tcp/ip. But the log is not showing
TCP/IP.
Thanks...Safeer
"Rick Byham, (MSFT)" <rickbyh@.REDMOND.CORP.MICROSOFT.COM> wrote in message
news:53642094-FE1C-4BFB-85BF-E114587DDB0F@.microsoft.com...
> It looks like your SQL Server is listening on shared memory (which is a
> local pipe) and named pipes, but is not listening on TCP/IP. So if you
want
> to connect using TCP/IP and port 1433, you will have to enable TCP/IP and
> restart SQL Server. You use the Server Network Utility for that.
> --
> Rick Byham (MSFT)
> This posting is provided "AS IS" with no warranties, and confers no
rights.[vbcol=seagreen]
> "Safeer" <safeerm@.gmail.com> wrote in message
> news:uCxeUt5VHHA.868@.TK2MSFTNGP05.phx.gbl...
Edition[vbcol=seagreen]
MSTSC.[vbcol=seagreen]
message[vbcol=seagreen]
I[vbcol=seagreen]
I
>
|||Is the SQL Server Browser service started?
____________________________________
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)
------
"Safeer" <safeerm@.gmail.com> wrote in message
news:e%23n1O5eWHHA.4668@.TK2MSFTNGP04.phx.gbl...
> Hi Rick,
> I've already did that. Now I did it again and restarted the server. In the
> Server Netwrok Utility, its showing tcp/ip. But the log is not showing
> TCP/IP.
> Thanks...Safeer
>
> "Rick Byham, (MSFT)" <rickbyh@.REDMOND.CORP.MICROSOFT.COM> wrote in message
> news:53642094-FE1C-4BFB-85BF-E114587DDB0F@.microsoft.com...
> want
> rights.
> Edition
> MSTSC.
> message
> I
> I
>
|||Its SQL Server 2000.
"William (Bill) Vaughn" <billvaRemoveThis@.nwlink.com> wrote in message
news:uPPE4YgWHHA.4384@.TK2MSFTNGP02.phx.gbl...
> Is the SQL Server Browser service started?
> --
> ____________________________________
> 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)
> ----
---[vbcol=seagreen]
> "Safeer" <safeerm@.gmail.com> wrote in message
> news:e%23n1O5eWHHA.4668@.TK2MSFTNGP04.phx.gbl...
the[vbcol=seagreen]
message[vbcol=seagreen]
and[vbcol=seagreen]
to
>
|||Okay, did you follow the checklist shown in:
http://betav.com/blog/billva/2006/06/getting_and_staying_connected.html ?
____________________________________
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)
------
"Safeer" <safeerm@.gmail.com> wrote in message
news:eR6kqFsWHHA.3332@.TK2MSFTNGP04.phx.gbl...
> Its SQL Server 2000.
>
> "William (Bill) Vaughn" <billvaRemoveThis@.nwlink.com> wrote in message
> news:uPPE4YgWHHA.4384@.TK2MSFTNGP02.phx.gbl...
> rights.
> the
> message
> and
> to
>

Connecting to Sql Server 2005 Express from three projects

Hi

I have set up a solution in Visual web developer 2005 express which is made up of three projects:

Website(this is the solution)
Admin (Sub directory of website)
members (Sub Directory of Website)

All three projects need to share the same database. However for devlopment purposes I only have Sql Server 2005 Express. Is this possible?

Any pointer would be great.

Thanks in advance

1. connectivity to a database can be done from any web page/any project
2. A database can hold many tables
3. Since it can have many tables, you can have any kind of and as much data you want there, even from different projects

The base answer is yes - there's no problem here - I guess we'd need a more exact question to get any further along.

|||

Besides using SQL Surface Area Configuration tool to configure SQL 2005 Express Edition with Advanced Services (SSEA) for allowing remote connections using TCP/IP only, I created an SQL user with password using SQL Management Studio Express in Security-Logins. This user was granted access to a specific database on the Server (a WinXP SP2 machine).Then I tried to connect to SSEA from another machine using OLEDB Provider for SQL Server, SQL Server authentication with above username and password, typed in the Database name, typed Server Name as\\MachineName\SQLExpress, but could not connect. What might have gone wrong? What more settings, if any need to be done on the Server end? I am not sure what roles need to be assigned to the SQL User, so I ticked all.

Mark Nongkhlaw

|||Is communucation at all possible between the two boxes? My point - might be a firewall stopping that traffic?|||

Hi

What I mean is if I have three projects, they will have three app_data folders. Now, so far I have only got Sql Server 2005 express to work when there is a mdb file in the app_data folder and it is attached to the sql server. Now if I have to do this for three separate projects I surely will not be able to share the same database between the three.

So the connection string I am currently using is

<addname="LocalSqlServer"connectionString="Data Source=.\SQLExpress;Integrated Security=True;User Instance=True;AttachDBFilename=|DataDirectory|aspnetdb.mdf"providerName="System.Data.SqlClient"/>

Can you connect to a sql server 2005 express database in the old fashion way with out having to use theAttachDBFilename?

The database will be running on the same machine as the website so I guess it can be considered a local connection (I understand that there are difficulties with remote connections) .

I hope this makes more sense.

Cheers Steve

|||

Finally I understand your problem :)

Have you tried to specify a full path?

AttachDBFileName=c:\the-path-to-othersite-data-directory\aspnetdb.mdf

|||

And yes you can use SQLExpress as a "regular" database - that's what I do (never uses AttachFile) so connecting with for example

Server=SH-W2003CP\SQLEXPRESS;Database=kbmentor;Trusted_Connection=False;uid=sa;pwd=stefan;

is fine.

|||

Thanks,aspcode.net- The culprit WAS the WinXP firewall. I configured exceptions for SQL Server Express and SQL Browser and it now works.

Mark

|||Thanks guys, I too have now managed to get my site(s) to work.