MSDE 2000 Question

Can you install the SQL client tools on a box running msde and register the msde database under enterprise manager?
Thanksyes, you cansql

MSDE 2000 installation on Windows 98 SE

Hi,
I have Installed MSDE 2000 on Windows 98 SE box After REBOOT MSDE
service is running.
I am not able to connect to the MSDE in WIndows Authentication mode
while using Login ( sa ) / password the connectivity is done.
My GUI uses the MSDE connection in "Windows Authentication Mode" which
is working fine with the 2K/XP but not with 98SE/ME.
The MSDE Readme.txt says that on 98 / ME the default Connectivity mode
is "Windows Authentication" BUT its not working in that way.
I have tried SECURITYMODE=SQL as command line to setup.exe as well but
results are same.
Any clue to run it in WMA Mode on Win98SE/ME ?
thanks
kapil
Hi Kaps,
Win98 doesn't provide the infrastructure that MSDE needs to use Windows
Authentication. You will need to use SQL Server authentication and specify
an password for sa (SAPWD) while installing it.
HTH,
Greg Low [MVP]
MSDE Manager SQL Tools
www.whitebearconsulting.com
"kaps" <kapilkj@.gmail.com> wrote in message
news:1103617693.026085.125330@.f14g2000cwb.googlegr oups.com...
> Hi,
> I have Installed MSDE 2000 on Windows 98 SE box After REBOOT MSDE
> service is running.
> I am not able to connect to the MSDE in WIndows Authentication mode
> while using Login ( sa ) / password the connectivity is done.
> My GUI uses the MSDE connection in "Windows Authentication Mode" which
> is working fine with the 2K/XP but not with 98SE/ME.
> The MSDE Readme.txt says that on 98 / ME the default Connectivity mode
> is "Windows Authentication" BUT its not working in that way.
> I have tried SECURITYMODE=SQL as command line to setup.exe as well but
> results are same.
> Any clue to run it in WMA Mode on Win98SE/ME ?
>
> thanks
> kapil
>

msde & windows xp sp2 question

hosting an msde 2000 sp1 instance on a windows xp sp 2 box, what steps can i
take to ensure other workstations can connect? The msde instance was
created with merge modules, and I cannot update to sp3a without the
manufacturer providing an installation, which isn't going to happen
apparently. Currently, none of my workstations can connect; i've attempted
to add sqlsvr.exe to the exception list, and also open port 1433 tcp on the
host system, with no luck.
Any assistance would be greatly appreciated!
S. Purkiss.
Have you tried disabling the firewall & then attempting to connect? Does it
work?
Cheers,
James Goodman
"S Purkiss" <shel@.shel.com> wrote in message
news:MNqdnQgi5cqwVffcRVn-rw@.rogers.com...
> hosting an msde 2000 sp1 instance on a windows xp sp 2 box, what steps can
> i
> take to ensure other workstations can connect? The msde instance was
> created with merge modules, and I cannot update to sp3a without the
> manufacturer providing an installation, which isn't going to happen
> apparently. Currently, none of my workstations can connect; i've
> attempted
> to add sqlsvr.exe to the exception list, and also open port 1433 tcp on
> the
> host system, with no luck.
> Any assistance would be greatly appreciated!
> S. Purkiss.
>
>
|||Hi James
Yep, I've tried this. Disabling the firewall doesn't improve the situation.
I have two theories on this...
1. i've heard it said that sp2's firewall doesn't actually go all the way
down when turned off
2. perhaps some netoworking protocol for sql is turned off when sp2 is
installed?
Take care,
Sheldon
"James Goodman" <jamesATnorton-associates.co.ukREMOVE> wrote in message
news:ux8vBpGsEHA.3896@.TK2MSFTNGP15.phx.gbl...
> Have you tried disabling the firewall & then attempting to connect? Does
> it work?
>
> --
> Cheers,
> James Goodman
> "S Purkiss" <shel@.shel.com> wrote in message
> news:MNqdnQgi5cqwVffcRVn-rw@.rogers.com...
>
|||If you added sqlsvr.exe to the exception list that should open up port 1433
or whatever port your using if it is a named instance and also udp 1434.
Make sure you have file and print sharing enabled as well.
"S Purkiss" wrote:

> Hi James
> Yep, I've tried this. Disabling the firewall doesn't improve the situation.
> I have two theories on this...
> 1. i've heard it said that sp2's firewall doesn't actually go all the way
> down when turned off
> 2. perhaps some netoworking protocol for sql is turned off when sp2 is
> installed?
> Take care,
> Sheldon
>
> "James Goodman" <jamesATnorton-associates.co.ukREMOVE> wrote in message
> news:ux8vBpGsEHA.3896@.TK2MSFTNGP15.phx.gbl...
>
>

msde & windows xp sp2 question

hosting an msde 2000 sp1 instance on a windows xp sp 2 box, what steps can i
take to ensure other workstations can connect? The msde instance was
created with merge modules, and I cannot update to sp3a without the
manufacturer providing an installation, which isn't going to happen
apparently. Currently, none of my workstations can connect; i've attempted
to add sqlsvr.exe to the exception list, and also open port 1433 tcp on the
host system, with no luck.
Any assistance would be greatly appreciated!
S. Purkiss.
S Purkiss wrote:
> hosting an msde 2000 sp1 instance on a windows xp sp 2 box, what steps can i
> take to ensure other workstations can connect? The msde instance was
> created with merge modules, and I cannot update to sp3a without the
> manufacturer providing an installation, which isn't going to happen
> apparently. Currently, none of my workstations can connect; i've attempted
> to add sqlsvr.exe to the exception list, and also open port 1433 tcp on the
> host system, with no luck.
> Any assistance would be greatly appreciated!
> S. Purkiss.
>
Hi Sheldon
For a default instance of MSDE you need to open TCP 1433.
For a named instance you need to open UDP 1434 and the TCP port that the
named instance is using. You can find this port from the registry key
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
Server\YourNamedInstance\MSSQLServer\SuperSocketNe tLib\Tcp, key TcpPort.
Good luck!

msdb suspect

After move the whole sql server databases to a new box, msdb shows suspect,
the other databases all work fine.
A select statement shows that the staus of msdb is 280.
After I change the status to 24, it still does not work. I can't start
SQLServerAgent now.
Please help!!!
thanks, FeiCheck out the SQL Server errorlog why it became suspect. Perhaps you don't h
ave the files for msdb
in the same directory as the original SQL Server, for instance.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Fei" <Fei@.discussions.microsoft.com> wrote in message
news:81056E87-078C-4E54-91EA-D2A7273B4554@.microsoft.com...
> After move the whole sql server databases to a new box, msdb shows suspect
,
> the other databases all work fine.
> A select statement shows that the staus of msdb is 280.
> After I change the status to 24, it still does not work. I can't start
> SQLServerAgent now.
> Please help!!!
> thanks, Fei|||Tibor,
Thanks for your quick response.
I checked the errorlog and there is no related error msg found in the log.
The msdb files are on a different location (e:drive) from the original
installation (c: drive)because we wanted to seperate the datafiles from the
software files. The other system database files such as master, model are al
l
in the same location as the msdb and the other system databases are just
fine.
Any suggestions?
Fei
"Tibor Karaszi" wrote:

> Check out the SQL Server errorlog why it became suspect. Perhaps you don't
have the files for msdb
> in the same directory as the original SQL Server, for instance.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Fei" <Fei@.discussions.microsoft.com> wrote in message
> news:81056E87-078C-4E54-91EA-D2A7273B4554@.microsoft.com...
>|||Since the path for msdb is in the master database, it is expected that msdb
becomes suspect if you
move the files to some different location. I suggest you move the files back
and then follow
instructions in either KB 224071 if on 2000 or Books Online of on 2005 on ho
w to move files for
msdb.
Also, there *are* error messages for msdb to be found in the errorlog file,
you just need to find
the right errorlog file (first startup when it became suspect).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Fei" <Fei@.discussions.microsoft.com> wrote in message
news:36CB5CBE-2373-4261-97C0-1AA615E564E4@.microsoft.com...[vbcol=seagreen]
> Tibor,
> Thanks for your quick response.
> I checked the errorlog and there is no related error msg found in the log.
> The msdb files are on a different location (e:drive) from the original
> installation (c: drive)because we wanted to seperate the datafiles from th
e
> software files. The other system database files such as master, model are
all
> in the same location as the msdb and the other system databases are just
> fine.
> Any suggestions?
>
> Fei
> "Tibor Karaszi" wrote:
>|||Hi Tibor
> Since the path for msdb is in the master database, it is expected that
> msdb becomes suspect if you move the files to some different location.
In KB 224071 they mention in how to move MSDB database the different
location to be moved the MSDB database
4. Move the Msdbdata.mdf and Msdblog.ldf files from the current
location (D:\Mssql8\Data) to the new location (E:\Mssql8\Data).
However the new master's path is dE:\SQLDATA\master.mdf
and -lE:\SQLDATA\mastlog.ldf. So should msdb database be attach to the same
path?
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:C6840BE3-DB95-4C18-A44E-7630B5A67734@.microsoft.com...
> Since the path for msdb is in the master database, it is expected that
> msdb becomes suspect if you move the files to some different location. I
> suggest you move the files back and then follow instructions in either KB
> 224071 if on 2000 or Books Online of on 2005 on how to move files for
> msdb.
> Also, there *are* error messages for msdb to be found in the errorlog
> file, you just need to find the right errorlog file (first startup when it
> became suspect).
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Fei" <Fei@.discussions.microsoft.com> wrote in message
> news:36CB5CBE-2373-4261-97C0-1AA615E564E4@.microsoft.com...
>|||No msdb doesn't have to be in the same path as master. But the path to msdb
is *in* master, so you
can't just move the files to some other location (which is true for any data
base).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Uri Dimant" <urid@.iscar.co.il> wrote in message news:OhPtlBTvHHA.4540@.TK2MSFTNGP05.phx.gbl.
.
> Hi Tibor
> In KB 224071 they mention in how to move MSDB database the different loc
ation to be moved the
> MSDB database
> 4. Move the Msdbdata.mdf and Msdblog.ldf files from the current locat
ion (D:\Mssql8\Data) to
> the new location (E:\Mssql8\Data).
>
> However the new master's path is dE:\SQLDATA\master.mdf and -lE:\SQLDATA\m
astlog.ldf. So should
> msdb database be attach to the same path?
>
>
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote i
n message
> news:C6840BE3-DB95-4C18-A44E-7630B5A67734@.microsoft.com...
>|||Tibor
Ah, yes. I just misunderstood your comments.
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:uh84O8ZvHHA.4540@.TK2MSFTNGP05.phx.gbl...
> No msdb doesn't have to be in the same path as master. But the path to
> msdb is *in* master, so you can't just move the files to some other
> location (which is true for any database).
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Uri Dimant" <urid@.iscar.co.il> wrote in message
> news:OhPtlBTvHHA.4540@.TK2MSFTNGP05.phx.gbl...
>

msdb suspect

After move the whole sql server databases to a new box, msdb shows suspect,
the other databases all work fine.
A select statement shows that the staus of msdb is 280.
After I change the status to 24, it still does not work. I can't start
SQLServerAgent now.
Please help!!!
thanks, Fei
Check out the SQL Server errorlog why it became suspect. Perhaps you don't have the files for msdb
in the same directory as the original SQL Server, for instance.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Fei" <Fei@.discussions.microsoft.com> wrote in message
news:81056E87-078C-4E54-91EA-D2A7273B4554@.microsoft.com...
> After move the whole sql server databases to a new box, msdb shows suspect,
> the other databases all work fine.
> A select statement shows that the staus of msdb is 280.
> After I change the status to 24, it still does not work. I can't start
> SQLServerAgent now.
> Please help!!!
> thanks, Fei
|||Tibor,
Thanks for your quick response.
I checked the errorlog and there is no related error msg found in the log.
The msdb files are on a different location (e:drive) from the original
installation (c: drive)because we wanted to seperate the datafiles from the
software files. The other system database files such as master, model are all
in the same location as the msdb and the other system databases are just
fine.
Any suggestions?
Fei
"Tibor Karaszi" wrote:

> Check out the SQL Server errorlog why it became suspect. Perhaps you don't have the files for msdb
> in the same directory as the original SQL Server, for instance.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Fei" <Fei@.discussions.microsoft.com> wrote in message
> news:81056E87-078C-4E54-91EA-D2A7273B4554@.microsoft.com...
>
|||Since the path for msdb is in the master database, it is expected that msdb becomes suspect if you
move the files to some different location. I suggest you move the files back and then follow
instructions in either KB 224071 if on 2000 or Books Online of on 2005 on how to move files for
msdb.
Also, there *are* error messages for msdb to be found in the errorlog file, you just need to find
the right errorlog file (first startup when it became suspect).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Fei" <Fei@.discussions.microsoft.com> wrote in message
news:36CB5CBE-2373-4261-97C0-1AA615E564E4@.microsoft.com...[vbcol=seagreen]
> Tibor,
> Thanks for your quick response.
> I checked the errorlog and there is no related error msg found in the log.
> The msdb files are on a different location (e:drive) from the original
> installation (c: drive)because we wanted to seperate the datafiles from the
> software files. The other system database files such as master, model are all
> in the same location as the msdb and the other system databases are just
> fine.
> Any suggestions?
>
> Fei
> "Tibor Karaszi" wrote:
|||Hi Tibor
> Since the path for msdb is in the master database, it is expected that
> msdb becomes suspect if you move the files to some different location.
In KB 224071 they mention in how to move MSDB database the different
location to be moved the MSDB database
4. Move the Msdbdata.mdf and Msdblog.ldf files from the current
location (D:\Mssql8\Data) to the new location (E:\Mssql8\Data).
However the new master's path is dE:\SQLDATA\master.mdf
and -lE:\SQLDATA\mastlog.ldf. So should msdb database be attach to the same
path?
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:C6840BE3-DB95-4C18-A44E-7630B5A67734@.microsoft.com...
> Since the path for msdb is in the master database, it is expected that
> msdb becomes suspect if you move the files to some different location. I
> suggest you move the files back and then follow instructions in either KB
> 224071 if on 2000 or Books Online of on 2005 on how to move files for
> msdb.
> Also, there *are* error messages for msdb to be found in the errorlog
> file, you just need to find the right errorlog file (first startup when it
> became suspect).
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Fei" <Fei@.discussions.microsoft.com> wrote in message
> news:36CB5CBE-2373-4261-97C0-1AA615E564E4@.microsoft.com...
>
|||No msdb doesn't have to be in the same path as master. But the path to msdb is *in* master, so you
can't just move the files to some other location (which is true for any database).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Uri Dimant" <urid@.iscar.co.il> wrote in message news:OhPtlBTvHHA.4540@.TK2MSFTNGP05.phx.gbl...
> Hi Tibor
> In KB 224071 they mention in how to move MSDB database the different location to be moved the
> MSDB database
> 4. Move the Msdbdata.mdf and Msdblog.ldf files from the current location (D:\Mssql8\Data) to
> the new location (E:\Mssql8\Data).
>
> However the new master's path is dE:\SQLDATA\master.mdf and -lE:\SQLDATA\mastlog.ldf. So should
> msdb database be attach to the same path?
>
>
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in message
> news:C6840BE3-DB95-4C18-A44E-7630B5A67734@.microsoft.com...
>
|||Tibor
Ah, yes. I just misunderstood your comments.
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:uh84O8ZvHHA.4540@.TK2MSFTNGP05.phx.gbl...
> No msdb doesn't have to be in the same path as master. But the path to
> msdb is *in* master, so you can't just move the files to some other
> location (which is true for any database).
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Uri Dimant" <urid@.iscar.co.il> wrote in message
> news:OhPtlBTvHHA.4540@.TK2MSFTNGP05.phx.gbl...
>

msdb suspect

After move the whole sql server databases to a new box, msdb shows suspect,
the other databases all work fine.
A select statement shows that the staus of msdb is 280.
After I change the status to 24, it still does not work. I can't start
SQLServerAgent now.
Please help!!!
thanks, FeiCheck out the SQL Server errorlog why it became suspect. Perhaps you don't have the files for msdb
in the same directory as the original SQL Server, for instance.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Fei" <Fei@.discussions.microsoft.com> wrote in message
news:81056E87-078C-4E54-91EA-D2A7273B4554@.microsoft.com...
> After move the whole sql server databases to a new box, msdb shows suspect,
> the other databases all work fine.
> A select statement shows that the staus of msdb is 280.
> After I change the status to 24, it still does not work. I can't start
> SQLServerAgent now.
> Please help!!!
> thanks, Fei|||Tibor,
Thanks for your quick response.
I checked the errorlog and there is no related error msg found in the log.
The msdb files are on a different location (e:drive) from the original
installation (c: drive)because we wanted to seperate the datafiles from the
software files. The other system database files such as master, model are all
in the same location as the msdb and the other system databases are just
fine.
Any suggestions?
Fei
"Tibor Karaszi" wrote:
> Check out the SQL Server errorlog why it became suspect. Perhaps you don't have the files for msdb
> in the same directory as the original SQL Server, for instance.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Fei" <Fei@.discussions.microsoft.com> wrote in message
> news:81056E87-078C-4E54-91EA-D2A7273B4554@.microsoft.com...
> > After move the whole sql server databases to a new box, msdb shows suspect,
> > the other databases all work fine.
> >
> > A select statement shows that the staus of msdb is 280.
> >
> > After I change the status to 24, it still does not work. I can't start
> > SQLServerAgent now.
> >
> > Please help!!!
> >
> > thanks, Fei
>|||Since the path for msdb is in the master database, it is expected that msdb becomes suspect if you
move the files to some different location. I suggest you move the files back and then follow
instructions in either KB 224071 if on 2000 or Books Online of on 2005 on how to move files for
msdb.
Also, there *are* error messages for msdb to be found in the errorlog file, you just need to find
the right errorlog file (first startup when it became suspect).
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Fei" <Fei@.discussions.microsoft.com> wrote in message
news:36CB5CBE-2373-4261-97C0-1AA615E564E4@.microsoft.com...
> Tibor,
> Thanks for your quick response.
> I checked the errorlog and there is no related error msg found in the log.
> The msdb files are on a different location (e:drive) from the original
> installation (c: drive)because we wanted to seperate the datafiles from the
> software files. The other system database files such as master, model are all
> in the same location as the msdb and the other system databases are just
> fine.
> Any suggestions?
>
> Fei
> "Tibor Karaszi" wrote:
>> Check out the SQL Server errorlog why it became suspect. Perhaps you don't have the files for
>> msdb
>> in the same directory as the original SQL Server, for instance.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "Fei" <Fei@.discussions.microsoft.com> wrote in message
>> news:81056E87-078C-4E54-91EA-D2A7273B4554@.microsoft.com...
>> > After move the whole sql server databases to a new box, msdb shows suspect,
>> > the other databases all work fine.
>> >
>> > A select statement shows that the staus of msdb is 280.
>> >
>> > After I change the status to 24, it still does not work. I can't start
>> > SQLServerAgent now.
>> >
>> > Please help!!!
>> >
>> > thanks, Fei|||Hi Tibor
> Since the path for msdb is in the master database, it is expected that
> msdb becomes suspect if you move the files to some different location.
In KB 224071 they mention in how to move MSDB database the different
location to be moved the MSDB database
4. Move the Msdbdata.mdf and Msdblog.ldf files from the current
location (D:\Mssql8\Data) to the new location (E:\Mssql8\Data).
However the new master's path is dE:\SQLDATA\master.mdf
and -lE:\SQLDATA\mastlog.ldf. So should msdb database be attach to the same
path?
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:C6840BE3-DB95-4C18-A44E-7630B5A67734@.microsoft.com...
> Since the path for msdb is in the master database, it is expected that
> msdb becomes suspect if you move the files to some different location. I
> suggest you move the files back and then follow instructions in either KB
> 224071 if on 2000 or Books Online of on 2005 on how to move files for
> msdb.
> Also, there *are* error messages for msdb to be found in the errorlog
> file, you just need to find the right errorlog file (first startup when it
> became suspect).
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Fei" <Fei@.discussions.microsoft.com> wrote in message
> news:36CB5CBE-2373-4261-97C0-1AA615E564E4@.microsoft.com...
>> Tibor,
>> Thanks for your quick response.
>> I checked the errorlog and there is no related error msg found in the
>> log.
>> The msdb files are on a different location (e:drive) from the original
>> installation (c: drive)because we wanted to seperate the datafiles from
>> the
>> software files. The other system database files such as master, model are
>> all
>> in the same location as the msdb and the other system databases are just
>> fine.
>> Any suggestions?
>>
>> Fei
>> "Tibor Karaszi" wrote:
>> Check out the SQL Server errorlog why it became suspect. Perhaps you
>> don't have the files for msdb
>> in the same directory as the original SQL Server, for instance.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "Fei" <Fei@.discussions.microsoft.com> wrote in message
>> news:81056E87-078C-4E54-91EA-D2A7273B4554@.microsoft.com...
>> > After move the whole sql server databases to a new box, msdb shows
>> > suspect,
>> > the other databases all work fine.
>> >
>> > A select statement shows that the staus of msdb is 280.
>> >
>> > After I change the status to 24, it still does not work. I can't
>> > start
>> > SQLServerAgent now.
>> >
>> > Please help!!!
>> >
>> > thanks, Fei
>|||No msdb doesn't have to be in the same path as master. But the path to msdb is *in* master, so you
can't just move the files to some other location (which is true for any database).
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Uri Dimant" <urid@.iscar.co.il> wrote in message news:OhPtlBTvHHA.4540@.TK2MSFTNGP05.phx.gbl...
> Hi Tibor
>> Since the path for msdb is in the master database, it is expected that msdb becomes suspect if
>> you move the files to some different location.
> In KB 224071 they mention in how to move MSDB database the different location to be moved the
> MSDB database
> 4. Move the Msdbdata.mdf and Msdblog.ldf files from the current location (D:\Mssql8\Data) to
> the new location (E:\Mssql8\Data).
>
> However the new master's path is dE:\SQLDATA\master.mdf and -lE:\SQLDATA\mastlog.ldf. So should
> msdb database be attach to the same path?
>
>
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in message
> news:C6840BE3-DB95-4C18-A44E-7630B5A67734@.microsoft.com...
>> Since the path for msdb is in the master database, it is expected that msdb becomes suspect if
>> you move the files to some different location. I suggest you move the files back and then follow
>> instructions in either KB 224071 if on 2000 or Books Online of on 2005 on how to move files for
>> msdb.
>> Also, there *are* error messages for msdb to be found in the errorlog file, you just need to find
>> the right errorlog file (first startup when it became suspect).
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "Fei" <Fei@.discussions.microsoft.com> wrote in message
>> news:36CB5CBE-2373-4261-97C0-1AA615E564E4@.microsoft.com...
>> Tibor,
>> Thanks for your quick response.
>> I checked the errorlog and there is no related error msg found in the log.
>> The msdb files are on a different location (e:drive) from the original
>> installation (c: drive)because we wanted to seperate the datafiles from the
>> software files. The other system database files such as master, model are all
>> in the same location as the msdb and the other system databases are just
>> fine.
>> Any suggestions?
>>
>> Fei
>> "Tibor Karaszi" wrote:
>> Check out the SQL Server errorlog why it became suspect. Perhaps you don't have the files for
>> msdb
>> in the same directory as the original SQL Server, for instance.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "Fei" <Fei@.discussions.microsoft.com> wrote in message
>> news:81056E87-078C-4E54-91EA-D2A7273B4554@.microsoft.com...
>> > After move the whole sql server databases to a new box, msdb shows suspect,
>> > the other databases all work fine.
>> >
>> > A select statement shows that the staus of msdb is 280.
>> >
>> > After I change the status to 24, it still does not work. I can't start
>> > SQLServerAgent now.
>> >
>> > Please help!!!
>> >
>> > thanks, Fei
>>
>|||Tibor
Ah, yes. I just misunderstood your comments.
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:uh84O8ZvHHA.4540@.TK2MSFTNGP05.phx.gbl...
> No msdb doesn't have to be in the same path as master. But the path to
> msdb is *in* master, so you can't just move the files to some other
> location (which is true for any database).
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Uri Dimant" <urid@.iscar.co.il> wrote in message
> news:OhPtlBTvHHA.4540@.TK2MSFTNGP05.phx.gbl...
>> Hi Tibor
>> Since the path for msdb is in the master database, it is expected that
>> msdb becomes suspect if you move the files to some different location.
>> In KB 224071 they mention in how to move MSDB database the different
>> location to be moved the MSDB database
>> 4. Move the Msdbdata.mdf and Msdblog.ldf files from the current
>> location (D:\Mssql8\Data) to the new location (E:\Mssql8\Data).
>>
>> However the new master's path is dE:\SQLDATA\master.mdf
>> and -lE:\SQLDATA\mastlog.ldf. So should msdb database be attach to the
>> same path?
>>
>>
>> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote
>> in message news:C6840BE3-DB95-4C18-A44E-7630B5A67734@.microsoft.com...
>> Since the path for msdb is in the master database, it is expected that
>> msdb becomes suspect if you move the files to some different location. I
>> suggest you move the files back and then follow instructions in either
>> KB 224071 if on 2000 or Books Online of on 2005 on how to move files for
>> msdb.
>> Also, there *are* error messages for msdb to be found in the errorlog
>> file, you just need to find the right errorlog file (first startup when
>> it became suspect).
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "Fei" <Fei@.discussions.microsoft.com> wrote in message
>> news:36CB5CBE-2373-4261-97C0-1AA615E564E4@.microsoft.com...
>> Tibor,
>> Thanks for your quick response.
>> I checked the errorlog and there is no related error msg found in the
>> log.
>> The msdb files are on a different location (e:drive) from the original
>> installation (c: drive)because we wanted to seperate the datafiles from
>> the
>> software files. The other system database files such as master, model
>> are all
>> in the same location as the msdb and the other system databases are
>> just
>> fine.
>> Any suggestions?
>>
>> Fei
>> "Tibor Karaszi" wrote:
>> Check out the SQL Server errorlog why it became suspect. Perhaps you
>> don't have the files for msdb
>> in the same directory as the original SQL Server, for instance.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "Fei" <Fei@.discussions.microsoft.com> wrote in message
>> news:81056E87-078C-4E54-91EA-D2A7273B4554@.microsoft.com...
>> > After move the whole sql server databases to a new box, msdb shows
>> > suspect,
>> > the other databases all work fine.
>> >
>> > A select statement shows that the staus of msdb is 280.
>> >
>> > After I change the status to 24, it still does not work. I can't
>> > start
>> > SQLServerAgent now.
>> >
>> > Please help!!!
>> >
>> > thanks, Fei
>>
>>
>

msdb Restore......

I have restored the production msdb database on a test box. I can see my
entire DTS package and the scheduled jobs.
When I try to modify the job I am getting the following error.
Error 14274: Cannot add, update, or delete a job (or its steps or schedules)
that originated from an MSZSERVER. The job was not saved. OK Button
How to delete/update then?
SQL 2K.
Thank you,
Benjamin
Dear Benjamin,
Is the server was renamed from one name to another, if so see the
logins were in sync, another work around is
The best way to handle this problem after the rename process is to follow
these steps: 1. Rename the server back to the original name.
2. Script out all of the jobs and then delete them.
3. Rename the server to the new name.
4. Add back the jobs by running the script generated from step 2.
Or
1.Script the jobs in the server from where u backed up the msdb database.
2.Run the scripts in the new server.
for more details go through the following kb site
http://support.microsoft.com/default...b;en-us;281642
"Benjamin Nethan" wrote:

> I have restored the production msdb database on a test box. I can see my
> entire DTS package and the scheduled jobs.
> When I try to modify the job I am getting the following error.
> Error 14274: Cannot add, update, or delete a job (or its steps or schedules)
> that originated from an MSZSERVER. The job was not saved. OK Button
> How to delete/update then?
> SQL 2K.
> Thank you,
> Benjamin
>
>
>
|||You need to update the originating_server column in sysjobs to reflect the
name of the instance you restored the database to. You can use the following
code to do that http://sqldev.net/download/sqlagent/...ent_rename.sql
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Benjamin Nethan" <BNethan@.hotmail.com> wrote in message
news:e59AAE5pFHA.820@.TK2MSFTNGP09.phx.gbl...
>I have restored the production msdb database on a test box. I can see my
> entire DTS package and the scheduled jobs.
> When I try to modify the job I am getting the following error.
> Error 14274: Cannot add, update, or delete a job (or its steps or
> schedules)
> that originated from an MSZSERVER. The job was not saved. OK Button
> How to delete/update then?
> SQL 2K.
> Thank you,
> Benjamin
>
>

msdb Restore......

I have restored the production msdb database on a test box. I can see my
entire DTS package and the scheduled jobs.
When I try to modify the job I am getting the following error.
Error 14274: Cannot add, update, or delete a job (or its steps or schedules)
that originated from an MSZSERVER. The job was not saved. OK Button
How to delete/update then?
SQL 2K.
Thank you,
BenjaminDear Benjamin,
Is the server was renamed from one name to another, if so see the
logins were in sync, another work around is
The best way to handle this problem after the rename process is to follow
these steps: 1. Rename the server back to the original name.
2. Script out all of the jobs and then delete them.
3. Rename the server to the new name.
4. Add back the jobs by running the script generated from step 2.
Or
1.Script the jobs in the server from where u backed up the msdb database.
2.Run the scripts in the new server.
for more details go through the following kb site
http://support.microsoft.com/default.aspx?scid=kb;en-us;281642
"Benjamin Nethan" wrote:
> I have restored the production msdb database on a test box. I can see my
> entire DTS package and the scheduled jobs.
> When I try to modify the job I am getting the following error.
> Error 14274: Cannot add, update, or delete a job (or its steps or schedules)
> that originated from an MSZSERVER. The job was not saved. OK Button
> How to delete/update then?
> SQL 2K.
> Thank you,
> Benjamin
>
>
>|||You need to update the originating_server column in sysjobs to reflect the
name of the instance you restored the database to. You can use the following
code to do that http://sqldev.net/download/sqlagent/sp_sqlagent_rename.sql
--
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Benjamin Nethan" <BNethan@.hotmail.com> wrote in message
news:e59AAE5pFHA.820@.TK2MSFTNGP09.phx.gbl...
>I have restored the production msdb database on a test box. I can see my
> entire DTS package and the scheduled jobs.
> When I try to modify the job I am getting the following error.
> Error 14274: Cannot add, update, or delete a job (or its steps or
> schedules)
> that originated from an MSZSERVER. The job was not saved. OK Button
> How to delete/update then?
> SQL 2K.
> Thank you,
> Benjamin
>
>

msdb Restore......

I have restored the production msdb database on a test box. I can see my
entire DTS package and the scheduled jobs.
When I try to modify the job I am getting the following error.
Error 14274: Cannot add, update, or delete a job (or its steps or schedules)
that originated from an MSZSERVER. The job was not saved. OK Button
How to delete/update then?
SQL 2K.
Thank you,
BenjaminDear Benjamin,
Is the server was renamed from one name to another, if so see the
logins were in sync, another work around is
The best way to handle this problem after the rename process is to follow
these steps: 1. Rename the server back to the original name.
2. Script out all of the jobs and then delete them.
3. Rename the server to the new name.
4. Add back the jobs by running the script generated from step 2.
Or
1.Script the jobs in the server from where u backed up the msdb database.
2.Run the scripts in the new server.
for more details go through the following kb site
http://support.microsoft.com/defaul...kb;en-us;281642
"Benjamin Nethan" wrote:

> I have restored the production msdb database on a test box. I can see my
> entire DTS package and the scheduled jobs.
> When I try to modify the job I am getting the following error.
> Error 14274: Cannot add, update, or delete a job (or its steps or schedule
s)
> that originated from an MSZSERVER. The job was not saved. OK Button
> How to delete/update then?
> SQL 2K.
> Thank you,
> Benjamin
>
>
>|||You need to update the originating_server column in sysjobs to reflect the
name of the instance you restored the database to. You can use the following
code to do that http://sqldev.net/download/sqlagent...gent_rename.sql
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Benjamin Nethan" <BNethan@.hotmail.com> wrote in message
news:e59AAE5pFHA.820@.TK2MSFTNGP09.phx.gbl...
>I have restored the production msdb database on a test box. I can see my
> entire DTS package and the scheduled jobs.
> When I try to modify the job I am getting the following error.
> Error 14274: Cannot add, update, or delete a job (or its steps or
> schedules)
> that originated from an MSZSERVER. The job was not saved. OK Button
> How to delete/update then?
> SQL 2K.
> Thank you,
> Benjamin
>
>

msdb restore

Hello --
Using SQL 2000. When performing a trans log restore to our backup SQL box
the server locked up. After I got the server restarted the msdb was marked
'suspect'. I don't have a backup of the msdb. I can still perform
restores, but I get error message about the msdb. Do I need to re-install
SQL on this box? I'm not sure what to do (besides doing msdb backups from
now on). Any help would be appreciated. Thank you.Hi,
No need to install SQL Server.
Start SQL Server with Trace 3608 from command prompt
SQLSERVER -T3608 -m
Drop or detach the MSDB database and rebuild the MSDB using the installation
script(INSTMSDB.SQL) in the SLQ Server install folder. But after this
you need to create all your sql agent jobs manually. Please ensure that you
do a backup of MSDB database hereafter :)
One more solution-
Start SQL Server with Trace 3608 from command prompt
SQLSERVER -T3608 -m
From query analyzer Detach MSDB database, copy the files from the CD (in
x86\Data) and then attach this files.
Thanks
Hari
SQL Server MVP
"FRR" <FRR@.discussions.microsoft.com> wrote in message
news:51EACBD9-BB21-4FB6-9C2F-2A5C5B74D083@.microsoft.com...
> Hello --
> Using SQL 2000. When performing a trans log restore to our backup SQL box
> the server locked up. After I got the server restarted the msdb was
> marked
> 'suspect'. I don't have a backup of the msdb. I can still perform
> restores, but I get error message about the msdb. Do I need to re-install
> SQL on this box? I'm not sure what to do (besides doing msdb backups from
> now on). Any help would be appreciated. Thank you.

MSDB Permissions Error

Hi,
We've just upgraded a server to a new box and copied all of the settings
from the existing box. We are running a VB client front end, with COM+ as
middle tier and SQL Server 2000 as BE.
The COM+ account is running under a windows domain account (which is also in
the local server administrators group), but all connections to the SQL Serve
r
database are under an SQL login 'AppUser'.
We are just testing the new configuration but are getting all sorts of
errors in the VB client FE. First of all, the FE tries to submit a job and
received error
'SELECT permission denied on msdb.sysjobs'
Does anyone know the cause of this error. As far as I can see, all of the
permissions on our new server are the same as the previous server' The logi
n
AppUser seems to be in all the correct groups.
(Just for testing purposes, I've made 'AppUser' part of the db_owner
database role in both these databases which of course fixes the above errors
.
But I do not want to leave it like this!!)
Any advice appreciated
ThanksHas the guest account been disabled in the msdb database. In the msdb
database, in Query Analyzer run the following command :
Select * from sysusers where name = 'guest'
Check the hasdbaccess column. It should be 1. If not run the following in
the msdb database:
sp_grantdbaccess 'guest'
Rand
This posting is provided "as is" with no warranties and confers no rights.|||Hi Rand,
Thanks for response, i ran the SQL & 'hasdbaccess' column is flagged as 1.
Any other possibilities to check...?
Thanks
Dylan|||Check the permissions of the public role in the database.
Rand
This posting is provided "as is" with no warranties and confers no rights.

msdb is Suspect

Is am running SQL 2000 SP3 on a Win 2000 box.
My msdb is marked suspet. I ran sp_resetstatus and restarted SQL and
the dB is still suspect.
I found an article that recommends...
One approach would be to drop & recreate the msdb databases (see
instmsdb.sql and instserv.sql in the c:\mssql\install directory of your
sqlserver install). You would lose backup/restore histories, all
operators, scheduled tasks, etc. but would get it back up and running.
Is this the only solution? Is there a way to do this without loosing
my backup history?
TIA,
Larry...
Paul,
You are the man!!! This did the trick.
As always, thanks for your help!!!!
Larry...