Appreciate if anyone can help me on the following questions:
(1) Is MSDE necessary if we wish to install Windows SharePoint Team service
and/or MS Project Server?
(2) MSDE installation problems -- please read below.
Followed article
http://msdn.microsoft.com/library/de...stsql_84xl.asp
for many many times and never succeeded -- maybe just because I am new to
this.
Using example of the article - setup SAPWD="AStrongSAPwd"
What exactly show we put inside " "? A real strong password, or as
literally the same as in the example -- AStrongSAPwd?
Do we include " " or not?
I tried once with the exact thing as - setup SAPWD="AStrongSAPwd", word by
word, and the best thing that I could get from testing (based on
http://support.microsoft.com/default...36&Product=sql )
is to have the following result: 1>
And there is no instructions for what to do next in the article. I pressed
Enter, it will become 2> and go on. I typed something else, no response at
all.
Other times, it will become as the following - which i changed to the mixed
mode but still failed.
The following error message indicates that the computer that is running SQL
Server is set to Windows Authentication only:
Login failed for user 'sa'. Reason: Not associated with a trusted SQL Server
connection.
I also tried the section -
How to Change Your SA Password
Still wont work.
So your advise is deeply appreciated.
Thanks in advance.
hi,
"xfile" <cou-cou@.remove.nospam.com> ha scritto nel messaggio
news:%23JlIhmdsEHA.2720@.TK2MSFTNGP12.phx.gbl
> Hi:
> Appreciate if anyone can help me on the following questions:
> (1) Is MSDE necessary if we wish to install Windows SharePoint Team
> service and/or MS Project Server?
yes... I do think SharePoint installs it' own instance of a modified MSDE
release...
> (2) MSDE installation problems -- please read below.
> Followed article
>
http://msdn.microsoft.com/library/de...stsql_84xl.asp
> for many many times and never succeeded -- maybe just because I am
> new to this.
> Using example of the article - setup SAPWD="AStrongSAPwd"
> What exactly show we put inside " "? A real strong password, or as
> literally the same as in the example -- AStrongSAPwd?
your own strong password for the special SQL Server account known as "sa",
an administrative account that can not be dropped...
> Do we include " " or not?
yes
> I tried once with the exact thing as - setup SAPWD="AStrongSAPwd",
> word by word, and the best thing that I could get from testing (based
> on
> http://support.microsoft.com/default...36&Product=sql
> ) is to have the following result: 1>
>
:-|
if you resulted in oSql.exe output
1>
that means you do not have a password for "sa" Login
else you'd would have been pompted for a password like
c:\>osql -Usa
Password: [here caret blinks]
> And there is no instructions for what to do next in the article. I
> pressed Enter, it will become 2> and go on. I typed something else,
> no response at all.
if you want to (and should) set a strong password for your "sa" login,
please repeat the described steps as above..
then at the 1> prompt, type
1>sp_password @.old = NULL , @.new = 'yourStrongPassword' , @.loginame =
'sa' --hit return
2>GO -- hit return
GO is a special word that will execute all the statements preceding it as a
single batch...
obviously change
'yourStrongPassword'
with your own password...
> Other times, it will become as the following - which i changed to the
> mixed mode but still failed.
> --
> The following error message indicates that the computer that is
> running SQL Server is set to Windows Authentication only:
> Login failed for user 'sa'. Reason: Not associated with a trusted SQL
> Server connection.
> --
this must be managed via Windows registry modification, as described in
http://support.microsoft.com/default...us;Q285097...
stop and restart the MSDE instance service
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Hi:
Thanks for your kind response and I just installed another time before
reading your message, for which the installation appears to be successful.
I use the utility - DbaMGR2k and set it to use "Trusted NT connection" and I
can see all things are there. But I still could not figure out if the
password is correct or not.
I guess what I will try to do is to install again with the "mix mode" and
leave the password blank during installation.
Then I would follow your instructions to check again if the password is
blank, if so, using the following to set a password -
1>sp_password @.old = NULL , @.new = 'yourStrongPassword' , @.loginame =
> 'sa' --hit return
> 2>GO -- hit return
One more question about the strong password. Do we have to strictly follow
the strong password rules for choosing the password, or could we just use
some combinations of characters and numbers?
Thanks so much.
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it>
??:2t75bqF1s1tkjU1@.uni-berlin.de...
> hi,
> "xfile" <cou-cou@.remove.nospam.com> ha scritto nel messaggio
> news:%23JlIhmdsEHA.2720@.TK2MSFTNGP12.phx.gbl
> yes... I do think SharePoint installs it' own instance of a modified MSDE
> release...
> http://msdn.microsoft.com/library/de...stsql_84xl.asp
> your own strong password for the special SQL Server account known as "sa",
> an administrative account that can not be dropped...
>
> yes
>
> :-|
> if you resulted in oSql.exe output
> 1>
> that means you do not have a password for "sa" Login
> else you'd would have been pompted for a password like
> c:\>osql -Usa
> Password: [here caret blinks]
>
> if you want to (and should) set a strong password for your "sa" login,
> please repeat the described steps as above..
> then at the 1> prompt, type
> 1>sp_password @.old = NULL , @.new = 'yourStrongPassword' , @.loginame =
> 'sa' --hit return
> 2>GO -- hit return
> GO is a special word that will execute all the statements preceding it as
> a
> single batch...
> obviously change
> 'yourStrongPassword'
> with your own password...
>
> this must be managed via Windows registry modification, as described in
> http://support.microsoft.com/default...us;Q285097...
> stop and restart the MSDE instance service
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
|||Hi:
This is an update status -- it is done.
Use mixed mode and the following instructions for changing password, I am
able to reset the password to the one I wanted,
Thanks for the kind help
"xfile" <cou-cou@.remove.nospam.com>
??:uXSTNsesEHA.2664@.TK2MSFTNGP12.phx.gbl...
> Hi:
> Thanks for your kind response and I just installed another time before
> reading your message, for which the installation appears to be successful.
> I use the utility - DbaMGR2k and set it to use "Trusted NT connection" and
> I can see all things are there. But I still could not figure out if the
> password is correct or not.
> I guess what I will try to do is to install again with the "mix mode" and
> leave the password blank during installation.
> Then I would follow your instructions to check again if the password is
> blank, if so, using the following to set a password -
> 1>sp_password @.old = NULL , @.new = 'yourStrongPassword' , @.loginame =
> One more question about the strong password. Do we have to strictly
> follow the strong password rules for choosing the password, or could we
> just use some combinations of characters and numbers?
> Thanks so much.
>
>
>
> "Andrea Montanari" <andrea.sqlDMO@.virgilio.it>
> ??:2t75bqF1s1tkjU1@.uni-berlin.de...
>
|||hi,
"xfile" <cou-cou@.remove.nospam.com> ha scritto nel messaggio
news:uXSTNsesEHA.2664@.TK2MSFTNGP12.phx.gbl
>....
> One more question about the strong password. Do we have to strictly
> follow the strong password rules for choosing the password, or could
> we just use some combinations of characters and numbers?
>
you should use a combination of chars and digits... this will improve the
security of your pwd... and wathc about the lenght... not just a 4 or 5
chars lenght...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
sql
No comments:
Post a Comment