Showing posts with label latest. Show all posts
Showing posts with label latest. Show all posts

Tuesday, March 27, 2012

Cannot remotely login to SQL Express since last windows update

Since today (after installing the latest Windows Updates !on my local machine!) I cannot login to a SQLExpress instance remotely; stating that it cannot find the server/instance.

The weird thing is: it only happens when I want to login to the non-default instance (sqlexpress 2005) (<IP>\<instance>).

When i'm using the default instance (msde 2000 or sqlexpress 2005 on another machine) (<IP>) it seems to work fine.

Does this have something to do with the windows updates, or is it just a coincedence?

Thanks in advance,

Remco RosThis is probably due to the update changed your setting. Just check your firewall on the server and put sqlbrowser.exe or UDP port 1434 to exception. Also make sure your sqlbrowser is running.|||we didn't install the updates on the server (yet) only on the client, so it must be a client thing.

Server:
Win 2003 / SQL Express 2005
Tcp/ip / named pipes: yes
sqlbrowser running
firewall exception on 1434udp 1433tcp.

tested on these client(s):
Local (without latest updates): CAN connect
XP Home with SQL Server Management studio (with lates windows updates): CANNOT connect
XP Pro with SQL Server Management studio Express (with lates windows updates): CANNOT connect
Win 2003 with SQL Server Management studio Express

(WITHOUT lates windows updates): CAN connect.

I see a pattern here...|||Are you sure your SQL Express listens on TCP port 1433 since your put 1433 in exception? What's the result if you run "telnet yourserver sql_tcp_port"? Can it connect? Could it be possible that IPSEC blocked the traffic between the problem machine if the IPSEC is on?

Saturday, February 25, 2012

Cannot Install DB

Hi,
I have installed the latest MSDE and am entering the following text in the
query analyzer:
EXEC sp_attach_db @.dbname = 'SRPA',
@.filename1 = '{c:\SRPA\SRPA.MDF}',
@.filename2 = '{c:\SPRA\SRPA.LDF}';
but i'm getting the following error:
Error: Device activation error. The physical file name 'c:\SRPA\SRPA.MDF'
may be incorrect.
I have checked and double checked the name/location etc and it all matches..
any help would be greatly appreciated, Thanks
Matt
You dont need these curly brackets. Just type in (as filename is expecting
a nvarchar)
EXEC sp_attach_db @.dbname = 'SRPA',
@.filename1 = N'c:\SRPA\SRPA.MDF',
@.filename2 = N'c:\SPRA\SRPA.LDF'
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
"Matt" <Matt@.discussions.microsoft.com> schrieb im Newsbeitrag
news:C7340567-DD95-4534-A75E-0583F630E6E0@.microsoft.com...
> Hi,
> I have installed the latest MSDE and am entering the following text in the
> query analyzer:
> EXEC sp_attach_db @.dbname = 'SRPA',
> @.filename1 = '{c:\SRPA\SRPA.MDF}',
> @.filename2 = '{c:\SPRA\SRPA.LDF}';
> but i'm getting the following error:
> Error: Device activation error. The physical file name 'c:\SRPA\SRPA.MDF'
> may be incorrect.
> I have checked and double checked the name/location etc and it all
> matches..
> any help would be greatly appreciated, Thanks
> Matt
>
|||Thanks, Tried it but still the same error.
"Jens Sü?meyer" wrote:

> You don′t need these curly brackets. Just type in (as filename is expecting
> a nvarchar)
> EXEC sp_attach_db @.dbname = 'SRPA',
> @.filename1 = N'c:\SRPA\SRPA.MDF',
> @.filename2 = N'c:\SPRA\SRPA.LDF'
> HTH, Jens Suessmeyer.
> --
> http://www.sqlserver2005.de
> --
> "Matt" <Matt@.discussions.microsoft.com> schrieb im Newsbeitrag
> news:C7340567-DD95-4534-A75E-0583F630E6E0@.microsoft.com...
>
>
|||Just a moment, i saw that you are using the QA ?!
So perhaps you are not connected to the MSDE rathjer than to a SQL Server.
If you issue the command
sp_Attach_db the SQL Server / MSDE will always look on Local drives to get
control over the datafile. So if you are connected to a remote server rather
than to the MSDE it will tell you that the files are not present.
If you really want to make sure that you are working on the MSDE, just do
this on the command line:
OSQL -E (if you are using Integrated Security, if not
use -UUsername -PPassword)
Then type in the Command i gave you in the last post, that should really
help, if not there MUST be a difference in the location you specified.
HTH, Jens SUessmeyer.
http://www.sqlserver2005.de
"Matt" <Matt@.discussions.microsoft.com> schrieb im Newsbeitrag
news:0206A4CE-541A-4CA8-B5A6-5213E982D1EC@.microsoft.com...[vbcol=seagreen]
> Thanks, Tried it but still the same error.
>
> "Jens Smeyer" wrote:
|||Thats got it..with the OSQL -E it worked fine thru cmd.. Thanks for your help
"Jens Sü?meyer" wrote:

> Just a moment, i saw that you are using the QA ?!
> So perhaps you are not connected to the MSDE rathjer than to a SQL Server.
> If you issue the command
> sp_Attach_db the SQL Server / MSDE will always look on Local drives to get
> control over the datafile. So if you are connected to a remote server rather
> than to the MSDE it will tell you that the files are not present.
> If you really want to make sure that you are working on the MSDE, just do
> this on the command line:
> OSQL -E (if you are using Integrated Security, if not
> use -UUsername -PPassword)
> Then type in the Command i gave you in the last post, that should really
> help, if not there MUST be a difference in the location you specified.
> HTH, Jens SUessmeyer.
> --
> http://www.sqlserver2005.de
> --
> "Matt" <Matt@.discussions.microsoft.com> schrieb im Newsbeitrag
> news:0206A4CE-541A-4CA8-B5A6-5213E982D1EC@.microsoft.com...
>
>