Considerations... Backing up IIS 6 web files and SQL Server 2005 Express database

Anyone know of a good "free" way to back up web files and SQL Server 2005 Express Database?

I was able to use Windows Server 2003 Backup utility to back up the folder where the Databases were stored, as well as the web files, with no errors.

But I have heard a lot of discussion that you can't just simply backup SQL Server data files?

I'm wondering how sound the backup I've created is...

Any suggestions?

Try the link below to dowload the eval version of the full SQL Server 2005 it is good for 180 days so you have to buy the developer edition which is $60 or less later. Install it as a named instance and register the Express so you can use the backup and restore wizard to backup your databases. You don't need any third party tool to backup SQL Server if your databases are less than 1000. Hope this helps.

http://www.microsoft.com/sql/downloads/trial-software.mspx

Consfued on how to handle memoey issue

Okay here is the question for all of brilliant guys. I have a server
loaded with windows 2003 Enterprise Edition with SP2 on it. I've 2
instanaces on sql 2000 sp3a running on them currently memory for the
box is 8 GB. Now the problem is, one of the instance is of ecommerce
database and that database is massive around 800-900 GB. currently,
it's running under memory pressure i mean sql server process is taking
around 1.8 GB but it's not going beyond that I know it's a problem
with 32-bit edition but we can't move our stuff to 64-bit right away.
I would like to know best way to tackle this problem. I mean what i
have to do to give in order to use more memory. Do i need to enable
AWE on both the instance and use /PAE switch or go beyond that and
use /3GB switch in boot.ini. Let me know.
Thanks,Hi
Which edition of SQL 2000 is this?
You can configure the maximum memory to use with sp_configure 'max server
memory' You can set values for each instance so they add up to 5 GB.
Have you enabled AWE on each instance.
John
"kulkarni.ninad@.gmail.com" wrote:
> Okay here is the question for all of brilliant guys. I have a server
> loaded with windows 2003 Enterprise Edition with SP2 on it. I've 2
> instanaces on sql 2000 sp3a running on them currently memory for the
> box is 8 GB. Now the problem is, one of the instance is of ecommerce
> database and that database is massive around 800-900 GB. currently,
> it's running under memory pressure i mean sql server process is taking
> around 1.8 GB but it's not going beyond that I know it's a problem
> with 32-bit edition but we can't move our stuff to 64-bit right away.
> I would like to know best way to tackle this problem. I mean what i
> have to do to give in order to use more memory. Do i need to enable
> AWE on both the instance and use /PAE switch or go beyond that and
> use /3GB switch in boot.ini. Let me know.
> Thanks,
>|||On Sep 27, 12:54 pm, John Bell <jbellnewspo...@.hotmail.com> wrote:
> Hi
> Which edition of SQL 2000 is this?
> You can configure the maximum memory to use with sp_configure 'max server
> memory' You can set values for each instance so they add up to 5 GB.
> Have you enabled AWE on each instance.
> John
>
> "kulkarni.ni...@.gmail.com" wrote:
> > Okay here is the question for all of brilliant guys. I have a server
> > loaded with windows 2003 Enterprise Edition with SP2 on it. I've 2
> > instanaces on sql 2000 sp3a running on them currently memory for the
> > box is 8 GB. Now the problem is, one of the instance is of ecommerce
> > database and that database is massive around 800-900 GB. currently,
> > it's running under memory pressure i mean sql server process is taking
> > around 1.8 GB but it's not going beyond that I know it's a problem
> > with 32-bit edition but we can't move our stuff to 64-bit right away.
> > I would like to know best way to tackle this problem. I mean what i
> > have to do to give in order to use more memory. Do i need to enable
> > AWE on both the instance and use /PAE switch or go beyond that and
> > use /3GB switch in boot.ini. Let me know.
> > Thanks,- Hide quoted text -
> - Show quoted text -
No we haven't enabled AWE actually and that's where I'm confused at
because in past, I have enabled AWE for single instance but haven't
done it for multiple instances.
Will it work if I enable AWE on both the instance of sql server? and
BTW, sql edition is Enterprise Edition.
Thanks,|||Hi
You should be able to enable AWE for both instances, but even if you enable
it for only one instance you should set the maximum memory for that instance
to avoid it grabbing all the memory.
John
"kulkarni.ninad@.gmail.com" wrote:
> On Sep 27, 12:54 pm, John Bell <jbellnewspo...@.hotmail.com> wrote:
> > Hi
> >
> > Which edition of SQL 2000 is this?
> >
> > You can configure the maximum memory to use with sp_configure 'max server
> > memory' You can set values for each instance so they add up to 5 GB.
> > Have you enabled AWE on each instance.
> >
> > John
> >
> >
> >
> > "kulkarni.ni...@.gmail.com" wrote:
> > > Okay here is the question for all of brilliant guys. I have a server
> > > loaded with windows 2003 Enterprise Edition with SP2 on it. I've 2
> > > instanaces on sql 2000 sp3a running on them currently memory for the
> > > box is 8 GB. Now the problem is, one of the instance is of ecommerce
> > > database and that database is massive around 800-900 GB. currently,
> > > it's running under memory pressure i mean sql server process is taking
> > > around 1.8 GB but it's not going beyond that I know it's a problem
> > > with 32-bit edition but we can't move our stuff to 64-bit right away.
> > > I would like to know best way to tackle this problem. I mean what i
> > > have to do to give in order to use more memory. Do i need to enable
> > > AWE on both the instance and use /PAE switch or go beyond that and
> > > use /3GB switch in boot.ini. Let me know.
> >
> > > Thanks,- Hide quoted text -
> >
> > - Show quoted text -
> No we haven't enabled AWE actually and that's where I'm confused at
> because in past, I have enabled AWE for single instance but haven't
> done it for multiple instances.
> Will it work if I enable AWE on both the instance of sql server? and
> BTW, sql edition is Enterprise Edition.
> Thanks,
>|||You do not need to add /3GB switch to the boot.ini file; however, you need
to add /PAE to be able to use 6GB of RAM over 8GB. Only enabling AWE won't
let you use 6GB of RAM. (You can use 6GB because Kernel Components and
Operating System use 2GB of RAM) And this process (enabling AWE and PAE)
needs a reboot of your server.
--
Ekrem Önsoy
<kulkarni.ninad@.gmail.com> wrote in message
news:1190914211.251116.224130@.57g2000hsv.googlegroups.com...
> On Sep 27, 12:54 pm, John Bell <jbellnewspo...@.hotmail.com> wrote:
>> Hi
>> Which edition of SQL 2000 is this?
>> You can configure the maximum memory to use with sp_configure 'max server
>> memory' You can set values for each instance so they add up to 5 GB.
>> Have you enabled AWE on each instance.
>> John
>>
>> "kulkarni.ni...@.gmail.com" wrote:
>> > Okay here is the question for all of brilliant guys. I have a server
>> > loaded with windows 2003 Enterprise Edition with SP2 on it. I've 2
>> > instanaces on sql 2000 sp3a running on them currently memory for the
>> > box is 8 GB. Now the problem is, one of the instance is of ecommerce
>> > database and that database is massive around 800-900 GB. currently,
>> > it's running under memory pressure i mean sql server process is taking
>> > around 1.8 GB but it's not going beyond that I know it's a problem
>> > with 32-bit edition but we can't move our stuff to 64-bit right away.
>> > I would like to know best way to tackle this problem. I mean what i
>> > have to do to give in order to use more memory. Do i need to enable
>> > AWE on both the instance and use /PAE switch or go beyond that and
>> > use /3GB switch in boot.ini. Let me know.
>> > Thanks,- Hide quoted text -
>> - Show quoted text -
> No we haven't enabled AWE actually and that's where I'm confused at
> because in past, I have enabled AWE for single instance but haven't
> done it for multiple instances.
> Will it work if I enable AWE on both the instance of sql server? and
> BTW, sql edition is Enterprise Edition.
> Thanks,
>|||Hi
See http://www.sql-server-performance.com/tips/awe_memory_p1.aspx
John
"Ekrem Ã?nsoy" wrote:
> You do not need to add /3GB switch to the boot.ini file; however, you need
> to add /PAE to be able to use 6GB of RAM over 8GB. Only enabling AWE won't
> let you use 6GB of RAM. (You can use 6GB because Kernel Components and
> Operating System use 2GB of RAM) And this process (enabling AWE and PAE)
> needs a reboot of your server.
> --
> Ekrem nsoy
>
>
> <kulkarni.ninad@.gmail.com> wrote in message
> news:1190914211.251116.224130@.57g2000hsv.googlegroups.com...
> > On Sep 27, 12:54 pm, John Bell <jbellnewspo...@.hotmail.com> wrote:
> >> Hi
> >>
> >> Which edition of SQL 2000 is this?
> >>
> >> You can configure the maximum memory to use with sp_configure 'max server
> >> memory' You can set values for each instance so they add up to 5 GB.
> >> Have you enabled AWE on each instance.
> >>
> >> John
> >>
> >>
> >>
> >> "kulkarni.ni...@.gmail.com" wrote:
> >> > Okay here is the question for all of brilliant guys. I have a server
> >> > loaded with windows 2003 Enterprise Edition with SP2 on it. I've 2
> >> > instanaces on sql 2000 sp3a running on them currently memory for the
> >> > box is 8 GB. Now the problem is, one of the instance is of ecommerce
> >> > database and that database is massive around 800-900 GB. currently,
> >> > it's running under memory pressure i mean sql server process is taking
> >> > around 1.8 GB but it's not going beyond that I know it's a problem
> >> > with 32-bit edition but we can't move our stuff to 64-bit right away.
> >> > I would like to know best way to tackle this problem. I mean what i
> >> > have to do to give in order to use more memory. Do i need to enable
> >> > AWE on both the instance and use /PAE switch or go beyond that and
> >> > use /3GB switch in boot.ini. Let me know.
> >>
> >> > Thanks,- Hide quoted text -
> >>
> >> - Show quoted text -
> >
> > No we haven't enabled AWE actually and that's where I'm confused at
> > because in past, I have enabled AWE for single instance but haven't
> > done it for multiple instances.
> > Will it work if I enable AWE on both the instance of sql server? and
> > BTW, sql edition is Enterprise Edition.
> >
> > Thanks,
> >
>|||Well, I'm not really sure of using /3GB all the time at least if it's really
unnecessary. I would not use it unless I really need that 1GB of RAM.
--
Ekrem Ã?nsoy
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:D2EE787C-CC99-4F84-8872-09B30278CD6A@.microsoft.com...
> Hi
> See http://www.sql-server-performance.com/tips/awe_memory_p1.aspx
> John
> "Ekrem Ã?nsoy" wrote:
>> You do not need to add /3GB switch to the boot.ini file; however, you
>> need
>> to add /PAE to be able to use 6GB of RAM over 8GB. Only enabling AWE
>> won't
>> let you use 6GB of RAM. (You can use 6GB because Kernel Components and
>> Operating System use 2GB of RAM) And this process (enabling AWE and PAE)
>> needs a reboot of your server.
>> --
>> Ekrem nsoy
>>
>>
>> <kulkarni.ninad@.gmail.com> wrote in message
>> news:1190914211.251116.224130@.57g2000hsv.googlegroups.com...
>> > On Sep 27, 12:54 pm, John Bell <jbellnewspo...@.hotmail.com> wrote:
>> >> Hi
>> >>
>> >> Which edition of SQL 2000 is this?
>> >>
>> >> You can configure the maximum memory to use with sp_configure 'max
>> >> server
>> >> memory' You can set values for each instance so they add up to 5 GB.
>> >> Have you enabled AWE on each instance.
>> >>
>> >> John
>> >>
>> >>
>> >>
>> >> "kulkarni.ni...@.gmail.com" wrote:
>> >> > Okay here is the question for all of brilliant guys. I have a server
>> >> > loaded with windows 2003 Enterprise Edition with SP2 on it. I've 2
>> >> > instanaces on sql 2000 sp3a running on them currently memory for the
>> >> > box is 8 GB. Now the problem is, one of the instance is of ecommerce
>> >> > database and that database is massive around 800-900 GB. currently,
>> >> > it's running under memory pressure i mean sql server process is
>> >> > taking
>> >> > around 1.8 GB but it's not going beyond that I know it's a problem
>> >> > with 32-bit edition but we can't move our stuff to 64-bit right
>> >> > away.
>> >> > I would like to know best way to tackle this problem. I mean what i
>> >> > have to do to give in order to use more memory. Do i need to enable
>> >> > AWE on both the instance and use /PAE switch or go beyond that and
>> >> > use /3GB switch in boot.ini. Let me know.
>> >>
>> >> > Thanks,- Hide quoted text -
>> >>
>> >> - Show quoted text -
>> >
>> > No we haven't enabled AWE actually and that's where I'm confused at
>> > because in past, I have enabled AWE for single instance but haven't
>> > done it for multiple instances.
>> > Will it work if I enable AWE on both the instance of sql server? and
>> > BTW, sql edition is Enterprise Edition.
>> >
>> > Thanks,
>> >|||Hi
There should not be an issue using it as there is only a limited amount of
memory in the server. If the OP is seeing memory presure once AWE has been
enabled, then it is certainly something he should be doing.
John
"Ekrem Ã?nsoy" wrote:
> Well, I'm not really sure of using /3GB all the time at least if it's really
> unnecessary. I would not use it unless I really need that 1GB of RAM.
> --
> Ekrem Ã?nsoy
>
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:D2EE787C-CC99-4F84-8872-09B30278CD6A@.microsoft.com...
> > Hi
> >
> > See http://www.sql-server-performance.com/tips/awe_memory_p1.aspx
> >
> > John
> >
> > "Ekrem Ã?nsoy" wrote:
> >
> >> You do not need to add /3GB switch to the boot.ini file; however, you
> >> need
> >> to add /PAE to be able to use 6GB of RAM over 8GB. Only enabling AWE
> >> won't
> >> let you use 6GB of RAM. (You can use 6GB because Kernel Components and
> >> Operating System use 2GB of RAM) And this process (enabling AWE and PAE)
> >> needs a reboot of your server.
> >>
> >> --
> >> Ekrem nsoy
> >>
> >>
> >>
> >>
> >> <kulkarni.ninad@.gmail.com> wrote in message
> >> news:1190914211.251116.224130@.57g2000hsv.googlegroups.com...
> >> > On Sep 27, 12:54 pm, John Bell <jbellnewspo...@.hotmail.com> wrote:
> >> >> Hi
> >> >>
> >> >> Which edition of SQL 2000 is this?
> >> >>
> >> >> You can configure the maximum memory to use with sp_configure 'max
> >> >> server
> >> >> memory' You can set values for each instance so they add up to 5 GB.
> >> >> Have you enabled AWE on each instance.
> >> >>
> >> >> John
> >> >>
> >> >>
> >> >>
> >> >> "kulkarni.ni...@.gmail.com" wrote:
> >> >> > Okay here is the question for all of brilliant guys. I have a server
> >> >> > loaded with windows 2003 Enterprise Edition with SP2 on it. I've 2
> >> >> > instanaces on sql 2000 sp3a running on them currently memory for the
> >> >> > box is 8 GB. Now the problem is, one of the instance is of ecommerce
> >> >> > database and that database is massive around 800-900 GB. currently,
> >> >> > it's running under memory pressure i mean sql server process is
> >> >> > taking
> >> >> > around 1.8 GB but it's not going beyond that I know it's a problem
> >> >> > with 32-bit edition but we can't move our stuff to 64-bit right
> >> >> > away.
> >> >> > I would like to know best way to tackle this problem. I mean what i
> >> >> > have to do to give in order to use more memory. Do i need to enable
> >> >> > AWE on both the instance and use /PAE switch or go beyond that and
> >> >> > use /3GB switch in boot.ini. Let me know.
> >> >>
> >> >> > Thanks,- Hide quoted text -
> >> >>
> >> >> - Show quoted text -
> >> >
> >> > No we haven't enabled AWE actually and that's where I'm confused at
> >> > because in past, I have enabled AWE for single instance but haven't
> >> > done it for multiple instances.
> >> > Will it work if I enable AWE on both the instance of sql server? and
> >> > BTW, sql edition is Enterprise Edition.
> >> >
> >> > Thanks,
> >> >
> >>
>

Connectivity?

Dev Tool: VB6
Server: SQL Server 2000.
Environment: Windows 2000/Windows XP/Windows 2000 Server
I have changed a user connectivity from WINDOWS NT trusted connection to
SQL Server Authentication.
I have granted the same permissions to the new user.
The problem is as follows:
The new user cannot execute stored procedures which contains INSERT staments
.
Having the same connection and user id. When I execute the stored procedure
in the Query Analyzer console I have no problem, but when I execute it in a
Visual Basic 6.0 Application, using ADO, I get the following message:
"Operation is not Allowed when the Object is closed."
Note: I created the table, so I'm the owner, I should have no problems(??)
Any ideas?
RickRick,
Can you send your vb code where you open the ADO connection, execute the
stored proc, and then close the connection?
Thanks,
Yosh
"Rick" <Rick@.discussions.microsoft.com> wrote in message
news:131F18F8-146E-410F-8E84-2610E2871512@.microsoft.com...
> Dev Tool: VB6
> Server: SQL Server 2000.
> Environment: Windows 2000/Windows XP/Windows 2000 Server
> I have changed a user connectivity from WINDOWS NT trusted connection to
> SQL Server Authentication.
> I have granted the same permissions to the new user.
> The problem is as follows:
> The new user cannot execute stored procedures which contains INSERT
> staments.
> Having the same connection and user id. When I execute the stored
> procedure
> in the Query Analyzer console I have no problem, but when I execute it in
> a
> Visual Basic 6.0 Application, using ADO, I get the following message:
> "Operation is not Allowed when the Object is closed."
> Note: I created the table, so I'm the owner, I should have no problems(?)
> Any ideas?
>
> --
> Rick|||I get an error with the debugger.
Rick
"Yosh" wrote:

> Rick,
> Can you send your vb code where you open the ADO connection, execute the
> stored proc, and then close the connection?
> Thanks,
> Yosh
> "Rick" <Rick@.discussions.microsoft.com> wrote in message
> news:131F18F8-146E-410F-8E84-2610E2871512@.microsoft.com...
>
>

Connectivity to FoxPro (dbf) from SQL 2005 on x64 Windows 2003

I have installed SQL Sever 2005 on an x64 bit machine running Windows 2003.
When I go to the ODBC Data Source Administrator, and click on the Drivers
tab, it only shows:
SQL Native Client
SQL Server
I would like it to show the "other" drivers that I see in other
installations - to connect to .mdb, .dbf, etc.
I tried installing MDAC 2.8, but it didn't affect the drivers shown in the
list.
Any suggestions? My goal is to write a SSIS package that connects to a
FoxPro (.dbf) file.
Thanks
PaulHi Paul,
There are two methods for connecting to Fox tables - OLE DB and ODBC. The
OLE DB data provider for VFP is only 32-bit compatible. There are no plans
to develop a 64-bit OLE DB data provider for VFP. I assume that the ODBC
drivers for VFP are also only 32-bit compatible (I'm not sure) but I am sure
that there won't be any new ODBC drivers for VFP.
Sorry to be the bearer of bad news.
Cindy Winegarden MCSD, Microsoft Most Valuable Professional
cindy@.cindywinegarden.com
"Paul in Denver" <Paul in Denver@.discussions.microsoft.com> wrote in message
news:F0E93714-1075-446D-AEF9-48D70D0834E1@.microsoft.com...
>I have installed SQL Sever 2005 on an x64 bit machine ...

> Any suggestions? My goal is to write a SSIS package that connects to a
> FoxPro (.dbf) file.

Connectivity Problem for Expert

Hi All,
I have an intriguing problem and I wanted to see if somebody could help me.
ENVIRONMENT:
Server Side: 2 identical Windows servers 2000 with SQL Server 2000
Enterprise Edition SP3a
Client Side: workstation with Windows 2000 PRO
Protocols enabled in the server and client: TCP/IP and Named Pipes.
1) I create a new user in the domain, DM001\testesql
2) I create a new login in the SQL Server (one in each SQL Server). For
this, I used script below:
EXEC sp_grantlogin 'DM001\testesql'
GO
EXEC sp_defaultdb 'DM001\testesql', 'Pubs'
GO
USE Pubs
GO
EXEC sp_grantdbaccess 'DM001\testesql', 'testesql'
GO
EXEC sp_addrolemember 'db_owner', 'testesql'
GO
sp_helpuser
THE PROBLEM:
After this, I connected myself in one workstation with the new user of
domain (DM001\testesql)and try a connection via osql utility using the
command line below. Well, in 1 server the connection was made successfully
and got the waited result, but in the other server I received the error:
Login failed for user '(null)'. Reason: Not associated with a trusted SQL
Server connection.
Comand line for SQLServer1 ==> successfully
C:\osql - SSQLServer1 - and - Q"select TOP 1 au_lname, au_fname from
pubs..authors".
--Result:
au_lname au_fname
--- --
Bennet Abraham
(1 row(s) affected)
Comand line for SQLServer2 ==> failed
C:\osql - SSQLServer2 - and - Q"select TOP 1 au_lname, au_fname from
pubs..authors".
Login failed for user '(null)'. Reason: Not associated with a trusted SQL
Server connection.
Please, somebody has idea of that can be happening?
Thx
Nilton Pinheiro
Message posted via http://www.droptable.com
Sorry... SQL Server is set up to use Mixed Mode Authentication in both the
servers.
Thx
Nilton
Message posted via http://www.droptable.com
|||Hi... I solve this problem change permission in Local Policy
thx
Message posted via http://www.droptable.com
|||If you try to connect to a SQL Server using windows
authentication and the error is:
Login failed for user '(null)'.
this generally indicates that the user can't be validated
through the domain controller or the local security database
so null is passed to SQL Server. So it's generally
indicative of an issue with the account, access to the
domain controller or something along those lines.
Check the event logs on the client PC and look for any
network, domain related issues. Check the event logs on the
DC as well.
-Sue
On Wed, 04 May 2005 20:33:12 GMT, "Nilton Pinheiro via
droptable.com" <forum@.nospam.droptable.com> wrote:

>Hi All,
>I have an intriguing problem and I wanted to see if somebody could help me.
>ENVIRONMENT:
>Server Side: 2 identical Windows servers 2000 with SQL Server 2000
>Enterprise Edition SP3a
>Client Side: workstation with Windows 2000 PRO
>Protocols enabled in the server and client: TCP/IP and Named Pipes.
>1) I create a new user in the domain, DM001\testesql
>2) I create a new login in the SQL Server (one in each SQL Server). For
>this, I used script below:
>EXEC sp_grantlogin 'DM001\testesql'
>GO
>EXEC sp_defaultdb 'DM001\testesql', 'Pubs'
>GO
>USE Pubs
>GO
>EXEC sp_grantdbaccess 'DM001\testesql', 'testesql'
>GO
>EXEC sp_addrolemember 'db_owner', 'testesql'
>GO
>sp_helpuser
>
>THE PROBLEM:
>After this, I connected myself in one workstation with the new user of
>domain (DM001\testesql)and try a connection via osql utility using the
>command line below. Well, in 1 server the connection was made successfully
>and got the waited result, but in the other server I received the error:
>Login failed for user '(null)'. Reason: Not associated with a trusted SQL
>Server connection.
>Comand line for SQLServer1 ==> successfully
>C:\osql - SSQLServer1 - and - Q"select TOP 1 au_lname, au_fname from
>pubs..authors".
>--Result:
>au_lname au_fname
>--- --
>Bennet Abraham
>(1 row(s) affected)
>Comand line for SQLServer2 ==> failed
>C:\osql - SSQLServer2 - and - Q"select TOP 1 au_lname, au_fname from
>pubs..authors".
>Login failed for user '(null)'. Reason: Not associated with a trusted SQL
>Server connection.
>Please, somebody has idea of that can be happening?
>Thx
>Nilton Pinheiro
|||Hi Nilton,
I am having similar issue, can you share what steps you followed to resolve
this issue.
--Manoj
"Nilton Pinheiro via droptable.com" wrote:

> Hi... I solve this problem change permission in Local Policy
> thx
> --
> Message posted via http://www.droptable.com
>

Connectivity Problem for Expert

Hi All,
I have an intriguing problem and I wanted to see if somebody could help me.
ENVIRONMENT:
Server Side: 2 identical Windows servers 2000 with SQL Server 2000
Enterprise Edition SP3a
Client Side: workstation with Windows 2000 PRO
Protocols enabled in the server and client: TCP/IP and Named Pipes.
1) I create a new user in the domain, DM001\testesql
2) I create a new login in the SQL Server (one in each SQL Server). For
this, I used script below:
EXEC sp_grantlogin 'DM001\testesql'
GO
EXEC sp_defaultdb 'DM001\testesql', 'Pubs'
GO
USE Pubs
GO
EXEC sp_grantdbaccess 'DM001\testesql', 'testesql'
GO
EXEC sp_addrolemember 'db_owner', 'testesql'
GO
sp_helpuser
THE PROBLEM:
After this, I connected myself in one workstation with the new user of
domain (DM001\testesql)and try a connection via osql utility using the
command line below. Well, in 1 server the connection was made successfully
and got the waited result, but in the other server I received the error:
Login failed for user '(null)'. Reason: Not associated with a trusted SQL
Server connection.
Comand line for SQLServer1 ==> successfully
C:\osql - SSQLServer1 - and - Q"select TOP 1 au_lname, au_fname from
pubs..authors".
--Result:
au_lname au_fname
--- --
Bennet Abraham
(1 row(s) affected)
Comand line for SQLServer2 ==> failed
C:\osql - SSQLServer2 - and - Q"select TOP 1 au_lname, au_fname from
pubs..authors".
Login failed for user '(null)'. Reason: Not associated with a trusted SQL
Server connection.
Please, somebody has idea of that can be happening?
Thx
Nilton Pinheiro
Message posted via http://www.droptable.comSorry... SQL Server is set up to use Mixed Mode Authentication in both the
servers.
Thx
Nilton
Message posted via http://www.droptable.com|||Hi... I solve this problem change permission in Local Policy
thx
Message posted via http://www.droptable.com|||If you try to connect to a SQL Server using windows
authentication and the error is:
Login failed for user '(null)'.
this generally indicates that the user can't be validated
through the domain controller or the local security database
so null is passed to SQL Server. So it's generally
indicative of an issue with the account, access to the
domain controller or something along those lines.
Check the event logs on the client PC and look for any
network, domain related issues. Check the event logs on the
DC as well.
-Sue
On Wed, 04 May 2005 20:33:12 GMT, "Nilton Pinheiro via
droptable.com" <forum@.nospam.droptable.com> wrote:

>Hi All,
>I have an intriguing problem and I wanted to see if somebody could help me.
>ENVIRONMENT:
>Server Side: 2 identical Windows servers 2000 with SQL Server 2000
>Enterprise Edition SP3a
>Client Side: workstation with Windows 2000 PRO
>Protocols enabled in the server and client: TCP/IP and Named Pipes.
>1) I create a new user in the domain, DM001\testesql
>2) I create a new login in the SQL Server (one in each SQL Server). For
>this, I used script below:
>EXEC sp_grantlogin 'DM001\testesql'
>GO
>EXEC sp_defaultdb 'DM001\testesql', 'Pubs'
>GO
>USE Pubs
>GO
>EXEC sp_grantdbaccess 'DM001\testesql', 'testesql'
>GO
>EXEC sp_addrolemember 'db_owner', 'testesql'
>GO
>sp_helpuser
>
>THE PROBLEM:
>After this, I connected myself in one workstation with the new user of
>domain (DM001\testesql)and try a connection via osql utility using the
>command line below. Well, in 1 server the connection was made successfully
>and got the waited result, but in the other server I received the error:
>Login failed for user '(null)'. Reason: Not associated with a trusted SQL
>Server connection.
>Comand line for SQLServer1 ==> successfully
>C:\osql - SSQLServer1 - and - Q"select TOP 1 au_lname, au_fname from
>pubs..authors".
>--Result:
>au_lname au_fname
>--- --
>Bennet Abraham
>(1 row(s) affected)
>Comand line for SQLServer2 ==> failed
>C:\osql - SSQLServer2 - and - Q"select TOP 1 au_lname, au_fname from
>pubs..authors".
>Login failed for user '(null)'. Reason: Not associated with a trusted SQL
>Server connection.
>Please, somebody has idea of that can be happening?
>Thx
>Nilton Pinheiro|||Hi Nilton,
I am having similar issue, can you share what steps you followed to resolve
this issue.
--Manoj
"Nilton Pinheiro via droptable.com" wrote:

> Hi... I solve this problem change permission in Local Policy
> thx
> --
> Message posted via http://www.droptable.com
>

connectivity problem

good morning!
All was fine until a few hours ago. the sequel was set to windows
authentication only. then i realized i needed a sequel user account which i
then created. then i tried to switch back to mixed mode to make the account
work. things hung for a while and when restarted the sequel no longer accepts
either windows accounts or the new sequel account. so i have basically locked
myself out. do i need to reinstall? is there an easy way to reset the
authentication mode without being able to get into the engine itself? thanks.
-BahmanYou should be able to switch between the authentication modes. Did you get
any error message when tryin to log in?
Linchi
"Bahman" wrote:
> good morning!
> All was fine until a few hours ago. the sequel was set to windows
> authentication only. then i realized i needed a sequel user account which i
> then created. then i tried to switch back to mixed mode to make the account
> work. things hung for a while and when restarted the sequel no longer accepts
> either windows accounts or the new sequel account. so i have basically locked
> myself out. do i need to reinstall? is there an easy way to reset the
> authentication mode without being able to get into the engine itself? thanks.
> -Bahman
>|||yes i did.
it said that it could not connect to sequel. it said one reason could be
that by default sequel 2005 does not allow remote connections.
so i went into surface area and added that functionlity. but surface area
does not allow me to check on authentication mode and switch it. the only
place i could do that was on the engine itself, which i cannot get to at the
moment.
the other issue is that the agent does not start at all. if i try to start
the service is says the service did not start and did not return an error
code. so, i don't know what it is i need to fix.
-Bahman
"Linchi Shea" wrote:
> You should be able to switch between the authentication modes. Did you get
> any error message when tryin to log in?
> Linchi
> "Bahman" wrote:
> > good morning!
> >
> > All was fine until a few hours ago. the sequel was set to windows
> > authentication only. then i realized i needed a sequel user account which i
> > then created. then i tried to switch back to mixed mode to make the account
> > work. things hung for a while and when restarted the sequel no longer accepts
> > either windows accounts or the new sequel account. so i have basically locked
> > myself out. do i need to reinstall? is there an easy way to reset the
> > authentication mode without being able to get into the engine itself? thanks.
> >
> > -Bahman
> >
> >|||Bahman,
Are the buttons greyed out for switching modes. I need to switch from
windows to mixed in 2005 but both buttons are greyed out. Any ideas on how I
can switch to mixed?
Thanks
John
"Bahman" wrote:
> yes i did.
> it said that it could not connect to sequel. it said one reason could be
> that by default sequel 2005 does not allow remote connections.
> so i went into surface area and added that functionlity. but surface area
> does not allow me to check on authentication mode and switch it. the only
> place i could do that was on the engine itself, which i cannot get to at the
> moment.
> the other issue is that the agent does not start at all. if i try to start
> the service is says the service did not start and did not return an error
> code. so, i don't know what it is i need to fix.
> -Bahman
> "Linchi Shea" wrote:
> > You should be able to switch between the authentication modes. Did you get
> > any error message when tryin to log in?
> >
> > Linchi
> >
> > "Bahman" wrote:
> >
> > > good morning!
> > >
> > > All was fine until a few hours ago. the sequel was set to windows
> > > authentication only. then i realized i needed a sequel user account which i
> > > then created. then i tried to switch back to mixed mode to make the account
> > > work. things hung for a while and when restarted the sequel no longer accepts
> > > either windows accounts or the new sequel account. so i have basically locked
> > > myself out. do i need to reinstall? is there an easy way to reset the
> > > authentication mode without being able to get into the engine itself? thanks.
> > >
> > > -Bahman
> > >
> > >|||John,
sorry for delay.
I rebuilt the system. It was gone too far away.
-Bahman
"John B." wrote:
> Bahman,
> Are the buttons greyed out for switching modes. I need to switch from
> windows to mixed in 2005 but both buttons are greyed out. Any ideas on how I
> can switch to mixed?
> Thanks
> John
> "Bahman" wrote:
> > yes i did.
> >
> > it said that it could not connect to sequel. it said one reason could be
> > that by default sequel 2005 does not allow remote connections.
> >
> > so i went into surface area and added that functionlity. but surface area
> > does not allow me to check on authentication mode and switch it. the only
> > place i could do that was on the engine itself, which i cannot get to at the
> > moment.
> >
> > the other issue is that the agent does not start at all. if i try to start
> > the service is says the service did not start and did not return an error
> > code. so, i don't know what it is i need to fix.
> >
> > -Bahman
> >
> > "Linchi Shea" wrote:
> >
> > > You should be able to switch between the authentication modes. Did you get
> > > any error message when tryin to log in?
> > >
> > > Linchi
> > >
> > > "Bahman" wrote:
> > >
> > > > good morning!
> > > >
> > > > All was fine until a few hours ago. the sequel was set to windows
> > > > authentication only. then i realized i needed a sequel user account which i
> > > > then created. then i tried to switch back to mixed mode to make the account
> > > > work. things hung for a while and when restarted the sequel no longer accepts
> > > > either windows accounts or the new sequel account. so i have basically locked
> > > > myself out. do i need to reinstall? is there an easy way to reset the
> > > > authentication mode without being able to get into the engine itself? thanks.
> > > >
> > > > -Bahman
> > > >
> > > >

Connectivity Issue between XP, SQL Server 2000 & SPSS

Hi,
I am trying to build an application with Windows XP, SPSS & SQL
Server 2000. I am using SQL Server built in stored procedure 'xp_cmdshell'
with sa login to run batch file which starts SPSS. However 'xp_cmdshell'
keeps on running & nothing happens.
I tried the same thing on Windows 2003 server. It ran after I installed
.Net frame work 2.0 I did the same thing on Windows XP but it doesn't help.
I wonder what I have to do make it run on XP
Any help would be greatly appreciated.
Regards
IT Dev.Hi
"IT Developer" wrote:
> Hi,
> I am trying to build an application with Windows XP, SPSS & SQL
> Server 2000. I am using SQL Server built in stored procedure 'xp_cmdshell'
> with sa login to run batch file which starts SPSS. However 'xp_cmdshell'
> keeps on running & nothing happens.
> I tried the same thing on Windows 2003 server. It ran after I installed
> .Net frame work 2.0 I did the same thing on Windows XP but it doesn't help.
> I wonder what I have to do make it run on XP
> Any help would be greatly appreciated.
>
> Regards
>
> IT Dev.
>
I am not familiar with SPSS, but if you are trying to start a windows
application that requres user input from xp_cmdshell then you should try a
different method. I assume SPSS is on the SQL Server itself?
John

Connectivity Issue between XP, SQL Server 2000 & SPSS

Hi,
I am trying to build an application with Windows XP, SPSS & SQL
Server 2000. I am using SQL Server built in stored procedure 'xp_cmdshell'
with sa login to run batch file which starts SPSS. However 'xp_cmdshell'
keeps on running & nothing happens.
I tried the same thing on Windows 2003 server. It ran after I installed
..Net frame work 2.0 I did the same thing on Windows XP but it doesn't help.
I wonder what I have to do make it run on XP
Any help would be greatly appreciated.
Regards
IT Dev.
Hi
"IT Developer" wrote:

> Hi,
> I am trying to build an application with Windows XP, SPSS & SQL
> Server 2000. I am using SQL Server built in stored procedure 'xp_cmdshell'
> with sa login to run batch file which starts SPSS. However 'xp_cmdshell'
> keeps on running & nothing happens.
> I tried the same thing on Windows 2003 server. It ran after I installed
> .Net frame work 2.0 I did the same thing on Windows XP but it doesn't help.
> I wonder what I have to do make it run on XP
> Any help would be greatly appreciated.
>
> Regards
>
> IT Dev.
>
I am not familiar with SPSS, but if you are trying to start a windows
application that requres user input from xp_cmdshell then you should try a
different method. I assume SPSS is on the SQL Server itself?
John

Connectivity issue - SQLServer not listening on port 1433/ms-sql-s

Hi. I'm a SQL Server novice, so apologies if any of this sounds simple.

I am running Windows XP SP2, and have just installed SQLServer 2000. I
need another application to connect to SQLServer, and am specifying it
to do so via localhost:1433, but keep getting an error whenever I try
doing so saying it cannot connect to the database. A colleague of mine
has the exact same set up on his machine, and he can connect to SQL
Server fine. Running 'netstat -a' at the command line on his machine
reveals that the system is listening to port 1433/ms-sql-s. Running
netstat on my machine shows that the system is not listening to
1433/ms-sql-ms. I have checked in Network Config in SQLServer
Enterprise Manager, and TCP/IP is set to be using 1433.

To confirm this, my application can connect over the network to my
colleague's SQL Server. but he cannot connect over the network to mine.

So I'm pretty sure the issue is related to this 1433/ms-sql-s problem.
Does anyone know how to resolve this? Many thanks.I just installed SQL Server Service Pack 3, and the problem is now
resolved. Perhaps it was related to the Slammer worm.

Connectivity

Hi
Im very new to SQL server so forgive me if this is a basic
question. Im running SQL server on a windows 2000 machine
and when I run Analysis Services it picks up the server
(my local computer name) perfectly. However, when I try
and register the server in Enterprise Manager it cant find
it, doesnt make sense to me. Could it be because I am
logged into our network and not logged on the computer as
an administrator and therefore dont have admin rights on
the PC.
Thanks
John
What error do you get when yo try to register the SQL Server?
Rand
This posting is provided "as is" with no warranties and confers no rights.
|||Try using the ip address of your computer instead of the computer name and
see if it connects...How were you trying to connect, using sql server
authentication or Windows authentication? Try to connect using sql server
authentication. If this is a fresh install, sa user will probably have a
blank password, use the sa account to try to connect and see if it does.
HTH.
=)
Ricky Artigas
"John" <woody77_80@.hotmail.com> wrote in message
news:1037901c43f40$9e5e3f10$a601280a@.phx.gbl...
> Hi
> Im very new to SQL server so forgive me if this is a basic
> question. Im running SQL server on a windows 2000 machine
> and when I run Analysis Services it picks up the server
> (my local computer name) perfectly. However, when I try
> and register the server in Enterprise Manager it cant find
> it, doesnt make sense to me. Could it be because I am
> logged into our network and not logged on the computer as
> an administrator and therefore dont have admin rights on
> the PC.
> Thanks
> John
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.688 / Virus Database: 449 - Release Date: 5/18/2004
|||Hi john
the problem you have due to two things
1)please load the sql server service pack 3 or 4
it solve your problem.
you can download from microsoft site
second one may be please reinstall and look the sql80 folder.if after uninstall it may be occur in the comp then remove it.again load it
..
biswajit
|||Hi
Thanks for the responses, still not working. I tried
setting it up as LOCAL and got the error
message, "specified SQL server not found (ConnectionOpen
(Connect). Same message when using the computer name or IP
address. Using SQL server pack 4.
Thanks
John

>--Original Message--
>What error do you get when yo try to register the SQL
Server?
>Rand
>This posting is provided "as is" with no warranties and
confers no rights.
>.
>
|||If this is new instance is a named instance it will not communicate on
port 1433 as unamed (default) instances do. Use start>run>
Cliconfig.exe and set the instance up with an alias to be able to set
a fixed port number. Other tools installed previously may look for the
1433 port.
On Fri, 21 May 2004 07:33:44 -0700, "John" <woody77_80@.hotmail.com>
wrote:

>Hi
>Im very new to SQL server so forgive me if this is a basic
>question. Im running SQL server on a windows 2000 machine
>and when I run Analysis Services it picks up the server
>(my local computer name) perfectly. However, when I try
>and register the server in Enterprise Manager it cant find
>it, doesnt make sense to me. Could it be because I am
>logged into our network and not logged on the computer as
>an administrator and therefore dont have admin rights on
>the PC.
>Thanks
>John
sqlsql

Connectionstring

Im using sql server express advanced edition and Windows Vista. My Windows
account doesnt have any permissions to the sql server at all, so I need to
use sql server logins in my connectionstring. How can I provide that when
using attachdb?
This is my connectionstring today:
Data Source=. \SQLEXPRESS;AttachDbFilename=|DataDirect
ory|\site_db.mdf;User
Instance=False;Initial Catalog=site_db;
StigSee http://www.microsoft.com/sql/howtob...stasupport.mspx for
considerations on using SQL 2005 under Vista. Note that SP2 is still in CTP
(beta).
I haven't played around with SQL Express but you ought to be able to add the
desired SQL login credentials in the connection string:
Data Source=. \SQLEXPRESS;AttachDbFilename=|DataDirect
ory|\site_db.mdf;User
Instance=False;Initial Catalog=site_db;User Id=MyLogin;Password=MyPassword
Hope this helps.
Dan Guzman
SQL Server MVP
"Stig Kulvedrsten" <stig@.spire.as> wrote in message
news:0ABA74C2-E6C4-4E84-B331-3633D0BEC597@.microsoft.com...
> Im using sql server express advanced edition and Windows Vista. My Windows
> account doesnt have any permissions to the sql server at all, so I need to
> use sql server logins in my connectionstring. How can I provide that when
> using attachdb?
> This is my connectionstring today:
> Stig|||I reinstalled and got my sql server express up and running. I then loaded up
VS.NET and tried to run my website.
Right away I got this error:
Timeout expired. The timeout period elapsed prior to obtaining a connection
from the pool. This may have occurred because all pooled connections were
in use and max pool size was reached.
What causes this error at first runtime?
Stig
"Stig Kulvedrsten" <stig@.spire.as> wrote in message
news:0ABA74C2-E6C4-4E84-B331-3633D0BEC597@.microsoft.com...
> Im using sql server express advanced edition and Windows Vista. My Windows
> account doesnt have any permissions to the sql server at all, so I need to
> use sql server logins in my connectionstring. How can I provide that when
> using attachdb?
> This is my connectionstring today:
> Data Source=. \SQLEXPRESS;AttachDbFilename=|DataDirect
ory|\site_db.mdf;User
> Instance=False;Initial Catalog=site_db;
> Stig

ConnectionOpen(Connect()) in SQL server 2000

hi,
i am new to SQL Server 2000 n trying to set up a Server in Windows 200
pro,
but whenever i try to Register the server it fails n gives the below
error,
ConnectionOpen(Connect()) faIled.
plz if some one can rectify this issue,
thanks in advance,
mandeepFirstly check if your SQL Server services are running; If yes then
proceed
Start-->programs --> Microsoft SQL Server --> Client Network Utility
Check to see if TCP/IP and NamedPipes are enabled only check if Shared
Memory is checked, if its not checked, check it

Connection works for a while then gets this : [DBMSLPCN]SQL Server does not exist or acces

Situation:
We have some custom code running on microsoft great plains **under
terminal services** on a windows 2003 machine.
We have a program (running under great plains) that will run for about
5 minutes, then give the error
[Microsoft][ODBC SQL Server Driver][DBMSLPNCN]SQL Server does not exist
or access denied.
I've tried disabling the shared memory protocol in the client network
utility. That didn't have any effect...even though the error points to
the shared memory protocol.
Now, I've got aql running on a non-standard port or 1150. If I change
this back to the default 1433, the program works fine.
Any ideas why?
Steven Vallarian
Hi
You may look at netstat to see what is connected to the ports of use PortQry
to see if you can connect:
http://support.microsoft.com/default...b;en-us;310099
It may be that you just have general network problems such as a faulty
switch.
John
"svallarian" <svallarian@.hotmail.com> wrote in message
news:1109778822.752029.318690@.l41g2000cwc.googlegr oups.com...
> Situation:
> We have some custom code running on microsoft great plains **under
> terminal services** on a windows 2003 machine.
> We have a program (running under great plains) that will run for about
> 5 minutes, then give the error
> [Microsoft][ODBC SQL Server Driver][DBMSLPNCN]SQL Server does not exist
> or access denied.
> I've tried disabling the shared memory protocol in the client network
> utility. That didn't have any effect...even though the error points to
> the shared memory protocol.
> Now, I've got aql running on a non-standard port or 1150. If I change
> this back to the default 1433, the program works fine.
> Any ideas why?
>
> Steven Vallarian
>

Connection works for a while then gets this : [DBMSLPCN]SQL Server does not exist or a

Situation:
We have some custom code running on microsoft great plains **under
terminal services** on a windows 2003 machine.
We have a program (running under great plains) that will run for about
5 minutes, then give the error
[Microsoft][ODBC SQL Server Driver][DBMSLPNCN]SQL Server does no
t exist
or access denied.
I've tried disabling the shared memory protocol in the client network
utility. That didn't have any effect...even though the error points to
the shared memory protocol.
Now, I've got aql running on a non-standard port or 1150. If I change
this back to the default 1433, the program works fine.
Any ideas why?
Steven VallarianHi
You may look at netstat to see what is connected to the ports of use PortQry
to see if you can connect:
http://support.microsoft.com/defaul...kb;en-us;310099
It may be that you just have general network problems such as a faulty
switch.
John
"svallarian" <svallarian@.hotmail.com> wrote in message
news:1109778822.752029.318690@.l41g2000cwc.googlegroups.com...
> Situation:
> We have some custom code running on microsoft great plains **under
> terminal services** on a windows 2003 machine.
> We have a program (running under great plains) that will run for about
> 5 minutes, then give the error
> [Microsoft][ODBC SQL Server Driver][DBMSLPNCN]SQL Server does
not exist
> or access denied.
> I've tried disabling the shared memory protocol in the client network
> utility. That didn't have any effect...even though the error points to
> the shared memory protocol.
> Now, I've got aql running on a non-standard port or 1150. If I change
> this back to the default 1433, the program works fine.
> Any ideas why?
>
> Steven Vallarian
>

Connection to SQL Server 2000 thinks it is 2005

Hi
I have a SQL Server 2000 database that I can connect to from an ASP.NET web
site quite happily. Using the same connection string in a Windows Forms
application I get the message "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").
Please could anyone advise.
Marek
Hi
It does not think it is SQL Server 2005 ("when"), but gives additional
information, in case you are trying to connect to SQL Server 2005. Part of
the enhanced error information that helps with troubleshooting.
Have you tried connecting though TCP/IP (adding "Network Library=DBMSSOCN"
to your connection string)?
You web server might be configured differently. Running cliconfg.exe on your
machine will allow you to configure the default library.
Regards
Mike
This posting is provided "AS IS" with no warranties, and confers no rights.
"Marek" <mav@.community.nospam> wrote in message
news:B89D86BB-AF20-4E90-89AE-C690A07BC232@.microsoft.com...
> Hi
> I have a SQL Server 2000 database that I can connect to from an ASP.NET
> web
> site quite happily. Using the same connection string in a Windows Forms
> application I get the message "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").
> Please could anyone advise.
> Marek

Connection to SQL Server 2000 thinks it is 2005

Hi
I have a SQL Server 2000 database that I can connect to from an ASP.NET web
site quite happily. Using the same connection string in a Windows Forms
application I get the message "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: 4
0
- Could not open a connection to SQL Server").
Please could anyone advise.
MarekHi
It does not think it is SQL Server 2005 ("when"), but gives additional
information, in case you are trying to connect to SQL Server 2005. Part of
the enhanced error information that helps with troubleshooting.
Have you tried connecting though TCP/IP (adding "Network Library=DBMSSOCN"
to your connection string)?
You web server might be configured differently. Running cliconfg.exe on your
machine will allow you to configure the default library.
Regards
--
Mike
This posting is provided "AS IS" with no warranties, and confers no rights.
"Marek" <mav@.community.nospam> wrote in message
news:B89D86BB-AF20-4E90-89AE-C690A07BC232@.microsoft.com...
> Hi
> I have a SQL Server 2000 database that I can connect to from an ASP.NET
> web
> site quite happily. Using the same connection string in a Windows Forms
> application I get the message "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").
> Please could anyone advise.
> Marek

Connection to database on a remote server

Here is my environment and problem:

I have VWD 2005 and SSE 2005 installed on my local machine. I also have these installed on my Windows 2003 Server. I developed my database using SSE on my local machine but pointing to directory on my server. I have been developing the web app using VWD on my server. I now want to use VWD on my local machine and point to the project on my server. I am able to open the project. In order to access the database in the "Database Explorer" I use as my "Data Source", "MS SQL Server (SQL Client) and it attaches fine and I can see my tables and data.

Now for my problem:

When I try to run the application "VIew in Browser", which login.aspx page is my first page, I get the page, but it doesn't inherit my master page which has the basic navigation and layout. Then after I try to login I get this message.

The file "W:\BBApp\App_Data\TimeTracker.mdf" is on a network path that is not supported for database files.
An attempt to attach an auto-named database for file W:\BBApp\App_Data\TimeTracker.mdf failed. A database with the same name exists, or specified file cannot be opened, or it is located on UNC share.

Here is a portion of my web.config file for the connection string.

<connectionStrings>

<removename="LocalSqlServer" />

<addname="LocalSqlServer"connectionString="Data Source=.\SQLExpress;Integrated Security=true;AttachDBFilename=|DataDirectory|TimeTracker.mdf;User Instance=true" />

My website I started with the source code for the TimeTracker start kit and have added more pages and changed the sitemap.

In general I guess I need to know how to handle using VWD on my local machine, but accessing the project on the server. The reason I'm doing this is because my colleague needs to be able to access the web app too to add pages to the site.

Thank you for any help.

Take a read of this articlehttp://www.aspspider.net/resources/Resource170.aspx
should see you right. Also if you are using membership remember you will need to take
care about the aspnetdb.mdf aswell.

Hope it help, if not let me know.

Connection strings and SQL Express 2005

Hello,

I am working on porting a Windows Forms VB.net VS 2003 app with a SQL 2000 backend - to using VS 2005 with SQL Express 2005.

I cannot seem to figure out how to set my connection string to work in the new environment. I have already recreated my database in SQL Express 2005 and ported the VS project to VS 2005.

The old string was (in my app.config file):

<add key="ConnectionString" value="workstation id=MAIN1;packet size=4096;user id=sa;data source=MAIN1;persist security info=True;initial catalog=Dbname;password=####" />

Any ideas?

Thanks,

Sam

Which error do you get ? SQL Server Express is disabled for remote connection by default, you might check the Screencast on my site to see how to enable that.

HTH; jens Suessmeyer.

http://www.sqlserver2005.de

connection string using sql authentication

i'm having trouble getting my project to work on other machines using windows authentication, so as this is urgent I want to change it to sql authentication. I've enabled sql authentication and enabled the sa login, could someone please tell me how to connect to my db

my connection string is currently as follows using windows authentication:

<

connectionStrings>

<

addname="GuitarShackConnection"connectionString="Server=(local)\SqlExpress;Integrated Security=True;Database=GuitarShack;"providerName="System.Data.SqlClient"/>

<

addname="GuitarShackConnectionString"connectionString="Data Source=(local)\SQLEXPRESS;Initial Catalog=GuitarShack;Integrated Security=True"providerName="System.Data.SqlClient"/>

<

addname="CustomerNameDS"connectionString="Data Source=.\SQLEXPRESS;AttachDbFilename=|DataDirectory|\ASPNETDB.MDF;Integrated Security=True;User Instance=True"providerName="System.Data.SqlClient"/>

</

connectionStrings><add name="ConnectionString" connectionString="Server=.\SQLEXPRESS;Database=xxxxxxxxxx;User ID=xxxxxxx;Password=xxxxxxx;Trusted_Connection=False"
providerName="System.Data.SqlClient" />|||

i've enabled sa and restarted the sql service but when i go to modify the connection in the database explorer and enter the credentials it returns an error when i test the connection:

the user sa is not associated with a trusted sql connection

any ideas what would cause this?

|||The full ins and outs of Sql Server permissions are beyond me, because I find it difficult to remember what user can do what. So I administer my servers using Windows Authentication on the local machine, set the Server up to operate in Mixed Mode, then create application users. I give these users the absolute minimum permissions possible, which is only actuallyExecute on the stored procedures I create for the app. They have no SELECT, DELETE, UPDATE or INSERT permissions. I know that you must NEVER use the sa account to connect to SQL Server from your ASP.NET app. That user has every privilege going.|||

Hi, the follow steps may be helpful to you.

To change security authentication mode
1. In SQL Server Management Studio Object Explorer, right-click your server, and then click Properties.
2. On the Security page, under Server authentication, select the new server authentication mode, and then click OK.
3. In the SQL Server Management Studio dialog box, click OK, to acknowledge the need to restart SQL Server.

To restart SQL Server from SQL Server Management Studio
1. In Object Explorer, right-click your server, and then click Restart. If running, SQL Server Agent must also be restarted.

To enable the sa login
1. Execute the following statements to enable the sa password and assign a password.
ALTER LOGIN sa ENABLE ;
GO
ALTER LOGIN sa WITH PASSWORD = '<password>' ;
GO

Thanks.