Friday, March 30, 2012
MSDE and Access Project Issue
SAPWD=abc456
instancename=MSDE01
DISABLENETWORKPROTOCOLS=0
SECURITYMODE=SQL
DATADIR="C:\MSDE"
TARGETDIR="C:\MSDE"
I went to services and started MSSQL$MSDE01 and SQLAgent$MSDE01.
I opened up MSACCESS 2003 and created a new project with new data. The SQL Server Database Wizard popped up and I entered (local)MSDE01 for the SQL server and clicked the Use Trusted Connection.
After several seconds, I receive an error message:
Connection failed:
SQLState: '01000'
SQL Server Error: 53
[Microsoft][ODBC SQL Server Driver][DBMSLPCN]ConnectionOpen(Connect()).
Connection failed:
SQLState: '08001'
SQL Server Error: 17
[Microsoft][ODBC SQL Server Driver][DBMSLPCN]SQL Server does not exist or access denied.
I can connect to this instance of MSDE using ASP.NET and the Server Explorer. So I'm pretty sure that I have a good install of MSDE.
Does anyone have a clue as to what I am doing wrong when I try to connect via Access?
Posted using Wimdows.net NntpNews Component -
Post Made from http://www.SqlJunkies.com/newsgroups Our newsgroup engine supports Post Alerts, Ratings, and Searching.
Hi,
Try (local)\MSDE01 instead.
HTH,
Greg Low (MVP)
MSDE Manager SQL Tools
www.whitebearconsulting.com
"SqlJunkies User" <User@.-NOSPAM-SqlJunkies.com> wrote in message
news:uv46MJeIEHA.3968@.TK2MSFTNGP12.phx.gbl...
> I installed MSDE SP3a on my XP Pro laptop using the following options:
> SAPWD=abc456
> instancename=MSDE01
> DISABLENETWORKPROTOCOLS=0
> SECURITYMODE=SQL
> DATADIR="C:\MSDE"
> TARGETDIR="C:\MSDE"
> I went to services and started MSSQL$MSDE01 and SQLAgent$MSDE01.
> I opened up MSACCESS 2003 and created a new project with new data. The
SQL Server Database Wizard popped up and I entered (local)MSDE01 for the SQL
server and clicked the Use Trusted Connection.
> After several seconds, I receive an error message:
> Connection failed:
> SQLState: '01000'
> SQL Server Error: 53
> [Microsoft][ODBC SQL Server Driver][DBMSLPCN]ConnectionOpen(Connect()).
> Connection failed:
> SQLState: '08001'
> SQL Server Error: 17
> [Microsoft][ODBC SQL Server Driver][DBMSLPCN]SQL Server does not exist or
access denied.
> I can connect to this instance of MSDE using ASP.NET and the Server
Explorer. So I'm pretty sure that I have a good install of MSDE.
> Does anyone have a clue as to what I am doing wrong when I try to connect
via Access?
>
> --
> Posted using Wimdows.net NntpNews Component -
> Post Made from http://www.SqlJunkies.com/newsgroups Our newsgroup engine
supports Post Alerts, Ratings, and Searching.
|||or .\MSDE01
HTH,
Greg Low (MVP)
MSDE Manager SQL Tools
www.whitebearconsulting.com
"SqlJunkies User" <User@.-NOSPAM-SqlJunkies.com> wrote in message
news:uv46MJeIEHA.3968@.TK2MSFTNGP12.phx.gbl...
> I installed MSDE SP3a on my XP Pro laptop using the following options:
> SAPWD=abc456
> instancename=MSDE01
> DISABLENETWORKPROTOCOLS=0
> SECURITYMODE=SQL
> DATADIR="C:\MSDE"
> TARGETDIR="C:\MSDE"
> I went to services and started MSSQL$MSDE01 and SQLAgent$MSDE01.
> I opened up MSACCESS 2003 and created a new project with new data. The
SQL Server Database Wizard popped up and I entered (local)MSDE01 for the SQL
server and clicked the Use Trusted Connection.
> After several seconds, I receive an error message:
> Connection failed:
> SQLState: '01000'
> SQL Server Error: 53
> [Microsoft][ODBC SQL Server Driver][DBMSLPCN]ConnectionOpen(Connect()).
> Connection failed:
> SQLState: '08001'
> SQL Server Error: 17
> [Microsoft][ODBC SQL Server Driver][DBMSLPCN]SQL Server does not exist or
access denied.
> I can connect to this instance of MSDE using ASP.NET and the Server
Explorer. So I'm pretty sure that I have a good install of MSDE.
> Does anyone have a clue as to what I am doing wrong when I try to connect
via Access?
>
> --
> Posted using Wimdows.net NntpNews Component -
> Post Made from http://www.SqlJunkies.com/newsgroups Our newsgroup engine
supports Post Alerts, Ratings, and Searching.
Wednesday, March 28, 2012
MSDE 2000A Upgrade to SQL Express SP1 with Merge Replication
Hello,
I have the following scenario. An application using SQL Server 2000 SP3 on the server side and clients using MSDE 2000A (SP3a) on the client machine. Since the client is offline quite often merge replication is used to keep the clients in sync.
Now we try to upgrade to SQL Server 2005 SP1. The publisher and distributor upgrade (on the same box) worked fine and all clients could still synchronize. Fine :-)
Now we try to upgrade the clients to SQL Express SP1. Now the problems start :-(
1) After the upgrade the entry within the Synchronization Manager is gone (we can overcome this by using sp_MSregistersubscription or by manually disable and enable Synchronization manager on the subscription properties)
2) Initial Synchronization (takes a long time but) works fine, if I apply changes to the subscriber or force a reinitialize all following synchronization will fail. With the following messages:
Error messages:
The merge process could not clean up the subscription to 'tstvmw23':'TestBase:'TestBase'. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147200965)
Get help: http://help/MSSQL_REPL-2147200965
New request is not allowed to start because it should come with valid transaction descriptor. (Source: MSSQLServer, Error number: 3989)
Get help: http://help/3989
Remark the test system I use is a nearly empty db (only with full schema and a few lookup tables) with 15MB. The same error occures if I create a new database an subscribe to the same publication.
Please help otherwise I'm forced to step back to MSDE.
Thanks in advance,
Thomas Hotz
Hi,just to make sure you do not want SQL Server Express to the a merge replicant...
http://msdn2.microsoft.com/en-us/library/ms165616.aspx
HTH, Jens K. Suessmeyer.
http://www.sqlserver2005.de|||What this table on the BOL means is that SQL Server Express cannot act as a Distributor/Publisher on a merge replication and the main cause is that it does not have an Agent.
http://technet.microsoft.com/en-us/library/ms143470.aspx
See the topic SQL Server does not include an agent on that reference.
SQL Server Express can act as a subscriber on Merge Replication though. If you have a type of subscription Pull, as the Agent runs on the subscribers you have to use RMO on your code to instantiate an agent or use Windows Synchronization Manager (Start Menu-> Accessories -> Synchronize)
We have SQLE running as subscribers on a pull merge replication topology...sql
MSDE 2000A Upgrade to SQL Express SP1 with Merge Replication
Hello,
I have the following scenario. An application using SQL Server 2000 SP3 on the server side and clients using MSDE 2000A (SP3a) on the client machine. Since the client is offline quite often merge replication is used to keep the clients in sync.
Now we try to upgrade to SQL Server 2005 SP1. The publisher and distributor upgrade (on the same box) worked fine and all clients could still synchronize. Fine :-)
Now we try to upgrade the clients to SQL Express SP1. Now the problems start :-(
1) After the upgrade the entry within the Synchronization Manager is gone (we can overcome this by using sp_MSregistersubscription or by manually disable and enable Synchronization manager on the subscription properties)
2) Initial Synchronization (takes a long time but) works fine, if I apply changes to the subscriber or force a reinitialize all following synchronization will fail. With the following messages:
Error messages:
The merge process could not clean up the subscription to 'tstvmw23':'TestBase:'TestBase'. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147200965)
Get help: http://help/MSSQL_REPL-2147200965
New request is not allowed to start because it should come with valid transaction descriptor. (Source: MSSQLServer, Error number: 3989)
Get help: http://help/3989
Remark the test system I use is a nearly empty db (only with full schema and a few lookup tables) with 15MB. The same error occures if I create a new database an subscribe to the same publication.
Please help otherwise I'm forced to step back to MSDE.
Thanks in advance,
Thomas Hotz
Hi,just to make sure you do not want SQL Server Express to the a merge replicant...
http://msdn2.microsoft.com/en-us/library/ms165616.aspx
HTH, Jens K. Suessmeyer.
http://www.sqlserver2005.de
|||What this table on the BOL means is that SQL Server Express cannot act as a Distributor/Publisher on a merge replication and the main cause is that it does not have an Agent.
http://technet.microsoft.com/en-us/library/ms143470.aspx
See the topic SQL Server does not include an agent on that reference.
SQL Server Express can act as a subscriber on Merge Replication though. If you have a type of subscription Pull, as the Agent runs on the subscribers you have to use RMO on your code to instantiate an agent or use Windows Synchronization Manager (Start Menu-> Accessories -> Synchronize)
We have SQLE running as subscribers on a pull merge replication topology...
MSDE 2000A inner join problems
I am using VB6 and MSDE 2000
I previously used Access 2000 and used the following ado sql to create a
temp table in access
(Invoice table contains Invoice data such as Invoice number, date etc.
Idetail table contains details of the invoice individual items e.g product
code, Invoice Number etc) The link is the Invoice Number field in each table
(Master/Detail)
sql = "SELECT idetail.qty, idetail.prod_code, invoice.inv_date,
idetail.price INTO idetailtemp IN '" & App.path & "\data\tramcarstemp.mdb'
FROM idetail inner join [invoice] on idetail.inv_num = invoice.inv_num where
invoice.inv_date between #" & Format(DT1.Value, "m-d-yyyy") & "# and #" &
Format(DT2.Value, "m-d-yyyy") & "#"
cn.execute sql
This worked fine in Access 2000
I am upgrading to MSDE2000 and using the following code in TSql
Private Sub maketable()
Dim a, fso As New FileSystemObject
Dim x As Integer
Set a = fso.CreateTextFile(App.path & "\sql\BackupTramcars.sql", True)
a.WriteLine ("EXEC sp_dboption 'Tramcars', 'select into/bulkcopy', 'true'")
a.WriteLine ("GO")
a.WriteLine ("USE " & "Tramcars")
a.WriteLine ("SELECT idetail.qty, idetail.prod_code, invoice.inv_date,
idetail.price INTO idetailtemp")
a.WriteLine ("FROM idetail inner join [invoice] on idetail.inv_num =
invoice.inv_num")
a.WriteLine ("where invoice.inv_date between '" &
Format(frmorderhistory.DT1.Value, "m-d-yyyy") & "' and '" &
Format(frmorderhistory.DT2.Value, "m-d-yyyy") & "'")
a.WriteLine ("GO")
a.WriteLine ("EXEC sp_dboption 'Tramcars', 'select into/bulkcopy', 'false'")
a.WriteLine ("GO")
a.Close
Set a = Nothing
End Sub
The table is created but the inserted invoice dates are only ever 1 of 2
dates
Also when I read from the table to graph the data with
sql = "Select inv_date, sum(qty) as amount from [idetailtemp] where
[prod_code] = '" &
frmorderhistory.maingrid.TextMatrix(frmorderhistor y.maingrid.Row, 0) & "'
group by [inv_date]"
rs.Open sql, cn, adOpenDynamic, adLockReadOnly
There are several records in the recordset but calling rs.recordcount = -1,
which didn't happen in Access 2K
Any ideas
Steve
hi Steve,
steve wrote:
> Hi All
> ...
> Private Sub maketable()
> Dim a, fso As New FileSystemObject
> Dim x As Integer
> Set a = fso.CreateTextFile(App.path & "\sql\BackupTramcars.sql", True)
> a.WriteLine ("EXEC sp_dboption 'Tramcars', 'select into/bulkcopy',
> 'true'") a.WriteLine ("GO")
> a.WriteLine ("USE " & "Tramcars")
> a.WriteLine ("SELECT idetail.qty, idetail.prod_code, invoice.inv_date,
> idetail.price INTO idetailtemp")
> a.WriteLine ("FROM idetail inner join [invoice] on idetail.inv_num =
> invoice.inv_num")
> a.WriteLine ("where invoice.inv_date between '" &
> Format(frmorderhistory.DT1.Value, "m-d-yyyy") & "' and '" &
> Format(frmorderhistory.DT2.Value, "m-d-yyyy") & "'")
> a.WriteLine ("GO")
> a.WriteLine ("EXEC sp_dboption 'Tramcars', 'select into/bulkcopy',
> 'false'") a.WriteLine ("GO")
> a.Close
>
> The table is created but the inserted invoice dates are only ever 1
> of 2 dates
please use the ISO format when referencing dates... dates can be confusing,
but if you refer to them in the 'YYYYMMDD' or 'YYYY-MM-DD' format you will
be out of troubles.. please have a look at
http://www.windowsitpro.com/SQLServe...9147/9147.html ,
http://www.karaszi.com/SQLServer/info_datetime.asp for further info..
> Also when I read from the table to graph the data with
> sql = "Select inv_date, sum(qty) as amount from [idetailtemp] where
> [prod_code] = '" &
> frmorderhistory.maingrid.TextMatrix(frmorderhistor y.maingrid.Row, 0)
> & "' group by [inv_date]"
> rs.Open sql, cn, adOpenDynamic, adLockReadOnly
> There are several records in the recordset but calling rs.recordcount
> = -1, which didn't happen in Access 2K
this depends on the MDAC recordset type... the recordcount value will be
available when the recordset has been fully populated, that's to say as soon
as you perform a .MoveLast operation.. (BTW... .Movelast can be time
consuming as all rows must be fetched and transferred)..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Andrea
Thanks. Worked a treat
Steve
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:3k76maFt35b8U1@.individual.net...
> hi Steve,
> steve wrote:
> please use the ISO format when referencing dates... dates can be
> confusing, but if you refer to them in the 'YYYYMMDD' or 'YYYY-MM-DD'
> format you will be out of troubles.. please have a look at
> http://www.windowsitpro.com/SQLServe...9147/9147.html ,
> http://www.karaszi.com/SQLServer/info_datetime.asp for further info..
>
> this depends on the MDAC recordset type... the recordcount value will be
> available when the recordset has been fully populated, that's to say as
> soon as you perform a .MoveLast operation.. (BTW... .Movelast can be time
> consuming as all rows must be fetched and transferred)..
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
Monday, March 26, 2012
MSDE 2000 Replication to SQL Server 2000
i went through the documentation but i was not clear on following, here is the scenario :-
a Central server is having SQL Server 2000
3 Remote Locations :- Each having 4-5 no of computers, connected on a Lan, and on one of the machines MSDE 2000 will be running.
My Questions are :-
1. Can remote locations, update data locally and send changes (say in every one hour) to central server. If yes, then how ?
2. Same way they can receive updates from Central Server on whatever was updated on Centra Server or on the 3 remote locations. If yes, then How ?
any help will be highly appreciable.
Merge replication should be able to do this for you.|||Thanks for your answer.
Kindly note that if in this same scenario, can we do the same thing, if following combinations are used :-
1. SQL Express 2005 on Remote locations & on Central Server SQL Server 2005 is used ?
2. If Sql Express 2005 on Remote Locations & Central Database SQL Server 2000 is used ?
3. If MSDE 2000 on Remote Locations & Central Database SQL Server 2005 is used ?
|||#2 is not supported, this is documented in Books Online. #3 is supported, but you'll get better performance, scalability and functionality if #1 is used.
|||Thanks for reply... sorry for asking again n again...
For # 2 Option, if only features of SQL Server 2000 are used, still it is not possible ?
For #1 option, even i will prefer to use that, my only concern was in documentation they are mentioning that SQL Express server can only act as subscriber, so can it receive updates as well as send local updates, pls cfm ?
|||YOu can access SQL 2005 Books Online at http://msdn2.microsoft.com/en-us/library/ms203721.aspx. You can learn more about replication at http://msdn2.microsoft.com/en-us/library/ms151198.aspx.
A merge subscriber can upload and download changes.
Friday, March 23, 2012
MSDE 2000 Install - setup.ini
So far I have included the following parameters in the setup.ini file -
SAPWD=<my own SA password>
SECURITYMODE=SQL
COLLATION=SQL_Latin1_General_CP1_CI_AS
My next test is to connect to a database on the laptop from my desktop (via my LAN) using SQL Server 2000 Enterprise Manager and/or Query Analyser.
The problem is that although I can 'see' my laptop (ping/My Network Places etc.), I can not see the MSDE installation hense my database on the laptop. The message I get is '[Microsoft]ODBC SQL server driver [DBNETLIB] SQL Server does not exist or access denied'
Have I missed a parameter i.e. do I need to set up a parameter to ensure I can connect to the installation from remote?
Being new to installing MSDE, are there any other parameters I have missed?
Ian
p.s. Anyone know of a simple to follow install instruction set for MSDE 2000 which shows what parameters can be set upSolved the problem myself.
With Service Pack 3, msde has added a new parameter to the install = DISABLENETWORKPROTOCOLS. This parameter is defaulted to 1 which blocks remote access to the database. By adding the parameter with a value of 0 to the setup.ini file I can now connect from remote.
Ian
Originally posted by Ian Grant
I have installed MSDE 2000 on my Windows 2000 laptop using the SP3 setup.exe and associated setup.ini file.
So far I have included the following parameters in the setup.ini file -
SAPWD=<my own SA password>
SECURITYMODE=SQL
COLLATION=SQL_Latin1_General_CP1_CI_AS
My next test is to connect to a database on the laptop from my desktop (via my LAN) using SQL Server 2000 Enterprise Manager and/or Query Analyser.
The problem is that although I can 'see' my laptop (ping/My Network Places etc.), I can not see the MSDE installation hense my database on the laptop. The message I get is '[Microsoft]ODBC SQL server driver [DBNETLIB] SQL Server does not exist or access denied'
Have I missed a parameter i.e. do I need to set up a parameter to ensure I can connect to the installation from remote?
Being new to installing MSDE, are there any other parameters I have missed?
Ian
p.s. Anyone know of a simple to follow install instruction set for MSDE 2000 which shows what parameters can be set up
Wednesday, March 21, 2012
MSDE + Static IP Address ?
1) A central computer with a static IP address exposed to the internet would be used to store a small database.
2) A couple of computers located around the country would access this database through the internet. THe client they would use would be in EXE form, ( a custom built application) , which would use the Static IP as the database server name. Basically eac
h locatoin would have their own software install, and instead of comunicating on their local LAN to the db-server, they would use the static IP to connect to the remote database.
Would the above work? or is there a special requirement for the above that i've missed?
Thanks.
Hi,
You can connect MSDE to the internet and the remote apps should be able to
talk to the MSDE.
just make sure that you enable the required Protocols for the SQL Server
and make sure that the port is available.
Configure Firewall etc.
HTH
Ashish
This posting is provided "AS IS" with no warranties, and confers no rights.
|||Hi, Thanks for the info,
So basically i just configure the internet protocols, and use the IP as my database server "Setting" in my client-exe along with the database name... wow that would be cool.
>Hi,
>You can connect MSDE to the internet and the remote apps should be able to
>talk to the MSDE.
>just make sure that you enable the required Protocols for the SQL Server
>and make sure that the port is available.
>Configure Firewall etc.
|||Hi,
In addition, we sometimes find increasing the connection timeout in the
connectionstring of your application might be necessary in this scenario.
Otherwise, works ok.
I'd strongly suggest moving the MSDE to a high non-standard port (ie 47857)
instead of 1433 and employing some form of port-sniffing detection on the
system it's running on, if it's directly connected.
HTH,
Greg Low (MVP)
MSDE Manager SQL Tools
www.whitebearconsulting.com
"SQL-Warrior" <anonymous@.discussions.microsoft.com> wrote in message
news:9FBD8FAA-1080-482A-B55A-4411792F3AFF@.microsoft.com...
> Hi, Thanks for the info,
> So basically i just configure the internet protocols, and use the IP as my
database server "Setting" in my client-exe along with the database name...
wow that would be cool.[vbcol=seagreen]
>
to
>
>
|||Ok, thanks for the info,
i can't wait to try it out.
|||I forgot to ask, is there any special setup required on the server? Or is it one of those install MSDE and make sure the machine has a static IP and is connected to the internet installs?
|||You need to make sure the network protocols are enabled. You can do this
after installation (and applying any patches, etc.) by running svrnetcn.exe
(ie the server network utility). Use it to both enable tcp and to set it to
a different port.
HTH,
Greg Low (MVP)
MSDE Manager SQL Tools
www.whitebearconsulting.com
"SQL-Warrior" <anonymous@.discussions.microsoft.com> wrote in message
news:D74B7469-B7EF-4EBC-9955-082183E9B464@.microsoft.com...
> I forgot to ask, is there any special setup required on the server? Or is
it one of those install MSDE and make sure the machine has a static IP and
is connected to the internet installs?
|||Ahhh, ok thanks !
this is soo cool.
sql
Monday, March 19, 2012
MSDE -> Express Upgrade problem.
Hello!
I'm trying to upgrade old MSDE instances to SQL Server 2005 Express SP1.
The following command fails:
SQLEXPR.EXE /qb UPGRADE=SQL_Engine INSTANCENAME=XXX ADDLOCAL=Client_Components,Connectivity
because the domain\x user cannot login. We have disabled Windows authentication. Is there a way to supply the SA login instead of a domain user?
Problem no #2:
After upgrading with Windows Authentication turned on, current SQL users cannot login (sa). Is Mixed authentication mode turned off during upgrade? Or what else could be the problem?
Our application is distributed around Europe. We have no control over our customers security settings/logins.
Also, the database contains sensitive data. Giving Windows Administrators access to the database is out of the question.
Kind regards
A
Check in the template.ini file that's in the high-level directory of the install media; the options are explained pretty well in there but in brief you can specify accounts, passwords, and security mode.Saturday, February 25, 2012
msdb marked as suspect
Following error message is displayed whenever i open the Sql Server
Management Studio
Database 'msdb' cannot be opened. It has been marked SUSPECT by recovery.
See the SQL Server errorlog for more information. (.Net SqlClient Data
Provider)
I am using Sql Server 2005 with single instance
-Regards,
Seems you are in for a restore of your msdb database:
http://www.karaszi.com/SQLServer/inf...suspect_db.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Kallu" <Kallu@.discussions.microsoft.com> wrote in message
news:75BDFAB6-C334-475E-B60F-6327C32C4E8D@.microsoft.com...
> Hi All,
> Following error message is displayed whenever i open the Sql Server
> Management Studio
> Database 'msdb' cannot be opened. It has been marked SUSPECT by recovery.
> See the SQL Server errorlog for more information. (.Net SqlClient Data
> Provider)
> I am using Sql Server 2005 with single instance
> -Regards,
>
msdb marked as suspect
Following error message is displayed whenever i open the Sql Server
Management Studio
Database 'msdb' cannot be opened. It has been marked SUSPECT by recovery.
See the SQL Server errorlog for more information. (.Net SqlClient Data
Provider)
I am using Sql Server 2005 with single instance
-Regards,Seems you are in for a restore of your msdb database:
http://www.karaszi.com/SQLServer/info_corrupt_suspect_db.asp
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Kallu" <Kallu@.discussions.microsoft.com> wrote in message
news:75BDFAB6-C334-475E-B60F-6327C32C4E8D@.microsoft.com...
> Hi All,
> Following error message is displayed whenever i open the Sql Server
> Management Studio
> Database 'msdb' cannot be opened. It has been marked SUSPECT by recovery.
> See the SQL Server errorlog for more information. (.Net SqlClient Data
> Provider)
> I am using Sql Server 2005 with single instance
> -Regards,
>
msdb marked as suspect
Following error message is displayed whenever i open the Sql Server
Management Studio
Database 'msdb' cannot be opened. It has been marked SUSPECT by recovery.
See the SQL Server errorlog for more information. (.Net SqlClient Data
Provider)
I am using Sql Server 2005 with single instance
-Regards,Seems you are in for a restore of your msdb database:
http://www.karaszi.com/SQLServer/in..._suspect_db.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Kallu" <Kallu@.discussions.microsoft.com> wrote in message
news:75BDFAB6-C334-475E-B60F-6327C32C4E8D@.microsoft.com...
> Hi All,
> Following error message is displayed whenever i open the Sql Server
> Management Studio
> Database 'msdb' cannot be opened. It has been marked SUSPECT by recovery.
> See the SQL Server errorlog for more information. (.Net SqlClient Data
> Provider)
> I am using Sql Server 2005 with single instance
> -Regards,
>
Monday, February 20, 2012
MSDB database restore
following message:
V-79-57344-33938 -
An error occurred on a query to database msdb.
V-79-57344-33938 - The backup of the system database on device
msdb_00__60f69b04_bfad_4b17_a284_4047d59b9e28_ cannot be restored because it
was created by a different version of the server (134218407) than this server
(134218262).
I understand what the message is saying but how do I find out what SPs and
hotfixes I need to install in order to get the target server to the correct
version? Is there a table or a document that will tell me what needs to be
installed on the target server?
ThanksYou can restore to a new version so as long as your up to the latest version
you should be OK. This generally isn't an issue when moving between service
pack and hot fixes so my guess is that you are trying to restore to a
pre-released version of SQL Server. Looking at the SELECT @.@.version output
should help determine what you are running.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Paul Oren" <PaulOren@.discussions.microsoft.com> wrote in message
news:0C01112B-319F-4B14-8A49-F1EBAB72BF6A@.microsoft.com...
>I am trying to restore the msdb to another server. When I do, I get the
> following message:
> V-79-57344-33938 -
> An error occurred on a query to database msdb.
> V-79-57344-33938 - The backup of the system database on device
> msdb_00__60f69b04_bfad_4b17_a284_4047d59b9e28_ cannot be restored because
> it
> was created by a different version of the server (134218407) than this
> server
> (134218262).
> I understand what the message is saying but how do I find out what SPs and
> hotfixes I need to install in order to get the target server to the
> correct
> version? Is there a table or a document that will tell me what needs to
> be
> installed on the target server?
> Thanks
>|||The backup I am restoring from is on tape so I can not get it restored in
order to run the the select statement. All my databases were loaded from MS
CDs so a pre-released version of SQL server should not be an issue.
"Roger Wolter[MSFT]" wrote:
> You can restore to a new version so as long as your up to the latest version
> you should be OK. This generally isn't an issue when moving between service
> pack and hot fixes so my guess is that you are trying to restore to a
> pre-released version of SQL Server. Looking at the SELECT @.@.version output
> should help determine what you are running.
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "Paul Oren" <PaulOren@.discussions.microsoft.com> wrote in message
> news:0C01112B-319F-4B14-8A49-F1EBAB72BF6A@.microsoft.com...
> >I am trying to restore the msdb to another server. When I do, I get the
> > following message:
> >
> > V-79-57344-33938 -
> > An error occurred on a query to database msdb.
> > V-79-57344-33938 - The backup of the system database on device
> > msdb_00__60f69b04_bfad_4b17_a284_4047d59b9e28_ cannot be restored because
> > it
> > was created by a different version of the server (134218407) than this
> > server
> > (134218262).
> >
> > I understand what the message is saying but how do I find out what SPs and
> > hotfixes I need to install in order to get the target server to the
> > correct
> > version? Is there a table or a document that will tell me what needs to
> > be
> > installed on the target server?
> >
> > Thanks
> >
>|||So apply SQL 2005 SP2 and you will assuredly be more recent that the tape
backup.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Paul Oren" <PaulOren@.discussions.microsoft.com> wrote in message
news:339C5DF0-6C3A-4FDA-B0AF-F65D59CB7349@.microsoft.com...
> The backup I am restoring from is on tape so I can not get it restored in
> order to run the the select statement. All my databases were loaded from
> MS
> CDs so a pre-released version of SQL server should not be an issue.
> "Roger Wolter[MSFT]" wrote:
>> You can restore to a new version so as long as your up to the latest
>> version
>> you should be OK. This generally isn't an issue when moving between
>> service
>> pack and hot fixes so my guess is that you are trying to restore to a
>> pre-released version of SQL Server. Looking at the SELECT @.@.version
>> output
>> should help determine what you are running.
>> --
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>> Use of included script samples are subject to the terms specified at
>> http://www.microsoft.com/info/cpyright.htm
>> "Paul Oren" <PaulOren@.discussions.microsoft.com> wrote in message
>> news:0C01112B-319F-4B14-8A49-F1EBAB72BF6A@.microsoft.com...
>> >I am trying to restore the msdb to another server. When I do, I get the
>> > following message:
>> >
>> > V-79-57344-33938 -
>> > An error occurred on a query to database msdb.
>> > V-79-57344-33938 - The backup of the system database on device
>> > msdb_00__60f69b04_bfad_4b17_a284_4047d59b9e28_ cannot be restored
>> > because
>> > it
>> > was created by a different version of the server (134218407) than this
>> > server
>> > (134218262).
>> >
>> > I understand what the message is saying but how do I find out what SPs
>> > and
>> > hotfixes I need to install in order to get the target server to the
>> > correct
>> > version? Is there a table or a document that will tell me what needs
>> > to
>> > be
>> > installed on the target server?
>> >
>> > Thanks
>> >|||We are running SQL 2000 not SQL 2005.
"Roger Wolter[MSFT]" wrote:
> So apply SQL 2005 SP2 and you will assuredly be more recent that the tape
> backup.
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "Paul Oren" <PaulOren@.discussions.microsoft.com> wrote in message
> news:339C5DF0-6C3A-4FDA-B0AF-F65D59CB7349@.microsoft.com...
> > The backup I am restoring from is on tape so I can not get it restored in
> > order to run the the select statement. All my databases were loaded from
> > MS
> > CDs so a pre-released version of SQL server should not be an issue.
> >
> > "Roger Wolter[MSFT]" wrote:
> >
> >> You can restore to a new version so as long as your up to the latest
> >> version
> >> you should be OK. This generally isn't an issue when moving between
> >> service
> >> pack and hot fixes so my guess is that you are trying to restore to a
> >> pre-released version of SQL Server. Looking at the SELECT @.@.version
> >> output
> >> should help determine what you are running.
> >>
> >> --
> >> This posting is provided "AS IS" with no warranties, and confers no
> >> rights.
> >> Use of included script samples are subject to the terms specified at
> >> http://www.microsoft.com/info/cpyright.htm
> >>
> >> "Paul Oren" <PaulOren@.discussions.microsoft.com> wrote in message
> >> news:0C01112B-319F-4B14-8A49-F1EBAB72BF6A@.microsoft.com...
> >> >I am trying to restore the msdb to another server. When I do, I get the
> >> > following message:
> >> >
> >> > V-79-57344-33938 -
> >> > An error occurred on a query to database msdb.
> >> > V-79-57344-33938 - The backup of the system database on device
> >> > msdb_00__60f69b04_bfad_4b17_a284_4047d59b9e28_ cannot be restored
> >> > because
> >> > it
> >> > was created by a different version of the server (134218407) than this
> >> > server
> >> > (134218262).
> >> >
> >> > I understand what the message is saying but how do I find out what SPs
> >> > and
> >> > hotfixes I need to install in order to get the target server to the
> >> > correct
> >> > version? Is there a table or a document that will tell me what needs
> >> > to
> >> > be
> >> > installed on the target server?
> >> >
> >> > Thanks
> >> >
> >>
>
MSDB Backup Fails on SQL Server 7.0
SQL Server. I have it scheduled to run once a week and when I check
the event viewer I see the following:
SQL Server Scheduled Job 'msdb backup'
(0x1DA8D66C8D076D4D973B1AF97C122CA7) - Status: Failed - Invoked on:
8/13/2006 12:00:00 AM - Message: The job failed. The Job was invoked
by Schedule 4209 (Schedule 1). The last step to run was step 1 (Step
1).
Event ID: 208
The script I'm using for my backup is as follows:
BACKUP DATABASE [msdb] TO [H:\SQLServerBackUpNBR] WITH NOINIT ,
NOUNLOAD , NAME = N'msdb backup', SKIP , STATS = 10, NOFORMAT
DECLARE @.i INT
select @.i = position from msdb..backupset where database_name='msdb'and
type!='F' and backup_set_id=(select max(backup_set_id) from
msdb..backupset where database_name='msdb')
RESTORE VERIFYONLY FROM [H:\SQLServerBackUpNBR] WITH FILE = @.iCan you post the Error / message from the step 1: of this job. That
probability gives more info. regarding the failure.
-Saravanan
"Creative" <GraberJ@.gmail.com> wrote in message
news:1155651035.260790.231840@.i42g2000cwa.googlegroups.com...
> I'm having the following problem with the backup I have running on our
> SQL Server. I have it scheduled to run once a week and when I check
> the event viewer I see the following:
> SQL Server Scheduled Job 'msdb backup'
> (0x1DA8D66C8D076D4D973B1AF97C122CA7) - Status: Failed - Invoked on:
> 8/13/2006 12:00:00 AM - Message: The job failed. The Job was invoked
> by Schedule 4209 (Schedule 1). The last step to run was step 1 (Step
> 1).
> Event ID: 208
> The script I'm using for my backup is as follows:
> BACKUP DATABASE [msdb] TO [H:\SQLServerBackUpNBR] WITH NOINIT ,
> NOUNLOAD , NAME = N'msdb backup', SKIP , STATS = 10, NOFORMAT
> DECLARE @.i INT
> select @.i = position from msdb..backupset where database_name='msdb'and
> type!='F' and backup_set_id=(select max(backup_set_id) from
> msdb..backupset where database_name='msdb')
> RESTORE VERIFYONLY FROM [H:\SQLServerBackUpNBR] WITH FILE = @.i
>|||Are you referring to within SQL Server? Sorry I'm a little new at
troubleshooting SQL Server and I'm not sure where the error message is
you're looking for. All I can find is the one in the Event Viewer that
I posted below and the other is when I view Job History I see "The job
failed. The Job was invoked by Schedule 4209 (Schedule 1). The last
step to run was step 1 (Step 1)." which tells me nothing.
If this isn't what you wanted please tell me where to find what you are
referring to.
Thanks
Saravanan Palanivelu wrote:
> Can you post the Error / message from the step 1: of this job. That
> probability gives more info. regarding the failure.
>
> -Saravanan
>
> "Creative" <GraberJ@.gmail.com> wrote in message
> news:1155651035.260790.231840@.i42g2000cwa.googlegroups.com...
> > I'm having the following problem with the backup I have running on our
> > SQL Server. I have it scheduled to run once a week and when I check
> > the event viewer I see the following:
> >
> > SQL Server Scheduled Job 'msdb backup'
> > (0x1DA8D66C8D076D4D973B1AF97C122CA7) - Status: Failed - Invoked on:
> > 8/13/2006 12:00:00 AM - Message: The job failed. The Job was invoked
> > by Schedule 4209 (Schedule 1). The last step to run was step 1 (Step
> > 1).
> >
> > Event ID: 208
> >
> > The script I'm using for my backup is as follows:
> >
> > BACKUP DATABASE [msdb] TO [H:\SQLServerBackUpNBR] WITH NOINIT ,
> > NOUNLOAD , NAME = N'msdb backup', SKIP , STATS = 10, NOFORMAT
> > DECLARE @.i INT
> > select @.i = position from msdb..backupset where database_name='msdb'and
> > type!='F' and backup_set_id=(select max(backup_set_id) from
> > msdb..backupset where database_name='msdb')
> > RESTORE VERIFYONLY FROM [H:\SQLServerBackUpNBR] WITH FILE = @.i
> >|||Ok here is the error message from the Job History File. Any
suggestions would be appreciated.
No entry in sysdevices for backup device 'H:\SQLServerBackUpNBR'.
Update sysdevices and rerun statement. [SQLSTATE 42000] (Error 3206)
Backup or restore operation terminating abnormally. [SQLSTATE 42000]
(Error 3013) Associated statement is not prepared [SQLSTATE HY007]
(Error 0) No entry in sysdevices for backup device
'H:\SQLServerBackUpNBR'. Update sysdevices and rerun statement.
[SQLSTATE 42000] (Error 3206) Backup or restore operation terminating
abnormally. [SQLSTATE 42000] (Error 3013). The step failed.
Creative wrote:
> Are you referring to within SQL Server? Sorry I'm a little new at
> troubleshooting SQL Server and I'm not sure where the error message is
> you're looking for. All I can find is the one in the Event Viewer that
> I posted below and the other is when I view Job History I see "The job
> failed. The Job was invoked by Schedule 4209 (Schedule 1). The last
> step to run was step 1 (Step 1)." which tells me nothing.
> If this isn't what you wanted please tell me where to find what you are
> referring to.
> Thanks
>
> Saravanan Palanivelu wrote:
> > Can you post the Error / message from the step 1: of this job. That
> > probability gives more info. regarding the failure.
> >
> >
> >
> > -Saravanan
> >
> >
> >
> > "Creative" <GraberJ@.gmail.com> wrote in message
> > news:1155651035.260790.231840@.i42g2000cwa.googlegroups.com...
> > > I'm having the following problem with the backup I have running on our
> > > SQL Server. I have it scheduled to run once a week and when I check
> > > the event viewer I see the following:
> > >
> > > SQL Server Scheduled Job 'msdb backup'
> > > (0x1DA8D66C8D076D4D973B1AF97C122CA7) - Status: Failed - Invoked on:
> > > 8/13/2006 12:00:00 AM - Message: The job failed. The Job was invoked
> > > by Schedule 4209 (Schedule 1). The last step to run was step 1 (Step
> > > 1).
> > >
> > > Event ID: 208
> > >
> > > The script I'm using for my backup is as follows:
> > >
> > > BACKUP DATABASE [msdb] TO [H:\SQLServerBackUpNBR] WITH NOINIT ,
> > > NOUNLOAD , NAME = N'msdb backup', SKIP , STATS = 10, NOFORMAT
> > > DECLARE @.i INT
> > > select @.i = position from msdb..backupset where database_name='msdb'and
> > > type!='F' and backup_set_id=(select max(backup_set_id) from
> > > msdb..backupset where database_name='msdb')
> > > RESTORE VERIFYONLY FROM [H:\SQLServerBackUpNBR] WITH FILE = @.i
> > >
MSDB Backup Fails on SQL Server 7.0
SQL Server. I have it scheduled to run once a week and when I check
the event viewer I see the following:
SQL Server Scheduled Job 'msdb backup'
(0x1DA8D66C8D076D4D973B1AF97C122CA7) - Status: Failed - Invoked on:
8/13/2006 12:00:00 AM - Message: The job failed. The Job was invoked
by Schedule 4209 (Schedule 1). The last step to run was step 1 (Step
1).
Event ID: 208
The script I'm using for my backup is as follows:
BACKUP DATABASE [msdb] TO [H:\SQLServerBackUpNBR] WITH NOINIT ,
NOUNLOAD , NAME = N'msdb backup', SKIP , STATS = 10, NOFORMAT
DECLARE @.i INT
select @.i = position from msdb..backupset where database_name='msdb'and
type!='F' and backup_set_id=(select max(backup_set_id) from
msdb..backupset where database_name='msdb')
RESTORE VERIFYONLY FROM [H:\SQLServerBackUpNBR] WITH FILE = @.iCan you post the Error / message from the step 1: of this job. That
probability gives more info. regarding the failure.
-Saravanan
"Creative" <GraberJ@.gmail.com> wrote in message
news:1155651035.260790.231840@.i42g2000cwa.googlegroups.com...
> I'm having the following problem with the backup I have running on our
> SQL Server. I have it scheduled to run once a week and when I check
> the event viewer I see the following:
> SQL Server Scheduled Job 'msdb backup'
> (0x1DA8D66C8D076D4D973B1AF97C122CA7) - Status: Failed - Invoked on:
> 8/13/2006 12:00:00 AM - Message: The job failed. The Job was invoked
> by Schedule 4209 (Schedule 1). The last step to run was step 1 (Step
> 1).
> Event ID: 208
> The script I'm using for my backup is as follows:
> BACKUP DATABASE [msdb] TO [H:\SQLServerBackUpNBR] WITH NOINIT ,
> NOUNLOAD , NAME = N'msdb backup', SKIP , STATS = 10, NOFORMAT
> DECLARE @.i INT
> select @.i = position from msdb..backupset where database_name='msdb'and
> type!='F' and backup_set_id=(select max(backup_set_id) from
> msdb..backupset where database_name='msdb')
> RESTORE VERIFYONLY FROM [H:\SQLServerBackUpNBR] WITH FILE = @.i
>|||Are you referring to within SQL Server? Sorry I'm a little new at
troubleshooting SQL Server and I'm not sure where the error message is
you're looking for. All I can find is the one in the Event Viewer that
I posted below and the other is when I view Job History I see "The job
failed. The Job was invoked by Schedule 4209 (Schedule 1). The last
step to run was step 1 (Step 1)." which tells me nothing.
If this isn't what you wanted please tell me where to find what you are
referring to.
Thanks
Saravanan Palanivelu wrote:[vbcol=seagreen]
> Can you post the Error / message from the step 1: of this job. That
> probability gives more info. regarding the failure.
>
> -Saravanan
>
> "Creative" <GraberJ@.gmail.com> wrote in message
> news:1155651035.260790.231840@.i42g2000cwa.googlegroups.com...|||Ok here is the error message from the Job History File. Any
suggestions would be appreciated.
No entry in sysdevices for backup device 'H:\SQLServerBackUpNBR'.
Update sysdevices and rerun statement. [SQLSTATE 42000] (Error 3206)
Backup or restore operation terminating abnormally. [SQLSTATE 42000]
(Error 3013) Associated statement is not prepared [SQLSTATE HY007]
(Error 0) No entry in sysdevices for backup device
'H:\SQLServerBackUpNBR'. Update sysdevices and rerun statement.
[SQLSTATE 42000] (Error 3206) Backup or restore operation terminating
abnormally. [SQLSTATE 42000] (Error 3013). The step failed.
Creative wrote:[vbcol=seagreen]
> Are you referring to within SQL Server? Sorry I'm a little new at
> troubleshooting SQL Server and I'm not sure where the error message is
> you're looking for. All I can find is the one in the Event Viewer that
> I posted below and the other is when I view Job History I see "The job
> failed. The Job was invoked by Schedule 4209 (Schedule 1). The last
> step to run was step 1 (Step 1)." which tells me nothing.
> If this isn't what you wanted please tell me where to find what you are
> referring to.
> Thanks
>
> Saravanan Palanivelu wrote: