Showing posts with label vista. Show all posts
Showing posts with label vista. Show all posts

Thursday, March 29, 2012

Can't connect from a vista client to SQL 2005 box,other machines work fine

Hey. I've a windows vista machine which can't connect to SQL 2005 box. Other machines which are lower than vista work fine. Also, vista box can connect to other SQL 2005 instances but can't connect to only one instance. But, I can connect to the instance fine from my XP box. Also, it's not a permissions issue. This user is an SA and can connect form some other machine. SQL 2005 box is at 2047 version right now. And, the user is able to connect to some other boxes which are also at 2047. Please help. Thank you

Add the account sepcifically to the SQL Server. When you connect from Vista (because of the UAC) it strips out your group SID from local admins, so SQL Server doesn't know who you are, and that's probably what is causing your issue. Add the user's account by name to the box.

If this post answers your question, make sure you mark it "answered" so others can find it quickly.

Thanks -

Buck Woody
http://www.buckwoody.com

Sunday, March 25, 2012

Can't attach 2005 DB on Vista - Erland? Anyone? Help me please!

Dear Group

I've installed MSSQL 2005 STD on Vista and now can't attach my
databases.
I've installed SQL SP2 and the SQL Vista Beta Update.
The error I'm getting is:

Unable to open the physical file <Path to MDF>. Operating system error
5: '''5(Error not found)'''. (Microsoft SQL Server, Error: 5120)

Thanks for your help. All your hints are very much appreciated.

Thanks,

Martin N Feuersteiner
Invent2b GroupOn 1 Mar, 14:19, theintrepid...@.hotmail.com wrote:

Quote:

Originally Posted by

Dear Group
>
I've installed MSSQL 2005 STD on Vista and now can't attach my
databases.
I've installed SQL SP2 and the SQL Vista Beta Update.
The error I'm getting is:
>
Unable to open the physical file <Path to MDF>. Operating system error
5: '''5(Error not found)'''. (Microsoft SQL Server, Error: 5120)


Found the Solution on Vista:

- Go to Control Panel and Switch to Classic View
- Click on User Accounts
- Click on Turn User Account Control on or off
- Uncheck use User Account Control (UAC) to help protect your
computer.
- OK
- Restart System

Try again to attach the DB. It should work now.

Hope this helps anyone else having this problem.

Martin
Invent2b Group|||(theintrepidfox@.hotmail.com) writes:

Quote:

Originally Posted by

Found the Solution on Vista:
>
- Go to Control Panel and Switch to Classic View
- Click on User Accounts
- Click on Turn User Account Control on or off
- Uncheck use User Account Control (UAC) to help protect your
computer.
- OK
- Restart System
>
Try again to attach the DB. It should work now.
>
Hope this helps anyone else having this problem.


Maybe a bit heavy-duty. The point with UAC in Vista as I understand it,
is that you should not run as Administrator all the time, only when you
need it. While running as Administrator is convenient, it makes it
easier for any infections your machines may catch to spread. I think
there is a context-menu option "Run As Administrator".

Personally, I have not had any encounter with Vista yet.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx|||On 1 Mar, 22:13, Erland Sommarskog <esq...@.sommarskog.sewrote:

Quote:

Originally Posted by

(theintrepid...@.hotmail.com) writes:

Quote:

Originally Posted by

Found the Solution on Vista:


>

Quote:

Originally Posted by

- Go to Control Panel and Switch to Classic View
- Click on User Accounts
- Click on Turn User Account Control on or off
- Uncheck use User Account Control (UAC) to help protect your
computer.
- OK
- Restart System


>

Quote:

Originally Posted by

Try again to attach the DB. It should work now.


>

Quote:

Originally Posted by

Hope this helps anyone else having this problem.


>
Maybe a bit heavy-duty. The point with UAC in Vista as I understand it,
is that you should not run as Administrator all the time, only when you
need it. While running as Administrator is convenient, it makes it
easier for any infections your machines may catch to spread. I think
there is a context-menu option "Run As Administrator".
>
Personally, I have not had any encounter with Vista yet.
>
--
Erland Sommarskog, SQL Server MVP, esq...@.sommarskog.se
>
Books Online for SQL Server 2005 athttp://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books...
Books Online for SQL Server 2000 athttp://www.microsoft.com/sql/prodinfo/previousversions/books.mspx


Hi Erland

Correct. It's heavy duty and my first attempt was to right-click on
the Management Studio Icon and to choose the 'Run As Administrator'
option which didn't work.
UAC is indeed a good feature and helps to protect. But following this
process didn't solve the problem and there was no other choice than
having to turn off UAC.
I haven't tried turning UAC on since I attached the databases to see
what its effect is.

To put it short, UAC is good but not in a development environemnt.
Despite having turned it off VS 2005 still warns me that it may not
work correctly, needing Admin rights but it starts fine without any
errors so far. And anyway, what's the REAL risk of having it turned
off. A Vista machine with UAC off won't become less protected than a
XP machine used to be and any additional security software and common
user sense will help protect the same way. I reckon it's rather good
for my dad who clicks on and executes everything he's prompted with.
Bless him and his viruses.

If anyone has a better suggestion to this workaround which will work
with UAC on, please post it here.

All the best,

Martin
Invent2b Group|||(theintrepidfox@.hotmail.com) writes:

Quote:

Originally Posted by

Correct. It's heavy duty and my first attempt was to right-click on
the Management Studio Icon and to choose the 'Run As Administrator'
option which didn't work.
UAC is indeed a good feature and helps to protect. But following this
process didn't solve the problem and there was no other choice than
having to turn off UAC.
I haven't tried turning UAC on since I attached the databases to see
what its effect is.


Having today having had my first encounter with Vista, and I agree that it
is very irritating. (Then again, there seems to be a whole lot of
irritating fluff in Vista. I want to computer to run SQL Server on, I
don't want this "My Music" etc.)

No, I never came as far installing SQL Server. About every second time
I reboot, the machine powers off while Vista is starting. I will probably
change to a different motherboard.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx|||I agree UAC can be annoying on a development box but I've been running Vista
with UAC and haven't had to resort to turning it off. I need to run VS as
administrator. It's optional with SSMS depending on the features I use
(e.g. stop/start services requires admin).

--
Hope this helps.

Dan Guzman
SQL Server MVP

<theintrepidfox@.hotmail.comwrote in message
news:1173031039.763449.115250@.n33g2000cwc.googlegr oups.com...

Quote:

Originally Posted by

On 1 Mar, 22:13, Erland Sommarskog <esq...@.sommarskog.sewrote:

Quote:

Originally Posted by

> (theintrepid...@.hotmail.com) writes:

Quote:

Originally Posted by

Found the Solution on Vista:


>>

Quote:

Originally Posted by

- Go to Control Panel and Switch to Classic View
- Click on User Accounts
- Click on Turn User Account Control on or off
- Uncheck use User Account Control (UAC) to help protect your
computer.
- OK
- Restart System


>>

Quote:

Originally Posted by

Try again to attach the DB. It should work now.


>>

Quote:

Originally Posted by

Hope this helps anyone else having this problem.


>>
>Maybe a bit heavy-duty. The point with UAC in Vista as I understand it,
>is that you should not run as Administrator all the time, only when you
>need it. While running as Administrator is convenient, it makes it
>easier for any infections your machines may catch to spread. I think
>there is a context-menu option "Run As Administrator".
>>
>Personally, I have not had any encounter with Vista yet.
>>
>--
>Erland Sommarskog, SQL Server MVP, esq...@.sommarskog.se
>>
>Books Online for SQL Server 2005
>athttp://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books...
>Books Online for SQL Server 2000
>athttp://www.microsoft.com/sql/prodinfo/previousversions/books.mspx


>
Hi Erland
>
Correct. It's heavy duty and my first attempt was to right-click on
the Management Studio Icon and to choose the 'Run As Administrator'
option which didn't work.
UAC is indeed a good feature and helps to protect. But following this
process didn't solve the problem and there was no other choice than
having to turn off UAC.
I haven't tried turning UAC on since I attached the databases to see
what its effect is.
>
To put it short, UAC is good but not in a development environemnt.
Despite having turned it off VS 2005 still warns me that it may not
work correctly, needing Admin rights but it starts fine without any
errors so far. And anyway, what's the REAL risk of having it turned
off. A Vista machine with UAC off won't become less protected than a
XP machine used to be and any additional security software and common
user sense will help protect the same way. I reckon it's rather good
for my dad who clicks on and executes everything he's prompted with.
Bless him and his viruses.
>
If anyone has a better suggestion to this workaround which will work
with UAC on, please post it here.
>
All the best,
>
Martin
Invent2b Group
>

|||>

Quote:

Originally Posted by

No, I never came as far installing SQL Server. About every second time
I reboot, the machine powers off while Vista is starting. I will probably
change to a different motherboard.
>
--
Erland Sommarskog, SQL Server MVP, esq...@.sommarskog.se
>


How does Vista behave if you install it on a non Vista PC under
Virtual PC 2007?
It does reboot during setup start-up without warning and a blank
screen but else it's much more stable and fine. Just setting up SBS
and some client PCs under Virtual Server on it.
I had that rebooting thing during startup and freezing with three PCs
(non Vista) until it turned out to be a really nasty virus despite
running all sorts of virus checks.
The solution was to actually take the drive out, and stick it as a
slave in another PC with up-to date Free AVG running which actually
detected that bugger.

The only thing that still bugs me with Vista is, and I think it's a
Vista issue, I doesn't list the databases on the SQL Server when
trying to connect (connecting is fine) to an existing instance from
Outlook Business Contact Manager. Checked all the SQL security,
logins, protocols. Any idea?

Thursday, March 22, 2012

Cant Access SQL Server (on Vista) from other Network PC (XP)

I have just installed Vista on one of my home network pcs. I also installed Outlook 2005 with Business Contact Manager. It installs an instance of SQL Server Express.

I have created another database on this engine that I need to access from other PCs on my network.

The server address is PCNAME\MSSMLBIZ and I can access the data the database using this name from the the Vista PC (PCNAME).

When I try to acess the database using the same credentials (server, database, username (sa) and password) from an XP PC on the network - it times out and returns an error . My guess is that it is not seeing the database service at all.

I have SQL Server Management Studio installed on the Vista PC and have full access to the instance.

Server authentication is set for SQL Server and Windows Authentication mode.

Can anyone help me?. I need to access the SQL Server from the XP PC.

Ian

Make sure that SQL Server Browser is running, you firewall is configured properly to allow the SQL Server traffic and that Remote connections are enabled for SQL Server. (See the screencats on my site for more information).

Firewall configuration: http://support.microsoft.com/default.aspx?scid=kb%3ben-us%3b914277


Jens K. Suessmeyer.

http://www.sqlserver2005.de

|||

Yes - that worked - as soon as I set remote access on Surface Area Configuration for Services and Connections page.

Regards Ian

|||I have just installed SQL Server 2005 Developer Edition on Windows Vista Ultimate, but i cant access and see "sql server managment studio" The only things i have are these >>>

Cant Access SQL Server (on Vista)

I have just installed Vista on one of my home network pcs. I also installed Outlook 2005 with Business Contact Manager. It installs an instance of SQL Server Express.

I have created another database on this engine that I need to access from other PCs on my network.

The server address is PCNAME\MSSMLBIZ and I can access the data the database using this name from the the Vista PC (PCNAME).

When I try to acess the database using the same credentials (server, database, username (sa) and password) from an XP PC on the network - it times out and returns an error . My guess is that it is not seeing the database service at all.

I have SQL Server Management Studio installed on the Vista PC and have full access to the instance.

Server authentication is set for SQL Server and Windows Authentication mode.

Can anyone help me?. I need to access the SQL Server from the XP PC.

Ian

Make sure that SQL Server Browser is running, you firewall is configured properly to allow the SQL Server traffic and that Remote connections are enabled for SQL Server. (See the screencats on my site for more information).

Firewall configuration: http://support.microsoft.com/default.aspx?scid=kb%3ben-us%3b914277


Jens K. Suessmeyer.

http://www.sqlserver2005.de

|||

Yes - that worked - as soon as I set remote access on Surface Area Configuration for Services and Connections page.

Regards Ian

|||I have just installed SQL Server 2005 Developer Edition on Windows Vista Ultimate, but i cant access and see "sql server managment studio" The only things i have are these >>>

Monday, March 19, 2012

Cannot view reports, SSRS on Vista

Hello!
I have installed/configured SSRS on a Vista-laptop but I cannot view reports
in IE.
Finally, I got the reportserver running under IIS 7.0.The report works fine
in VS2005 and deployment (finally!!) works fine from the editor.
But the infamous 'rsReportNotReady'-error shows once I try to view a report.
Other strange stuff: When I click on the link "ReportViewer.aspx" IE only
shows the reportServer root-directory. And the same thing happens if I
create a dumb .aspx-file and put into the reportServer/Pages directory.
The installation has been hellish so far, and I have read SO many blogs and
tips but nothing works...
* Yes, I have tried to turn off database snapshot isolation level for the
SSRS-databases
* Yes, I have installed Service Pack 2 (twice)
Im hoping for your help, as I see no path to a solution for this mystery!
Cheers DavidTwo things to try (I have never done this, this is from the newsgroup).
1) Control Panel / User Accounts / Turn User Account Control - off
2) run "%windir%\Microsoft.NET\Framework\version\aspnet_regiis.exe" -i
My advice is to try #1 first. I have seen this multiple times. As far as #2,
that I have only seen once in the newsgroup.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"David" <david_sundstrom_sandegard.nospam@.hotmail.com> wrote in message
news:OW%23s1iLbIHA.4476@.TK2MSFTNGP06.phx.gbl...
> Hello!
> I have installed/configured SSRS on a Vista-laptop but I cannot view
> reports in IE.
> Finally, I got the reportserver running under IIS 7.0.The report works
> fine in VS2005 and deployment (finally!!) works fine from the editor.
> But the infamous 'rsReportNotReady'-error shows once I try to view a
> report.
> Other strange stuff: When I click on the link "ReportViewer.aspx" IE only
> shows the reportServer root-directory. And the same thing happens if I
> create a dumb .aspx-file and put into the reportServer/Pages directory.
> The installation has been hellish so far, and I have read SO many blogs
> and tips but nothing works...
> * Yes, I have tried to turn off database snapshot isolation level for the
> SSRS-databases
> * Yes, I have installed Service Pack 2 (twice)
> Im hoping for your help, as I see no path to a solution for this mystery!
> Cheers David|||I managed to get thíngs running by un-installing the whole SQL-server package.
(I believe that I might have had a mix-up of editions installed)
Took me anothier full two hours, but now the thing works!
Thx for helping out!
David
"Bruce L-C [MVP]" wrote:
> Two things to try (I have never done this, this is from the newsgroup).
> 1) Control Panel / User Accounts / Turn User Account Control - off
> 2) run "%windir%\Microsoft.NET\Framework\version\aspnet_regiis.exe" -i
> My advice is to try #1 first. I have seen this multiple times. As far as #2,
> that I have only seen once in the newsgroup.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
>
> "David" <david_sundstrom_sandegard.nospam@.hotmail.com> wrote in message
> news:OW%23s1iLbIHA.4476@.TK2MSFTNGP06.phx.gbl...
> > Hello!
> >
> > I have installed/configured SSRS on a Vista-laptop but I cannot view
> > reports in IE.
> >
> > Finally, I got the reportserver running under IIS 7.0.The report works
> > fine in VS2005 and deployment (finally!!) works fine from the editor.
> >
> > But the infamous 'rsReportNotReady'-error shows once I try to view a
> > report.
> >
> > Other strange stuff: When I click on the link "ReportViewer.aspx" IE only
> > shows the reportServer root-directory. And the same thing happens if I
> > create a dumb .aspx-file and put into the reportServer/Pages directory.
> >
> > The installation has been hellish so far, and I have read SO many blogs
> > and tips but nothing works...
> >
> > * Yes, I have tried to turn off database snapshot isolation level for the
> > SSRS-databases
> > * Yes, I have installed Service Pack 2 (twice)
> >
> > Im hoping for your help, as I see no path to a solution for this mystery!
> >
> > Cheers David
>
>

Sunday, March 11, 2012

Cannot use Windows Authentication to connect to local Sql 2005

Hi,
I am building my workstation again, freshly installing everything.
The OS is Vista Business, 32 bit. I've installed Sql Server 2005
Developer Edition fine and applied service pack 2 successfully. It
seems to run fine, with one exception.
I can't logon using Windows Authentication. I'm a member of the Local
administrators group (as well as a Domain admin), but my domain
\username gets a logon denied error. I can logon just fine with the
sa account, but I prefer Windows Authentication.
Any ideas?
Thanks
AndyAndy (andyj@.med-associates.com) writes:
> I am building my workstation again, freshly installing everything.
> The OS is Vista Business, 32 bit. I've installed Sql Server 2005
> Developer Edition fine and applied service pack 2 successfully. It
> seems to run fine, with one exception.
> I can't logon using Windows Authentication. I'm a member of the Local
> administrators group (as well as a Domain admin), but my domain
> \username gets a logon denied error. I can logon just fine with the
> sa account, but I prefer Windows Authentication.
Did you run the special Vista thing at the end of the SP2 setup? Keep in
mind that on Vista you are normally not admin, only if you request and
confirm. Either start Mgmt Studio with Run As Administrator, or - better -
add your Windows user as a long and grant it CONTROL SERVER.
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx|||On Jul 12, 6:30 pm, Erland Sommarskog <esq...@.sommarskog.se> wrote:
> Did you run the special Vista thing at the end of the SP2 setup? Keep in
> mind that on Vista you are normally not admin, only if you request and
> confirm. Either start Mgmt Studio with Run As Administrator, or - better -
> add your Windows user as a long and grant it CONTROL SERVER.
Yes, I ran the provisioning tool. I added my user specifically and
granted connect and control server, that seems to have worked. I
thought I had tried something similar by adding domain admins, but
that didn't seem to work.
Thanks for the tip.
Andy

Thursday, March 8, 2012

cannot upgrade management studio

Hi,

I have clean install of Vista and Orcas March CTP. Vista automatically downloaded SP2 for SQL services. It does not come with Management Studio however, so I have to download it from web. There is only unupdated version for download, so I downloaded it and installed it. It does not work of course, but when I run the SP2 pack, it wrote me that half of the products are already updated and half of them are not updatable by the pack.

What should I do?

SQL Server SP2 does update the enterprise Management Studio, so I assume you are talking about Management Studio Express.

You should be able to uninstall Management Studio Express and then install Management Studio Express SP2 from this web site: http://www.microsoft.com/downloads/details.aspx?familyid=6053C6F8-82C8-479C-B25B-9ACA13141C9E&displaylang=en If you've already done that, you can verify that you have Management Studio Express SP2 by starting the application and then looking at the Help > About... dialog. SP2 is version 9.0.3042.

Hope this helps,

Steve

|||As explained you can accomplish as per the explanation above, if you are using ENterprise Management studio then you might try again applying the Service pack2.

cannot upgrade management studio

Hi,

I have clean install of Vista and Orcas March CTP. Vista automatically downloaded SP2 for SQL services. It does not come with Management Studio however, so I have to download it from web. There is only unupdated version for download, so I downloaded it and installed it. It does not work of course, but when I run the SP2 pack, it wrote me that half of the products are already updated and half of them are not updatable by the pack.

What should I do?

SQL Server SP2 does update the enterprise Management Studio, so I assume you are talking about Management Studio Express.

You should be able to uninstall Management Studio Express and then install Management Studio Express SP2 from this web site: http://www.microsoft.com/downloads/details.aspx?familyid=6053C6F8-82C8-479C-B25B-9ACA13141C9E&displaylang=en If you've already done that, you can verify that you have Management Studio Express SP2 by starting the application and then looking at the Help > About... dialog. SP2 is version 9.0.3042.

Hope this helps,

Steve

|||As explained you can accomplish as per the explanation above, if you are using ENterprise Management studio then you might try again applying the Service pack2.

Saturday, February 25, 2012

Cannot Start SQL Server 2000 after installing Vista

Just installed the Vista Business Upgrade. Now I cannot start SQL Server 200
0
even though my Windows Authentication has not changed. The Service Manager
reports "Access Denied" when I try to start the server.
Do I need to reinstall the server or is there a workaround? I tried the SSMS
but had no success.
--
malcolmHi,
can you elaborate more, is you MSSQL service run under domain or local
account?...However you an use registry rebuild to rebuild sql server
instllation and accounts without effecting your databases.
Omar
"malcolm" wrote:

> Just installed the Vista Business Upgrade. Now I cannot start SQL Server 2
000
> even though my Windows Authentication has not changed. The Service Manager
> reports "Access Denied" when I try to start the server.
> Do I need to reinstall the server or is there a workaround? I tried the SS
MS
> but had no success.
> --
> malcolm|||malcolm (ramartower@.access312.com) writes:
> Just installed the Vista Business Upgrade. Now I cannot start SQL Server
> 2000 even though my Windows Authentication has not changed. The Service
> Manager reports "Access Denied" when I try to start the server.
> Do I need to reinstall the server or is there a workaround? I tried the
> SSMS but had no success.
You could try to start it from Computer Management, or run Service Manager
by running as Admin. I guess the first showstopper is the UAC. But the
more basic problem is that SQL 2000 is not supported on Vista, so you may
not get it work at all. If you need the databases, you will need to find
another machine with a different operating system, or upgrade to SQL 2005.
(And you need SP2 of SQL 2005 to run on Vista.)
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx

Sunday, February 12, 2012

Cannot restore databse from file

Hi,

I have Sql server management studio express install on one pc with windows server 2003 os , working ok.

I also installed the same on my vista machine.

I use backup tool to store the back file from the windows server 2003 and to restore it back in the vista.

After connect to the SQLEXPRESS instance in the management studio

I right click the Database folder ->"Restore Database"->To database "xxx" (same name as was in the prev os)

From device->...->backup media - file , Add - choose the file with .back extension -> OK

In this stage there are 2 windows:

"Sql server windows NT has stop working"

And the collecting information for ms to help me..

With 3 files:

C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Report17f38cd5\WER80EE.tmp.version.txt

C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Report17f38cd5\WER80EF.tmp.appcompat.txt

C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Report17f38cd5\WER8C3C.tmp.mdmp

After click cancel , the management studio popup exception window with those details:

TITLE: Microsoft SQL Server Management Studio Express

An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.Express.ConnectionInfo)


ADDITIONAL INFORMATION:

A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - The specified network name is no longer available.) (Microsoft SQL Server, Error: 64)

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


BUTTONS:

OK

Exception details:

===================================

An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.Express.ConnectionInfo)


Program Location:

at Microsoft.SqlServer.Management.Common.ServerConnection.ExecuteWithResults(String sqlCommand)
at Microsoft.SqlServer.Management.Smo.ExecutionManager.ExecuteWithResults(String query)
at Microsoft.SqlServer.Management.Smo.BackupRestoreBase.ExecuteSqlWithResults(Server server, String cmd)
at Microsoft.SqlServer.Management.Smo.Restore.ReadBackupHeader(Server srv)
at Microsoft.SqlServer.Management.SqlManagerUI.SqlRestoreDatabaseGeneral.buttonSelectDevice_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

===================================

A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - The specified network name is no longer available.) (.Net SqlClient Data Provider)


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


Server Name: MY-DEVPC\SQLEXPRESS
Error Number: 64
Severity: 20
State: 0



Program Location:

at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParserStateObject.ReadSniError(TdsParserStateObject stateObj, UInt32 error)
at System.Data.SqlClient.TdsParserStateObject.ReadSni(DbAsyncResult asyncResult, TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParserStateObject.ReadPacket(Int32 bytesExpected)
at System.Data.SqlClient.TdsParserStateObject.ReadBuffer()
at System.Data.SqlClient.TdsParserStateObject.ReadByte()
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlDataReader.ConsumeMetaData()
at System.Data.SqlClient.SqlDataReader.get_MetaData()
at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)
at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method)
at System.Data.SqlClient.SqlCommand.ExecuteDbDataReader(CommandBehavior behavior)
at System.Data.Common.DbCommand.System.Data.IDbCommand.ExecuteReader(CommandBehavior behavior)
at System.Data.Common.DbDataAdapter.FillInternal(DataSet dataset, DataTable[] datatables, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior)
at System.Data.Common.DbDataAdapter.Fill(DataSet dataSet, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior)
at System.Data.Common.DbDataAdapter.Fill(DataSet dataSet)
at Microsoft.SqlServer.Management.Common.ServerConnection.ExecuteWithResults(String sqlCommand)

after this I can see in the SQL server configuration manager that the service of "SQL Server (SQLEXPRESS)" is stopped

I try to play with the protocols for sqlexpress enable and disable some of them , using only tcp etc etc , nothing work.

product version details:

1. Microsoft SQL Server Management Studio Express 9.00.2047.00
Microsoft Data Access Components (MDAC) 6.0.6000.16386 (vista_rtm.061101-2205)
Microsoft MSXML 3.0 5.0 6.0
Microsoft Internet Explorer 7.0.6000.16473
Microsoft .NET Framework 2.0.50727.312
Operating System 6.0.6000

2. SQL Server Configuration Manager , Microsoft Corporation , Version: 2005.090.3042.00

all opertaions under administrator account

thanks!

I would use the following list to investigate:

-Make sure that the backup you took is restoreable on any other server than the crashing one.
-If no, make a new backup on the source server including the verify option for checking the database backup after the beackup process.
-If yes, resinatll SQL Server on that machine OR call PSS Support and send them the MiniDump created in the files mentioned.

Jens K. Suessmeyer

http://www.sqlserver2005.de

|||

thanks

I created new backup files as you told me , and test them first in the source machine - work fine

and when try to restore db at the vista machine it throw other error :

TITLE: Microsoft SQL Server Management Studio Express

An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.Express.ConnectionInfo)

ADDITIONAL INFORMATION:

The media family on device 'C:\test.bak' is incorrectly formed. SQL Server cannot process this media family.

RESTORE HEADERONL

this is the same file that was work correctly in the source machine...

I saw other difference:

source machine sql server managment studio express

version: 9.00.3042.00 / OS Windows server 2003 web edition sp2

target (error) machine sql server managment studio express

version: 9.00.2047.00 / OS Vista

I saw couple of articles about vista & sql server and confused..

I try to downloadthe sql server sp1 for vista , but in the installation it's told me that I have already newer version

should I install other thing ? (sp2?) on the vista machine ?

from where , is it already supported ?

thanks

|||I don?t know if the backup files of a higher version are compatible with a lower version of the backup within one version of SQL Server Express but it seems that they changed something in the meta data making it not possible to restore the file. As the update to SP2 is anyway prefered you should do the update and restore the database afterwards which could fix the problem.


Jens K. Suessmeyer

http://www.sqlserver2005.de

Friday, February 10, 2012

Cannot restore databse from file

Hi,

I have Sql server management studio express install on one pc with windows server 2003 os , working ok.

I also installed the same on my vista machine.

I use backup tool to store the back file from the windows server 2003 and to restore it back in the vista.

After connect to the SQLEXPRESS instance in the management studio

I right click the Database folder ->"Restore Database"->To database "xxx" (same name as was in the prev os)

From device->...->backup media - file , Add - choose the file with .back extension -> OK

In this stage there are 2 windows:

"Sql server windows NT has stop working"

And the collecting information for ms to help me..

With 3 files:

C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Report17f38cd5\WER80EE.tmp.version.txt

C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Report17f38cd5\WER80EF.tmp.appcompat.txt

C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Report17f38cd5\WER8C3C.tmp.mdmp

After click cancel , the management studio popup exception window with those details:

TITLE: Microsoft SQL Server Management Studio Express

An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.Express.ConnectionInfo)


ADDITIONAL INFORMATION:

A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - The specified network name is no longer available.) (Microsoft SQL Server, Error: 64)

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


BUTTONS:

OK

Exception details:

===================================

An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.Express.ConnectionInfo)


Program Location:

at Microsoft.SqlServer.Management.Common.ServerConnection.ExecuteWithResults(String sqlCommand)
at Microsoft.SqlServer.Management.Smo.ExecutionManager.ExecuteWithResults(String query)
at Microsoft.SqlServer.Management.Smo.BackupRestoreBase.ExecuteSqlWithResults(Server server, String cmd)
at Microsoft.SqlServer.Management.Smo.Restore.ReadBackupHeader(Server srv)
at Microsoft.SqlServer.Management.SqlManagerUI.SqlRestoreDatabaseGeneral.buttonSelectDevice_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

===================================

A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - The specified network name is no longer available.) (.Net SqlClient Data Provider)


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


Server Name: MY-DEVPC\SQLEXPRESS
Error Number: 64
Severity: 20
State: 0



Program Location:

at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParserStateObject.ReadSniError(TdsParserStateObject stateObj, UInt32 error)
at System.Data.SqlClient.TdsParserStateObject.ReadSni(DbAsyncResult asyncResult, TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParserStateObject.ReadPacket(Int32 bytesExpected)
at System.Data.SqlClient.TdsParserStateObject.ReadBuffer()
at System.Data.SqlClient.TdsParserStateObject.ReadByte()
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlDataReader.ConsumeMetaData()
at System.Data.SqlClient.SqlDataReader.get_MetaData()
at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)
at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method)
at System.Data.SqlClient.SqlCommand.ExecuteDbDataReader(CommandBehavior behavior)
at System.Data.Common.DbCommand.System.Data.IDbCommand.ExecuteReader(CommandBehavior behavior)
at System.Data.Common.DbDataAdapter.FillInternal(DataSet dataset, DataTable[] datatables, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior)
at System.Data.Common.DbDataAdapter.Fill(DataSet dataSet, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior)
at System.Data.Common.DbDataAdapter.Fill(DataSet dataSet)
at Microsoft.SqlServer.Management.Common.ServerConnection.ExecuteWithResults(String sqlCommand)

after this I can see in the SQL server configuration manager that the service of "SQL Server (SQLEXPRESS)" is stopped

I try to play with the protocols for sqlexpress enable and disable some of them , using only tcp etc etc , nothing work.

product version details:

1. Microsoft SQL Server Management Studio Express 9.00.2047.00
Microsoft Data Access Components (MDAC) 6.0.6000.16386 (vista_rtm.061101-2205)
Microsoft MSXML 3.0 5.0 6.0
Microsoft Internet Explorer 7.0.6000.16473
Microsoft .NET Framework 2.0.50727.312
Operating System 6.0.6000

2. SQL Server Configuration Manager , Microsoft Corporation , Version: 2005.090.3042.00

all opertaions under administrator account

thanks!

I would use the following list to investigate:

-Make sure that the backup you took is restoreable on any other server than the crashing one.
-If no, make a new backup on the source server including the verify option for checking the database backup after the beackup process.
-If yes, resinatll SQL Server on that machine OR call PSS Support and send them the MiniDump created in the files mentioned.

Jens K. Suessmeyer

http://www.sqlserver2005.de

|||

thanks

I created new backup files as you told me , and test them first in the source machine - work fine

and when try to restore db at the vista machine it throw other error :

TITLE: Microsoft SQL Server Management Studio Express

An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.Express.ConnectionInfo)

ADDITIONAL INFORMATION:

The media family on device 'C:\test.bak' is incorrectly formed. SQL Server cannot process this media family.

RESTORE HEADERONL

this is the same file that was work correctly in the source machine...

I saw other difference:

source machine sql server managment studio express

version: 9.00.3042.00 / OS Windows server 2003 web edition sp2

target (error) machine sql server managment studio express

version: 9.00.2047.00 / OS Vista

I saw couple of articles about vista & sql server and confused..

I try to downloadthe sql server sp1 for vista , but in the installation it's told me that I have already newer version

should I install other thing ? (sp2?) on the vista machine ?

from where , is it already supported ?

thanks

|||I don?t know if the backup files of a higher version are compatible with a lower version of the backup within one version of SQL Server Express but it seems that they changed something in the meta data making it not possible to restore the file. As the update to SP2 is anyway prefered you should do the update and restore the database afterwards which could fix the problem.


Jens K. Suessmeyer

http://www.sqlserver2005.de