MSDE 2000 mulituser on a single computer

The installation works fine, when I restarted the machine and login as an
administrator it works fine...
But when I logon as a normal user (whitout administravie rights) its no fun
anymore.
The "SQL Server Service Manager" is blank (no server or services), but I can
fill the fields with values and the service is started but they disappear
when i restart the machine, and the MSSQLSERVER service IS started!?!
But when I enable NetworkProtocols (with "Svrnetcn.exe") it works fine for
all...
Is there any other way to solve the problem?
Where can I find Microsofts documentation about this?
/Erik Fahlstrm
hi Erik,
"Erik Fahlstrm" <erik(dot)fahlstrom(at-sign)intentia(dot)se> ha scritto nel
messaggio news:%23mA1CJ3MEHA.684@.TK2MSFTNGP09.phx.gbl...
> The installation works fine, when I restarted the machine and login as an
> administrator it works fine...
> But when I logon as a normal user (whitout administravie rights) its no
fun
> anymore.
> The "SQL Server Service Manager" is blank (no server or services), but I
can
> fill the fields with values and the service is started but they disappear
> when i restart the machine, and the MSSQLSERVER service IS started!?!
> But when I enable NetworkProtocols (with "Svrnetcn.exe") it works fine for
> all...
> Is there any other way to solve the problem?
> Where can I find Microsofts documentation about this?
> /Erik Fahlstrm
this is a known issue as
http://support.microsoft.com/default...b;EN-US;814132 reports..
hth
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.7.0 - DbaMgr ver 0.53.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply

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 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 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 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...