I set up MSDE that came with VS.NET and, using the Server Explorer, created a database called 'pubs' on my server. The MSSQLServer icon is lit up in the System Tray and has been started. When I created 'pubs', I was prompted whether I wanted to use NT Integrated Security or SQL Server Authentication. I was forced to choose the NT option because any login name that I used, including my administrator account, the 'aspnet_wp account', 'SQLDebugger' and 'sa'. Every time I tried to use the SQL Server Auth. option, I would get the following error prompt:
ADO Error: '
Login failed for user 'whateverItried'. Reason: Not associated with a trusted SQL Server connection.
When running the following:
Dim myConnection As SqlConnection = New SqlConnection("server=(local);database=pubs;uid=sa;pwd=")
it would result in this error message:
Index #0
Error: System.Data.SqlClient.SqlError: SQL Server does not exist or access denied.
I also tried using 'localhost' and <my-computername>\<my-servername> for the server. For my database name, I tried both pubs and dbo.pubs. I also tried every username I could think of.
No luck.
Here's the funny thing: I was able to create a View on the database that did exactly what I was trying to do in code, so the DB is working.
If anyone has sucessfully ran the first example program in Chapter 16 of Beginning VB.NET 2nd edition, please respond. That's where I got this example.
Thanks for any help!
JasonWhat is the authentication mode used to connect?
Refer to books online for Troubleshooting the Transact-SQL Debugger topic.|||Originally posted by Satya
What is the authentication mode used to connect?
Refer to books online for Troubleshooting the Transact-SQL Debugger topic.
I'm not sure what you are asking. Remember that I'm using MSDE and I don't go through a lot of the setup that MS SQL uses.
I was forced to use the NT Integrated Security, since no usernames or password combinations that I knew would work for the SQL option, if that's what you mean.|||True, update the SQL Server Authentication mode back to SQL Server Authentification as referred in this KBA (http://support.microsoft.com/default.aspx?scid=kb;EN-US;285097).|||I have only one icon running in my system tray and it is set to SQL Server, not SQL Server Agent.
Do I need both running? If so, how can I get an instance of Agent to run as well as the server, as suggested in the KBA?
By the way, thanks for your response!
Jason|||Also, what username do I use? 'SA'?
Jason
Originally posted by jtimms
I have only one icon running in my system tray and it is set to SQL Server, not SQL Server Agent.
Do I need both running? If so, how can I get an instance of Agent to run as well as the server, as suggested in the KBA?
By the way, thanks for your response!
Jason|||We have the same issue. If you also have Enterprise Manager installed on the same machine, use it to be sure TCP/IP is an enabled protocol. We did that and were able to connect.
The 64 dollar question is how you do this if you DON'T have Enterprise manager. Anyone know how to do it programatically?
Jim M.
Orrtax Software|||Of course you can!
Search for this file:
svrnetcn.exe
usually in:
"C:\Program Files\Microsoft SQL Server\80\Tools\Binn\svrnetcn.exe"
which is the Server Network Configuration|||Manowar...thank you! I had the same problem as above, and it turned out that my server had not had TCP/IP enabled! Thank you so much!|||hi manomar - thanks a lot for your entry to this forum. i have had exactly the same problem and thru your entries - now it works!
regards,
Originally posted by manowar
Of course you can!
Search for this file:
svrnetcn.exe
usually in:
"C:\Program Files\Microsoft SQL Server\80\Tools\Binn\svrnetcn.exe"
which is the Server Network Configuration|||MSDE usually installs as a named instance, rather than the default instance (this way no two MSDE installs can interfere with each other...theoretically). Check in Administrative tools->services, and check the name of the MSSQL service. If it is MSSQLService, then it is amazingly the default instance. If it is MSSQL$blah, then you have a named instance. In order to address a named instance, you need to specify the name of the server, and the name of the instance as
server=servername\blah
You can also use IP addresses:
10.10.10.10\blah
Not sure if this works:
(local)\blah
Note that while the service is named with a '$', and all folders related to the instance are named with a '$', the service is addressed with '\'. Intuitive, right?|||I have another strange problem:
When I use SVRNETCN or click on the properties in enterprise manager, I see that TCP/IP is enabled for my msde Instance.
But when I look in the error.log of my instance, I see only the entry:
SQL server listening on Named Pipes
There is no entry that the server is listening on TCP/IP and I still get the error message "SQL Server does not exist or access denied" when I try to connect to my database over the network.
So I think my server is still not listening on TCP/IP.
Has anyone a workaround for this problem?
Thanks in advance
Showing posts with label created. Show all posts
Showing posts with label created. Show all posts
Friday, March 30, 2012
Wednesday, March 28, 2012
MSDE 2000 SP4 Merge Modules
I have a MSDE 2000 InstallShield install package that I've created using the
merge modules. I downloaded the SP4 of the desktop engine from the microsoft
site. When downloaded and extracted, there is a folder on my machine
\MSDE\MSM which has all of the merge modules. I've noticed that the SP4
release has 3 new mm's: msxmlsql32.msm, msxmlsqlr32.msm, and qfepatch.msm.
In the InstallShield DevStudio 9.01 IDE, I check the 3 new mm's. When I go
and build I receive the following error: "Error retrieving dependency
MSXMLSQL1033.996A3FBA_B9BC_4189_9DB1_2B3C86B526BC: 1033 of C:\Program
Files\InstallShield\DevStudio 9\Modules\i386\MSXMLSQL32.MSM". Anyone know
why I'm getting this error?
Thanks.
Joanne
hi Joanne
jbayog wrote:
> I have a MSDE 2000 InstallShield install package that I've created
> using the merge modules. I downloaded the SP4 of the desktop engine
> from the microsoft site. When downloaded and extracted, there is a
> folder on my machine \MSDE\MSM which has all of the merge modules.
> I've noticed that the SP4 release has 3 new mm's: msxmlsql32.msm,
> msxmlsqlr32.msm, and qfepatch.msm. In the InstallShield DevStudio
> 9.01 IDE, I check the 3 new mm's. When I go and build I receive the
> following error: "Error retrieving dependency
> MSXMLSQL1033.996A3FBA_B9BC_4189_9DB1_2B3C86B526BC: 1033 of C:\Program
> Files\InstallShield\DevStudio 9\Modules\i386\MSXMLSQL32.MSM". Anyone
> know why I'm getting this error?
no idea, never used MSDE merge modules, always installed using the setup.exe
boostrap installer.... but have you tried modifying the order of
installation?
http://msdn.microsoft.com/library/de...stsql_8yeq.asp
has not been updated (as BOL in general) at sp4 level, so no additional info
about those new merge modules seems available..
BTW, the MSDE readme file, at point 4.2 MSDE 2000 SP4 File location
specifies:
"Note Merge modules are not supported for new installations. They are
provided in SP4 for servicing instances of MSDE 2000 that were previously
installed using merge modules."
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
|||I don't know much about MSDE and am just doing some research on it as of
this week.
However, I cam across this link yesterday which might be useful:
http://www.microsoft.com/sql/downloads/2000/sp4.asp
Here is an extract from the site:
"Users who have an existing instance of MSDE 2000 must know how their
instance of MSDE 2000 was installed to know how to update it. In particular,
you must know the original package name for your instance of MSDE 2000. To
determine the original package name, see the article How To Identify Which
MSI File Was Used for an Existing MSDE Installation in the Microsoft
Knowledge Base."
"jbayog" <jbayog@.discussions.microsoft.com> wrote in message
news:8D058312-1747-4A51-A100-FE79DC32C086@.microsoft.com...
>I have a MSDE 2000 InstallShield install package that I've created using
>the
> merge modules. I downloaded the SP4 of the desktop engine from the
> microsoft
> site. When downloaded and extracted, there is a folder on my machine
> \MSDE\MSM which has all of the merge modules. I've noticed that the SP4
> release has 3 new mm's: msxmlsql32.msm, msxmlsqlr32.msm, and
> qfepatch.msm.
> In the InstallShield DevStudio 9.01 IDE, I check the 3 new mm's. When I
> go
> and build I receive the following error: "Error retrieving dependency
> MSXMLSQL1033.996A3FBA_B9BC_4189_9DB1_2B3C86B526BC: 1033 of C:\Program
> Files\InstallShield\DevStudio 9\Modules\i386\MSXMLSQL32.MSM". Anyone know
> why I'm getting this error?
> Thanks.
> Joanne
|||Thanks so much for your help. This an existing MSDE 2000 InstallShield
install package and we have a client who wants to upgrade to SP4 so that is
why I'm trying to build an upgrade for them. I'd like to get rid of using
the MSDE 2000 merge modules per Microsoft's comment. I got it to build by
editing the msxmlsql32.msm and the msxmlsqlr32.msm using the Orca tool. I
think there is a problem with the rows in the ModuleDependency table. I
guess I have the option of building it without these two mm's as our database
application doesn't use xml. I'm a little apprehensive of doing this only
because there is no documentation on these new mm's. I might post to
InstallShield also. Again thanks.
Joanne
Joanne
"Andrea Montanari" wrote:
> hi Joanne
> jbayog wrote:
> no idea, never used MSDE merge modules, always installed using the setup.exe
> boostrap installer.... but have you tried modifying the order of
> installation?
> http://msdn.microsoft.com/library/de...stsql_8yeq.asp
> has not been updated (as BOL in general) at sp4 level, so no additional info
> about those new merge modules seems available..
> BTW, the MSDE readme file, at point 4.2 MSDE 2000 SP4 File location
> specifies:
> "Note Merge modules are not supported for new installations. They are
> provided in SP4 for servicing instances of MSDE 2000 that were previously
> installed using merge modules."
> --
> 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
>
>
merge modules. I downloaded the SP4 of the desktop engine from the microsoft
site. When downloaded and extracted, there is a folder on my machine
\MSDE\MSM which has all of the merge modules. I've noticed that the SP4
release has 3 new mm's: msxmlsql32.msm, msxmlsqlr32.msm, and qfepatch.msm.
In the InstallShield DevStudio 9.01 IDE, I check the 3 new mm's. When I go
and build I receive the following error: "Error retrieving dependency
MSXMLSQL1033.996A3FBA_B9BC_4189_9DB1_2B3C86B526BC: 1033 of C:\Program
Files\InstallShield\DevStudio 9\Modules\i386\MSXMLSQL32.MSM". Anyone know
why I'm getting this error?
Thanks.
Joanne
hi Joanne
jbayog wrote:
> I have a MSDE 2000 InstallShield install package that I've created
> using the merge modules. I downloaded the SP4 of the desktop engine
> from the microsoft site. When downloaded and extracted, there is a
> folder on my machine \MSDE\MSM which has all of the merge modules.
> I've noticed that the SP4 release has 3 new mm's: msxmlsql32.msm,
> msxmlsqlr32.msm, and qfepatch.msm. In the InstallShield DevStudio
> 9.01 IDE, I check the 3 new mm's. When I go and build I receive the
> following error: "Error retrieving dependency
> MSXMLSQL1033.996A3FBA_B9BC_4189_9DB1_2B3C86B526BC: 1033 of C:\Program
> Files\InstallShield\DevStudio 9\Modules\i386\MSXMLSQL32.MSM". Anyone
> know why I'm getting this error?
no idea, never used MSDE merge modules, always installed using the setup.exe
boostrap installer.... but have you tried modifying the order of
installation?
http://msdn.microsoft.com/library/de...stsql_8yeq.asp
has not been updated (as BOL in general) at sp4 level, so no additional info
about those new merge modules seems available..
BTW, the MSDE readme file, at point 4.2 MSDE 2000 SP4 File location
specifies:
"Note Merge modules are not supported for new installations. They are
provided in SP4 for servicing instances of MSDE 2000 that were previously
installed using merge modules."
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
|||I don't know much about MSDE and am just doing some research on it as of
this week.
However, I cam across this link yesterday which might be useful:
http://www.microsoft.com/sql/downloads/2000/sp4.asp
Here is an extract from the site:
"Users who have an existing instance of MSDE 2000 must know how their
instance of MSDE 2000 was installed to know how to update it. In particular,
you must know the original package name for your instance of MSDE 2000. To
determine the original package name, see the article How To Identify Which
MSI File Was Used for an Existing MSDE Installation in the Microsoft
Knowledge Base."
"jbayog" <jbayog@.discussions.microsoft.com> wrote in message
news:8D058312-1747-4A51-A100-FE79DC32C086@.microsoft.com...
>I have a MSDE 2000 InstallShield install package that I've created using
>the
> merge modules. I downloaded the SP4 of the desktop engine from the
> microsoft
> site. When downloaded and extracted, there is a folder on my machine
> \MSDE\MSM which has all of the merge modules. I've noticed that the SP4
> release has 3 new mm's: msxmlsql32.msm, msxmlsqlr32.msm, and
> qfepatch.msm.
> In the InstallShield DevStudio 9.01 IDE, I check the 3 new mm's. When I
> go
> and build I receive the following error: "Error retrieving dependency
> MSXMLSQL1033.996A3FBA_B9BC_4189_9DB1_2B3C86B526BC: 1033 of C:\Program
> Files\InstallShield\DevStudio 9\Modules\i386\MSXMLSQL32.MSM". Anyone know
> why I'm getting this error?
> Thanks.
> Joanne
|||Thanks so much for your help. This an existing MSDE 2000 InstallShield
install package and we have a client who wants to upgrade to SP4 so that is
why I'm trying to build an upgrade for them. I'd like to get rid of using
the MSDE 2000 merge modules per Microsoft's comment. I got it to build by
editing the msxmlsql32.msm and the msxmlsqlr32.msm using the Orca tool. I
think there is a problem with the rows in the ModuleDependency table. I
guess I have the option of building it without these two mm's as our database
application doesn't use xml. I'm a little apprehensive of doing this only
because there is no documentation on these new mm's. I might post to
InstallShield also. Again thanks.
Joanne
Joanne
"Andrea Montanari" wrote:
> hi Joanne
> jbayog wrote:
> no idea, never used MSDE merge modules, always installed using the setup.exe
> boostrap installer.... but have you tried modifying the order of
> installation?
> http://msdn.microsoft.com/library/de...stsql_8yeq.asp
> has not been updated (as BOL in general) at sp4 level, so no additional info
> about those new merge modules seems available..
> BTW, the MSDE readme file, at point 4.2 MSDE 2000 SP4 File location
> specifies:
> "Note Merge modules are not supported for new installations. They are
> provided in SP4 for servicing instances of MSDE 2000 that were previously
> installed using merge modules."
> --
> 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 problems with linked server
I have set up several servers with MSDE 2000 sp4, have created tables in
these databases, can access, read, write data to the database through win sql
and asp. I have set up a linked server to an oracle database and created a
linkedsrvlogin. I can select data from my oracle database throught SQL using
the linked server. All of my servers are working fine except one. Onne
particular server is taking an extrememly long time to retrive certain data.
For example, I have one server that can get 31000 rows from my linked server
in 14 seconds, using anohter server, it takes almost 3 mins to get back 773
rows from the same table.
Any ideas? Its driving me crazy!!!
Hi Lloyd
Have you tried adding a host file entry to the oracle server on the machine
which is slower than the others, it's a stab in the dark but your one machine
could be talking longer to resolve the name of the oracle db.
Regards
charl
http://www.sqlserver.co.za
"Lloyd Harrison" wrote:
> I have set up several servers with MSDE 2000 sp4, have created tables in
> these databases, can access, read, write data to the database through win sql
> and asp. I have set up a linked server to an oracle database and created a
> linkedsrvlogin. I can select data from my oracle database throught SQL using
> the linked server. All of my servers are working fine except one. Onne
> particular server is taking an extrememly long time to retrive certain data.
> For example, I have one server that can get 31000 rows from my linked server
> in 14 seconds, using anohter server, it takes almost 3 mins to get back 773
> rows from the same table.
> Any ideas? Its driving me crazy!!!
these databases, can access, read, write data to the database through win sql
and asp. I have set up a linked server to an oracle database and created a
linkedsrvlogin. I can select data from my oracle database throught SQL using
the linked server. All of my servers are working fine except one. Onne
particular server is taking an extrememly long time to retrive certain data.
For example, I have one server that can get 31000 rows from my linked server
in 14 seconds, using anohter server, it takes almost 3 mins to get back 773
rows from the same table.
Any ideas? Its driving me crazy!!!
Hi Lloyd
Have you tried adding a host file entry to the oracle server on the machine
which is slower than the others, it's a stab in the dark but your one machine
could be talking longer to resolve the name of the oracle db.
Regards
charl
http://www.sqlserver.co.za
"Lloyd Harrison" wrote:
> I have set up several servers with MSDE 2000 sp4, have created tables in
> these databases, can access, read, write data to the database through win sql
> and asp. I have set up a linked server to an oracle database and created a
> linkedsrvlogin. I can select data from my oracle database throught SQL using
> the linked server. All of my servers are working fine except one. Onne
> particular server is taking an extrememly long time to retrive certain data.
> For example, I have one server that can get 31000 rows from my linked server
> in 14 seconds, using anohter server, it takes almost 3 mins to get back 773
> rows from the same table.
> Any ideas? Its driving me crazy!!!
MSDE 2000 problems with linked server
I have set up several servers with MSDE 2000 sp4, have created tables in
these databases, can access, read, write data to the database through win sql
and asp. I have set up a linked server to an oracle database and created a
linkedsrvlogin. I can select data from my oracle database throught SQL using
the linked server. All of my servers are working fine except one. Onne
particular server is taking an extrememly long time to retrive certain data.
For example, I have one server that can get 31000 rows from my linked server
in 14 seconds, using anohter server, it takes almost 3 mins to get back 773
rows from the same table.
Any ideas? Its driving me crazy!!!Hi Lloyd
Have you tried adding a host file entry to the oracle server on the machine
which is slower than the others, it's a stab in the dark but your one machine
could be talking longer to resolve the name of the oracle db.
Regards
charl
http://www.sqlserver.co.za
"Lloyd Harrison" wrote:
> I have set up several servers with MSDE 2000 sp4, have created tables in
> these databases, can access, read, write data to the database through win sql
> and asp. I have set up a linked server to an oracle database and created a
> linkedsrvlogin. I can select data from my oracle database throught SQL using
> the linked server. All of my servers are working fine except one. Onne
> particular server is taking an extrememly long time to retrive certain data.
> For example, I have one server that can get 31000 rows from my linked server
> in 14 seconds, using anohter server, it takes almost 3 mins to get back 773
> rows from the same table.
> Any ideas? Its driving me crazy!!!
these databases, can access, read, write data to the database through win sql
and asp. I have set up a linked server to an oracle database and created a
linkedsrvlogin. I can select data from my oracle database throught SQL using
the linked server. All of my servers are working fine except one. Onne
particular server is taking an extrememly long time to retrive certain data.
For example, I have one server that can get 31000 rows from my linked server
in 14 seconds, using anohter server, it takes almost 3 mins to get back 773
rows from the same table.
Any ideas? Its driving me crazy!!!Hi Lloyd
Have you tried adding a host file entry to the oracle server on the machine
which is slower than the others, it's a stab in the dark but your one machine
could be talking longer to resolve the name of the oracle db.
Regards
charl
http://www.sqlserver.co.za
"Lloyd Harrison" wrote:
> I have set up several servers with MSDE 2000 sp4, have created tables in
> these databases, can access, read, write data to the database through win sql
> and asp. I have set up a linked server to an oracle database and created a
> linkedsrvlogin. I can select data from my oracle database throught SQL using
> the linked server. All of my servers are working fine except one. Onne
> particular server is taking an extrememly long time to retrive certain data.
> For example, I have one server that can get 31000 rows from my linked server
> in 14 seconds, using anohter server, it takes almost 3 mins to get back 773
> rows from the same table.
> Any ideas? Its driving me crazy!!!
MSDE 2000 problems with linked server
I have set up several servers with MSDE 2000 sp4, have created tables in
these databases, can access, read, write data to the database through win sq
l
and asp. I have set up a linked server to an oracle database and created a
linkedsrvlogin. I can select data from my oracle database throught SQL usin
g
the linked server. All of my servers are working fine except one. Onne
particular server is taking an extrememly long time to retrive certain data.
For example, I have one server that can get 31000 rows from my linked server
in 14 seconds, using anohter server, it takes almost 3 mins to get back 773
rows from the same table.
Any ideas? Its driving me crazy!!!Hi Lloyd
Have you tried adding a host file entry to the oracle server on the machine
which is slower than the others, it's a stab in the dark but your one machin
e
could be talking longer to resolve the name of the oracle db.
Regards
charl
http://www.sqlserver.co.za
"Lloyd Harrison" wrote:
> I have set up several servers with MSDE 2000 sp4, have created tables in
> these databases, can access, read, write data to the database through win
sql
> and asp. I have set up a linked server to an oracle database and created a
> linkedsrvlogin. I can select data from my oracle database throught SQL us
ing
> the linked server. All of my servers are working fine except one. Onne
> particular server is taking an extrememly long time to retrive certain dat
a.
> For example, I have one server that can get 31000 rows from my linked serv
er
> in 14 seconds, using anohter server, it takes almost 3 mins to get back 77
3
> rows from the same table.
> Any ideas? Its driving me crazy!!!
these databases, can access, read, write data to the database through win sq
l
and asp. I have set up a linked server to an oracle database and created a
linkedsrvlogin. I can select data from my oracle database throught SQL usin
g
the linked server. All of my servers are working fine except one. Onne
particular server is taking an extrememly long time to retrive certain data.
For example, I have one server that can get 31000 rows from my linked server
in 14 seconds, using anohter server, it takes almost 3 mins to get back 773
rows from the same table.
Any ideas? Its driving me crazy!!!Hi Lloyd
Have you tried adding a host file entry to the oracle server on the machine
which is slower than the others, it's a stab in the dark but your one machin
e
could be talking longer to resolve the name of the oracle db.
Regards
charl
http://www.sqlserver.co.za
"Lloyd Harrison" wrote:
> I have set up several servers with MSDE 2000 sp4, have created tables in
> these databases, can access, read, write data to the database through win
sql
> and asp. I have set up a linked server to an oracle database and created a
> linkedsrvlogin. I can select data from my oracle database throught SQL us
ing
> the linked server. All of my servers are working fine except one. Onne
> particular server is taking an extrememly long time to retrive certain dat
a.
> For example, I have one server that can get 31000 rows from my linked serv
er
> in 14 seconds, using anohter server, it takes almost 3 mins to get back 77
3
> rows from the same table.
> Any ideas? Its driving me crazy!!!
Wednesday, March 21, 2012
MSDE + SSL
Hi!
I had a working Win2003 server with Backup Exec 9.1 and Exchange 2003 OWA.
I installed SP1 for Win2003, WSUS and I created a certificate for OWA with
help from SelfSSL.
After this, I cant start my Backup Exec services, complaining about some SSL
error:
SSL Security error
ConnectionOpen (SECDoHandshake()).
and
[DBNETLIB][ConnectionOpen (SECDoHandshake()).]SSL Security error.
I think all this is a problem with SSL and MSDE.
Veritas says "talk to Microsoft" and gues what MS says...
What does SelfSSL to do with MSDE? Or what shoult I do to make MSDE (8.0)
run nice beside SSL for our OWA access.
Thanks!
Mattias
hi Mattias,
MrM wrote:
> Hi!
> I had a working Win2003 server with Backup Exec 9.1 and Exchange 2003
> OWA. I installed SP1 for Win2003, WSUS and I created a certificate
> for OWA with help from SelfSSL.
> After this, I cant start my Backup Exec services, complaining about
> some SSL error:
> --
> SSL Security error
> ConnectionOpen (SECDoHandshake()).
> and
> [DBNETLIB][ConnectionOpen (SECDoHandshake()).]SSL Security error.
> --
> I think all this is a problem with SSL and MSDE.
> Veritas says "talk to Microsoft" and gues what MS says...
> What does SelfSSL to do with MSDE? Or what shoult I do to make MSDE
> (8.0) run nice beside SSL for our OWA access.
>
please try having a look at
http://support.microsoft.com/default.aspx?id=309398 and
http://www.fftf.org/news/Aug05feed/M...ouble.rss.html
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
I had a working Win2003 server with Backup Exec 9.1 and Exchange 2003 OWA.
I installed SP1 for Win2003, WSUS and I created a certificate for OWA with
help from SelfSSL.
After this, I cant start my Backup Exec services, complaining about some SSL
error:
SSL Security error
ConnectionOpen (SECDoHandshake()).
and
[DBNETLIB][ConnectionOpen (SECDoHandshake()).]SSL Security error.
I think all this is a problem with SSL and MSDE.
Veritas says "talk to Microsoft" and gues what MS says...
What does SelfSSL to do with MSDE? Or what shoult I do to make MSDE (8.0)
run nice beside SSL for our OWA access.
Thanks!
Mattias
hi Mattias,
MrM wrote:
> Hi!
> I had a working Win2003 server with Backup Exec 9.1 and Exchange 2003
> OWA. I installed SP1 for Win2003, WSUS and I created a certificate
> for OWA with help from SelfSSL.
> After this, I cant start my Backup Exec services, complaining about
> some SSL error:
> --
> SSL Security error
> ConnectionOpen (SECDoHandshake()).
> and
> [DBNETLIB][ConnectionOpen (SECDoHandshake()).]SSL Security error.
> --
> I think all this is a problem with SSL and MSDE.
> Veritas says "talk to Microsoft" and gues what MS says...
> What does SelfSSL to do with MSDE? Or what shoult I do to make MSDE
> (8.0) run nice beside SSL for our OWA access.
>
please try having a look at
http://support.microsoft.com/default.aspx?id=309398 and
http://www.fftf.org/news/Aug05feed/M...ouble.rss.html
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.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 19, 2012
MSDE : find out what triggers are created
Hi
may i know is there anyway for me to find out from any system table in
MSDE what are the triggers that have been created ?
I wish to delete all and log in a new set of triggers, just in case
some old triggers cause some problems to the new ones.
Thank you
Best regards
Boon Yiang
Hi,
From OSQL Query the SYSOBJECTS table.
use <dbname>
go
Select name from sysobjects where xtype = 'tr'
Thanks
Hari
<chuaby@.hotmail.com> wrote in message
news:1174143091.658347.48080@.e65g2000hsc.googlegro ups.com...
> Hi
> may i know is there anyway for me to find out from any system table in
> MSDE what are the triggers that have been created ?
> I wish to delete all and log in a new set of triggers, just in case
> some old triggers cause some problems to the new ones.
> Thank you
> Best regards
> Boon Yiang
>
may i know is there anyway for me to find out from any system table in
MSDE what are the triggers that have been created ?
I wish to delete all and log in a new set of triggers, just in case
some old triggers cause some problems to the new ones.
Thank you
Best regards
Boon Yiang
Hi,
From OSQL Query the SYSOBJECTS table.
use <dbname>
go
Select name from sysobjects where xtype = 'tr'
Thanks
Hari
<chuaby@.hotmail.com> wrote in message
news:1174143091.658347.48080@.e65g2000hsc.googlegro ups.com...
> Hi
> may i know is there anyway for me to find out from any system table in
> MSDE what are the triggers that have been created ?
> I wish to delete all and log in a new set of triggers, just in case
> some old triggers cause some problems to the new ones.
> Thank you
> Best regards
> Boon Yiang
>
Friday, March 9, 2012
MSDE - ADP Question
Hi,
After upsizing on MSDE, I created ADP on my terminal.
When the created ADP I need to copy to another user to get connected to MSDE hosted on my pc I followed these steps.
First I copied ADP to the user's pc and
1. Opened Administration Tools on user's pc
2. Clicked twice Data Source (ODBC) icon
3. Selected System DSN and clicked Add
4. Selected SQL Server (Last item) and Finish
5. Given new connection name (any name) in the field 'Name'. Description left empty. In Servaer, typed server name.
6. In the next page, I selected SQL Server Authentication and...
Here is my question:
Should I use at this step System Administrator's login id and password ?
OR
Should I use user's pc id and password ?
I tried both way. But login fails.
Where might have gone wrong? BTW, this the first user I trying on.
Any help would be highly appreviated.
With kind regards,
Ashfaquecreate a sql login in our MSDE using sp_addlogin and then use sp_adduser to grant them specific db access. see details in BOL. if you are using Wndows XP SP2 you may have to create an exception in the personal firewall r drop it altogether.|||Thanks Thrasymachus,
I would appreciate it very much if you could little bit in detail as I am new bee for this area.
With kind regards,
Ashfaque|||Do you have Books Online? If so (it's included free with SQL Server), open it up and go to the Index tab. Type in "logins-SQL Server" and start reading. It will give you more than enough information to accomplish this task. You can also type in the stored procedures he gave you to get syntax and usage information.|||oh why use the reference material. I drove for a couple of years without a license when I was a kid.|||Hi Guys,
No, I don't have Books Online..
Justi moving around with the help of you people...
I attached jpg image to give you a clear pic to know whats wrong..
With kind regards,
Ashfaque|||Hello Gentlemen,
I am still waiting for your valuable response..
With kind regards,
Ashfaque
After upsizing on MSDE, I created ADP on my terminal.
When the created ADP I need to copy to another user to get connected to MSDE hosted on my pc I followed these steps.
First I copied ADP to the user's pc and
1. Opened Administration Tools on user's pc
2. Clicked twice Data Source (ODBC) icon
3. Selected System DSN and clicked Add
4. Selected SQL Server (Last item) and Finish
5. Given new connection name (any name) in the field 'Name'. Description left empty. In Servaer, typed server name.
6. In the next page, I selected SQL Server Authentication and...
Here is my question:
Should I use at this step System Administrator's login id and password ?
OR
Should I use user's pc id and password ?
I tried both way. But login fails.
Where might have gone wrong? BTW, this the first user I trying on.
Any help would be highly appreviated.
With kind regards,
Ashfaquecreate a sql login in our MSDE using sp_addlogin and then use sp_adduser to grant them specific db access. see details in BOL. if you are using Wndows XP SP2 you may have to create an exception in the personal firewall r drop it altogether.|||Thanks Thrasymachus,
I would appreciate it very much if you could little bit in detail as I am new bee for this area.
With kind regards,
Ashfaque|||Do you have Books Online? If so (it's included free with SQL Server), open it up and go to the Index tab. Type in "logins-SQL Server" and start reading. It will give you more than enough information to accomplish this task. You can also type in the stored procedures he gave you to get syntax and usage information.|||oh why use the reference material. I drove for a couple of years without a license when I was a kid.|||Hi Guys,
No, I don't have Books Online..
Justi moving around with the help of you people...
I attached jpg image to give you a clear pic to know whats wrong..
With kind regards,
Ashfaque|||Hello Gentlemen,
I am still waiting for your valuable response..
With kind regards,
Ashfaque
Saturday, February 25, 2012
msdb refuses to back up w/ plan
All,
I've created (and re-created) a Mx plan for the system databases.
Part of it is a complete backup. All the default options in the
wizard were chosen, including the option to verify.
Master and Model back up fine. MSDB, however, fails. According to
the Mx Plan log, the backup completes successfully, but the verify
fails as follows:
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3201:
[Microsoft][ODBC SQL Server Driver][SQL Server]Cannot open backu
p
device 'd:\sql_data\MSSQL\BACKUP\msdb_db_200407
042207.BAK'. Device
error or device off-line. See the SQL Server error log for more
details.
[Microsoft][ODBC SQL Server Driver][SQL Server]VERIFY DATABASE i
s
terminating abnormally.
1- It doesn't appear that the backup actually succeeded, as there is
no msdb_db_200407042207.bak file in the directory.
2- There is no additional information in the SQL Server error log
3- I can successfully back up msdb -manually- without a hiccup.
I've tried:
1- Recreating a new Mx Plan from scratch (no effect)
2- Can full index/optimizations on msdb (no errors found)
3- Tried shrinking the database (it's 215MBish) to make it faster
4- Tried a full backup/restore of msdb in case it had any mystery
corruption (no effect)
Oh yes, SQL Server standard 2000 sp3 on W2.3K standard. NTFS
partition. SQL Agent using a domain account, SQL Server running under
the same account.
Can anyone shed light on this? I can come up with no reason why the
Mx plan would fail for just this one database, when I can back it up
just fine manually.
GeofHere's some more info:
I did find some additional information in the app event log, giving the spec
ific T-SQL that was failing:
BACKUP DATABASE [msdb] TO DISK = N'd:\sql_data\MSSQL\BACKUP\msdb_db_200
407042238.BAK' WITH INIT , NOUNLOAD , NOSKIP , STATS = 10, NOFORMAT
After some pondering and re-reading my own post, I went ahead and logged int
o the server interactively using SQL Server's account. I attempted to execu
te the above SQL and lo and behond, it failed (General Network Error). When
executed under my normal U
serID, it executed fine.
Trial and error then produced the rather odd discovery that the problem part
of the statement is the seemingly innocuous "STATS=10" command. If the sam
e statement is run under the SQL Server account EXCEPT for removing the stat
s=10 command, it works fine|||Go the Maintenance Plan and right click and view maintenance history out
there ...Thats where most of the reasoning is for the failure..
"Geof" <Geof@.discussions.microsoft.com> wrote in message
news:C6436F94-BF81-41FD-9869-5595F7FBA6B4@.microsoft.com...
> Here's some more info:
> I did find some additional information in the app event log, giving the
specific T-SQL that was failing:
> BACKUP DATABASE [msdb] TO DISK =
N'd:\sql_data\MSSQL\BACKUP\msdb_db_20040
7042238.BAK' WITH INIT , NOUNLOAD
, NOSKIP , STATS = 10, NOFORMAT
> After some pondering and re-reading my own post, I went ahead and logged
into the server interactively using SQL Server's account. I attempted to
execute the above SQL and lo and behond, it failed (General Network Error).
When executed under my normal UserID, it executed fine.
> Trial and error then produced the rather odd discovery that the problem
part of the statement is the seemingly innocuous "STATS=10" command. If the
same statement is run under the SQL Server account EXCEPT for removing the
stats=10 command, it works fine.
> While I've gotten more information on exactly what is causing the problem,
I:
> 1- Have no idea why the problem is occurring, and
> 2- Don't know a way around it (other than backup w/o using a Mx Plan)
> My nearest stab would be that this particular T-SQL (and STATS option in
particular) is causing some sort of collision between SQL Server and SQL
Server Agent since they would both be running under the same account. (But
surely I'm not the only one in the history of SQL Server to have created a
sysdb mx plan w/ both SQL and SQL Agent running under an identical domain
account, huh')
> Ideas'|||In my first post I listed what was in the Mx Plan History. Does
anyone have any other ideas?
Geof
"Hassan" <fatima_ja@.hotmail.com> wrote in message news:<#GDGyveYEHA.996@.TK2MSFTNGP12.phx.gbl
>...
> Go the Maintenance Plan and right click and view maintenance history out
> there ...Thats where most of the reasoning is for the failure..
I've created (and re-created) a Mx plan for the system databases.
Part of it is a complete backup. All the default options in the
wizard were chosen, including the option to verify.
Master and Model back up fine. MSDB, however, fails. According to
the Mx Plan log, the backup completes successfully, but the verify
fails as follows:
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3201:
[Microsoft][ODBC SQL Server Driver][SQL Server]Cannot open backu
p
device 'd:\sql_data\MSSQL\BACKUP\msdb_db_200407
042207.BAK'. Device
error or device off-line. See the SQL Server error log for more
details.
[Microsoft][ODBC SQL Server Driver][SQL Server]VERIFY DATABASE i
s
terminating abnormally.
1- It doesn't appear that the backup actually succeeded, as there is
no msdb_db_200407042207.bak file in the directory.
2- There is no additional information in the SQL Server error log
3- I can successfully back up msdb -manually- without a hiccup.
I've tried:
1- Recreating a new Mx Plan from scratch (no effect)
2- Can full index/optimizations on msdb (no errors found)
3- Tried shrinking the database (it's 215MBish) to make it faster
4- Tried a full backup/restore of msdb in case it had any mystery
corruption (no effect)
Oh yes, SQL Server standard 2000 sp3 on W2.3K standard. NTFS
partition. SQL Agent using a domain account, SQL Server running under
the same account.
Can anyone shed light on this? I can come up with no reason why the
Mx plan would fail for just this one database, when I can back it up
just fine manually.
GeofHere's some more info:
I did find some additional information in the app event log, giving the spec
ific T-SQL that was failing:
BACKUP DATABASE [msdb] TO DISK = N'd:\sql_data\MSSQL\BACKUP\msdb_db_200
407042238.BAK' WITH INIT , NOUNLOAD , NOSKIP , STATS = 10, NOFORMAT
After some pondering and re-reading my own post, I went ahead and logged int
o the server interactively using SQL Server's account. I attempted to execu
te the above SQL and lo and behond, it failed (General Network Error). When
executed under my normal U
serID, it executed fine.
Trial and error then produced the rather odd discovery that the problem part
of the statement is the seemingly innocuous "STATS=10" command. If the sam
e statement is run under the SQL Server account EXCEPT for removing the stat
s=10 command, it works fine|||Go the Maintenance Plan and right click and view maintenance history out
there ...Thats where most of the reasoning is for the failure..
"Geof" <Geof@.discussions.microsoft.com> wrote in message
news:C6436F94-BF81-41FD-9869-5595F7FBA6B4@.microsoft.com...
> Here's some more info:
> I did find some additional information in the app event log, giving the
specific T-SQL that was failing:
> BACKUP DATABASE [msdb] TO DISK =
N'd:\sql_data\MSSQL\BACKUP\msdb_db_20040
7042238.BAK' WITH INIT , NOUNLOAD
, NOSKIP , STATS = 10, NOFORMAT
> After some pondering and re-reading my own post, I went ahead and logged
into the server interactively using SQL Server's account. I attempted to
execute the above SQL and lo and behond, it failed (General Network Error).
When executed under my normal UserID, it executed fine.
> Trial and error then produced the rather odd discovery that the problem
part of the statement is the seemingly innocuous "STATS=10" command. If the
same statement is run under the SQL Server account EXCEPT for removing the
stats=10 command, it works fine.
> While I've gotten more information on exactly what is causing the problem,
I:
> 1- Have no idea why the problem is occurring, and
> 2- Don't know a way around it (other than backup w/o using a Mx Plan)
> My nearest stab would be that this particular T-SQL (and STATS option in
particular) is causing some sort of collision between SQL Server and SQL
Server Agent since they would both be running under the same account. (But
surely I'm not the only one in the history of SQL Server to have created a
sysdb mx plan w/ both SQL and SQL Agent running under an identical domain
account, huh')
> Ideas'|||In my first post I listed what was in the Mx Plan History. Does
anyone have any other ideas?
Geof
"Hassan" <fatima_ja@.hotmail.com> wrote in message news:<#GDGyveYEHA.996@.TK2MSFTNGP12.phx.gbl
>...
> Go the Maintenance Plan and right click and view maintenance history out
> there ...Thats where most of the reasoning is for the failure..
msdb refuses to back up w/ plan
All,
I've created (and re-created) a Mx plan for the system databases.
Part of it is a complete backup. All the default options in the
wizard were chosen, including the option to verify.
Master and Model back up fine. MSDB, however, fails. According to
the Mx Plan log, the backup completes successfully, but the verify
fails as follows:
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3201:
[Microsoft][ODBC SQL Server Driver][SQL Server]Cannot open backup
device 'd:\sql_data\MSSQL\BACKUP\msdb_db_200407042207.BAK '. Device
error or device off-line. See the SQL Server error log for more
details.
[Microsoft][ODBC SQL Server Driver][SQL Server]VERIFY DATABASE is
terminating abnormally.
1- It doesn't appear that the backup actually succeeded, as there is
no msdb_db_200407042207.bak file in the directory.
2- There is no additional information in the SQL Server error log
3- I can successfully back up msdb -manually- without a hiccup.
I've tried:
1- Recreating a new Mx Plan from scratch (no effect)
2- Can full index/optimizations on msdb (no errors found)
3- Tried shrinking the database (it's 215MBish) to make it faster
4- Tried a full backup/restore of msdb in case it had any mystery
corruption (no effect)
Oh yes, SQL Server standard 2000 sp3 on W2.3K standard. NTFS
partition. SQL Agent using a domain account, SQL Server running under
the same account.
Can anyone shed light on this? I can come up with no reason why the
Mx plan would fail for just this one database, when I can back it up
just fine manually.
Geof
Here's some more info:
I did find some additional information in the app event log, giving the specific T-SQL that was failing:
BACKUP DATABASE [msdb] TO DISK = N'd:\sql_data\MSSQL\BACKUP\msdb_db_200407042238.BA K' WITH INIT , NOUNLOAD , NOSKIP , STATS = 10, NOFORMAT
After some pondering and re-reading my own post, I went ahead and logged into the server interactively using SQL Server's account. I attempted to execute the above SQL and lo and behond, it failed (General Network Error). When executed under my normal U
serID, it executed fine.
Trial and error then produced the rather odd discovery that the problem part of the statement is the seemingly innocuous "STATS=10" command. If the same statement is run under the SQL Server account EXCEPT for removing the stats=10 command, it works fine
|||Go the Maintenance Plan and right click and view maintenance history out
there ...Thats where most of the reasoning is for the failure..
"Geof" <Geof@.discussions.microsoft.com> wrote in message
news:C6436F94-BF81-41FD-9869-5595F7FBA6B4@.microsoft.com...
> Here's some more info:
> I did find some additional information in the app event log, giving the
specific T-SQL that was failing:
> BACKUP DATABASE [msdb] TO DISK =
N'd:\sql_data\MSSQL\BACKUP\msdb_db_200407042238.BA K' WITH INIT , NOUNLOAD
, NOSKIP , STATS = 10, NOFORMAT
> After some pondering and re-reading my own post, I went ahead and logged
into the server interactively using SQL Server's account. I attempted to
execute the above SQL and lo and behond, it failed (General Network Error).
When executed under my normal UserID, it executed fine.
> Trial and error then produced the rather odd discovery that the problem
part of the statement is the seemingly innocuous "STATS=10" command. If the
same statement is run under the SQL Server account EXCEPT for removing the
stats=10 command, it works fine.
> While I've gotten more information on exactly what is causing the problem,
I:
> 1- Have no idea why the problem is occurring, and
> 2- Don't know a way around it (other than backup w/o using a Mx Plan)
> My nearest stab would be that this particular T-SQL (and STATS option in
particular) is causing some sort of collision between SQL Server and SQL
Server Agent since they would both be running under the same account. (But
surely I'm not the only one in the history of SQL Server to have created a
sysdb mx plan w/ both SQL and SQL Agent running under an identical domain
account, huh?)
> Ideas?
|||In my first post I listed what was in the Mx Plan History. Does
anyone have any other ideas?
Geof
"Hassan" <fatima_ja@.hotmail.com> wrote in message news:<#GDGyveYEHA.996@.TK2MSFTNGP12.phx.gbl>...
> Go the Maintenance Plan and right click and view maintenance history out
> there ...Thats where most of the reasoning is for the failure..
I've created (and re-created) a Mx plan for the system databases.
Part of it is a complete backup. All the default options in the
wizard were chosen, including the option to verify.
Master and Model back up fine. MSDB, however, fails. According to
the Mx Plan log, the backup completes successfully, but the verify
fails as follows:
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3201:
[Microsoft][ODBC SQL Server Driver][SQL Server]Cannot open backup
device 'd:\sql_data\MSSQL\BACKUP\msdb_db_200407042207.BAK '. Device
error or device off-line. See the SQL Server error log for more
details.
[Microsoft][ODBC SQL Server Driver][SQL Server]VERIFY DATABASE is
terminating abnormally.
1- It doesn't appear that the backup actually succeeded, as there is
no msdb_db_200407042207.bak file in the directory.
2- There is no additional information in the SQL Server error log
3- I can successfully back up msdb -manually- without a hiccup.
I've tried:
1- Recreating a new Mx Plan from scratch (no effect)
2- Can full index/optimizations on msdb (no errors found)
3- Tried shrinking the database (it's 215MBish) to make it faster
4- Tried a full backup/restore of msdb in case it had any mystery
corruption (no effect)
Oh yes, SQL Server standard 2000 sp3 on W2.3K standard. NTFS
partition. SQL Agent using a domain account, SQL Server running under
the same account.
Can anyone shed light on this? I can come up with no reason why the
Mx plan would fail for just this one database, when I can back it up
just fine manually.
Geof
Here's some more info:
I did find some additional information in the app event log, giving the specific T-SQL that was failing:
BACKUP DATABASE [msdb] TO DISK = N'd:\sql_data\MSSQL\BACKUP\msdb_db_200407042238.BA K' WITH INIT , NOUNLOAD , NOSKIP , STATS = 10, NOFORMAT
After some pondering and re-reading my own post, I went ahead and logged into the server interactively using SQL Server's account. I attempted to execute the above SQL and lo and behond, it failed (General Network Error). When executed under my normal U
serID, it executed fine.
Trial and error then produced the rather odd discovery that the problem part of the statement is the seemingly innocuous "STATS=10" command. If the same statement is run under the SQL Server account EXCEPT for removing the stats=10 command, it works fine
|||Go the Maintenance Plan and right click and view maintenance history out
there ...Thats where most of the reasoning is for the failure..
"Geof" <Geof@.discussions.microsoft.com> wrote in message
news:C6436F94-BF81-41FD-9869-5595F7FBA6B4@.microsoft.com...
> Here's some more info:
> I did find some additional information in the app event log, giving the
specific T-SQL that was failing:
> BACKUP DATABASE [msdb] TO DISK =
N'd:\sql_data\MSSQL\BACKUP\msdb_db_200407042238.BA K' WITH INIT , NOUNLOAD
, NOSKIP , STATS = 10, NOFORMAT
> After some pondering and re-reading my own post, I went ahead and logged
into the server interactively using SQL Server's account. I attempted to
execute the above SQL and lo and behond, it failed (General Network Error).
When executed under my normal UserID, it executed fine.
> Trial and error then produced the rather odd discovery that the problem
part of the statement is the seemingly innocuous "STATS=10" command. If the
same statement is run under the SQL Server account EXCEPT for removing the
stats=10 command, it works fine.
> While I've gotten more information on exactly what is causing the problem,
I:
> 1- Have no idea why the problem is occurring, and
> 2- Don't know a way around it (other than backup w/o using a Mx Plan)
> My nearest stab would be that this particular T-SQL (and STATS option in
particular) is causing some sort of collision between SQL Server and SQL
Server Agent since they would both be running under the same account. (But
surely I'm not the only one in the history of SQL Server to have created a
sysdb mx plan w/ both SQL and SQL Agent running under an identical domain
account, huh?)
> Ideas?
|||In my first post I listed what was in the Mx Plan History. Does
anyone have any other ideas?
Geof
"Hassan" <fatima_ja@.hotmail.com> wrote in message news:<#GDGyveYEHA.996@.TK2MSFTNGP12.phx.gbl>...
> Go the Maintenance Plan and right click and view maintenance history out
> there ...Thats where most of the reasoning is for the failure..
msdb refuses to back up w/ plan
All,
I've created (and re-created) a Mx plan for the system databases.
Part of it is a complete backup. All the default options in the
wizard were chosen, including the option to verify.
Master and Model back up fine. MSDB, however, fails. According to
the Mx Plan log, the backup completes successfully, but the verify
fails as follows:
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3201:
[Microsoft][ODBC SQL Server Driver][SQL Server]Cannot open backup
device 'd:\sql_data\MSSQL\BACKUP\msdb_db_200407042207.BAK'. Device
error or device off-line. See the SQL Server error log for more
details.
[Microsoft][ODBC SQL Server Driver][SQL Server]VERIFY DATABASE is
terminating abnormally.
1- It doesn't appear that the backup actually succeeded, as there is
no msdb_db_200407042207.bak file in the directory.
2- There is no additional information in the SQL Server error log
3- I can successfully back up msdb -manually- without a hiccup.
I've tried:
1- Recreating a new Mx Plan from scratch (no effect)
2- Can full index/optimizations on msdb (no errors found)
3- Tried shrinking the database (it's 215MBish) to make it faster
4- Tried a full backup/restore of msdb in case it had any mystery
corruption (no effect)
Oh yes, SQL Server standard 2000 sp3 on W2.3K standard. NTFS
partition. SQL Agent using a domain account, SQL Server running under
the same account.
Can anyone shed light on this? I can come up with no reason why the
Mx plan would fail for just this one database, when I can back it up
just fine manually.
GeofHere's some more info:
I did find some additional information in the app event log, giving the specific T-SQL that was failing:
BACKUP DATABASE [msdb] TO DISK = N'd:\sql_data\MSSQL\BACKUP\msdb_db_200407042238.BAK' WITH INIT , NOUNLOAD , NOSKIP , STATS = 10, NOFORMAT
After some pondering and re-reading my own post, I went ahead and logged into the server interactively using SQL Server's account. I attempted to execute the above SQL and lo and behond, it failed (General Network Error). When executed under my normal UserID, it executed fine.
Trial and error then produced the rather odd discovery that the problem part of the statement is the seemingly innocuous "STATS=10" command. If the same statement is run under the SQL Server account EXCEPT for removing the stats=10 command, it works fine.
While I've gotten more information on exactly what is causing the problem, I:
1- Have no idea why the problem is occurring, and
2- Don't know a way around it (other than backup w/o using a Mx Plan)
My nearest stab would be that this particular T-SQL (and STATS option in particular) is causing some sort of collision between SQL Server and SQL Server Agent since they would both be running under the same account. (But surely I'm not the only one in the history of SQL Server to have created a sysdb mx plan w/ both SQL and SQL Agent running under an identical domain account, huh')
Ideas'|||Go the Maintenance Plan and right click and view maintenance history out
there ...Thats where most of the reasoning is for the failure..
"Geof" <Geof@.discussions.microsoft.com> wrote in message
news:C6436F94-BF81-41FD-9869-5595F7FBA6B4@.microsoft.com...
> Here's some more info:
> I did find some additional information in the app event log, giving the
specific T-SQL that was failing:
> BACKUP DATABASE [msdb] TO DISK =N'd:\sql_data\MSSQL\BACKUP\msdb_db_200407042238.BAK' WITH INIT , NOUNLOAD
, NOSKIP , STATS = 10, NOFORMAT
> After some pondering and re-reading my own post, I went ahead and logged
into the server interactively using SQL Server's account. I attempted to
execute the above SQL and lo and behond, it failed (General Network Error).
When executed under my normal UserID, it executed fine.
> Trial and error then produced the rather odd discovery that the problem
part of the statement is the seemingly innocuous "STATS=10" command. If the
same statement is run under the SQL Server account EXCEPT for removing the
stats=10 command, it works fine.
> While I've gotten more information on exactly what is causing the problem,
I:
> 1- Have no idea why the problem is occurring, and
> 2- Don't know a way around it (other than backup w/o using a Mx Plan)
> My nearest stab would be that this particular T-SQL (and STATS option in
particular) is causing some sort of collision between SQL Server and SQL
Server Agent since they would both be running under the same account. (But
surely I'm not the only one in the history of SQL Server to have created a
sysdb mx plan w/ both SQL and SQL Agent running under an identical domain
account, huh')
> Ideas'|||In my first post I listed what was in the Mx Plan History. Does
anyone have any other ideas?
Geof
"Hassan" <fatima_ja@.hotmail.com> wrote in message news:<#GDGyveYEHA.996@.TK2MSFTNGP12.phx.gbl>...
> Go the Maintenance Plan and right click and view maintenance history out
> there ...Thats where most of the reasoning is for the failure..
I've created (and re-created) a Mx plan for the system databases.
Part of it is a complete backup. All the default options in the
wizard were chosen, including the option to verify.
Master and Model back up fine. MSDB, however, fails. According to
the Mx Plan log, the backup completes successfully, but the verify
fails as follows:
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3201:
[Microsoft][ODBC SQL Server Driver][SQL Server]Cannot open backup
device 'd:\sql_data\MSSQL\BACKUP\msdb_db_200407042207.BAK'. Device
error or device off-line. See the SQL Server error log for more
details.
[Microsoft][ODBC SQL Server Driver][SQL Server]VERIFY DATABASE is
terminating abnormally.
1- It doesn't appear that the backup actually succeeded, as there is
no msdb_db_200407042207.bak file in the directory.
2- There is no additional information in the SQL Server error log
3- I can successfully back up msdb -manually- without a hiccup.
I've tried:
1- Recreating a new Mx Plan from scratch (no effect)
2- Can full index/optimizations on msdb (no errors found)
3- Tried shrinking the database (it's 215MBish) to make it faster
4- Tried a full backup/restore of msdb in case it had any mystery
corruption (no effect)
Oh yes, SQL Server standard 2000 sp3 on W2.3K standard. NTFS
partition. SQL Agent using a domain account, SQL Server running under
the same account.
Can anyone shed light on this? I can come up with no reason why the
Mx plan would fail for just this one database, when I can back it up
just fine manually.
GeofHere's some more info:
I did find some additional information in the app event log, giving the specific T-SQL that was failing:
BACKUP DATABASE [msdb] TO DISK = N'd:\sql_data\MSSQL\BACKUP\msdb_db_200407042238.BAK' WITH INIT , NOUNLOAD , NOSKIP , STATS = 10, NOFORMAT
After some pondering and re-reading my own post, I went ahead and logged into the server interactively using SQL Server's account. I attempted to execute the above SQL and lo and behond, it failed (General Network Error). When executed under my normal UserID, it executed fine.
Trial and error then produced the rather odd discovery that the problem part of the statement is the seemingly innocuous "STATS=10" command. If the same statement is run under the SQL Server account EXCEPT for removing the stats=10 command, it works fine.
While I've gotten more information on exactly what is causing the problem, I:
1- Have no idea why the problem is occurring, and
2- Don't know a way around it (other than backup w/o using a Mx Plan)
My nearest stab would be that this particular T-SQL (and STATS option in particular) is causing some sort of collision between SQL Server and SQL Server Agent since they would both be running under the same account. (But surely I'm not the only one in the history of SQL Server to have created a sysdb mx plan w/ both SQL and SQL Agent running under an identical domain account, huh')
Ideas'|||Go the Maintenance Plan and right click and view maintenance history out
there ...Thats where most of the reasoning is for the failure..
"Geof" <Geof@.discussions.microsoft.com> wrote in message
news:C6436F94-BF81-41FD-9869-5595F7FBA6B4@.microsoft.com...
> Here's some more info:
> I did find some additional information in the app event log, giving the
specific T-SQL that was failing:
> BACKUP DATABASE [msdb] TO DISK =N'd:\sql_data\MSSQL\BACKUP\msdb_db_200407042238.BAK' WITH INIT , NOUNLOAD
, NOSKIP , STATS = 10, NOFORMAT
> After some pondering and re-reading my own post, I went ahead and logged
into the server interactively using SQL Server's account. I attempted to
execute the above SQL and lo and behond, it failed (General Network Error).
When executed under my normal UserID, it executed fine.
> Trial and error then produced the rather odd discovery that the problem
part of the statement is the seemingly innocuous "STATS=10" command. If the
same statement is run under the SQL Server account EXCEPT for removing the
stats=10 command, it works fine.
> While I've gotten more information on exactly what is causing the problem,
I:
> 1- Have no idea why the problem is occurring, and
> 2- Don't know a way around it (other than backup w/o using a Mx Plan)
> My nearest stab would be that this particular T-SQL (and STATS option in
particular) is causing some sort of collision between SQL Server and SQL
Server Agent since they would both be running under the same account. (But
surely I'm not the only one in the history of SQL Server to have created a
sysdb mx plan w/ both SQL and SQL Agent running under an identical domain
account, huh')
> Ideas'|||In my first post I listed what was in the Mx Plan History. Does
anyone have any other ideas?
Geof
"Hassan" <fatima_ja@.hotmail.com> wrote in message news:<#GDGyveYEHA.996@.TK2MSFTNGP12.phx.gbl>...
> Go the Maintenance Plan and right click and view maintenance history out
> there ...Thats where most of the reasoning is for the failure..
Subscribe to:
Posts (Atom)