Help with a connection string

I have a two computers, in one of them I install the SQL Server 2005 express with server name USER\SQLEXPRESS and ip 192.168.3.15.The data base name is Prueba.mdf

In the other computer I have VB 2005 express , and I want to connect with Prueba.mdf in the the other pc. Can you help me?

Hi

Try the below connection string settings

User ID=sa; ( if you configured your own, then replace user name and password acc)

password=sa;

Data Source=USER\SQLEXPRESS;

database=Prueba;

Connect Timeout=1800;

Regards,

Dhinesh Kumar

|||If you want to connect to a user instance, you should use one of the strings at www.connectionstrings.com , look for SQL Server 2005 and user instances, there are some strings which will help you.

HTH, jens Suessmeyer.

http://www.sqlserver2005.de

Help w/ installing SW on SQL server (2005).

I have a server that has SQL server 2005 installed. I am trying to install additional sw and there seems to be a password algorithm set by our network that is too advanced for the sw i am trying to install. I get a error message stating "password to short" and "password doesnt meet complexity requirements".

Does anyone know if there is a way to turn off, disable or bypass the password algorithm?

Thanks!If I understand you correctly...the password complexity checkbox is in the properties of the login (user) you are trying to use. Open the default instance on your server, expand the security folder and click on the logins folder. Right click the user you are attempting to login with and select properties. In the middle of the properties page you will see 3 check boxes with the options you are seeking. Hope this is what you needed.

HELP URGENT - Error 17832 after SQL 7 SP4 install and MS03-039 install

I have an application that was developed in an older version of VB (I think
4.0). The users are heavily dependent on this application (and of course,
no source code). Yesterday the users were able to connect to the SQL 7
database. Last night I ran the Service Pack 4 on the SQL 7 machine and
today the users are unable to connect. They just get an error message
(Invalid SQL Server Login). When I look in the error log on the server I
see Error: 17832, Severity: 18, State: 7 Connection opened but invalid
login packet(s) sent. Connection closed.
Also, the latest security patch from Microsoft (MS03-039) was installed on
the server that houses the database. It is running Windows 2000.
Thanks
Any assistance would be greatly appreciated.Connie,
The only reference to 17832 that I could find was in this article:
INF: SQL Communication Errors 17832, 17824, 1608, 232, and 109 (KB Article
109787)
http://tinyurl.com/nfm8
17832 Unable to read login packet(s). [NT only]
This can happen if a client starts to connect, but never successfully
completes the attempt because of a client operating system or application
failure. It could also be caused by the network failing between the time a
connection attempt is initiated, and when it completes.
Of course, several changes were made, all at once, which is always risky.
(We always apply upgrades to a DEV or QA server before moving on to
production, if at all possible.)
This may be due to either SP4 or MS03-039. I see that MS03-039 patches RPC.
Although your application should (ideally) not need that facility I have no
way of knowing.
A more likely possibility: Did you us SP4 to update client software as
well? Some SPs have client and server components. Usually this is not a
problem, but sometimes it has caused grief.
Russell Fields
"Connie" <cfelt@.ga.wa.gov> wrote in message
news:%23oGDh66eDHA.2352@.TK2MSFTNGP09.phx.gbl...
> I have an application that was developed in an older version of VB (I
think
> 4.0). The users are heavily dependent on this application (and of course,
> no source code). Yesterday the users were able to connect to the SQL 7
> database. Last night I ran the Service Pack 4 on the SQL 7 machine and
> today the users are unable to connect. They just get an error message
> (Invalid SQL Server Login). When I look in the error log on the server I
> see Error: 17832, Severity: 18, State: 7 Connection opened but invalid
> login packet(s) sent. Connection closed.
> Also, the latest security patch from Microsoft (MS03-039) was installed on
> the server that houses the database. It is running Windows 2000.
> Thanks
> Any assistance would be greatly appreciated.
>|||You might want to check if the authentication mode got changed. Some of the
SQL service packs try to force Windows authentication or give the sa a
password other than blank. Go to SQL Server properties in SQL enterprise
manager, and check the security tab. See if you are in mixed mode or not.
From a DOS prompt on the server, you might also want to try
osql -U<user> -P<password> -S<servername>
for a user who cannot log on. That might give you a better error message.
--
***********************************
Andy S.
andy_mcdba@.yahoo.com
***********************************
"Connie" <cfelt@.ga.wa.gov> wrote in message
news:%23oGDh66eDHA.2352@.TK2MSFTNGP09.phx.gbl...
> I have an application that was developed in an older version of VB (I
think
> 4.0). The users are heavily dependent on this application (and of course,
> no source code). Yesterday the users were able to connect to the SQL 7
> database. Last night I ran the Service Pack 4 on the SQL 7 machine and
> today the users are unable to connect. They just get an error message
> (Invalid SQL Server Login). When I look in the error log on the server I
> see Error: 17832, Severity: 18, State: 7 Connection opened but invalid
> login packet(s) sent. Connection closed.
> Also, the latest security patch from Microsoft (MS03-039) was installed on
> the server that houses the database. It is running Windows 2000.
> Thanks
> Any assistance would be greatly appreciated.
>|||how is this application connecting to the SQL Server, an ODBC like? is that
pointed ata Named Pipe connection, if it is try switching it to a TCP/IP
like,
if not Look at your SQL Client Network Utility, if the default is Named
Pipes or you have a Named Pipes Alias try switching it to TCP/IP.
MS0-039 is has a lot of cross over with MS03-026, both applied a lot of
security to connectivity through Named Pipes.
HtH

Help Starting MSDE and creating a db + a log in problem! HELP!

Hello,
I downloaded MSDE from microsoft yesterday but I have been having alot of
problems setting it up. I started the install process with the following code
from te MSDN site:
Setup.exe /qb+ INSTANCENAME=VSDOTNET DISABLENETWORKPROTOCOLS=1 SAPWD=<my
password>
The instalation was to my local machine.
I have managed in visual studio to create a database with tables feild etc
but I keep on having a logon error
Can someone shed any light on the issue?
I assume my u/name is SA or my machine logon?
Did you try
OSQL -S<Servername\InstanceName> -U<Username> -P<password>
--or for integrated authentication
OSQL -S<Servername\InstanceName> -E
HTH, Jens Suessmeyer.

Help SP3a installation error

I have just installed a new Win2000 server, and loaded
SQL2000 Standard Edition. As soon as I try to install sp3a
I get the following error:
"Setup Initialization error.
Access is denied.
Source: D:\installs\SP3a-SQL2000\x86\setup\sqlspre.ini
Target: ...path\temp\setupsql.ini"
I am running the installation as administrator.| I have just installed a new Win2000 server, and loaded
| SQL2000 Standard Edition. As soon as I try to install sp3a
| I get the following error:
| "Setup Initialization error.
| Access is denied.
| Source: D:\installs\SP3a-SQL2000\x86\setup\sqlspre.ini
| Target: ...path\temp\setupsql.ini"
|
| I am running the installation as administrator.
--
Hi Sean,
Check c:\winnt\temp folder and see if setupsql.ini already exists. If it
does,
delete it. This should allow setupsql to complete successfully.
Hope this helps,
--
Eric Cárdenas
SQL Server support

HELP recovering from .Net 1.1 SP1 install

Report server has been failing on my machine ever since I installed the .Net
framework 1.1 SP1 to correct another problem. The error reported was that the
encryption keys were not working. Based on previous posts to solve this
problem I performed the following staps:
1. I ran rskeymgmt -d to delete the encrypted data.
2. restarted IIS
3. ran rsconfig with the following options
rsconfig -c -s <myserver> -d ReportServer -a Windows
rsconfig -c -s <myserver> -d ReportServerTempDB -a Windows
rsconfig -c -s <server> -d <database> -a Sql -u <username> -p
<password>
The above commands completed successfully
4. I tried to run rsactivate -r -c RSReportServer.config, but it responded
that the web service is already in a valid state or its state cannot be
determined.
When I try to access the report manager, I receive the following error:
The version of the report server database is either in a format that is
not valid, or it cannot be read. The found version is 'T.0.6.51'. The
expected version is 'C.0.6.51'.
I do not know what to try at this point other than trying to reinstall
report server, but from other posts it appears that a reinstall doesn't
always fix the problem.run rsconfig only once using the ReportServer database name. The temp
database name is always derived from the reportserver db name and you do not
need to use RSConfig to tell RS about the tempdb name.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"jbmeeh" <jbmeeh@.discussions.microsoft.com> wrote in message
news:4C7D2D20-F6B5-4616-8476-265FCC42E045@.microsoft.com...
> Report server has been failing on my machine ever since I installed the
.Net
> framework 1.1 SP1 to correct another problem. The error reported was that
the
> encryption keys were not working. Based on previous posts to solve this
> problem I performed the following staps:
> 1. I ran rskeymgmt -d to delete the encrypted data.
> 2. restarted IIS
> 3. ran rsconfig with the following options
> rsconfig -c -s <myserver> -d ReportServer -a Windows
> rsconfig -c -s <myserver> -d ReportServerTempDB -a Windows
> rsconfig -c -s <server> -d <database> -a Sql -u <username> -p
> <password>
> The above commands completed successfully
> 4. I tried to run rsactivate -r -c RSReportServer.config, but it responded
> that the web service is already in a valid state or its state cannot be
> determined.
> When I try to access the report manager, I receive the following error:
> The version of the report server database is either in a format that
is
> not valid, or it cannot be read. The found version is 'T.0.6.51'. The
> expected version is 'C.0.6.51'.
> I do not know what to try at this point other than trying to reinstall
> report server, but from other posts it appears that a reinstall doesn't
> always fix the problem.
>|||What do I do at this point?
"Daniel Reib [MSFT]" wrote:
> run rsconfig only once using the ReportServer database name. The temp
> database name is always derived from the reportserver db name and you do not
> need to use RSConfig to tell RS about the tempdb name.
> --
> -Daniel
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "jbmeeh" <jbmeeh@.discussions.microsoft.com> wrote in message
> news:4C7D2D20-F6B5-4616-8476-265FCC42E045@.microsoft.com...
> > Report server has been failing on my machine ever since I installed the
> ..Net
> > framework 1.1 SP1 to correct another problem. The error reported was that
> the
> > encryption keys were not working. Based on previous posts to solve this
> > problem I performed the following staps:
> >
> > 1. I ran rskeymgmt -d to delete the encrypted data.
> > 2. restarted IIS
> > 3. ran rsconfig with the following options
> >
> > rsconfig -c -s <myserver> -d ReportServer -a Windows
> > rsconfig -c -s <myserver> -d ReportServerTempDB -a Windows
> > rsconfig -c -s <server> -d <database> -a Sql -u <username> -p
> > <password>
> > The above commands completed successfully
> > 4. I tried to run rsactivate -r -c RSReportServer.config, but it responded
> > that the web service is already in a valid state or its state cannot be
> > determined.
> >
> > When I try to access the report manager, I receive the following error:
> >
> > The version of the report server database is either in a format that
> is
> > not valid, or it cannot be read. The found version is 'T.0.6.51'. The
> > expected version is 'C.0.6.51'.
> >
> > I do not know what to try at this point other than trying to reinstall
> > report server, but from other posts it appears that a reinstall doesn't
> > always fix the problem.
> >
>
>|||First decide if you are going to use windows auth or SQL auth. Then run
rsconfig passing in ReportServer for the -d option your choice for -a -u
and -p.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"jbmeeh" <jbmeeh@.discussions.microsoft.com> wrote in message
news:71D5A499-F838-4507-A64F-D6F6884B3118@.microsoft.com...
> What do I do at this point?
> "Daniel Reib [MSFT]" wrote:
> > run rsconfig only once using the ReportServer database name. The temp
> > database name is always derived from the reportserver db name and you do
not
> > need to use RSConfig to tell RS about the tempdb name.
> >
> > --
> > -Daniel
> > This posting is provided "AS IS" with no warranties, and confers no
rights.
> >
> >
> > "jbmeeh" <jbmeeh@.discussions.microsoft.com> wrote in message
> > news:4C7D2D20-F6B5-4616-8476-265FCC42E045@.microsoft.com...
> > > Report server has been failing on my machine ever since I installed
the
> > ..Net
> > > framework 1.1 SP1 to correct another problem. The error reported was
that
> > the
> > > encryption keys were not working. Based on previous posts to solve
this
> > > problem I performed the following staps:
> > >
> > > 1. I ran rskeymgmt -d to delete the encrypted data.
> > > 2. restarted IIS
> > > 3. ran rsconfig with the following options
> > >
> > > rsconfig -c -s <myserver> -d ReportServer -a Windows
> > > rsconfig -c -s <myserver> -d ReportServerTempDB -a Windows
> > > rsconfig -c -s <server> -d <database> -a Sql -u <username> -p
> > > <password>
> > > The above commands completed successfully
> > > 4. I tried to run rsactivate -r -c RSReportServer.config, but it
responded
> > > that the web service is already in a valid state or its state cannot
be
> > > determined.
> > >
> > > When I try to access the report manager, I receive the following
error:
> > >
> > > The version of the report server database is either in a format
that
> > is
> > > not valid, or it cannot be read. The found version is 'T.0.6.51'. The
> > > expected version is 'C.0.6.51'.
> > >
> > > I do not know what to try at this point other than trying to reinstall
> > > report server, but from other posts it appears that a reinstall
doesn't
> > > always fix the problem.
> > >
> >
> >
> >|||I gave up trying rebuild the encrypted data. I couldn't get around the
problem of the database version being incorrect. I reinstalled report server
and that cleared up the problem.
"Daniel Reib [MSFT]" wrote:
> First decide if you are going to use windows auth or SQL auth. Then run
> rsconfig passing in ReportServer for the -d option your choice for -a -u
> and -p.
> --
> -Daniel
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "jbmeeh" <jbmeeh@.discussions.microsoft.com> wrote in message
> news:71D5A499-F838-4507-A64F-D6F6884B3118@.microsoft.com...
> > What do I do at this point?
> >
> > "Daniel Reib [MSFT]" wrote:
> >
> > > run rsconfig only once using the ReportServer database name. The temp
> > > database name is always derived from the reportserver db name and you do
> not
> > > need to use RSConfig to tell RS about the tempdb name.
> > >
> > > --
> > > -Daniel
> > > This posting is provided "AS IS" with no warranties, and confers no
> rights.
> > >
> > >
> > > "jbmeeh" <jbmeeh@.discussions.microsoft.com> wrote in message
> > > news:4C7D2D20-F6B5-4616-8476-265FCC42E045@.microsoft.com...
> > > > Report server has been failing on my machine ever since I installed
> the
> > > ..Net
> > > > framework 1.1 SP1 to correct another problem. The error reported was
> that
> > > the
> > > > encryption keys were not working. Based on previous posts to solve
> this
> > > > problem I performed the following staps:
> > > >
> > > > 1. I ran rskeymgmt -d to delete the encrypted data.
> > > > 2. restarted IIS
> > > > 3. ran rsconfig with the following options
> > > >
> > > > rsconfig -c -s <myserver> -d ReportServer -a Windows
> > > > rsconfig -c -s <myserver> -d ReportServerTempDB -a Windows
> > > > rsconfig -c -s <server> -d <database> -a Sql -u <username> -p
> > > > <password>
> > > > The above commands completed successfully
> > > > 4. I tried to run rsactivate -r -c RSReportServer.config, but it
> responded
> > > > that the web service is already in a valid state or its state cannot
> be
> > > > determined.
> > > >
> > > > When I try to access the report manager, I receive the following
> error:
> > > >
> > > > The version of the report server database is either in a format
> that
> > > is
> > > > not valid, or it cannot be read. The found version is 'T.0.6.51'. The
> > > > expected version is 'C.0.6.51'.
> > > >
> > > > I do not know what to try at this point other than trying to reinstall
> > > > report server, but from other posts it appears that a reinstall
> doesn't
> > > > always fix the problem.
> > > >
> > >
> > >
> > >
>
>