Application SQL Server installing problems

Hello Folks,
Managed to loose my SQL Server while uninstalling application and now the
server doesn't get installed while trying to run the application installer
again. Is there any way to locate traces of the old installation anyhow...
or what could be the case.
Is it possible to trace down for example C:\Program Files\Microsoft SQL
Server\80\Tools\Binn\sqlmangr.exe for example if the registry settings have
somehow been vanished?
After the uninstallation and regcleaning traces of SQL were hanging still
for example in the XP Home Services prompt.
Thanks
http://support.microsoft.com/default...b;en-us;290991
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Kaide" <kai.porvali@.kotiportti.fi> wrote in message news:OVDn0mbqFHA.4072@.TK2MSFTNGP09.phx.gbl...
> Hello Folks,
> Managed to loose my SQL Server while uninstalling application and now the
> server doesn't get installed while trying to run the application installer
> again. Is there any way to locate traces of the old installation anyhow...
> or what could be the case.
> Is it possible to trace down for example C:\Program Files\Microsoft SQL
> Server\80\Tools\Binn\sqlmangr.exe for example if the registry settings have
> somehow been vanished?
> After the uninstallation and regcleaning traces of SQL were hanging still
> for example in the XP Home Services prompt.
> Thanks
>
>
>
|||Thanks for your reply!
While editing values used, by Murphy, Regedit in the first faze. Is there
anything that could be done anymore or do I have to reinstall XP again.
Forgot to tell you that the first problems started after running repair
installation of XP. SQL just quit responding.
Best Regards!
Kaide
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> kirjoitti
viestiss:O4ZiyrgqFHA.2968@.TK2MSFTNGP10.phx.gbl... [vbcol=seagreen]
> http://support.microsoft.com/default...b;en-us;290991
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Kaide" <kai.porvali@.kotiportti.fi> wrote in message
> news:OVDn0mbqFHA.4072@.TK2MSFTNGP09.phx.gbl...
|||Not sure what you are saying. Do you want to remove all traces of SQL Server so you can install SQL
Server again? If so, the link I posted should help you.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Kaide" <kai.porvali@.kotiportti.fi> wrote in message news:OBkdQ79qFHA.2244@.tk2msftngp13.phx.gbl...
> Thanks for your reply!
> While editing values used, by Murphy, Regedit in the first faze. Is there anything that could be
> done anymore or do I have to reinstall XP again. Forgot to tell you that the first problems
> started after running repair installation of XP. SQL just quit responding.
> Best Regards!
> Kaide
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> kirjoitti
> viestiss:O4ZiyrgqFHA.2968@.TK2MSFTNGP10.phx.gbl...
>
|||Yes Tibor, and Thank You!
"Haste takes pleasure out of everything"! like they say. Respectivly, I
posted my question without checking all details...
Got server running after removing all known instances of the SQL and
reinstalling the application. I'm happy with the result that has bothered me
a lot during the last weeks.
Thanks' for your help once more! Even the software supplier couldn't help
with this issue even they got all info needed. (And this "Pineapple" company
should have a good customer support)!
Best Regards
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> kirjoitti
viestiss:uWBRKM%23qFHA.4044@.TK2MSFTNGP09.phx.gbl. ..
> Not sure what you are saying. Do you want to remove all traces of SQL
> Server so you can install SQL Server again? If so, the link I posted
> should help you.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Kaide" <kai.porvali@.kotiportti.fi> wrote in message
> news:OBkdQ79qFHA.2244@.tk2msftngp13.phx.gbl...
>
|||Top paraphrase another saying: "KB is your friend". :-)
Glad you sorted it.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Kaide" <kai.porvali@.kotiportti.fi> wrote in message news:OEHCnT$qFHA.3096@.TK2MSFTNGP15.phx.gbl...
> Yes Tibor, and Thank You!
> "Haste takes pleasure out of everything"! like they say. Respectivly, I posted my question without
> checking all details...
> Got server running after removing all known instances of the SQL and reinstalling the application.
> I'm happy with the result that has bothered me a lot during the last weeks.
> Thanks' for your help once more! Even the software supplier couldn't help with this issue even
> they got all info needed. (And this "Pineapple" company should have a good customer support)!
> Best Regards
>
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> kirjoitti
> viestiss:uWBRKM%23qFHA.4044@.TK2MSFTNGP09.phx.gbl. ..
>
|||Hello once more,
Hmm... KB is short for what... lacking a one letter propably?
Kaide
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> kirjoitti
viestiss:%23%23ahJ%23$qFHA.240@.tk2msftngp13.phx.g bl...
> Top paraphrase another saying: "KB is your friend". :-)
> Glad you sorted it.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Kaide" <kai.porvali@.kotiportti.fi> wrote in message
> news:OEHCnT$qFHA.3096@.TK2MSFTNGP15.phx.gbl...
>
|||KB = KnowledgeBase :-)
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Kaide" <kai.porvali@.kotiportti.fi> wrote in message news:%23$TUGRCrFHA.3736@.TK2MSFTNGP10.phx.gbl...
> Hello once more,
> Hmm... KB is short for what... lacking a one letter propably?
> Kaide
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> kirjoitti
> viestiss:%23%23ahJ%23$qFHA.240@.tk2msftngp13.phx.g bl...
>

Application sending email

Hi:
I would like to know security implications on two different ways to enable
an application to email alerts.
1. Installing outlook client for application to call.
2. Using CDOSYS to point to SMTP server and send email using AD
username/password.
Thanks for any input.Option 1 -very bad choice. Outlook has too many security issues to safely in
stall on a server.
Option 2. klutzy but will/could work But waitk there are better choices.
Option 3. SQL 2000 download xp_smtpmail from [url]http://www.sqldev.net/xp/xpsmtp.htm[/
url]
Option 3. SQL 2005 -Use the included smtp mail server. Look up sp_send_dbmai
l in Books on Line.
--
Arnie Rowland*
"To be successful, your heart must accompany your knowledge."
"Cindy" <Cindy@.discussions.microsoft.com> wrote in message news:943EC1D1-1E2A-413A-8DF5-A5F9
19125DD9@.microsoft.com...
> Hi:
> I would like to know security implications on two different ways to enable
> an application to email alerts.
>
> 1. Installing outlook client for application to call.
>
> 2. Using CDOSYS to point to SMTP server and send email using AD
> username/password.
>
> Thanks for any input.|||Thanks for the information, but can you point me to some specifics about the
Outlook security issues. I am bringing up new SQL database with accounting
package. Package developers want to install Outlook on SQL server (has to b
e
2000 not compatiable with 2005). Need facts to support my posiition. If i
have no choice but to install outlook how can I secure?
If CDOSYS is klutzy is it more secure than outlook?
Thanks, Cindy
"Arnie Rowland" wrote:
[vbcol=seagreen]
> Option 1 -very bad choice. Outlook has too many security issues to safely
install on a server.
> Option 2. klutzy but will/could work But waitk there are better choices.
> Option 3. SQL 2000 download xp_smtpmail from http://www.sqldev.net/xp/xpsmtp.htm

> Option 3. SQL 2005 -Use the included smtp mail server. Look up sp_send_dbm
ail in Books on Line.
> --
> Arnie Rowland*
> "To be successful, your heart must accompany your knowledge."
>
>
> "Cindy" <Cindy@.discussions.microsoft.com> wrote in message news:943EC1D1-1
E2A-413A-8DF5-A5F919125DD9@.microsoft.com...|||Here is some sources of information about Outlook/MAPI issues.
http://support.microsoft.com/defaul...b;en-us;Q315886
Top Causes of SQL Server Downtime (Item #2)
http://www.sqlmag.com/Article/Artic...rver_40011.html
http://www.karaszi.com/SQLServer/info_no_mapi.asp
Google for "SQL Server" + MAPI + problems
Microsoft has 'dumped' MAPI for SQL Server 2005, instead using a built in
SMTP client.
--> check out xp_smtpmail. It's very easy to set up and very easy to use.
<--
The question to raise, "Is it better to use a mail client that has no
documented problems running or SQL Server, or a mail client that has a long
history of problems, including causing the SQL Server to fail."
What difference to the developers as long as there is a flexible way to send
messages.
And your last question, how can you secure Outlook... possibly never.
Recognize that as the number one mail client, it is the biggest target for
any hackers (new expliots are regularly found), and what do hackers want to
hack? -data servers.
If you can't tell, I have a 'little' bias on this issue... Outlook/MAPI on
SQL Server is a big AND unnecesssary mistake.
Arnie Rowland*
"To be successful, your heart must accompany your knowledge."
"Cindy" <Cindy@.discussions.microsoft.com> wrote in message
news:464BAE44-2A86-4DDA-AF3C-9726B9AFAC03@.microsoft.com...[vbcol=seagreen]
> Thanks for the information, but can you point me to some specifics about
> the
> Outlook security issues. I am bringing up new SQL database with
> accounting
> package. Package developers want to install Outlook on SQL server (has to
> be
> 2000 not compatiable with 2005). Need facts to support my posiition. If
> i
> have no choice but to install outlook how can I secure?
> If CDOSYS is klutzy is it more secure than outlook?
> Thanks, Cindy
> "Arnie Rowland" wrote:
>|||Thanks for the info.
Cindy
"Arnie Rowland" wrote:

> Here is some sources of information about Outlook/MAPI issues.
> http://support.microsoft.com/defaul...b;en-us;Q315886
> Top Causes of SQL Server Downtime (Item #2)
> http://www.sqlmag.com/Article/Artic...rver_40011.html
> http://www.karaszi.com/SQLServer/info_no_mapi.asp
> Google for "SQL Server" + MAPI + problems
> Microsoft has 'dumped' MAPI for SQL Server 2005, instead using a built in
> SMTP client.
> --> check out xp_smtpmail. It's very easy to set up and very easy to use.
> <--
> The question to raise, "Is it better to use a mail client that has no
> documented problems running or SQL Server, or a mail client that has a lon
g
> history of problems, including causing the SQL Server to fail."
> What difference to the developers as long as there is a flexible way to se
nd
> messages.
> And your last question, how can you secure Outlook... possibly never.
> Recognize that as the number one mail client, it is the biggest target for
> any hackers (new expliots are regularly found), and what do hackers want t
o
> hack? -data servers.
> If you can't tell, I have a 'little' bias on this issue... Outlook/MAPI on
> SQL Server is a big AND unnecesssary mistake.
> --
> Arnie Rowland*
> "To be successful, your heart must accompany your knowledge."
>
> "Cindy" <Cindy@.discussions.microsoft.com> wrote in message
> news:464BAE44-2A86-4DDA-AF3C-9726B9AFAC03@.microsoft.com...
>
>|||Understanding that Outlook has security issues, I personally have used SQL
Mail in the past with the Outlook client and had great success. Although it
may be one of the top reasons for 'downtime' (if you call a reboot
downtime), how much downtime is that? If you have 99.9% uptime and SQL Mail
is responsible for .1% downtime, is that acceptible? It was for me.
If you stay on top of your Outlook updates, restrict access to the xp_'s
(xp_sendmail, for example), and do your homework on SQL Mail, there is some
reward to offset the risk. There are factors that may sway you one way or
another depending on your situation.
My server sent an average of around 100 emails per minute - with SQL Mail
and the Outlook client.
"Cindy" <Cindy@.discussions.microsoft.com> wrote in message
news:943EC1D1-1E2A-413A-8DF5-A5F919125DD9@.microsoft.com...
> Hi:
> I would like to know security implications on two different ways to enable
> an application to email alerts.
> 1. Installing outlook client for application to call.
> 2. Using CDOSYS to point to SMTP server and send email using AD
> username/password.
> Thanks for any input.

Anyone use Litespeed?

I attempted installing yesterday on a cluster, and the installation
went fine, but when I kicked off the backup via Litespeed, I received
the following error...
[Microsoft][SQL Native Client][SQL Server]Failed to create the s
ecurity
environment for VDI. Ensure that the SQL Server Service account has
administrator access to this server. Note: Administrator privilege
can be restriced by registry/file and policy changes that can prevent
this operation from succeeding.
The SQL Service acct does have admin rights on the server. I installed
it as someone in the admin group. And I kicked off the backup as an
admin. I'm waiting for a call back from Imceda software on this, but
wanted to see if anyone out there had any ideas.Corey,
Might try making sure the SQL Agent is running under the SYSADMIN fixed
server role and that the domain user account for the SQL Server and SQL
Server Agent services have the necessary permissions to write backup files
to the disk.
HTH
Jerry
"Corey Bunch" <unc27932@.yahoo.com> wrote in message
news:1129206377.601106.49240@.z14g2000cwz.googlegroups.com...
>I attempted installing yesterday on a cluster, and the installation
> went fine, but when I kicked off the backup via Litespeed, I received
> the following error...
> [Microsoft][SQL Native Client][SQL Server]Failed to create the
security
> environment for VDI. Ensure that the SQL Server Service account has
> administrator access to this server. Note: Administrator privilege
> can be restriced by registry/file and policy changes that can prevent
> this operation from succeeding.
> The SQL Service acct does have admin rights on the server. I installed
> it as someone in the admin group. And I kicked off the backup as an
> admin. I'm waiting for a call back from Imceda software on this, but
> wanted to see if anyone out there had any ideas.
>|||The account for the agent is a local administrator, and it always
writes it native backups to the same spot, so still not sure why
Litespeed isn't working. I installed on a standalone server (not a
cluster) in the same domain, and pointed to the same backup loaction,
and everything worked. I've got a ticket in with Imceda, so I'll write
back with the results/findings.
Jerry Spivey wrote:[vbcol=seagreen]
> Corey,
> Might try making sure the SQL Agent is running under the SYSADMIN fixed
> server role and that the domain user account for the SQL Server and SQL
> Server Agent services have the necessary permissions to write backup files
> to the disk.
> HTH
> Jerry
> "Corey Bunch" <unc27932@.yahoo.com> wrote in message
> news:1129206377.601106.49240@.z14g2000cwz.googlegroups.com...

Anyone use Litespeed?

I attempted installing yesterday on a cluster, and the installation
went fine, but when I kicked off the backup via Litespeed, I received
the following error...
[Microsoft][SQL Native Client][SQL Server]Failed to create the security
environment for VDI. Ensure that the SQL Server Service account has
administrator access to this server. Note: Administrator privilege
can be restriced by registry/file and policy changes that can prevent
this operation from succeeding.
The SQL Service acct does have admin rights on the server. I installed
it as someone in the admin group. And I kicked off the backup as an
admin. I'm waiting for a call back from Imceda software on this, but
wanted to see if anyone out there had any ideas.Corey,
Might try making sure the SQL Agent is running under the SYSADMIN fixed
server role and that the domain user account for the SQL Server and SQL
Server Agent services have the necessary permissions to write backup files
to the disk.
HTH
Jerry
"Corey Bunch" <unc27932@.yahoo.com> wrote in message
news:1129206377.601106.49240@.z14g2000cwz.googlegroups.com...
>I attempted installing yesterday on a cluster, and the installation
> went fine, but when I kicked off the backup via Litespeed, I received
> the following error...
> [Microsoft][SQL Native Client][SQL Server]Failed to create the security
> environment for VDI. Ensure that the SQL Server Service account has
> administrator access to this server. Note: Administrator privilege
> can be restriced by registry/file and policy changes that can prevent
> this operation from succeeding.
> The SQL Service acct does have admin rights on the server. I installed
> it as someone in the admin group. And I kicked off the backup as an
> admin. I'm waiting for a call back from Imceda software on this, but
> wanted to see if anyone out there had any ideas.
>|||The account for the agent is a local administrator, and it always
writes it native backups to the same spot, so still not sure why
Litespeed isn't working. I installed on a standalone server (not a
cluster) in the same domain, and pointed to the same backup loaction,
and everything worked. I've got a ticket in with Imceda, so I'll write
back with the results/findings.
Jerry Spivey wrote:
> Corey,
> Might try making sure the SQL Agent is running under the SYSADMIN fixed
> server role and that the domain user account for the SQL Server and SQL
> Server Agent services have the necessary permissions to write backup files
> to the disk.
> HTH
> Jerry
> "Corey Bunch" <unc27932@.yahoo.com> wrote in message
> news:1129206377.601106.49240@.z14g2000cwz.googlegroups.com...
> >I attempted installing yesterday on a cluster, and the installation
> > went fine, but when I kicked off the backup via Litespeed, I received
> > the following error...
> >
> > [Microsoft][SQL Native Client][SQL Server]Failed to create the security
> > environment for VDI. Ensure that the SQL Server Service account has
> > administrator access to this server. Note: Administrator privilege
> > can be restriced by registry/file and policy changes that can prevent
> > this operation from succeeding.
> >
> > The SQL Service acct does have admin rights on the server. I installed
> > it as someone in the admin group. And I kicked off the backup as an
> > admin. I'm waiting for a call back from Imceda software on this, but
> > wanted to see if anyone out there had any ideas.
> >

Anyone use Litespeed?

I attempted installing yesterday on a cluster, and the installation
went fine, but when I kicked off the backup via Litespeed, I received
the following error...
[Microsoft][SQL Native Client][SQL Server]Failed to create the security
environment for VDI. Ensure that the SQL Server Service account has
administrator access to this server. Note: Administrator privilege
can be restriced by registry/file and policy changes that can prevent
this operation from succeeding.
The SQL Service acct does have admin rights on the server. I installed
it as someone in the admin group. And I kicked off the backup as an
admin. I'm waiting for a call back from Imceda software on this, but
wanted to see if anyone out there had any ideas.
Corey,
Might try making sure the SQL Agent is running under the SYSADMIN fixed
server role and that the domain user account for the SQL Server and SQL
Server Agent services have the necessary permissions to write backup files
to the disk.
HTH
Jerry
"Corey Bunch" <unc27932@.yahoo.com> wrote in message
news:1129206377.601106.49240@.z14g2000cwz.googlegro ups.com...
>I attempted installing yesterday on a cluster, and the installation
> went fine, but when I kicked off the backup via Litespeed, I received
> the following error...
> [Microsoft][SQL Native Client][SQL Server]Failed to create the security
> environment for VDI. Ensure that the SQL Server Service account has
> administrator access to this server. Note: Administrator privilege
> can be restriced by registry/file and policy changes that can prevent
> this operation from succeeding.
> The SQL Service acct does have admin rights on the server. I installed
> it as someone in the admin group. And I kicked off the backup as an
> admin. I'm waiting for a call back from Imceda software on this, but
> wanted to see if anyone out there had any ideas.
>
|||The account for the agent is a local administrator, and it always
writes it native backups to the same spot, so still not sure why
Litespeed isn't working. I installed on a standalone server (not a
cluster) in the same domain, and pointed to the same backup loaction,
and everything worked. I've got a ticket in with Imceda, so I'll write
back with the results/findings.
Jerry Spivey wrote:[vbcol=seagreen]
> Corey,
> Might try making sure the SQL Agent is running under the SYSADMIN fixed
> server role and that the domain user account for the SQL Server and SQL
> Server Agent services have the necessary permissions to write backup files
> to the disk.
> HTH
> Jerry
> "Corey Bunch" <unc27932@.yahoo.com> wrote in message
> news:1129206377.601106.49240@.z14g2000cwz.googlegro ups.com...