I installed SQL2005 (Standard Edition - 32 bit) for the 1st time and it
seemed to install fine. However, I wasn't prompted for licensing info (per
processor or per
seat) as SQL2000 does. Did I miss an option somewhere? The licensetype is
now disabled and numlicenses is now null.
Also unlike the SQL2000 install, I didn't see where you have the option to
put the database files (for master, msdb) should you not want them under
C:\program files.
Thanks for any help.
Ron
>I installed SQL2005 (Standard Edition - 32 bit) for the 1st time and it
> seemed to install fine. However, I wasn't prompted for licensing info
> (per
> processor or per
> seat) as SQL2000 does. Did I miss an option somewhere? The licensetype
> is
> now disabled and numlicenses is now null.
Sounds like you installed an MSDN version, in which case, licensing is
disabled. MSDN versions are for testing and development, and processor/CAL
licensing becomes irrelevant. You should not be running the MSDN version of
SQL Server on a machine where licensing is a concern.
> Also unlike the SQL2000 install, I didn't see where you have the option to
> put the database files (for master, msdb) should you not want them under
> C:\program files.
That option is there, it's just not front and center... it's in one of the
options tabs where you breakdown all of the installable features.
A
|||I really don't see any indication that it's an MSDN version. The CDs show:
On left hand size -
English
Microsoft SQL Server 2005
Standard Edition
(32 Bit)
(Disc 1 of 2)
On right hand size-
December 2005
Servers
Servers
Application
It also reads Microsoft Licensing in several places. No mention of MSDN.
"Aaron Bertrand [SQL Server MVP]" wrote:
> Sounds like you installed an MSDN version, in which case, licensing is
> disabled. MSDN versions are for testing and development, and processor/CAL
> licensing becomes irrelevant. You should not be running the MSDN version of
> SQL Server on a machine where licensing is a concern.
>
> That option is there, it's just not front and center... it's in one of the
> options tabs where you breakdown all of the installable features.
> A
>
>
|||>I really don't see any indication that it's an MSDN version. The CDs show:
> On left hand size -
> English
> Microsoft SQL Server 2005
> Standard Edition
> (32 Bit)
> (Disc 1 of 2)
> On right hand size-
> December 2005
> Servers
> Servers
> Application
> It also reads Microsoft Licensing in several places. No mention of MSDN.
Does it say "Not for resale" or "Not for Retail" or "NFR" or "Not for OEM
Distribution" anywhere on the disc?
There are a few obscure cases where licensing becomes disabled, but 99% of
the time it's because it's an intentionall crippled edition.
A
|||Yes, it does show "Not for OEM or retail distribution" in the smaller print.
Should I be using another version?
"Aaron Bertrand [SQL Server MVP]" wrote:
> Does it say "Not for resale" or "Not for Retail" or "NFR" or "Not for OEM
> Distribution" anywhere on the disc?
> There are a few obscure cases where licensing becomes disabled, but 99% of
> the time it's because it's an intentionall crippled edition.
> A
>
>
|||> Yes, it does show "Not for OEM or retail distribution" in the smaller
> print.
> Should I be using another version?
I am not sure what you are using it for, if you require licensing, what your
compliance status is, whether it's personal or company, etc. If you are
using this for production then yes you should have official licenses I am
sure.
|||I'm told we have Volume Licensing and the CDs were not MSDN. I uninstalled
sql2005 and downloaded the SQL2005 standard edition via the MVLS website. I
installed that version and still no prompt for licensing (asking for per
processor or per seat).
The licensetype is disabled and numlicenses is null.
As this will eventually be a production server so I'm concerned that all
will be well. Since I'm convinced we are properly licensed, should I be
concerned as to the values in the server property setting?
Thanks again.
Ron
"Aaron Bertrand [SQL Server MVP]" wrote:
> I am not sure what you are using it for, if you require licensing, what your
> compliance status is, whether it's personal or company, etc. If you are
> using this for production then yes you should have official licenses I am
> sure.
>
>
|||SQL Server 2005 no longer tracks license information. The thinking at the
time this decision was made was that since license restrictions never were
enforced, eliminating the license information would reduce the number of
support calls generated when someone entered the wrong data or wanted to
switch license types. The license information columns weren't removed from
the system tables to keep from breaking applications that depend on them -
that's the normal deprecation policy - so they are still there but contain
no useful information. Now SQL works like most other MS server products -
the license is only a paper document that you need to have if you get
audited.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Ron" <Ron@.discussions.microsoft.com> wrote in message
news:734EF6A3-B060-452B-B505-6DBE4C601BA6@.microsoft.com...[vbcol=seagreen]
> I'm told we have Volume Licensing and the CDs were not MSDN. I
> uninstalled
> sql2005 and downloaded the SQL2005 standard edition via the MVLS website.
> I
> installed that version and still no prompt for licensing (asking for per
> processor or per seat).
> The licensetype is disabled and numlicenses is null.
> As this will eventually be a production server so I'm concerned that all
> will be well. Since I'm convinced we are properly licensed, should I be
> concerned as to the values in the server property setting?
> Thanks again.
> Ron
> "Aaron Bertrand [SQL Server MVP]" wrote:
Showing posts with label standard. Show all posts
Showing posts with label standard. Show all posts
Friday, March 30, 2012
Install question
I installed SQL2005 (Standard Edition - 32 bit) for the 1st time and it
seemed to install fine. However, I wasn't prompted for licensing info (per
processor or per
seat) as SQL2000 does. Did I miss an option somewhere? The licensetype is
now disabled and numlicenses is now null.
Also unlike the SQL2000 install, I didn't see where you have the option to
put the database files (for master, msdb) should you not want them under
C:\program files.
Thanks for any help.
Ron>I installed SQL2005 (Standard Edition - 32 bit) for the 1st time and it
> seemed to install fine. However, I wasn't prompted for licensing info
> (per
> processor or per
> seat) as SQL2000 does. Did I miss an option somewhere? The licensetype
> is
> now disabled and numlicenses is now null.
Sounds like you installed an MSDN version, in which case, licensing is
disabled. MSDN versions are for testing and development, and processor/CAL
licensing becomes irrelevant. You should not be running the MSDN version of
SQL Server on a machine where licensing is a concern.
> Also unlike the SQL2000 install, I didn't see where you have the option to
> put the database files (for master, msdb) should you not want them under
> C:\program files.
That option is there, it's just not front and center... it's in one of the
options tabs where you breakdown all of the installable features.
A|||I really don't see any indication that it's an MSDN version. The CDs show:
On left hand size -
English
Microsoft SQL Server 2005
Standard Edition
(32 Bit)
(Disc 1 of 2)
On right hand size-
December 2005
Servers
Servers
Application
It also reads Microsoft Licensing in several places. No mention of MSDN.
"Aaron Bertrand [SQL Server MVP]" wrote:
> Sounds like you installed an MSDN version, in which case, licensing is
> disabled. MSDN versions are for testing and development, and processor/CA
L
> licensing becomes irrelevant. You should not be running the MSDN version
of
> SQL Server on a machine where licensing is a concern.
>
> That option is there, it's just not front and center... it's in one of the
> options tabs where you breakdown all of the installable features.
> A
>
>|||>I really don't see any indication that it's an MSDN version. The CDs show:
> On left hand size -
> English
> Microsoft SQL Server 2005
> Standard Edition
> (32 Bit)
> (Disc 1 of 2)
> On right hand size-
> December 2005
> Servers
> Servers
> Application
> It also reads Microsoft Licensing in several places. No mention of MSDN.
Does it say "Not for resale" or "Not for Retail" or "NFR" or "Not for OEM
Distribution" anywhere on the disc?
There are a few obscure cases where licensing becomes disabled, but 99% of
the time it's because it's an intentionall crippled edition.
A|||Yes, it does show "Not for OEM or retail distribution" in the smaller print.
Should I be using another version?
"Aaron Bertrand [SQL Server MVP]" wrote:
> Does it say "Not for resale" or "Not for Retail" or "NFR" or "Not for OEM
> Distribution" anywhere on the disc?
> There are a few obscure cases where licensing becomes disabled, but 99% of
> the time it's because it's an intentionall crippled edition.
> A
>
>|||> Yes, it does show "Not for OEM or retail distribution" in the smaller
> print.
> Should I be using another version?
I am not sure what you are using it for, if you require licensing, what your
compliance status is, whether it's personal or company, etc. If you are
using this for production then yes you should have official licenses I am
sure.|||I'm told we have Volume Licensing and the CDs were not MSDN. I uninstalled
sql2005 and downloaded the SQL2005 standard edition via the MVLS website. I
installed that version and still no prompt for licensing (asking for per
processor or per seat).
The licensetype is disabled and numlicenses is null.
As this will eventually be a production server so I'm concerned that all
will be well. Since I'm convinced we are properly licensed, should I be
concerned as to the values in the server property setting?
Thanks again.
Ron
"Aaron Bertrand [SQL Server MVP]" wrote:
> I am not sure what you are using it for, if you require licensing, what yo
ur
> compliance status is, whether it's personal or company, etc. If you are
> using this for production then yes you should have official licenses I am
> sure.
>
>|||SQL Server 2005 no longer tracks license information. The thinking at the
time this decision was made was that since license restrictions never were
enforced, eliminating the license information would reduce the number of
support calls generated when someone entered the wrong data or wanted to
switch license types. The license information columns weren't removed from
the system tables to keep from breaking applications that depend on them -
that's the normal deprecation policy - so they are still there but contain
no useful information. Now SQL works like most other MS server products -
the license is only a paper document that you need to have if you get
audited.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Ron" <Ron@.discussions.microsoft.com> wrote in message
news:734EF6A3-B060-452B-B505-6DBE4C601BA6@.microsoft.com...[vbcol=seagreen]
> I'm told we have Volume Licensing and the CDs were not MSDN. I
> uninstalled
> sql2005 and downloaded the SQL2005 standard edition via the MVLS website.
> I
> installed that version and still no prompt for licensing (asking for per
> processor or per seat).
> The licensetype is disabled and numlicenses is null.
> As this will eventually be a production server so I'm concerned that all
> will be well. Since I'm convinced we are properly licensed, should I be
> concerned as to the values in the server property setting?
> Thanks again.
> Ron
> "Aaron Bertrand [SQL Server MVP]" wrote:
>
seemed to install fine. However, I wasn't prompted for licensing info (per
processor or per
seat) as SQL2000 does. Did I miss an option somewhere? The licensetype is
now disabled and numlicenses is now null.
Also unlike the SQL2000 install, I didn't see where you have the option to
put the database files (for master, msdb) should you not want them under
C:\program files.
Thanks for any help.
Ron>I installed SQL2005 (Standard Edition - 32 bit) for the 1st time and it
> seemed to install fine. However, I wasn't prompted for licensing info
> (per
> processor or per
> seat) as SQL2000 does. Did I miss an option somewhere? The licensetype
> is
> now disabled and numlicenses is now null.
Sounds like you installed an MSDN version, in which case, licensing is
disabled. MSDN versions are for testing and development, and processor/CAL
licensing becomes irrelevant. You should not be running the MSDN version of
SQL Server on a machine where licensing is a concern.
> Also unlike the SQL2000 install, I didn't see where you have the option to
> put the database files (for master, msdb) should you not want them under
> C:\program files.
That option is there, it's just not front and center... it's in one of the
options tabs where you breakdown all of the installable features.
A|||I really don't see any indication that it's an MSDN version. The CDs show:
On left hand size -
English
Microsoft SQL Server 2005
Standard Edition
(32 Bit)
(Disc 1 of 2)
On right hand size-
December 2005
Servers
Servers
Application
It also reads Microsoft Licensing in several places. No mention of MSDN.
"Aaron Bertrand [SQL Server MVP]" wrote:
> Sounds like you installed an MSDN version, in which case, licensing is
> disabled. MSDN versions are for testing and development, and processor/CA
L
> licensing becomes irrelevant. You should not be running the MSDN version
of
> SQL Server on a machine where licensing is a concern.
>
> That option is there, it's just not front and center... it's in one of the
> options tabs where you breakdown all of the installable features.
> A
>
>|||>I really don't see any indication that it's an MSDN version. The CDs show:
> On left hand size -
> English
> Microsoft SQL Server 2005
> Standard Edition
> (32 Bit)
> (Disc 1 of 2)
> On right hand size-
> December 2005
> Servers
> Servers
> Application
> It also reads Microsoft Licensing in several places. No mention of MSDN.
Does it say "Not for resale" or "Not for Retail" or "NFR" or "Not for OEM
Distribution" anywhere on the disc?
There are a few obscure cases where licensing becomes disabled, but 99% of
the time it's because it's an intentionall crippled edition.
A|||Yes, it does show "Not for OEM or retail distribution" in the smaller print.
Should I be using another version?
"Aaron Bertrand [SQL Server MVP]" wrote:
> Does it say "Not for resale" or "Not for Retail" or "NFR" or "Not for OEM
> Distribution" anywhere on the disc?
> There are a few obscure cases where licensing becomes disabled, but 99% of
> the time it's because it's an intentionall crippled edition.
> A
>
>|||> Yes, it does show "Not for OEM or retail distribution" in the smaller
> print.
> Should I be using another version?
I am not sure what you are using it for, if you require licensing, what your
compliance status is, whether it's personal or company, etc. If you are
using this for production then yes you should have official licenses I am
sure.|||I'm told we have Volume Licensing and the CDs were not MSDN. I uninstalled
sql2005 and downloaded the SQL2005 standard edition via the MVLS website. I
installed that version and still no prompt for licensing (asking for per
processor or per seat).
The licensetype is disabled and numlicenses is null.
As this will eventually be a production server so I'm concerned that all
will be well. Since I'm convinced we are properly licensed, should I be
concerned as to the values in the server property setting?
Thanks again.
Ron
"Aaron Bertrand [SQL Server MVP]" wrote:
> I am not sure what you are using it for, if you require licensing, what yo
ur
> compliance status is, whether it's personal or company, etc. If you are
> using this for production then yes you should have official licenses I am
> sure.
>
>|||SQL Server 2005 no longer tracks license information. The thinking at the
time this decision was made was that since license restrictions never were
enforced, eliminating the license information would reduce the number of
support calls generated when someone entered the wrong data or wanted to
switch license types. The license information columns weren't removed from
the system tables to keep from breaking applications that depend on them -
that's the normal deprecation policy - so they are still there but contain
no useful information. Now SQL works like most other MS server products -
the license is only a paper document that you need to have if you get
audited.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Ron" <Ron@.discussions.microsoft.com> wrote in message
news:734EF6A3-B060-452B-B505-6DBE4C601BA6@.microsoft.com...[vbcol=seagreen]
> I'm told we have Volume Licensing and the CDs were not MSDN. I
> uninstalled
> sql2005 and downloaded the SQL2005 standard edition via the MVLS website.
> I
> installed that version and still no prompt for licensing (asking for per
> processor or per seat).
> The licensetype is disabled and numlicenses is null.
> As this will eventually be a production server so I'm concerned that all
> will be well. Since I'm convinced we are properly licensed, should I be
> concerned as to the values in the server property setting?
> Thanks again.
> Ron
> "Aaron Bertrand [SQL Server MVP]" wrote:
>
Wednesday, March 28, 2012
Install Package: VB6.0 w/ SQL Server 2000
Hello,
I want to upgrade my Access 2003 app to have a
VB 6.0 front-end and SQL Server 2000 Standard back-end, that I want
to sell on the market. I do not want to use MSDE
because of the 2GB limitation. My questions are:
1) will my customers have to purchase SQL Server 2000?
(or me, and then give them the copy w/ my app).
2) what is the best way to wrap this up in an install
package? I already have InstallShield Express 4.0
and SageKey's Access 2003 MSI Wizard; am investigating
if these will let me include SQL Server. . . any ideas
on how to mass-sell something w/ SQL Server back-end?
Thanks,
Christy Warner.
Christy Warner
www.autoaudit.com
Christy Warner
www.autoaudit.com
"ChristyWarner" <cwarner@.autoaudit.com> wrote in message
news:DB69C611-0E69-47B1-B940-4FAB81DA9C36@.microsoft.com...
> Hello,
> I want to upgrade my Access 2003 app to have a
> VB 6.0 front-end and SQL Server 2000 Standard back-end, that I want
> to sell on the market. I do not want to use MSDE
> because of the 2GB limitation. My questions are:
Access suffers from the same 2 GB limitation on database size.
> 1) will my customers have to purchase SQL Server 2000?
> (or me, and then give them the copy w/ my app).
If MSDE is not an option, your customers should probably have SQL Server. I
wouldn't recommend buying a bunch of copies of SQL Server to bundle with
your app, as you don't necessarily know your clients' licensing needs, etc.
> 2) what is the best way to wrap this up in an install
> package? I already have InstallShield Express 4.0
> and SageKey's Access 2003 MSI Wizard; am investigating
> if these will let me include SQL Server. . . any ideas
> on how to mass-sell something w/ SQL Server back-end?
People mass-market SQL Server specific products all the time. You basically
need to test it on SQL Server and make sure you specify it in the system
requirements for your app. A quick question - are you selling to home users
or businesses? If you're selling to individual home users or small
businesses, you might reconsider using MSDE, as it is freely available, and
the 2 GB restriction shouldn't be so bad for an app that previously ran on
Access.
|||Yes, selling to businesses, hopefully larger ones, which is why
I'm switching to SQL Server.
When my customers install their SQL Server, can I still refer
to it in my VB code w/ the same connection string? e.g. server=(local),
or do I have to specify an exact server name that the customer
has assigned?
thanks,
Christy.
"Michael C#" wrote:
> "ChristyWarner" <cwarner@.autoaudit.com> wrote in message
> news:DB69C611-0E69-47B1-B940-4FAB81DA9C36@.microsoft.com...
> Access suffers from the same 2 GB limitation on database size.
>
> If MSDE is not an option, your customers should probably have SQL Server. I
> wouldn't recommend buying a bunch of copies of SQL Server to bundle with
> your app, as you don't necessarily know your clients' licensing needs, etc.
>
> People mass-market SQL Server specific products all the time. You basically
> need to test it on SQL Server and make sure you specify it in the system
> requirements for your app. A quick question - are you selling to home users
> or businesses? If you're selling to individual home users or small
> businesses, you might reconsider using MSDE, as it is freely available, and
> the 2 GB restriction shouldn't be so bad for an app that previously ran on
> Access.
>
>
|||It's best to give the customer an option to configure their SQL Server
settings themselves, either during Setup or within the app itself. If
you're planning to mass-market your app, you definitely need to allow for
changes to the connection settings somehow - not every business is going to
have their network configured the same way and you can't necessarily count
on the fact that they'll be running your app on the same box as SQL Server.
Additionally, they might be using SQL Authentication instead of Windows
Integrated, in which case they'll need to access the login
username/password, etc. And hard-coding your username/password into your
app is big security no-no; sticking the customer with a username/password
combo that might not meet their security policies and requirements is also
not a good thing.
"ChristyWarner" <cwarner@.autoaudit.com> wrote in message
news:43C2467F-8064-4822-9402-19482E8D3EE3@.microsoft.com...[vbcol=seagreen]
> Yes, selling to businesses, hopefully larger ones, which is why
> I'm switching to SQL Server.
> When my customers install their SQL Server, can I still refer
> to it in my VB code w/ the same connection string? e.g. server=(local),
> or do I have to specify an exact server name that the customer
> has assigned?
> thanks,
> Christy.
> "Michael C#" wrote:
I want to upgrade my Access 2003 app to have a
VB 6.0 front-end and SQL Server 2000 Standard back-end, that I want
to sell on the market. I do not want to use MSDE
because of the 2GB limitation. My questions are:
1) will my customers have to purchase SQL Server 2000?
(or me, and then give them the copy w/ my app).
2) what is the best way to wrap this up in an install
package? I already have InstallShield Express 4.0
and SageKey's Access 2003 MSI Wizard; am investigating
if these will let me include SQL Server. . . any ideas
on how to mass-sell something w/ SQL Server back-end?
Thanks,
Christy Warner.
Christy Warner
www.autoaudit.com
Christy Warner
www.autoaudit.com
"ChristyWarner" <cwarner@.autoaudit.com> wrote in message
news:DB69C611-0E69-47B1-B940-4FAB81DA9C36@.microsoft.com...
> Hello,
> I want to upgrade my Access 2003 app to have a
> VB 6.0 front-end and SQL Server 2000 Standard back-end, that I want
> to sell on the market. I do not want to use MSDE
> because of the 2GB limitation. My questions are:
Access suffers from the same 2 GB limitation on database size.
> 1) will my customers have to purchase SQL Server 2000?
> (or me, and then give them the copy w/ my app).
If MSDE is not an option, your customers should probably have SQL Server. I
wouldn't recommend buying a bunch of copies of SQL Server to bundle with
your app, as you don't necessarily know your clients' licensing needs, etc.
> 2) what is the best way to wrap this up in an install
> package? I already have InstallShield Express 4.0
> and SageKey's Access 2003 MSI Wizard; am investigating
> if these will let me include SQL Server. . . any ideas
> on how to mass-sell something w/ SQL Server back-end?
People mass-market SQL Server specific products all the time. You basically
need to test it on SQL Server and make sure you specify it in the system
requirements for your app. A quick question - are you selling to home users
or businesses? If you're selling to individual home users or small
businesses, you might reconsider using MSDE, as it is freely available, and
the 2 GB restriction shouldn't be so bad for an app that previously ran on
Access.
|||Yes, selling to businesses, hopefully larger ones, which is why
I'm switching to SQL Server.
When my customers install their SQL Server, can I still refer
to it in my VB code w/ the same connection string? e.g. server=(local),
or do I have to specify an exact server name that the customer
has assigned?
thanks,
Christy.
"Michael C#" wrote:
> "ChristyWarner" <cwarner@.autoaudit.com> wrote in message
> news:DB69C611-0E69-47B1-B940-4FAB81DA9C36@.microsoft.com...
> Access suffers from the same 2 GB limitation on database size.
>
> If MSDE is not an option, your customers should probably have SQL Server. I
> wouldn't recommend buying a bunch of copies of SQL Server to bundle with
> your app, as you don't necessarily know your clients' licensing needs, etc.
>
> People mass-market SQL Server specific products all the time. You basically
> need to test it on SQL Server and make sure you specify it in the system
> requirements for your app. A quick question - are you selling to home users
> or businesses? If you're selling to individual home users or small
> businesses, you might reconsider using MSDE, as it is freely available, and
> the 2 GB restriction shouldn't be so bad for an app that previously ran on
> Access.
>
>
|||It's best to give the customer an option to configure their SQL Server
settings themselves, either during Setup or within the app itself. If
you're planning to mass-market your app, you definitely need to allow for
changes to the connection settings somehow - not every business is going to
have their network configured the same way and you can't necessarily count
on the fact that they'll be running your app on the same box as SQL Server.
Additionally, they might be using SQL Authentication instead of Windows
Integrated, in which case they'll need to access the login
username/password, etc. And hard-coding your username/password into your
app is big security no-no; sticking the customer with a username/password
combo that might not meet their security policies and requirements is also
not a good thing.
"ChristyWarner" <cwarner@.autoaudit.com> wrote in message
news:43C2467F-8064-4822-9402-19482E8D3EE3@.microsoft.com...[vbcol=seagreen]
> Yes, selling to businesses, hopefully larger ones, which is why
> I'm switching to SQL Server.
> When my customers install their SQL Server, can I still refer
> to it in my VB code w/ the same connection string? e.g. server=(local),
> or do I have to specify an exact server name that the customer
> has assigned?
> thanks,
> Christy.
> "Michael C#" wrote:
Install Package: VB6.0 w/ SQL Server 2000
Hello,
I want to upgrade my Access 2003 app to have a
VB 6.0 front-end and SQL Server 2000 Standard back-end, that I want
to sell on the market. I do not want to use MSDE
because of the 2GB limitation. My questions are:
1) will my customers have to purchase SQL Server 2000?
(or me, and then give them the copy w/ my app).
2) what is the best way to wrap this up in an install
package? I already have InstallShield Express 4.0
and SageKey's Access 2003 MSI Wizard; am investigating
if these will let me include SQL Server. . . any ideas
on how to mass-sell something w/ SQL Server back-end'
Thanks,
Christy Warner.
Christy Warner
www.autoaudit.com
Christy Warner
www.autoaudit.com"ChristyWarner" <cwarner@.autoaudit.com> wrote in message
news:DB69C611-0E69-47B1-B940-4FAB81DA9C36@.microsoft.com...
> Hello,
> I want to upgrade my Access 2003 app to have a
> VB 6.0 front-end and SQL Server 2000 Standard back-end, that I want
> to sell on the market. I do not want to use MSDE
> because of the 2GB limitation. My questions are:
Access suffers from the same 2 GB limitation on database size.
> 1) will my customers have to purchase SQL Server 2000?
> (or me, and then give them the copy w/ my app).
If MSDE is not an option, your customers should probably have SQL Server. I
wouldn't recommend buying a bunch of copies of SQL Server to bundle with
your app, as you don't necessarily know your clients' licensing needs, etc.
> 2) what is the best way to wrap this up in an install
> package? I already have InstallShield Express 4.0
> and SageKey's Access 2003 MSI Wizard; am investigating
> if these will let me include SQL Server. . . any ideas
> on how to mass-sell something w/ SQL Server back-end'
People mass-market SQL Server specific products all the time. You basically
need to test it on SQL Server and make sure you specify it in the system
requirements for your app. A quick question - are you selling to home users
or businesses? If you're selling to individual home users or small
businesses, you might reconsider using MSDE, as it is freely available, and
the 2 GB restriction shouldn't be so bad for an app that previously ran on
Access.|||Yes, selling to businesses, hopefully larger ones, which is why
I'm switching to SQL Server.
When my customers install their SQL Server, can I still refer
to it in my VB code w/ the same connection string? e.g. server=(local),
or do I have to specify an exact server name that the customer
has assigned?
thanks,
Christy.
"Michael C#" wrote:
> "ChristyWarner" <cwarner@.autoaudit.com> wrote in message
> news:DB69C611-0E69-47B1-B940-4FAB81DA9C36@.microsoft.com...
> Access suffers from the same 2 GB limitation on database size.
>
> If MSDE is not an option, your customers should probably have SQL Server.
I
> wouldn't recommend buying a bunch of copies of SQL Server to bundle with
> your app, as you don't necessarily know your clients' licensing needs, etc
.
>
> People mass-market SQL Server specific products all the time. You basical
ly
> need to test it on SQL Server and make sure you specify it in the system
> requirements for your app. A quick question - are you selling to home use
rs
> or businesses? If you're selling to individual home users or small
> businesses, you might reconsider using MSDE, as it is freely available, an
d
> the 2 GB restriction shouldn't be so bad for an app that previously ran on
> Access.
>
>|||It's best to give the customer an option to configure their SQL Server
settings themselves, either during Setup or within the app itself. If
you're planning to mass-market your app, you definitely need to allow for
changes to the connection settings somehow - not every business is going to
have their network configured the same way and you can't necessarily count
on the fact that they'll be running your app on the same box as SQL Server.
Additionally, they might be using SQL Authentication instead of Windows
Integrated, in which case they'll need to access the login
username/password, etc. And hard-coding your username/password into your
app is big security no-no; sticking the customer with a username/password
combo that might not meet their security policies and requirements is also
not a good thing.
"ChristyWarner" <cwarner@.autoaudit.com> wrote in message
news:43C2467F-8064-4822-9402-19482E8D3EE3@.microsoft.com...[vbcol=seagreen]
> Yes, selling to businesses, hopefully larger ones, which is why
> I'm switching to SQL Server.
> When my customers install their SQL Server, can I still refer
> to it in my VB code w/ the same connection string? e.g. server=(local),
> or do I have to specify an exact server name that the customer
> has assigned?
> thanks,
> Christy.
> "Michael C#" wrote:
>
I want to upgrade my Access 2003 app to have a
VB 6.0 front-end and SQL Server 2000 Standard back-end, that I want
to sell on the market. I do not want to use MSDE
because of the 2GB limitation. My questions are:
1) will my customers have to purchase SQL Server 2000?
(or me, and then give them the copy w/ my app).
2) what is the best way to wrap this up in an install
package? I already have InstallShield Express 4.0
and SageKey's Access 2003 MSI Wizard; am investigating
if these will let me include SQL Server. . . any ideas
on how to mass-sell something w/ SQL Server back-end'
Thanks,
Christy Warner.
Christy Warner
www.autoaudit.com
Christy Warner
www.autoaudit.com"ChristyWarner" <cwarner@.autoaudit.com> wrote in message
news:DB69C611-0E69-47B1-B940-4FAB81DA9C36@.microsoft.com...
> Hello,
> I want to upgrade my Access 2003 app to have a
> VB 6.0 front-end and SQL Server 2000 Standard back-end, that I want
> to sell on the market. I do not want to use MSDE
> because of the 2GB limitation. My questions are:
Access suffers from the same 2 GB limitation on database size.
> 1) will my customers have to purchase SQL Server 2000?
> (or me, and then give them the copy w/ my app).
If MSDE is not an option, your customers should probably have SQL Server. I
wouldn't recommend buying a bunch of copies of SQL Server to bundle with
your app, as you don't necessarily know your clients' licensing needs, etc.
> 2) what is the best way to wrap this up in an install
> package? I already have InstallShield Express 4.0
> and SageKey's Access 2003 MSI Wizard; am investigating
> if these will let me include SQL Server. . . any ideas
> on how to mass-sell something w/ SQL Server back-end'
People mass-market SQL Server specific products all the time. You basically
need to test it on SQL Server and make sure you specify it in the system
requirements for your app. A quick question - are you selling to home users
or businesses? If you're selling to individual home users or small
businesses, you might reconsider using MSDE, as it is freely available, and
the 2 GB restriction shouldn't be so bad for an app that previously ran on
Access.|||Yes, selling to businesses, hopefully larger ones, which is why
I'm switching to SQL Server.
When my customers install their SQL Server, can I still refer
to it in my VB code w/ the same connection string? e.g. server=(local),
or do I have to specify an exact server name that the customer
has assigned?
thanks,
Christy.
"Michael C#" wrote:
> "ChristyWarner" <cwarner@.autoaudit.com> wrote in message
> news:DB69C611-0E69-47B1-B940-4FAB81DA9C36@.microsoft.com...
> Access suffers from the same 2 GB limitation on database size.
>
> If MSDE is not an option, your customers should probably have SQL Server.
I
> wouldn't recommend buying a bunch of copies of SQL Server to bundle with
> your app, as you don't necessarily know your clients' licensing needs, etc
.
>
> People mass-market SQL Server specific products all the time. You basical
ly
> need to test it on SQL Server and make sure you specify it in the system
> requirements for your app. A quick question - are you selling to home use
rs
> or businesses? If you're selling to individual home users or small
> businesses, you might reconsider using MSDE, as it is freely available, an
d
> the 2 GB restriction shouldn't be so bad for an app that previously ran on
> Access.
>
>|||It's best to give the customer an option to configure their SQL Server
settings themselves, either during Setup or within the app itself. If
you're planning to mass-market your app, you definitely need to allow for
changes to the connection settings somehow - not every business is going to
have their network configured the same way and you can't necessarily count
on the fact that they'll be running your app on the same box as SQL Server.
Additionally, they might be using SQL Authentication instead of Windows
Integrated, in which case they'll need to access the login
username/password, etc. And hard-coding your username/password into your
app is big security no-no; sticking the customer with a username/password
combo that might not meet their security policies and requirements is also
not a good thing.
"ChristyWarner" <cwarner@.autoaudit.com> wrote in message
news:43C2467F-8064-4822-9402-19482E8D3EE3@.microsoft.com...[vbcol=seagreen]
> Yes, selling to businesses, hopefully larger ones, which is why
> I'm switching to SQL Server.
> When my customers install their SQL Server, can I still refer
> to it in my VB code w/ the same connection string? e.g. server=(local),
> or do I have to specify an exact server name that the customer
> has assigned?
> thanks,
> Christy.
> "Michael C#" wrote:
>
Install Package: VB6.0 w/ SQL Server 2000
Hello,
I want to upgrade my Access 2003 app to have a
VB 6.0 front-end and SQL Server 2000 Standard back-end, that I want
to sell on the market. I do not want to use MSDE
because of the 2GB limitation. My questions are:
1) will my customers have to purchase SQL Server 2000?
(or me, and then give them the copy w/ my app).
2) what is the best way to wrap this up in an install
package? I already have InstallShield Express 4.0
and SageKey's Access 2003 MSI Wizard; am investigating
if these will let me include SQL Server. . . any ideas
on how to mass-sell something w/ SQL Server back-end'
Thanks,
Christy Warner.
--
Christy Warner
www.autoaudit.com
--
Christy Warner
www.autoaudit.com"ChristyWarner" <cwarner@.autoaudit.com> wrote in message
news:DB69C611-0E69-47B1-B940-4FAB81DA9C36@.microsoft.com...
> Hello,
> I want to upgrade my Access 2003 app to have a
> VB 6.0 front-end and SQL Server 2000 Standard back-end, that I want
> to sell on the market. I do not want to use MSDE
> because of the 2GB limitation. My questions are:
Access suffers from the same 2 GB limitation on database size.
> 1) will my customers have to purchase SQL Server 2000?
> (or me, and then give them the copy w/ my app).
If MSDE is not an option, your customers should probably have SQL Server. I
wouldn't recommend buying a bunch of copies of SQL Server to bundle with
your app, as you don't necessarily know your clients' licensing needs, etc.
> 2) what is the best way to wrap this up in an install
> package? I already have InstallShield Express 4.0
> and SageKey's Access 2003 MSI Wizard; am investigating
> if these will let me include SQL Server. . . any ideas
> on how to mass-sell something w/ SQL Server back-end'
People mass-market SQL Server specific products all the time. You basically
need to test it on SQL Server and make sure you specify it in the system
requirements for your app. A quick question - are you selling to home users
or businesses? If you're selling to individual home users or small
businesses, you might reconsider using MSDE, as it is freely available, and
the 2 GB restriction shouldn't be so bad for an app that previously ran on
Access.|||Yes, selling to businesses, hopefully larger ones, which is why
I'm switching to SQL Server.
When my customers install their SQL Server, can I still refer
to it in my VB code w/ the same connection string? e.g. server=(local),
or do I have to specify an exact server name that the customer
has assigned?
thanks,
Christy.
"Michael C#" wrote:
> "ChristyWarner" <cwarner@.autoaudit.com> wrote in message
> news:DB69C611-0E69-47B1-B940-4FAB81DA9C36@.microsoft.com...
> > Hello,
> >
> > I want to upgrade my Access 2003 app to have a
> > VB 6.0 front-end and SQL Server 2000 Standard back-end, that I want
> > to sell on the market. I do not want to use MSDE
> > because of the 2GB limitation. My questions are:
> Access suffers from the same 2 GB limitation on database size.
> > 1) will my customers have to purchase SQL Server 2000?
> > (or me, and then give them the copy w/ my app).
> If MSDE is not an option, your customers should probably have SQL Server. I
> wouldn't recommend buying a bunch of copies of SQL Server to bundle with
> your app, as you don't necessarily know your clients' licensing needs, etc.
> > 2) what is the best way to wrap this up in an install
> > package? I already have InstallShield Express 4.0
> > and SageKey's Access 2003 MSI Wizard; am investigating
> > if these will let me include SQL Server. . . any ideas
> > on how to mass-sell something w/ SQL Server back-end'
> People mass-market SQL Server specific products all the time. You basically
> need to test it on SQL Server and make sure you specify it in the system
> requirements for your app. A quick question - are you selling to home users
> or businesses? If you're selling to individual home users or small
> businesses, you might reconsider using MSDE, as it is freely available, and
> the 2 GB restriction shouldn't be so bad for an app that previously ran on
> Access.
>
>|||It's best to give the customer an option to configure their SQL Server
settings themselves, either during Setup or within the app itself. If
you're planning to mass-market your app, you definitely need to allow for
changes to the connection settings somehow - not every business is going to
have their network configured the same way and you can't necessarily count
on the fact that they'll be running your app on the same box as SQL Server.
Additionally, they might be using SQL Authentication instead of Windows
Integrated, in which case they'll need to access the login
username/password, etc. And hard-coding your username/password into your
app is big security no-no; sticking the customer with a username/password
combo that might not meet their security policies and requirements is also
not a good thing.
"ChristyWarner" <cwarner@.autoaudit.com> wrote in message
news:43C2467F-8064-4822-9402-19482E8D3EE3@.microsoft.com...
> Yes, selling to businesses, hopefully larger ones, which is why
> I'm switching to SQL Server.
> When my customers install their SQL Server, can I still refer
> to it in my VB code w/ the same connection string? e.g. server=(local),
> or do I have to specify an exact server name that the customer
> has assigned?
> thanks,
> Christy.
> "Michael C#" wrote:
>> "ChristyWarner" <cwarner@.autoaudit.com> wrote in message
>> news:DB69C611-0E69-47B1-B940-4FAB81DA9C36@.microsoft.com...
>> > Hello,
>> >
>> > I want to upgrade my Access 2003 app to have a
>> > VB 6.0 front-end and SQL Server 2000 Standard back-end, that I want
>> > to sell on the market. I do not want to use MSDE
>> > because of the 2GB limitation. My questions are:
>> Access suffers from the same 2 GB limitation on database size.
>> > 1) will my customers have to purchase SQL Server 2000?
>> > (or me, and then give them the copy w/ my app).
>> If MSDE is not an option, your customers should probably have SQL Server.
>> I
>> wouldn't recommend buying a bunch of copies of SQL Server to bundle with
>> your app, as you don't necessarily know your clients' licensing needs,
>> etc.
>> > 2) what is the best way to wrap this up in an install
>> > package? I already have InstallShield Express 4.0
>> > and SageKey's Access 2003 MSI Wizard; am investigating
>> > if these will let me include SQL Server. . . any ideas
>> > on how to mass-sell something w/ SQL Server back-end'
>> People mass-market SQL Server specific products all the time. You
>> basically
>> need to test it on SQL Server and make sure you specify it in the system
>> requirements for your app. A quick question - are you selling to home
>> users
>> or businesses? If you're selling to individual home users or small
>> businesses, you might reconsider using MSDE, as it is freely available,
>> and
>> the 2 GB restriction shouldn't be so bad for an app that previously ran
>> on
>> Access.
>>
I want to upgrade my Access 2003 app to have a
VB 6.0 front-end and SQL Server 2000 Standard back-end, that I want
to sell on the market. I do not want to use MSDE
because of the 2GB limitation. My questions are:
1) will my customers have to purchase SQL Server 2000?
(or me, and then give them the copy w/ my app).
2) what is the best way to wrap this up in an install
package? I already have InstallShield Express 4.0
and SageKey's Access 2003 MSI Wizard; am investigating
if these will let me include SQL Server. . . any ideas
on how to mass-sell something w/ SQL Server back-end'
Thanks,
Christy Warner.
--
Christy Warner
www.autoaudit.com
--
Christy Warner
www.autoaudit.com"ChristyWarner" <cwarner@.autoaudit.com> wrote in message
news:DB69C611-0E69-47B1-B940-4FAB81DA9C36@.microsoft.com...
> Hello,
> I want to upgrade my Access 2003 app to have a
> VB 6.0 front-end and SQL Server 2000 Standard back-end, that I want
> to sell on the market. I do not want to use MSDE
> because of the 2GB limitation. My questions are:
Access suffers from the same 2 GB limitation on database size.
> 1) will my customers have to purchase SQL Server 2000?
> (or me, and then give them the copy w/ my app).
If MSDE is not an option, your customers should probably have SQL Server. I
wouldn't recommend buying a bunch of copies of SQL Server to bundle with
your app, as you don't necessarily know your clients' licensing needs, etc.
> 2) what is the best way to wrap this up in an install
> package? I already have InstallShield Express 4.0
> and SageKey's Access 2003 MSI Wizard; am investigating
> if these will let me include SQL Server. . . any ideas
> on how to mass-sell something w/ SQL Server back-end'
People mass-market SQL Server specific products all the time. You basically
need to test it on SQL Server and make sure you specify it in the system
requirements for your app. A quick question - are you selling to home users
or businesses? If you're selling to individual home users or small
businesses, you might reconsider using MSDE, as it is freely available, and
the 2 GB restriction shouldn't be so bad for an app that previously ran on
Access.|||Yes, selling to businesses, hopefully larger ones, which is why
I'm switching to SQL Server.
When my customers install their SQL Server, can I still refer
to it in my VB code w/ the same connection string? e.g. server=(local),
or do I have to specify an exact server name that the customer
has assigned?
thanks,
Christy.
"Michael C#" wrote:
> "ChristyWarner" <cwarner@.autoaudit.com> wrote in message
> news:DB69C611-0E69-47B1-B940-4FAB81DA9C36@.microsoft.com...
> > Hello,
> >
> > I want to upgrade my Access 2003 app to have a
> > VB 6.0 front-end and SQL Server 2000 Standard back-end, that I want
> > to sell on the market. I do not want to use MSDE
> > because of the 2GB limitation. My questions are:
> Access suffers from the same 2 GB limitation on database size.
> > 1) will my customers have to purchase SQL Server 2000?
> > (or me, and then give them the copy w/ my app).
> If MSDE is not an option, your customers should probably have SQL Server. I
> wouldn't recommend buying a bunch of copies of SQL Server to bundle with
> your app, as you don't necessarily know your clients' licensing needs, etc.
> > 2) what is the best way to wrap this up in an install
> > package? I already have InstallShield Express 4.0
> > and SageKey's Access 2003 MSI Wizard; am investigating
> > if these will let me include SQL Server. . . any ideas
> > on how to mass-sell something w/ SQL Server back-end'
> People mass-market SQL Server specific products all the time. You basically
> need to test it on SQL Server and make sure you specify it in the system
> requirements for your app. A quick question - are you selling to home users
> or businesses? If you're selling to individual home users or small
> businesses, you might reconsider using MSDE, as it is freely available, and
> the 2 GB restriction shouldn't be so bad for an app that previously ran on
> Access.
>
>|||It's best to give the customer an option to configure their SQL Server
settings themselves, either during Setup or within the app itself. If
you're planning to mass-market your app, you definitely need to allow for
changes to the connection settings somehow - not every business is going to
have their network configured the same way and you can't necessarily count
on the fact that they'll be running your app on the same box as SQL Server.
Additionally, they might be using SQL Authentication instead of Windows
Integrated, in which case they'll need to access the login
username/password, etc. And hard-coding your username/password into your
app is big security no-no; sticking the customer with a username/password
combo that might not meet their security policies and requirements is also
not a good thing.
"ChristyWarner" <cwarner@.autoaudit.com> wrote in message
news:43C2467F-8064-4822-9402-19482E8D3EE3@.microsoft.com...
> Yes, selling to businesses, hopefully larger ones, which is why
> I'm switching to SQL Server.
> When my customers install their SQL Server, can I still refer
> to it in my VB code w/ the same connection string? e.g. server=(local),
> or do I have to specify an exact server name that the customer
> has assigned?
> thanks,
> Christy.
> "Michael C#" wrote:
>> "ChristyWarner" <cwarner@.autoaudit.com> wrote in message
>> news:DB69C611-0E69-47B1-B940-4FAB81DA9C36@.microsoft.com...
>> > Hello,
>> >
>> > I want to upgrade my Access 2003 app to have a
>> > VB 6.0 front-end and SQL Server 2000 Standard back-end, that I want
>> > to sell on the market. I do not want to use MSDE
>> > because of the 2GB limitation. My questions are:
>> Access suffers from the same 2 GB limitation on database size.
>> > 1) will my customers have to purchase SQL Server 2000?
>> > (or me, and then give them the copy w/ my app).
>> If MSDE is not an option, your customers should probably have SQL Server.
>> I
>> wouldn't recommend buying a bunch of copies of SQL Server to bundle with
>> your app, as you don't necessarily know your clients' licensing needs,
>> etc.
>> > 2) what is the best way to wrap this up in an install
>> > package? I already have InstallShield Express 4.0
>> > and SageKey's Access 2003 MSI Wizard; am investigating
>> > if these will let me include SQL Server. . . any ideas
>> > on how to mass-sell something w/ SQL Server back-end'
>> People mass-market SQL Server specific products all the time. You
>> basically
>> need to test it on SQL Server and make sure you specify it in the system
>> requirements for your app. A quick question - are you selling to home
>> users
>> or businesses? If you're selling to individual home users or small
>> businesses, you might reconsider using MSDE, as it is freely available,
>> and
>> the 2 GB restriction shouldn't be so bad for an app that previously ran
>> on
>> Access.
>>
Monday, March 26, 2012
install newer standard etition over older enterprise edition
If I were to install SQL Server 2005 Standard over SQL Server 2003
Enterprise, would there be any negative effects? What would happen to the
features that are not supported by the newer Standard Edition? Would it be
better to uninstall SQL Server 2003 Enterprise before I install SQL Server
2005 Standard?
Daniel Brower
You can't upgrade from EE to Std editions. You will need to uninstall EE
first and then install the Std edition.
Andrew J. Kelly SQL MVP
"Daniel" <dwbnews@.hotmail.com> wrote in message
news:eoARzT$DGHA.128@.TK2MSFTNGP10.phx.gbl...
> If I were to install SQL Server 2005 Standard over SQL Server 2003
> Enterprise, would there be any negative effects? What would happen to the
> features that are not supported by the newer Standard Edition? Would it
> be better to uninstall SQL Server 2003 Enterprise before I install SQL
> Server 2005 Standard?
> Daniel Brower
>
|||there is NO SQL Server 2003 version.
If you mean 2000, then what the other guy wrote is correct. If you are on 7
DON"T uninstall as it will destroy your user databases.
d.
"Daniel" <dwbnews@.hotmail.com> wrote in message
news:eoARzT$DGHA.128@.TK2MSFTNGP10.phx.gbl...
> If I were to install SQL Server 2005 Standard over SQL Server 2003
> Enterprise, would there be any negative effects? What would happen to the
> features that are not supported by the newer Standard Edition? Would it
be
> better to uninstall SQL Server 2003 Enterprise before I install SQL Server
> 2005 Standard?
> Daniel Brower
>
Enterprise, would there be any negative effects? What would happen to the
features that are not supported by the newer Standard Edition? Would it be
better to uninstall SQL Server 2003 Enterprise before I install SQL Server
2005 Standard?
Daniel Brower
You can't upgrade from EE to Std editions. You will need to uninstall EE
first and then install the Std edition.
Andrew J. Kelly SQL MVP
"Daniel" <dwbnews@.hotmail.com> wrote in message
news:eoARzT$DGHA.128@.TK2MSFTNGP10.phx.gbl...
> If I were to install SQL Server 2005 Standard over SQL Server 2003
> Enterprise, would there be any negative effects? What would happen to the
> features that are not supported by the newer Standard Edition? Would it
> be better to uninstall SQL Server 2003 Enterprise before I install SQL
> Server 2005 Standard?
> Daniel Brower
>
|||there is NO SQL Server 2003 version.
If you mean 2000, then what the other guy wrote is correct. If you are on 7
DON"T uninstall as it will destroy your user databases.
d.
"Daniel" <dwbnews@.hotmail.com> wrote in message
news:eoARzT$DGHA.128@.TK2MSFTNGP10.phx.gbl...
> If I were to install SQL Server 2005 Standard over SQL Server 2003
> Enterprise, would there be any negative effects? What would happen to the
> features that are not supported by the newer Standard Edition? Would it
be
> better to uninstall SQL Server 2003 Enterprise before I install SQL Server
> 2005 Standard?
> Daniel Brower
>
install newer standard etition over older enterprise edition
If I were to install SQL Server 2005 Standard over SQL Server 2003
Enterprise, would there be any negative effects? What would happen to the
features that are not supported by the newer Standard Edition? Would it be
better to uninstall SQL Server 2003 Enterprise before I install SQL Server
2005 Standard?
Daniel Brower
You can't upgrade from EE to Std editions. You will need to uninstall EE
first and then install the Std edition.
Andrew J. Kelly SQL MVP
"Daniel" <dwbnews@.hotmail.com> wrote in message
news:eoARzT$DGHA.128@.TK2MSFTNGP10.phx.gbl...
> If I were to install SQL Server 2005 Standard over SQL Server 2003
> Enterprise, would there be any negative effects? What would happen to the
> features that are not supported by the newer Standard Edition? Would it
> be better to uninstall SQL Server 2003 Enterprise before I install SQL
> Server 2005 Standard?
> Daniel Brower
>
|||there is NO SQL Server 2003 version.
If you mean 2000, then what the other guy wrote is correct. If you are on 7
DON"T uninstall as it will destroy your user databases.
d.
"Daniel" <dwbnews@.hotmail.com> wrote in message
news:eoARzT$DGHA.128@.TK2MSFTNGP10.phx.gbl...
> If I were to install SQL Server 2005 Standard over SQL Server 2003
> Enterprise, would there be any negative effects? What would happen to the
> features that are not supported by the newer Standard Edition? Would it
be
> better to uninstall SQL Server 2003 Enterprise before I install SQL Server
> 2005 Standard?
> Daniel Brower
>
Enterprise, would there be any negative effects? What would happen to the
features that are not supported by the newer Standard Edition? Would it be
better to uninstall SQL Server 2003 Enterprise before I install SQL Server
2005 Standard?
Daniel Brower
You can't upgrade from EE to Std editions. You will need to uninstall EE
first and then install the Std edition.
Andrew J. Kelly SQL MVP
"Daniel" <dwbnews@.hotmail.com> wrote in message
news:eoARzT$DGHA.128@.TK2MSFTNGP10.phx.gbl...
> If I were to install SQL Server 2005 Standard over SQL Server 2003
> Enterprise, would there be any negative effects? What would happen to the
> features that are not supported by the newer Standard Edition? Would it
> be better to uninstall SQL Server 2003 Enterprise before I install SQL
> Server 2005 Standard?
> Daniel Brower
>
|||there is NO SQL Server 2003 version.
If you mean 2000, then what the other guy wrote is correct. If you are on 7
DON"T uninstall as it will destroy your user databases.
d.
"Daniel" <dwbnews@.hotmail.com> wrote in message
news:eoARzT$DGHA.128@.TK2MSFTNGP10.phx.gbl...
> If I were to install SQL Server 2005 Standard over SQL Server 2003
> Enterprise, would there be any negative effects? What would happen to the
> features that are not supported by the newer Standard Edition? Would it
be
> better to uninstall SQL Server 2003 Enterprise before I install SQL Server
> 2005 Standard?
> Daniel Brower
>
install newer standard etition over older enterprise edition
If I were to install SQL Server 2005 Standard over SQL Server 2003
Enterprise, would there be any negative effects? What would happen to the
features that are not supported by the newer Standard Edition? Would it be
better to uninstall SQL Server 2003 Enterprise before I install SQL Server
2005 Standard?
Daniel BrowerYou can't upgrade from EE to Std editions. You will need to uninstall EE
first and then install the Std edition.
--
Andrew J. Kelly SQL MVP
"Daniel" <dwbnews@.hotmail.com> wrote in message
news:eoARzT$DGHA.128@.TK2MSFTNGP10.phx.gbl...
> If I were to install SQL Server 2005 Standard over SQL Server 2003
> Enterprise, would there be any negative effects? What would happen to the
> features that are not supported by the newer Standard Edition? Would it
> be better to uninstall SQL Server 2003 Enterprise before I install SQL
> Server 2005 Standard?
> Daniel Brower
>|||there is NO SQL Server 2003 version.
If you mean 2000, then what the other guy wrote is correct. If you are on 7
DON"T uninstall as it will destroy your user databases.
d.
"Daniel" <dwbnews@.hotmail.com> wrote in message
news:eoARzT$DGHA.128@.TK2MSFTNGP10.phx.gbl...
> If I were to install SQL Server 2005 Standard over SQL Server 2003
> Enterprise, would there be any negative effects? What would happen to the
> features that are not supported by the newer Standard Edition? Would it
be
> better to uninstall SQL Server 2003 Enterprise before I install SQL Server
> 2005 Standard?
> Daniel Brower
>
Enterprise, would there be any negative effects? What would happen to the
features that are not supported by the newer Standard Edition? Would it be
better to uninstall SQL Server 2003 Enterprise before I install SQL Server
2005 Standard?
Daniel BrowerYou can't upgrade from EE to Std editions. You will need to uninstall EE
first and then install the Std edition.
--
Andrew J. Kelly SQL MVP
"Daniel" <dwbnews@.hotmail.com> wrote in message
news:eoARzT$DGHA.128@.TK2MSFTNGP10.phx.gbl...
> If I were to install SQL Server 2005 Standard over SQL Server 2003
> Enterprise, would there be any negative effects? What would happen to the
> features that are not supported by the newer Standard Edition? Would it
> be better to uninstall SQL Server 2003 Enterprise before I install SQL
> Server 2005 Standard?
> Daniel Brower
>|||there is NO SQL Server 2003 version.
If you mean 2000, then what the other guy wrote is correct. If you are on 7
DON"T uninstall as it will destroy your user databases.
d.
"Daniel" <dwbnews@.hotmail.com> wrote in message
news:eoARzT$DGHA.128@.TK2MSFTNGP10.phx.gbl...
> If I were to install SQL Server 2005 Standard over SQL Server 2003
> Enterprise, would there be any negative effects? What would happen to the
> features that are not supported by the newer Standard Edition? Would it
be
> better to uninstall SQL Server 2003 Enterprise before I install SQL Server
> 2005 Standard?
> Daniel Brower
>
install LOG SHIPPING with sql server 2000 standard
hi,
i want to customize Loga Shipping with Sql server 2000 standard
i use W2K3 OS.
but i don't find "How to" to configure Log shipping with Sql server 2000
standard edition
it's possible to use log shipping with Sql server standard edition?
thank for your help.
M'bark.
France
sorry for my english.
Here are some KB articles:
314515 INF: Frequently Asked Questions - SQL Server 2000 - Log Shipping
http://support.microsoft.com/?id=314515
323135 INF: Microsoft SQL Server 2000 - How to Set Up Log Shipping (White
Paper)
http://support.microsoft.com/?id=323135
325220 Support WebCast: Microsoft SQL Server 2000 Log Shipping
http://support.microsoft.com/?id=325220
821786 Support WebCast: Microsoft SQL Server 2000: Using Log Shipping
http://support.microsoft.com/?id=821786
321247 HOW TO: Configure Security for Log Shipping
http://support.microsoft.com/?id=321247
329133 INF: Troubleshooting SQL Server 2000 Log Shipping "Out of Sync"
Errors
http://support.microsoft.com/?id=329133
Keith
"M'bark BOULOUIRD" <bark.news@.DELETEspam.logaviv.com> wrote in message
news:e0gpZ1I0EHA.1392@.TK2MSFTNGP14.phx.gbl...
> hi,
> i want to customize Loga Shipping with Sql server 2000 standard
> i use W2K3 OS.
> but i don't find "How to" to configure Log shipping with Sql server 2000
> standard edition
> it's possible to use log shipping with Sql server standard edition?
> thank for your help.
> M'bark.
> France
> sorry for my english.
>
|||Hi
Integrated log shipping is a feature of Enterprise Edition. There is a log
shipping tool you can use for Standard Edtion which is available in the SQL
Server Resource kit
(http://www.microsoft.com/sql/techinf...it/default.asp).
The other option is to use scripts and do log shipping yourself. All what it
is, is a dump, copy and load.
Regards
Mike
"M'bark BOULOUIRD" wrote:
> hi,
> i want to customize Loga Shipping with Sql server 2000 standard
> i use W2K3 OS.
> but i don't find "How to" to configure Log shipping with Sql server 2000
> standard edition
> it's possible to use log shipping with Sql server standard edition?
> thank for your help.
> M'bark.
> France
> sorry for my english.
>
>
|||thanks
M'bark
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> a crit dans le message de
news: 073AE595-FC06-478A-A9E7-58A65EA759E1@.microsoft.com...[vbcol=seagreen]
> Hi
> Integrated log shipping is a feature of Enterprise Edition. There is a log
> shipping tool you can use for Standard Edtion which is available in the
> SQL
> Server Resource kit
> (http://www.microsoft.com/sql/techinf...it/default.asp).
> The other option is to use scripts and do log shipping yourself. All what
> it
> is, is a dump, copy and load.
> Regards
> Mike
> "M'bark BOULOUIRD" wrote:
|||If you're looking into log shipping with compressed backup files, our
product, MiniSQLBackup, can do that and more. See
http://www.yohz.com/articles_04.html for details on how MiniSQLBackup
supports log shipping with SQL2K standard.
Peter Yeoh
http://www.yohz.com
Need smaller SQL2K backup files? Use MiniSQLBackup Lite, free!
"M'bark BOULOUIRD" <bark.news@.DELETEspam.logaviv.com> wrote in message
news:e0gpZ1I0EHA.1392@.TK2MSFTNGP14.phx.gbl...
> hi,
> i want to customize Loga Shipping with Sql server 2000 standard
> i use W2K3 OS.
> but i don't find "How to" to configure Log shipping with Sql server 2000
> standard edition
> it's possible to use log shipping with Sql server standard edition?
> thank for your help.
> M'bark.
> France
> sorry for my english.
>
i want to customize Loga Shipping with Sql server 2000 standard
i use W2K3 OS.
but i don't find "How to" to configure Log shipping with Sql server 2000
standard edition
it's possible to use log shipping with Sql server standard edition?
thank for your help.
M'bark.
France
sorry for my english.
Here are some KB articles:
314515 INF: Frequently Asked Questions - SQL Server 2000 - Log Shipping
http://support.microsoft.com/?id=314515
323135 INF: Microsoft SQL Server 2000 - How to Set Up Log Shipping (White
Paper)
http://support.microsoft.com/?id=323135
325220 Support WebCast: Microsoft SQL Server 2000 Log Shipping
http://support.microsoft.com/?id=325220
821786 Support WebCast: Microsoft SQL Server 2000: Using Log Shipping
http://support.microsoft.com/?id=821786
321247 HOW TO: Configure Security for Log Shipping
http://support.microsoft.com/?id=321247
329133 INF: Troubleshooting SQL Server 2000 Log Shipping "Out of Sync"
Errors
http://support.microsoft.com/?id=329133
Keith
"M'bark BOULOUIRD" <bark.news@.DELETEspam.logaviv.com> wrote in message
news:e0gpZ1I0EHA.1392@.TK2MSFTNGP14.phx.gbl...
> hi,
> i want to customize Loga Shipping with Sql server 2000 standard
> i use W2K3 OS.
> but i don't find "How to" to configure Log shipping with Sql server 2000
> standard edition
> it's possible to use log shipping with Sql server standard edition?
> thank for your help.
> M'bark.
> France
> sorry for my english.
>
|||Hi
Integrated log shipping is a feature of Enterprise Edition. There is a log
shipping tool you can use for Standard Edtion which is available in the SQL
Server Resource kit
(http://www.microsoft.com/sql/techinf...it/default.asp).
The other option is to use scripts and do log shipping yourself. All what it
is, is a dump, copy and load.
Regards
Mike
"M'bark BOULOUIRD" wrote:
> hi,
> i want to customize Loga Shipping with Sql server 2000 standard
> i use W2K3 OS.
> but i don't find "How to" to configure Log shipping with Sql server 2000
> standard edition
> it's possible to use log shipping with Sql server standard edition?
> thank for your help.
> M'bark.
> France
> sorry for my english.
>
>
|||thanks
M'bark
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> a crit dans le message de
news: 073AE595-FC06-478A-A9E7-58A65EA759E1@.microsoft.com...[vbcol=seagreen]
> Hi
> Integrated log shipping is a feature of Enterprise Edition. There is a log
> shipping tool you can use for Standard Edtion which is available in the
> SQL
> Server Resource kit
> (http://www.microsoft.com/sql/techinf...it/default.asp).
> The other option is to use scripts and do log shipping yourself. All what
> it
> is, is a dump, copy and load.
> Regards
> Mike
> "M'bark BOULOUIRD" wrote:
|||If you're looking into log shipping with compressed backup files, our
product, MiniSQLBackup, can do that and more. See
http://www.yohz.com/articles_04.html for details on how MiniSQLBackup
supports log shipping with SQL2K standard.
Peter Yeoh
http://www.yohz.com
Need smaller SQL2K backup files? Use MiniSQLBackup Lite, free!
"M'bark BOULOUIRD" <bark.news@.DELETEspam.logaviv.com> wrote in message
news:e0gpZ1I0EHA.1392@.TK2MSFTNGP14.phx.gbl...
> hi,
> i want to customize Loga Shipping with Sql server 2000 standard
> i use W2K3 OS.
> but i don't find "How to" to configure Log shipping with Sql server 2000
> standard edition
> it's possible to use log shipping with Sql server standard edition?
> thank for your help.
> M'bark.
> France
> sorry for my english.
>
install LOG SHIPPING with sql server 2000 standard
hi,
i want to customize Loga Shipping with Sql server 2000 standard
i use W2K3 OS.
but i don't find "How to" to configure Log shipping with Sql server 2000
standard edition
it's possible to use log shipping with Sql server standard edition?
thank for your help.
M'bark.
France
sorry for my english.Here are some KB articles:
314515 INF: Frequently Asked Questions - SQL Server 2000 - Log Shipping
http://support.microsoft.com/?id=314515
323135 INF: Microsoft SQL Server 2000 - How to Set Up Log Shipping (White
Paper)
http://support.microsoft.com/?id=323135
325220 Support WebCast: Microsoft SQL Server 2000 Log Shipping
http://support.microsoft.com/?id=325220
821786 Support WebCast: Microsoft SQL Server 2000: Using Log Shipping
http://support.microsoft.com/?id=821786
321247 HOW TO: Configure Security for Log Shipping
http://support.microsoft.com/?id=321247
329133 INF: Troubleshooting SQL Server 2000 Log Shipping "Out of Sync"
Errors
http://support.microsoft.com/?id=329133
Keith
"M'bark BOULOUIRD" <bark.news@.DELETEspam.logaviv.com> wrote in message
news:e0gpZ1I0EHA.1392@.TK2MSFTNGP14.phx.gbl...
> hi,
> i want to customize Loga Shipping with Sql server 2000 standard
> i use W2K3 OS.
> but i don't find "How to" to configure Log shipping with Sql server 2000
> standard edition
> it's possible to use log shipping with Sql server standard edition?
> thank for your help.
> M'bark.
> France
> sorry for my english.
>|||Hi
Integrated log shipping is a feature of Enterprise Edition. There is a log
shipping tool you can use for Standard Edtion which is available in the SQL
Server Resource kit
(http://www.microsoft.com/sql/techin...kit/default.asp).
The other option is to use scripts and do log shipping yourself. All what it
is, is a dump, copy and load.
Regards
Mike
"M'bark BOULOUIRD" wrote:
> hi,
> i want to customize Loga Shipping with Sql server 2000 standard
> i use W2K3 OS.
> but i don't find "How to" to configure Log shipping with Sql server 2000
> standard edition
> it's possible to use log shipping with Sql server standard edition?
> thank for your help.
> M'bark.
> France
> sorry for my english.
>
>|||thanks
M'bark
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> a crit dans le message de
news: 073AE595-FC06-478A-A9E7-58A65EA759E1@.microsoft.com...[vbcol=seagreen]
> Hi
> Integrated log shipping is a feature of Enterprise Edition. There is a log
> shipping tool you can use for Standard Edtion which is available in the
> SQL
> Server Resource kit
> (http://www.microsoft.com/sql/techin...kit/default.asp).
> The other option is to use scripts and do log shipping yourself. All what
> it
> is, is a dump, copy and load.
> Regards
> Mike
> "M'bark BOULOUIRD" wrote:
>|||If you're looking into log shipping with compressed backup files, our
product, MiniSQLBackup, can do that and more. See
http://www.yohz.com/articles_04.html for details on how MiniSQLBackup
supports log shipping with SQL2K standard.
Peter Yeoh
http://www.yohz.com
Need smaller SQL2K backup files? Use MiniSQLBackup Lite, free!
"M'bark BOULOUIRD" <bark.news@.DELETEspam.logaviv.com> wrote in message
news:e0gpZ1I0EHA.1392@.TK2MSFTNGP14.phx.gbl...
> hi,
> i want to customize Loga Shipping with Sql server 2000 standard
> i use W2K3 OS.
> but i don't find "How to" to configure Log shipping with Sql server 2000
> standard edition
> it's possible to use log shipping with Sql server standard edition?
> thank for your help.
> M'bark.
> France
> sorry for my english.
>
i want to customize Loga Shipping with Sql server 2000 standard
i use W2K3 OS.
but i don't find "How to" to configure Log shipping with Sql server 2000
standard edition
it's possible to use log shipping with Sql server standard edition?
thank for your help.
M'bark.
France
sorry for my english.Here are some KB articles:
314515 INF: Frequently Asked Questions - SQL Server 2000 - Log Shipping
http://support.microsoft.com/?id=314515
323135 INF: Microsoft SQL Server 2000 - How to Set Up Log Shipping (White
Paper)
http://support.microsoft.com/?id=323135
325220 Support WebCast: Microsoft SQL Server 2000 Log Shipping
http://support.microsoft.com/?id=325220
821786 Support WebCast: Microsoft SQL Server 2000: Using Log Shipping
http://support.microsoft.com/?id=821786
321247 HOW TO: Configure Security for Log Shipping
http://support.microsoft.com/?id=321247
329133 INF: Troubleshooting SQL Server 2000 Log Shipping "Out of Sync"
Errors
http://support.microsoft.com/?id=329133
Keith
"M'bark BOULOUIRD" <bark.news@.DELETEspam.logaviv.com> wrote in message
news:e0gpZ1I0EHA.1392@.TK2MSFTNGP14.phx.gbl...
> hi,
> i want to customize Loga Shipping with Sql server 2000 standard
> i use W2K3 OS.
> but i don't find "How to" to configure Log shipping with Sql server 2000
> standard edition
> it's possible to use log shipping with Sql server standard edition?
> thank for your help.
> M'bark.
> France
> sorry for my english.
>|||Hi
Integrated log shipping is a feature of Enterprise Edition. There is a log
shipping tool you can use for Standard Edtion which is available in the SQL
Server Resource kit
(http://www.microsoft.com/sql/techin...kit/default.asp).
The other option is to use scripts and do log shipping yourself. All what it
is, is a dump, copy and load.
Regards
Mike
"M'bark BOULOUIRD" wrote:
> hi,
> i want to customize Loga Shipping with Sql server 2000 standard
> i use W2K3 OS.
> but i don't find "How to" to configure Log shipping with Sql server 2000
> standard edition
> it's possible to use log shipping with Sql server standard edition?
> thank for your help.
> M'bark.
> France
> sorry for my english.
>
>|||thanks
M'bark
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> a crit dans le message de
news: 073AE595-FC06-478A-A9E7-58A65EA759E1@.microsoft.com...[vbcol=seagreen]
> Hi
> Integrated log shipping is a feature of Enterprise Edition. There is a log
> shipping tool you can use for Standard Edtion which is available in the
> SQL
> Server Resource kit
> (http://www.microsoft.com/sql/techin...kit/default.asp).
> The other option is to use scripts and do log shipping yourself. All what
> it
> is, is a dump, copy and load.
> Regards
> Mike
> "M'bark BOULOUIRD" wrote:
>|||If you're looking into log shipping with compressed backup files, our
product, MiniSQLBackup, can do that and more. See
http://www.yohz.com/articles_04.html for details on how MiniSQLBackup
supports log shipping with SQL2K standard.
Peter Yeoh
http://www.yohz.com
Need smaller SQL2K backup files? Use MiniSQLBackup Lite, free!
"M'bark BOULOUIRD" <bark.news@.DELETEspam.logaviv.com> wrote in message
news:e0gpZ1I0EHA.1392@.TK2MSFTNGP14.phx.gbl...
> hi,
> i want to customize Loga Shipping with Sql server 2000 standard
> i use W2K3 OS.
> but i don't find "How to" to configure Log shipping with Sql server 2000
> standard edition
> it's possible to use log shipping with Sql server standard edition?
> thank for your help.
> M'bark.
> France
> sorry for my english.
>
install LOG SHIPPING with sql server 2000 standard
hi,
i want to customize Loga Shipping with Sql server 2000 standard
i use W2K3 OS.
but i don't find "How to" to configure Log shipping with Sql server 2000
standard edition
it's possible to use log shipping with Sql server standard edition?
thank for your help.
M'bark.
France
sorry for my english.Here are some KB articles:
314515 INF: Frequently Asked Questions - SQL Server 2000 - Log Shipping
http://support.microsoft.com/?id=314515
323135 INF: Microsoft SQL Server 2000 - How to Set Up Log Shipping (White
Paper)
http://support.microsoft.com/?id=323135
325220 Support WebCast: Microsoft SQL Server 2000 Log Shipping
http://support.microsoft.com/?id=325220
821786 Support WebCast: Microsoft SQL Server 2000: Using Log Shipping
http://support.microsoft.com/?id=821786
321247 HOW TO: Configure Security for Log Shipping
http://support.microsoft.com/?id=321247
329133 INF: Troubleshooting SQL Server 2000 Log Shipping "Out of Sync"
Errors
http://support.microsoft.com/?id=329133
--
Keith
"M'bark BOULOUIRD" <bark.news@.DELETEspam.logaviv.com> wrote in message
news:e0gpZ1I0EHA.1392@.TK2MSFTNGP14.phx.gbl...
> hi,
> i want to customize Loga Shipping with Sql server 2000 standard
> i use W2K3 OS.
> but i don't find "How to" to configure Log shipping with Sql server 2000
> standard edition
> it's possible to use log shipping with Sql server standard edition?
> thank for your help.
> M'bark.
> France
> sorry for my english.
>|||Hi
Integrated log shipping is a feature of Enterprise Edition. There is a log
shipping tool you can use for Standard Edtion which is available in the SQL
Server Resource kit
(http://www.microsoft.com/sql/techinfo/reskit/default.asp).
The other option is to use scripts and do log shipping yourself. All what it
is, is a dump, copy and load.
Regards
Mike
"M'bark BOULOUIRD" wrote:
> hi,
> i want to customize Loga Shipping with Sql server 2000 standard
> i use W2K3 OS.
> but i don't find "How to" to configure Log shipping with Sql server 2000
> standard edition
> it's possible to use log shipping with Sql server standard edition?
> thank for your help.
> M'bark.
> France
> sorry for my english.
>
>|||thanks
M'bark
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> a écrit dans le message de
news: 073AE595-FC06-478A-A9E7-58A65EA759E1@.microsoft.com...
> Hi
> Integrated log shipping is a feature of Enterprise Edition. There is a log
> shipping tool you can use for Standard Edtion which is available in the
> SQL
> Server Resource kit
> (http://www.microsoft.com/sql/techinfo/reskit/default.asp).
> The other option is to use scripts and do log shipping yourself. All what
> it
> is, is a dump, copy and load.
> Regards
> Mike
> "M'bark BOULOUIRD" wrote:
>> hi,
>> i want to customize Loga Shipping with Sql server 2000 standard
>> i use W2K3 OS.
>> but i don't find "How to" to configure Log shipping with Sql server 2000
>> standard edition
>> it's possible to use log shipping with Sql server standard edition?
>> thank for your help.
>> M'bark.
>> France
>> sorry for my english.
>>|||If you're looking into log shipping with compressed backup files, our
product, MiniSQLBackup, can do that and more. See
http://www.yohz.com/articles_04.html for details on how MiniSQLBackup
supports log shipping with SQL2K standard.
--
Peter Yeoh
http://www.yohz.com
Need smaller SQL2K backup files? Use MiniSQLBackup Lite, free!
"M'bark BOULOUIRD" <bark.news@.DELETEspam.logaviv.com> wrote in message
news:e0gpZ1I0EHA.1392@.TK2MSFTNGP14.phx.gbl...
> hi,
> i want to customize Loga Shipping with Sql server 2000 standard
> i use W2K3 OS.
> but i don't find "How to" to configure Log shipping with Sql server 2000
> standard edition
> it's possible to use log shipping with Sql server standard edition?
> thank for your help.
> M'bark.
> France
> sorry for my english.
>
i want to customize Loga Shipping with Sql server 2000 standard
i use W2K3 OS.
but i don't find "How to" to configure Log shipping with Sql server 2000
standard edition
it's possible to use log shipping with Sql server standard edition?
thank for your help.
M'bark.
France
sorry for my english.Here are some KB articles:
314515 INF: Frequently Asked Questions - SQL Server 2000 - Log Shipping
http://support.microsoft.com/?id=314515
323135 INF: Microsoft SQL Server 2000 - How to Set Up Log Shipping (White
Paper)
http://support.microsoft.com/?id=323135
325220 Support WebCast: Microsoft SQL Server 2000 Log Shipping
http://support.microsoft.com/?id=325220
821786 Support WebCast: Microsoft SQL Server 2000: Using Log Shipping
http://support.microsoft.com/?id=821786
321247 HOW TO: Configure Security for Log Shipping
http://support.microsoft.com/?id=321247
329133 INF: Troubleshooting SQL Server 2000 Log Shipping "Out of Sync"
Errors
http://support.microsoft.com/?id=329133
--
Keith
"M'bark BOULOUIRD" <bark.news@.DELETEspam.logaviv.com> wrote in message
news:e0gpZ1I0EHA.1392@.TK2MSFTNGP14.phx.gbl...
> hi,
> i want to customize Loga Shipping with Sql server 2000 standard
> i use W2K3 OS.
> but i don't find "How to" to configure Log shipping with Sql server 2000
> standard edition
> it's possible to use log shipping with Sql server standard edition?
> thank for your help.
> M'bark.
> France
> sorry for my english.
>|||Hi
Integrated log shipping is a feature of Enterprise Edition. There is a log
shipping tool you can use for Standard Edtion which is available in the SQL
Server Resource kit
(http://www.microsoft.com/sql/techinfo/reskit/default.asp).
The other option is to use scripts and do log shipping yourself. All what it
is, is a dump, copy and load.
Regards
Mike
"M'bark BOULOUIRD" wrote:
> hi,
> i want to customize Loga Shipping with Sql server 2000 standard
> i use W2K3 OS.
> but i don't find "How to" to configure Log shipping with Sql server 2000
> standard edition
> it's possible to use log shipping with Sql server standard edition?
> thank for your help.
> M'bark.
> France
> sorry for my english.
>
>|||thanks
M'bark
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> a écrit dans le message de
news: 073AE595-FC06-478A-A9E7-58A65EA759E1@.microsoft.com...
> Hi
> Integrated log shipping is a feature of Enterprise Edition. There is a log
> shipping tool you can use for Standard Edtion which is available in the
> SQL
> Server Resource kit
> (http://www.microsoft.com/sql/techinfo/reskit/default.asp).
> The other option is to use scripts and do log shipping yourself. All what
> it
> is, is a dump, copy and load.
> Regards
> Mike
> "M'bark BOULOUIRD" wrote:
>> hi,
>> i want to customize Loga Shipping with Sql server 2000 standard
>> i use W2K3 OS.
>> but i don't find "How to" to configure Log shipping with Sql server 2000
>> standard edition
>> it's possible to use log shipping with Sql server standard edition?
>> thank for your help.
>> M'bark.
>> France
>> sorry for my english.
>>|||If you're looking into log shipping with compressed backup files, our
product, MiniSQLBackup, can do that and more. See
http://www.yohz.com/articles_04.html for details on how MiniSQLBackup
supports log shipping with SQL2K standard.
--
Peter Yeoh
http://www.yohz.com
Need smaller SQL2K backup files? Use MiniSQLBackup Lite, free!
"M'bark BOULOUIRD" <bark.news@.DELETEspam.logaviv.com> wrote in message
news:e0gpZ1I0EHA.1392@.TK2MSFTNGP14.phx.gbl...
> hi,
> i want to customize Loga Shipping with Sql server 2000 standard
> i use W2K3 OS.
> but i don't find "How to" to configure Log shipping with Sql server 2000
> standard edition
> it's possible to use log shipping with Sql server standard edition?
> thank for your help.
> M'bark.
> France
> sorry for my english.
>
Friday, March 23, 2012
Install fails
sql server 2000 sp4 installation fails on windows server 2003 standard
edition with error "Sql server 2000 is not installed on this machine. Setup
will now exit." Trying to install on a vmware server. Have bounced the server
and retried without success. Any ideas?s5 wrote:
> sql server 2000 sp4 installation fails on windows server 2003 standard
> edition with error "Sql server 2000 is not installed on this machine. Setup
> will now exit." Trying to install on a vmware server. Have bounced the server
> and retried without success. Any ideas?
Do you have any problems with the SQL Server on that machine? Like
connection problems, etc.
--
Lasse Vågsæther Karlsen
http://usinglvkblog.blogspot.com/
mailto:lasse@.vkarlsen.no
PGP KeyID: 0x2A42A1C2sql
edition with error "Sql server 2000 is not installed on this machine. Setup
will now exit." Trying to install on a vmware server. Have bounced the server
and retried without success. Any ideas?s5 wrote:
> sql server 2000 sp4 installation fails on windows server 2003 standard
> edition with error "Sql server 2000 is not installed on this machine. Setup
> will now exit." Trying to install on a vmware server. Have bounced the server
> and retried without success. Any ideas?
Do you have any problems with the SQL Server on that machine? Like
connection problems, etc.
--
Lasse Vågsæther Karlsen
http://usinglvkblog.blogspot.com/
mailto:lasse@.vkarlsen.no
PGP KeyID: 0x2A42A1C2sql
Install errror in SQLServer 2005 SP1
I have a error instaling SP1 for SQLServer 2005 Standard Edition Spanish.
The log is the following:
.....
Doing Action: SetInstanceProperty
PerfTime Start: SetInstanceProperty : Wed Apr 26 16:02:31 2006
<Func Name='SetInstanceProperty'>
MSI (s) (48!D0) [16:02:31:827]: PROPERTY CHANGE: Adding SqlOriginalMachineName property. Its value is 'WS03'.
MSI (s) (48!D0) [16:02:31:827]: PROPERTY CHANGE: Adding SqlLegacyRegPath property. Its value is 'MSSQLServer'.
MSI (s) (48!D0) [16:02:31:859]: PROPERTY CHANGE: Adding PreviousInstId property. Its value is 'MSSQL.1'.
Using instanced id: MSSQL.1
MSI (s) (48!D0) [16:02:31:859]: PROPERTY CHANGE: Adding InstId property. Its value is 'MSSQL.1'.
Previous instance id: MSSQL.1
Using instance name: MSSQLSERVER
MSI (s) (48!D0) [16:02:31:890]: PROPERTY CHANGE: Adding PrevRegRootPath property. Its value is 'Software\Microsoft\Microsoft SQL Server\MSSQL.1'.
MSI (s) (48!D0) [16:02:31:921]: PROPERTY CHANGE: Adding Sql2KSxS property. Its value is '1'.
MSI (s) (48!D0) [16:02:31:921]: PROPERTY CHANGE: Adding InstanceName.D20239D7_E87C_40C9_9837_E70B8D4882C2 property. Its value is 'MSSQLSERVER'.
MSI (s) (48!D0) [16:02:31:921]: PROPERTY CHANGE: Adding ServicePrefixRS.6080319C_1466_426E_9E7A_1DD555143E0A property. Its value is 'SQLServer2005ReportServerUser$WS03$'.
MSI (s) (48!D0) [16:02:31:921]: PROPERTY CHANGE: Adding ServicePrefixSSIS.6080319C_1466_426E_9E7A_1DD555143E0A property. Its value is 'SQLServer2005DTSUser$WS03'.
MSI (s) (48!D0) [16:02:31:921]: PROPERTY CHANGE: Adding ServiceGroupSQLBrowser.2FC2D269_8625_4826_BB3F_F9059090CB38 property. Its value is 'SQLServer2005SQLBrowserUser$WS03'.
MSI (s) (48!D0) [16:02:31:921]: PROPERTY CHANGE: Adding QuotedServiceGroupSQLBrowser.2FC2D269_8625_4826_BB3F_F9059090CB38 property. Its value is 'RIEDER\SQLServer2005SQLBrowserUser$WS03'.
MSI (s) (48!D0) [16:02:31:921]: PROPERTY CHANGE: Adding ServiceGroupSQLBrowser.03BE59F9_3DFA_413B_A99C_B95CA31A7BFE property. Its value is 'SQLServer2005SQLBrowserUser$WS03'.
MSI (s) (48!D0) [16:02:31:921]: PROPERTY CHANGE: Adding QuotedServiceGroupSQLBrowser.03BE59F9_3DFA_413B_A99C_B95CA31A7BFE property. Its value is 'RIEDER\SQLServer2005SQLBrowserUser$WS03'.
MSI (s) (48!D0) [16:02:31:921]: PROPERTY CHANGE: Adding ServiceGroupSQLBrowser.879C8BDB_884A_4C3C_80C3_3452EA2B8439 property. Its value is 'SQLServer2005SQLBrowserUser$WS03'.
MSI (s) (48!D0) [16:02:31:921]: PROPERTY CHANGE: Adding QuotedServiceGroupSQLBrowser.879C8BDB_884A_4C3C_80C3_3452EA2B8439 property. Its value is 'RIEDER\SQLServer2005SQLBrowserUser$WS03'.
MSI (s) (48!D0) [16:02:31:921]: PROPERTY CHANGE: Adding ServiceGroupADHelper.2C8E638F_C982_4AA5_A173_7148A8E8649D property. Its value is 'SQLServer2005MSSQLServerADHelperUser$WS03'.
MSI (s) (48!D0) [16:02:31:921]: PROPERTY CHANGE: Adding QuotedServiceGroupADHelper.2C8E638F_C982_4AA5_A173_7148A8E8649D property. Its value is 'RIEDER\SQLServer2005MSSQLServerADHelperUser$WS03'.
MSI (s) (48!D0) [16:02:31:921]: PROPERTY CHANGE: Adding InstanceRegKey.2C8E638F_C982_4AA5_A173_7148A8E8649D property. Its value is 'Microsoft SQL Server\MSSQL.1'.
MSI (s) (48!D0) [16:02:31:921]: PROPERTY CHANGE: Adding DataInstanceTxt.EAD22282_F1AF_4119_B1F9_C9F1DCBC62FF property. Its value is 'C:\Archivos de programa\Microsoft SQL Server\MSSQL.1\MSSQL'.
MSI (s) (48!D0) [16:02:31:921]: PROPERTY CHANGE: Adding ServiceNameSQL.EAD22282_F1AF_4119_B1F9_C9F1DCBC62FF property. Its value is 'MSSQLSERVER'.
Using PrevRegRootPath: Software\Microsoft\Microsoft SQL Server\MSSQL.1
GetServiceUserGroup failed for MSSQLSERVER, 5
Error Code: 0x80070534 (1332)
Windows Error Text: No se ha efectuado ninguna asignación entre los nombres de cuenta y los identificadores de seguridad.
Source File Name: sqlca\sqlcax.cpp
Compiler Timestamp: Mon Feb 27 02:04:14 2006
Function Name: SetInstanceProperty
Source Line Number: 1223
MSI (s) (48!D0) [16:02:31:937]: Transforming table Error.
MSI (s) (48!D0) [16:02:31:937]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (48!D0) [16:02:31:937]: Transforming table Error.
MSI (s) (48!D0) [16:02:31:937]: Transforming table Error.
MSI (s) (48!D0) [16:02:31:937]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (48!D0) [16:02:31:937]: Transforming table Error.
MSI (s) (48!D0) [16:02:31:937]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (48!D0) [16:02:31:937]: Transforming table Error.
MSI (s) (48!D0) [16:02:31:937]: Note: 1: 2262 2: Error 3: -2147287038
Error Code: 1332
MSI (s) (48!D0) [16:02:31:952]: Transforming table Error.
MSI (s) (48!D0) [16:02:31:952]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (48!D0) [16:02:31:952]: Transforming table Error.
MSI (s) (48!D0) [16:02:31:952]: Transforming table Error.
MSI (s) (48!D0) [16:02:31:952]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (48!D0) [16:02:31:952]: Transforming table Error.
MSI (s) (48!D0) [16:02:31:952]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (48!D0) [16:02:31:952]: Transforming table Error.
MSI (s) (48!D0) [16:02:31:952]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (48!D0) [16:02:31:952]: Producto: Microsoft SQL Server 2005 -- Error 29528. El programa de instalación ha detectado un error inesperado al Estableciendo propiedades internas. El error es: Error grave durante la instalación.
.
Error 29528. El programa de instalación ha detectado un error inesperado al Estableciendo propiedades internas. El error es: Error grave durante la instalación.
.
<Failure Type='Fatal' Error='1332'>
<EndFunc Name='LaunchFunction' Return='1332' GetLastError='0'>
MSI (s) (48:9C) [16:02:31:952]: Transforming table InstallExecuteSequence.
MSI (s) (48:9C) [16:02:31:952]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (48:9C) [16:02:31:952]: Transforming table InstallExecuteSequence.
MSI (s) (48:9C) [16:02:31:952]: Transforming table InstallExecuteSequence.
MSI (s) (48:9C) [16:02:31:952]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (48:9C) [16:02:31:952]: Transforming table InstallExecuteSequence.
MSI (s) (48:9C) [16:02:31:952]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (48:9C) [16:02:31:952]: Transforming table InstallExecuteSequence.
MSI (s) (48:9C) [16:02:31:952]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
La acción terminó a las 16:02:31: SetInstanceProperty.D20239D7_E87C_40C9_9837_E70B8D4882C2. Valor devuelto: 3.
La acción terminó a las 16:02:31: INSTALL. Valor devuelto: 3.
Property(S): ProductCode = {FD515EB7-E1C3-4278-9EC2-047672A8B718}
Property(S): ProductLanguage = 3082
Property(S): Manufacturer = Microsoft Corporation
Property(S): ProductVersion = 9.1.2047.00
Property(S): MEDIAPACKAGEPATH = \Setup\
Property(S): ALLUSERS = 1
Property(S): NULLGUID = {00000000-0000-0000-0000-000000000000}
Property(S): ASPNetVersion = 2.0.50727
Property(S): ARPHELPLINK = http://go.microsoft.com/fwlink/?LinkId=52152
Property(S): ARPPRODUCTICON = ARPIcon.ico
Property(S): ARPNOREPAIR = 1
Property(S): ARPSYSTEMCOMPONENT = 1
Property(S): MsiHiddenProperties = SQLPASSWORD;AGTPASSWORD;ASPASSWORD;RSPASSWORD;SQLBROWSERPASSWORD;RSSQLPASSWORD;RSSQLPassword;RSSQLPasswordQuoted;RSSETUPPASSWORD;RSSetupPassword;SAPWD;saPWD;UPGRADEPWD;SqlUpgradePwd;SQLPassword;ServicePassword;ADMINPASSWORD;PIDKEY;FTEPassword.68C6D15C_77E0_11D5_8528_00C04F68155C;checksum.7354AFCB_913B_4E9F_B76C_2376101FDE0C;checksum.;DigitalProductID;DPID;Do_sqlScript.D20239D7_E87C_40C9_9837_E70B8D4882C2;Rollback_SqlConnection.D20239D7_E87C_40C9_9837_E70B8D4882C2;Do_XmlSingleNode.D20239D7_E87C_40C9_9837_E70B8D4882C2;Do_RSSetting.D20239D7_E87C_40C9_9837_E70B8D4882C2;PID;ProductID;RSUPGRADEPASSWORD;Do_RSSetSharePointExclusionPath.D20239D7_E87C_40C9_9837_E70B8D4882C2
Property(S): SecureCustomProperties = SQL_SHOWLIC;UPGRADESQL90
Property(S): SqlServerBuild = 1
Property(S): SqlCluster = 0
Property(S): INSTALLLEVEL = 90
Property(S): FXAssemblyVersion = 2.0.0.0
Property(S): VSAssemblyVersion = 8.0.0.0
Property(S): SqlErrorReporting = #0
Property(S): SqlSqmReporting = #0
Property(S): SqlEnableRanu = 0
Property(S): SqlPatchLevel = 9.1.2047
Property(S): ChannelID = 271
Property(S): PIDTemplate = 77656<````=````=````=````=`````>@.@.@.@.@.
Property(S): mpc = 77656
Property(S): OEMRelease = 0
Property(S): PIDKEY = **********
Property(S): ProgramFilesFolder = C:\Archivos de programa\
Property(S): ProductID = **********
Property(S): SqlInstanceName = MSSQLSERVER
Property(S): SqlSecurityMode = SQL
Property(S): SqlClusterSec = 0
Property(S): MDACSXS = 1
Property(S): DefaultUIFont = Tahoma8
Property(S): VersionNT = 502
Property(S): LocalSystemAccount = NT AUTHORITY\SYSTEM
Property(S): DefaultBuiltInAccount = LocalSystemAccount
.....
Thks
Emilio, unfortunately this is a known issue. Here is a snippet from a log I posted previously (from an English log).
The log post reads:
Using PrevRegRootPath: Software\Microsoft\Microsoft SQL Server\MSSQL.1
GetServiceUserGroup failed for MSSQLSERVER, 5
Error Code: 0x80070534 (1332)
Windows Error Text: No mapping between account names and security IDs was done.
We are currently investigating this issue, but my guess is that after RTM, someone deleted the user groups that were created during install. SQL setup creates several user groups that are used during setup. It appears that SP1 is also looking to use these and they no longer exist. The user groups are named in this fashion: SQLServer2005MSSQLUser$<MachineName>$<InstanceName>
We are still looking into it and hope to have a solution soon.
Thanks,
Samuel Lester (MSFT)
Is a solution to this available?
Regards,
Eric Lapham
SQL server uses local group for ACLs. When the server is installed the groups are created and their SIDs are stored in the registry. Somewhere along the way, the SID had to change and the SIDs in the registry were not valid anymore. Try to delete the values for the following values in Setup registry key the instance hive [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.1\Setup]
The registry values are:
AGTGroup
SQLGroup
FTSGroup
ASGroup
Thanks,
Samuel Lester (MSFT)
i deleted the registry value for AGTGroup, SQLGroupF, TSGroup and ASGroup and the setup ended now correct for all product.
Thanks for the help.
Regards,
Emilio
|||
Thank you; SP1 is installed. I found ASGroup in
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.2\Setup]
The fours keys appeared to be recreated by the install of SP1. Regards, Eric Lapham
|||Correct, I should have mentioned that as well. These keys will get recreated correctly during the following SP1 install. Glad to hear it works for you!Samuel Lester (MSFT)|||
Samuel, I am getting ready to install SP1. Would you recommend deleting these values prior to any attempt to install SP1
Regards,
Jon
Nope, no need to do this. This error only occurs if someone has explicitly deleted user groups after installing RTM. We haven't seen much of this happening, but in case it has, this is how to clean it up.
Go ahead and install SP1.
Thanks,
Sam
Hello Samuel,
I experienced the same problem when installing SQL 2005 SP2.
I removed the registry values as you suggested; but I still got the failures.
Here are the partial logs :
Configuring ACL for WMI namespace \\.\root\Microsoft\SqlServer\ComputerManagement
ACL: (A;CI;CCDCLCSWRPWPRCWD;;;BA)(A;CI;CC;;;WD)
<Func Name='SecureWMINamespace'>
No need to protect the namespace security
<EndFunc Name='SecureWMINamespace' Return='0' GetLastError='0'>
<EndFunc Name='Do_WMISecurity' Return='0' GetLastError='0'>
PerfTime Stop: Do_WMISecurity : Tue Jun 05 16:38:04 2007
MSI (s) (48:0C) [16:38:04:855]: Executing op: ActionStart(Name=CAFTEAddCertificate.68C6D15C_77E0_11D5_8528_00C04F68155C,,)
<EndFunc Name='LaunchFunction' Return='0' GetLastError='0'>
MSI (s) (48:0C) [16:38:04:855]: Executing op: CustomActionSchedule(Action=CAFTEAddCertificate.68C6D15C_77E0_11D5_8528_00C04F68155C,ActionType=1089,Source=BinaryData,Target=AddCertificate,CustomActionData=c:\Program Files\Microsoft SQL Server\MSSQL.2\MSSQL\Binn\)
MSI (s) (48:CC) [16:38:04:875]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI596.tmp, Entrypoint: AddCertificate
FTECa.DLL: INFO: FTE: AddCertificate(), Entering...
FTECa.DLL: INFO: FTE: AddCertificate: CustomActionData: c:\Program Files\Microsoft SQL Server\MSSQL.2\MSSQL\Binn\
MSI (s) (48:0C) [16:38:05:416]: Executing op: ActionStart(Name=CAFTEInstallPerfCounters.68C6D15C_77E0_11D5_8528_00C04F68155C,,)
FTECa.DLL: INFO: FTE: AddCertificate: Succeeded. Added Certificate from c:\Program Files\Microsoft SQL Server\MSSQL.2\MSSQL\Binn\msfte.dll
MSI (s) (48:0C) [16:38:05:416]: Executing op: CustomActionSchedule(Action=CAFTEInstallPerfCounters.68C6D15C_77E0_11D5_8528_00C04F68155C,ActionType=1089,Source=BinaryData,Target=InstallPerfCounters,CustomActionData=c:\Program Files\Microsoft SQL Server\MSSQL.2\MSSQL\Binn\
MSI (s) (48
C) [16:38:05:436]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI597.tmp, Entrypoint: InstallPerfCounters
FTECa.DLL: INFO: FTE: InstallPerfCounters(), Entering...
FTECa.DLL: INFO: InstallPerfCounters: CustomActionData: c:\Program Files\Microsoft SQL Server\MSSQL.2\MSSQL\Binn\:
FTECa.DLL: INFO: InstallPerfCounters: Instance name obtained:
FTECa.DLL: INFO: InstallPerfCounters: Instance home path: c:\Program Files\Microsoft SQL Server\MSSQL.2\MSSQL\Binn\
FTECa.DLL: INFO: Setting acls on c:\Program Files\Microsoft SQL Server\MSSQL.2\MSSQL\Binn\msfte.dll
FTECa.DLL: Warning: Failed to get BuiltinPerfMonitoringUsersSid win32error 87, this is only expected to work on w2k3+ systems
FTECa.DLL: INFO: InstallPerfCounters: Patching c:\Program Files\Microsoft SQL Server\MSSQL.2\MSSQL\Binn\fdcntrs.ini -> c:\Program Files\Microsoft SQL Server\MSSQL.2\MSSQL\Binn\ifdcntrs.ini, msftesqlFD -> msftesqlFD, MSFTESQL -> MSFTESQL
FTECa.DLL: INFO: InstallPerfCounters: Patching c:\Program Files\Microsoft SQL Server\MSSQL.2\MSSQL\Binn\ftecntrs.ini -> c:\Program Files\Microsoft SQL Server\MSSQL.2\MSSQL\Binn\iftcntrs.ini, msftesql -> msftesql, MSFTESQL -> MSFTESQL
FTECa.DLL: INFO: InstallPerfCounters: Patching c:\Program Files\Microsoft SQL Server\MSSQL.2\MSSQL\Binn\idxcntrs.ini -> c:\Program Files\Microsoft SQL Server\MSSQL.2\MSSQL\Binn\iindctrs.ini, msftesqlidx -> msftesqlidx, MSFTESQL -> MSFTESQL
FTECa.DLL: INFO: InstallPerfCounters: Perf counters from x "c:\Program Files\Microsoft SQL Server\MSSQL.2\MSSQL\Binn\ifdcntrs.ini have been installed.
FTECa.DLL: INFO: InstallPerfCounters: Perf counters from x "c:\Program Files\Microsoft SQL Server\MSSQL.2\MSSQL\Binn\iftcntrs.ini have been installed.
FTECa.DLL: INFO: InstallPerfCounters: Perf counters from x "c:\Program Files\Microsoft SQL Server\MSSQL.2\MSSQL\Binn\iindctrs.ini have been installed.
MSI (s) (48:0C) [16:38:06:127]: Executing op: ActionStart(Name=CARemoveFTEServiceDependency.68C6D15C_77E0_11D5_8528_00C04F68155C,,)
FTECa.DLL: INFO: FTE: InstallPerfCounters(), Exiting...
MSI (s) (48:0C) [16:38:06:127]: Executing op: CustomActionSchedule(Action=CARemoveFTEServiceDependency.68C6D15C_77E0_11D5_8528_00C04F68155C,ActionType=1025,Source=BinaryData,Target=RemoveFTEServiceDependency,CustomActionData=msftesql)
MSI (s) (48:34) [16:38:06:147]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI598.tmp, Entrypoint: RemoveFTEServiceDependency
FTECa.DLL: INFO: FTE: Enter RemoveFTEServiceDependency()
FTECa.DLL: INFO: FTE: RemoveFTEServiceDependency: Service name obtained: msftesql
MSI (s) (48:0C) [16:38:07:008]: Executing op: ActionStart(Name=CASetLaunchPermissions.68C6D15C_77E0_11D5_8528_00C04F68155C,,)
FTECa.DLL: INFO: FTE: Exit RemoveFTEServiceDependency()
MSI (s) (48:0C) [16:38:07:018]: Executing op: CustomActionSchedule(Action=CASetLaunchPermissions.68C6D15C_77E0_11D5_8528_00C04F68155C,ActionType=1089,Source=BinaryData,Target=SetLaunchPermissions,CustomActionData={68C6D318-77E0-11D5-8528-00C04F68155C}:NT AUTHORITY\SYSTEM)
MSI (s) (48:8C) [16:38:07:038]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI599.tmp, Entrypoint: SetLaunchPermissions
MSI (s) (48:0C) [16:38:07:228]: Executing op: ActionStart(Name=StartServices,Description=Starting services,Template=Service: [1])
MSI (s) (48:0C) [16:38:07:238]: Executing op: ProgressTotal(Total=6,Type=1,ByteEquivalent=1300000)
MSI (s) (48:0C) [16:38:07:238]: Executing op: ServiceControl(,Name=SQLWriter,Action=1,Wait=0,)
MSI (s) (48:0C) [16:38:37:277]: Transforming table Error.
MSI (s) (48:0C) [16:38:37:277]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (48:0C) [16:38:37:397]: Transforming table Error.
MSI (s) (48:0C) [16:38:37:407]: Transforming table Error.
MSI (s) (48:0C) [16:38:37:407]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (48:0C) [16:38:37:407]: Transforming table Error.
MSI (s) (48:0C) [16:38:37:407]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (48:0C) [16:38:37:407]: Transforming table Error.
MSI (s) (48:0C) [16:38:37:407]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (48:0C) [16:38:37:498]: Transforming table Error.
MSI (s) (48:0C) [16:38:37:498]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (48:0C) [16:38:37:528]: Transforming table Error.
MSI (s) (48:0C) [16:38:37:538]: Transforming table Error.
MSI (s) (48:0C) [16:38:37:538]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (48:0C) [16:38:37:538]: Transforming table Error.
MSI (s) (48:0C) [16:38:37:538]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (48:0C) [16:38:37:538]: Transforming table Error.
MSI (s) (48:0C) [16:38:37:538]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (48:0C) [16:38:37:538]: Product: Microsoft SQL Server 2005 -- Error 1920. Service 'SQLWriter' (SQLWriter) failed to start. Verify that you have sufficient privileges to start system services.
Error 1920. Service 'SQLWriter' (SQLWriter) failed to start. Verify that you have sufficient privileges to start system services.
MSI (s) (48:0C) [16:38:37:568]: User policy value 'DisableRollback' is 0
MSI (s) (48:0C) [16:38:37:568]: Machine policy value 'DisableRollback' is 0
Action ended 16:38:37: InstallFinalize. Return value 3.
Any suggestion are much appreciated
Thanks
David Chan
Install errror in SQLServer 2005 SP1
I have a error instaling SP1 for SQLServer 2005 Standard Edition Spanish.
The log is the following:
.....
Doing Action: SetInstanceProperty
PerfTime Start: SetInstanceProperty : Wed Apr 26 16:02:31 2006
<Func Name='SetInstanceProperty'>
MSI (s) (48!D0) [16:02:31:827]: PROPERTY CHANGE: Adding SqlOriginalMachineName property. Its value is 'WS03'.
MSI (s) (48!D0) [16:02:31:827]: PROPERTY CHANGE: Adding SqlLegacyRegPath property. Its value is 'MSSQLServer'.
MSI (s) (48!D0) [16:02:31:859]: PROPERTY CHANGE: Adding PreviousInstId property. Its value is 'MSSQL.1'.
Using instanced id: MSSQL.1
MSI (s) (48!D0) [16:02:31:859]: PROPERTY CHANGE: Adding InstId property. Its value is 'MSSQL.1'.
Previous instance id: MSSQL.1
Using instance name: MSSQLSERVER
MSI (s) (48!D0) [16:02:31:890]: PROPERTY CHANGE: Adding PrevRegRootPath property. Its value is 'Software\Microsoft\Microsoft SQL Server\MSSQL.1'.
MSI (s) (48!D0) [16:02:31:921]: PROPERTY CHANGE: Adding Sql2KSxS property. Its value is '1'.
MSI (s) (48!D0) [16:02:31:921]: PROPERTY CHANGE: Adding InstanceName.D20239D7_E87C_40C9_9837_E70B8D4882C2 property. Its value is 'MSSQLSERVER'.
MSI (s) (48!D0) [16:02:31:921]: PROPERTY CHANGE: Adding ServicePrefixRS.6080319C_1466_426E_9E7A_1DD555143E0A property. Its value is 'SQLServer2005ReportServerUser$WS03$'.
MSI (s) (48!D0) [16:02:31:921]: PROPERTY CHANGE: Adding ServicePrefixSSIS.6080319C_1466_426E_9E7A_1DD555143E0A property. Its value is 'SQLServer2005DTSUser$WS03'.
MSI (s) (48!D0) [16:02:31:921]: PROPERTY CHANGE: Adding ServiceGroupSQLBrowser.2FC2D269_8625_4826_BB3F_F9059090CB38 property. Its value is 'SQLServer2005SQLBrowserUser$WS03'.
MSI (s) (48!D0) [16:02:31:921]: PROPERTY CHANGE: Adding QuotedServiceGroupSQLBrowser.2FC2D269_8625_4826_BB3F_F9059090CB38 property. Its value is 'RIEDER\SQLServer2005SQLBrowserUser$WS03'.
MSI (s) (48!D0) [16:02:31:921]: PROPERTY CHANGE: Adding ServiceGroupSQLBrowser.03BE59F9_3DFA_413B_A99C_B95CA31A7BFE property. Its value is 'SQLServer2005SQLBrowserUser$WS03'.
MSI (s) (48!D0) [16:02:31:921]: PROPERTY CHANGE: Adding QuotedServiceGroupSQLBrowser.03BE59F9_3DFA_413B_A99C_B95CA31A7BFE property. Its value is 'RIEDER\SQLServer2005SQLBrowserUser$WS03'.
MSI (s) (48!D0) [16:02:31:921]: PROPERTY CHANGE: Adding ServiceGroupSQLBrowser.879C8BDB_884A_4C3C_80C3_3452EA2B8439 property. Its value is 'SQLServer2005SQLBrowserUser$WS03'.
MSI (s) (48!D0) [16:02:31:921]: PROPERTY CHANGE: Adding QuotedServiceGroupSQLBrowser.879C8BDB_884A_4C3C_80C3_3452EA2B8439 property. Its value is 'RIEDER\SQLServer2005SQLBrowserUser$WS03'.
MSI (s) (48!D0) [16:02:31:921]: PROPERTY CHANGE: Adding ServiceGroupADHelper.2C8E638F_C982_4AA5_A173_7148A8E8649D property. Its value is 'SQLServer2005MSSQLServerADHelperUser$WS03'.
MSI (s) (48!D0) [16:02:31:921]: PROPERTY CHANGE: Adding QuotedServiceGroupADHelper.2C8E638F_C982_4AA5_A173_7148A8E8649D property. Its value is 'RIEDER\SQLServer2005MSSQLServerADHelperUser$WS03'.
MSI (s) (48!D0) [16:02:31:921]: PROPERTY CHANGE: Adding InstanceRegKey.2C8E638F_C982_4AA5_A173_7148A8E8649D property. Its value is 'Microsoft SQL Server\MSSQL.1'.
MSI (s) (48!D0) [16:02:31:921]: PROPERTY CHANGE: Adding DataInstanceTxt.EAD22282_F1AF_4119_B1F9_C9F1DCBC62FF property. Its value is 'C:\Archivos de programa\Microsoft SQL Server\MSSQL.1\MSSQL'.
MSI (s) (48!D0) [16:02:31:921]: PROPERTY CHANGE: Adding ServiceNameSQL.EAD22282_F1AF_4119_B1F9_C9F1DCBC62FF property. Its value is 'MSSQLSERVER'.
Using PrevRegRootPath: Software\Microsoft\Microsoft SQL Server\MSSQL.1
GetServiceUserGroup failed for MSSQLSERVER, 5
Error Code: 0x80070534 (1332)
Windows Error Text: No se ha efectuado ninguna asignación entre los nombres de cuenta y los identificadores de seguridad.
Source File Name: sqlca\sqlcax.cpp
Compiler Timestamp: Mon Feb 27 02:04:14 2006
Function Name: SetInstanceProperty
Source Line Number: 1223
MSI (s) (48!D0) [16:02:31:937]: Transforming table Error.
MSI (s) (48!D0) [16:02:31:937]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (48!D0) [16:02:31:937]: Transforming table Error.
MSI (s) (48!D0) [16:02:31:937]: Transforming table Error.
MSI (s) (48!D0) [16:02:31:937]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (48!D0) [16:02:31:937]: Transforming table Error.
MSI (s) (48!D0) [16:02:31:937]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (48!D0) [16:02:31:937]: Transforming table Error.
MSI (s) (48!D0) [16:02:31:937]: Note: 1: 2262 2: Error 3: -2147287038
Error Code: 1332
MSI (s) (48!D0) [16:02:31:952]: Transforming table Error.
MSI (s) (48!D0) [16:02:31:952]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (48!D0) [16:02:31:952]: Transforming table Error.
MSI (s) (48!D0) [16:02:31:952]: Transforming table Error.
MSI (s) (48!D0) [16:02:31:952]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (48!D0) [16:02:31:952]: Transforming table Error.
MSI (s) (48!D0) [16:02:31:952]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (48!D0) [16:02:31:952]: Transforming table Error.
MSI (s) (48!D0) [16:02:31:952]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (48!D0) [16:02:31:952]: Producto: Microsoft SQL Server 2005 -- Error 29528. El programa de instalación ha detectado un error inesperado al Estableciendo propiedades internas. El error es: Error grave durante la instalación.
.
Error 29528. El programa de instalación ha detectado un error inesperado al Estableciendo propiedades internas. El error es: Error grave durante la instalación.
.
<Failure Type='Fatal' Error='1332'>
<EndFunc Name='LaunchFunction' Return='1332' GetLastError='0'>
MSI (s) (48:9C) [16:02:31:952]: Transforming table InstallExecuteSequence.
MSI (s) (48:9C) [16:02:31:952]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (48:9C) [16:02:31:952]: Transforming table InstallExecuteSequence.
MSI (s) (48:9C) [16:02:31:952]: Transforming table InstallExecuteSequence.
MSI (s) (48:9C) [16:02:31:952]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (48:9C) [16:02:31:952]: Transforming table InstallExecuteSequence.
MSI (s) (48:9C) [16:02:31:952]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (48:9C) [16:02:31:952]: Transforming table InstallExecuteSequence.
MSI (s) (48:9C) [16:02:31:952]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
La acción terminó a las 16:02:31: SetInstanceProperty.D20239D7_E87C_40C9_9837_E70B8D4882C2. Valor devuelto: 3.
La acción terminó a las 16:02:31: INSTALL. Valor devuelto: 3.
Property(S): ProductCode = {FD515EB7-E1C3-4278-9EC2-047672A8B718}
Property(S): ProductLanguage = 3082
Property(S): Manufacturer = Microsoft Corporation
Property(S): ProductVersion = 9.1.2047.00
Property(S): MEDIAPACKAGEPATH = \Setup\
Property(S): ALLUSERS = 1
Property(S): NULLGUID = {00000000-0000-0000-0000-000000000000}
Property(S): ASPNetVersion = 2.0.50727
Property(S): ARPHELPLINK = http://go.microsoft.com/fwlink/?LinkId=52152
Property(S): ARPPRODUCTICON = ARPIcon.ico
Property(S): ARPNOREPAIR = 1
Property(S): ARPSYSTEMCOMPONENT = 1
Property(S): MsiHiddenProperties = SQLPASSWORD;AGTPASSWORD;ASPASSWORD;RSPASSWORD;SQLBROWSERPASSWORD;RSSQLPASSWORD;RSSQLPassword;RSSQLPasswordQuoted;RSSETUPPASSWORD;RSSetupPassword;SAPWD;saPWD;UPGRADEPWD;SqlUpgradePwd;SQLPassword;ServicePassword;ADMINPASSWORD;PIDKEY;FTEPassword.68C6D15C_77E0_11D5_8528_00C04F68155C;checksum.7354AFCB_913B_4E9F_B76C_2376101FDE0C;checksum.;DigitalProductID;DPID;Do_sqlScript.D20239D7_E87C_40C9_9837_E70B8D4882C2;Rollback_SqlConnection.D20239D7_E87C_40C9_9837_E70B8D4882C2;Do_XmlSingleNode.D20239D7_E87C_40C9_9837_E70B8D4882C2;Do_RSSetting.D20239D7_E87C_40C9_9837_E70B8D4882C2;PID;ProductID;RSUPGRADEPASSWORD;Do_RSSetSharePointExclusionPath.D20239D7_E87C_40C9_9837_E70B8D4882C2
Property(S): SecureCustomProperties = SQL_SHOWLIC;UPGRADESQL90
Property(S): SqlServerBuild = 1
Property(S): SqlCluster = 0
Property(S): INSTALLLEVEL = 90
Property(S): FXAssemblyVersion = 2.0.0.0
Property(S): VSAssemblyVersion = 8.0.0.0
Property(S): SqlErrorReporting = #0
Property(S): SqlSqmReporting = #0
Property(S): SqlEnableRanu = 0
Property(S): SqlPatchLevel = 9.1.2047
Property(S): ChannelID = 271
Property(S): PIDTemplate = 77656<````=````=````=````=`````>@.@.@.@.@.
Property(S): mpc = 77656
Property(S): OEMRelease = 0
Property(S): PIDKEY = **********
Property(S): ProgramFilesFolder = C:\Archivos de programa\
Property(S): ProductID = **********
Property(S): SqlInstanceName = MSSQLSERVER
Property(S): SqlSecurityMode = SQL
Property(S): SqlClusterSec = 0
Property(S): MDACSXS = 1
Property(S): DefaultUIFont = Tahoma8
Property(S): VersionNT = 502
Property(S): LocalSystemAccount = NT AUTHORITY\SYSTEM
Property(S): DefaultBuiltInAccount = LocalSystemAccount
.....
Thks
Emilio, unfortunately this is a known issue. Here is a snippet from a log I posted previously (from an English log).
The log post reads:
Using PrevRegRootPath: Software\Microsoft\Microsoft SQL Server\MSSQL.1
GetServiceUserGroup failed for MSSQLSERVER, 5
Error Code: 0x80070534 (1332)
Windows Error Text: No mapping between account names and security IDs was done.
We are currently investigating this issue, but my guess is that after RTM, someone deleted the user groups that were created during install. SQL setup creates several user groups that are used during setup. It appears that SP1 is also looking to use these and they no longer exist. The user groups are named in this fashion: SQLServer2005MSSQLUser$<MachineName>$<InstanceName>
We are still looking into it and hope to have a solution soon.
Thanks,
Samuel Lester (MSFT)
Is a solution to this available?
Regards,
Eric Lapham
SQL server uses local group for ACLs. When the server is installed the groups are created and their SIDs are stored in the registry. Somewhere along the way, the SID had to change and the SIDs in the registry were not valid anymore. Try to delete the values for the following values in Setup registry key the instance hive [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.1\Setup]
The registry values are:
AGTGroup
SQLGroup
FTSGroup
ASGroup
Thanks,
Samuel Lester (MSFT)
i deleted the registry value for AGTGroup, SQLGroupF, TSGroup and ASGroup and the setup ended now correct for all product.
Thanks for the help.
Regards,
Emilio
|||
Thank you; SP1 is installed. I found ASGroup in
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.2\Setup]
The fours keys appeared to be recreated by the install of SP1. Regards, Eric Lapham
|||Correct, I should have mentioned that as well. These keys will get recreated correctly during the following SP1 install. Glad to hear it works for you!Samuel Lester (MSFT)|||
Samuel, I am getting ready to install SP1. Would you recommend deleting these values prior to any attempt to install SP1
Regards,
Jon
Nope, no need to do this. This error only occurs if someone has explicitly deleted user groups after installing RTM. We haven't seen much of this happening, but in case it has, this is how to clean it up.
Go ahead and install SP1.
Thanks,
Sam
Hello Samuel,
I experienced the same problem when installing SQL 2005 SP2.
I removed the registry values as you suggested; but I still got the failures.
Here are the partial logs :
Configuring ACL for WMI namespace \\.\root\Microsoft\SqlServer\ComputerManagement
ACL: (A;CI;CCDCLCSWRPWPRCWD;;;BA)(A;CI;CC;;;WD)
<Func Name='SecureWMINamespace'>
No need to protect the namespace security
<EndFunc Name='SecureWMINamespace' Return='0' GetLastError='0'>
<EndFunc Name='Do_WMISecurity' Return='0' GetLastError='0'>
PerfTime Stop: Do_WMISecurity : Tue Jun 05 16:38:04 2007
MSI (s) (48:0C) [16:38:04:855]: Executing op: ActionStart(Name=CAFTEAddCertificate.68C6D15C_77E0_11D5_8528_00C04F68155C,,)
<EndFunc Name='LaunchFunction' Return='0' GetLastError='0'>
MSI (s) (48:0C) [16:38:04:855]: Executing op: CustomActionSchedule(Action=CAFTEAddCertificate.68C6D15C_77E0_11D5_8528_00C04F68155C,ActionType=1089,Source=BinaryData,Target=AddCertificate,CustomActionData=c:\Program Files\Microsoft SQL Server\MSSQL.2\MSSQL\Binn\)
MSI (s) (48:CC) [16:38:04:875]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI596.tmp, Entrypoint: AddCertificate
FTECa.DLL: INFO: FTE: AddCertificate(), Entering...
FTECa.DLL: INFO: FTE: AddCertificate: CustomActionData: c:\Program Files\Microsoft SQL Server\MSSQL.2\MSSQL\Binn\
MSI (s) (48:0C) [16:38:05:416]: Executing op: ActionStart(Name=CAFTEInstallPerfCounters.68C6D15C_77E0_11D5_8528_00C04F68155C,,)
FTECa.DLL: INFO: FTE: AddCertificate: Succeeded. Added Certificate from c:\Program Files\Microsoft SQL Server\MSSQL.2\MSSQL\Binn\msfte.dll
MSI (s) (48:0C) [16:38:05:416]: Executing op: CustomActionSchedule(Action=CAFTEInstallPerfCounters.68C6D15C_77E0_11D5_8528_00C04F68155C,ActionType=1089,Source=BinaryData,Target=InstallPerfCounters,CustomActionData=c:\Program Files\Microsoft SQL Server\MSSQL.2\MSSQL\Binn\
MSI (s) (48C) [16:38:05:436]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI597.tmp, Entrypoint: InstallPerfCounters
FTECa.DLL: INFO: FTE: InstallPerfCounters(), Entering...
FTECa.DLL: INFO: InstallPerfCounters: CustomActionData: c:\Program Files\Microsoft SQL Server\MSSQL.2\MSSQL\Binn\:
FTECa.DLL: INFO: InstallPerfCounters: Instance name obtained:
FTECa.DLL: INFO: InstallPerfCounters: Instance home path: c:\Program Files\Microsoft SQL Server\MSSQL.2\MSSQL\Binn\
FTECa.DLL: INFO: Setting acls on c:\Program Files\Microsoft SQL Server\MSSQL.2\MSSQL\Binn\msfte.dll
FTECa.DLL: Warning: Failed to get BuiltinPerfMonitoringUsersSid win32error 87, this is only expected to work on w2k3+ systems
FTECa.DLL: INFO: InstallPerfCounters: Patching c:\Program Files\Microsoft SQL Server\MSSQL.2\MSSQL\Binn\fdcntrs.ini -> c:\Program Files\Microsoft SQL Server\MSSQL.2\MSSQL\Binn\ifdcntrs.ini, msftesqlFD -> msftesqlFD, MSFTESQL -> MSFTESQL
FTECa.DLL: INFO: InstallPerfCounters: Patching c:\Program Files\Microsoft SQL Server\MSSQL.2\MSSQL\Binn\ftecntrs.ini -> c:\Program Files\Microsoft SQL Server\MSSQL.2\MSSQL\Binn\iftcntrs.ini, msftesql -> msftesql, MSFTESQL -> MSFTESQL
FTECa.DLL: INFO: InstallPerfCounters: Patching c:\Program Files\Microsoft SQL Server\MSSQL.2\MSSQL\Binn\idxcntrs.ini -> c:\Program Files\Microsoft SQL Server\MSSQL.2\MSSQL\Binn\iindctrs.ini, msftesqlidx -> msftesqlidx, MSFTESQL -> MSFTESQL
FTECa.DLL: INFO: InstallPerfCounters: Perf counters from x "c:\Program Files\Microsoft SQL Server\MSSQL.2\MSSQL\Binn\ifdcntrs.ini have been installed.
FTECa.DLL: INFO: InstallPerfCounters: Perf counters from x "c:\Program Files\Microsoft SQL Server\MSSQL.2\MSSQL\Binn\iftcntrs.ini have been installed.
FTECa.DLL: INFO: InstallPerfCounters: Perf counters from x "c:\Program Files\Microsoft SQL Server\MSSQL.2\MSSQL\Binn\iindctrs.ini have been installed.
MSI (s) (48:0C) [16:38:06:127]: Executing op: ActionStart(Name=CARemoveFTEServiceDependency.68C6D15C_77E0_11D5_8528_00C04F68155C,,)
FTECa.DLL: INFO: FTE: InstallPerfCounters(), Exiting...
MSI (s) (48:0C) [16:38:06:127]: Executing op: CustomActionSchedule(Action=CARemoveFTEServiceDependency.68C6D15C_77E0_11D5_8528_00C04F68155C,ActionType=1025,Source=BinaryData,Target=RemoveFTEServiceDependency,CustomActionData=msftesql)
MSI (s) (48:34) [16:38:06:147]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI598.tmp, Entrypoint: RemoveFTEServiceDependency
FTECa.DLL: INFO: FTE: Enter RemoveFTEServiceDependency()
FTECa.DLL: INFO: FTE: RemoveFTEServiceDependency: Service name obtained: msftesql
MSI (s) (48:0C) [16:38:07:008]: Executing op: ActionStart(Name=CASetLaunchPermissions.68C6D15C_77E0_11D5_8528_00C04F68155C,,)
FTECa.DLL: INFO: FTE: Exit RemoveFTEServiceDependency()
MSI (s) (48:0C) [16:38:07:018]: Executing op: CustomActionSchedule(Action=CASetLaunchPermissions.68C6D15C_77E0_11D5_8528_00C04F68155C,ActionType=1089,Source=BinaryData,Target=SetLaunchPermissions,CustomActionData={68C6D318-77E0-11D5-8528-00C04F68155C}:NT AUTHORITY\SYSTEM)
MSI (s) (48:8C) [16:38:07:038]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI599.tmp, Entrypoint: SetLaunchPermissions
MSI (s) (48:0C) [16:38:07:228]: Executing op: ActionStart(Name=StartServices,Description=Starting services,Template=Service: [1])
MSI (s) (48:0C) [16:38:07:238]: Executing op: ProgressTotal(Total=6,Type=1,ByteEquivalent=1300000)
MSI (s) (48:0C) [16:38:07:238]: Executing op: ServiceControl(,Name=SQLWriter,Action=1,Wait=0,)
MSI (s) (48:0C) [16:38:37:277]: Transforming table Error.
MSI (s) (48:0C) [16:38:37:277]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (48:0C) [16:38:37:397]: Transforming table Error.
MSI (s) (48:0C) [16:38:37:407]: Transforming table Error.
MSI (s) (48:0C) [16:38:37:407]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (48:0C) [16:38:37:407]: Transforming table Error.
MSI (s) (48:0C) [16:38:37:407]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (48:0C) [16:38:37:407]: Transforming table Error.
MSI (s) (48:0C) [16:38:37:407]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (48:0C) [16:38:37:498]: Transforming table Error.
MSI (s) (48:0C) [16:38:37:498]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (48:0C) [16:38:37:528]: Transforming table Error.
MSI (s) (48:0C) [16:38:37:538]: Transforming table Error.
MSI (s) (48:0C) [16:38:37:538]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (48:0C) [16:38:37:538]: Transforming table Error.
MSI (s) (48:0C) [16:38:37:538]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (48:0C) [16:38:37:538]: Transforming table Error.
MSI (s) (48:0C) [16:38:37:538]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (48:0C) [16:38:37:538]: Product: Microsoft SQL Server 2005 -- Error 1920. Service 'SQLWriter' (SQLWriter) failed to start. Verify that you have sufficient privileges to start system services.
Error 1920. Service 'SQLWriter' (SQLWriter) failed to start. Verify that you have sufficient privileges to start system services.
MSI (s) (48:0C) [16:38:37:568]: User policy value 'DisableRollback' is 0
MSI (s) (48:0C) [16:38:37:568]: Machine policy value 'DisableRollback' is 0
Action ended 16:38:37: InstallFinalize. Return value 3.
Any suggestion are much appreciated
Thanks
David Chan
Install errror in SQLServer 2005 SP1
I have a error instaling SP1 for SQLServer 2005 Standard Edition Spanish.
The log is the following:
.....
Doing Action: SetInstanceProperty
PerfTime Start: SetInstanceProperty : Wed Apr 26 16:02:31 2006
<Func Name='SetInstanceProperty'>
MSI (s) (48!D0) [16:02:31:827]: PROPERTY CHANGE: Adding SqlOriginalMachineName property. Its value is 'WS03'.
MSI (s) (48!D0) [16:02:31:827]: PROPERTY CHANGE: Adding SqlLegacyRegPath property. Its value is 'MSSQLServer'.
MSI (s) (48!D0) [16:02:31:859]: PROPERTY CHANGE: Adding PreviousInstId property. Its value is 'MSSQL.1'.
Using instanced id: MSSQL.1
MSI (s) (48!D0) [16:02:31:859]: PROPERTY CHANGE: Adding InstId property. Its value is 'MSSQL.1'.
Previous instance id: MSSQL.1
Using instance name: MSSQLSERVER
MSI (s) (48!D0) [16:02:31:890]: PROPERTY CHANGE: Adding PrevRegRootPath property. Its value is 'Software\Microsoft\Microsoft SQL Server\MSSQL.1'.
MSI (s) (48!D0) [16:02:31:921]: PROPERTY CHANGE: Adding Sql2KSxS property. Its value is '1'.
MSI (s) (48!D0) [16:02:31:921]: PROPERTY CHANGE: Adding InstanceName.D20239D7_E87C_40C9_9837_E70B8D4882C2 property. Its value is 'MSSQLSERVER'.
MSI (s) (48!D0) [16:02:31:921]: PROPERTY CHANGE: Adding ServicePrefixRS.6080319C_1466_426E_9E7A_1DD555143E0A property. Its value is 'SQLServer2005ReportServerUser$WS03$'.
MSI (s) (48!D0) [16:02:31:921]: PROPERTY CHANGE: Adding ServicePrefixSSIS.6080319C_1466_426E_9E7A_1DD555143E0A property. Its value is 'SQLServer2005DTSUser$WS03'.
MSI (s) (48!D0) [16:02:31:921]: PROPERTY CHANGE: Adding ServiceGroupSQLBrowser.2FC2D269_8625_4826_BB3F_F9059090CB38 property. Its value is 'SQLServer2005SQLBrowserUser$WS03'.
MSI (s) (48!D0) [16:02:31:921]: PROPERTY CHANGE: Adding QuotedServiceGroupSQLBrowser.2FC2D269_8625_4826_BB3F_F9059090CB38 property. Its value is 'RIEDER\SQLServer2005SQLBrowserUser$WS03'.
MSI (s) (48!D0) [16:02:31:921]: PROPERTY CHANGE: Adding ServiceGroupSQLBrowser.03BE59F9_3DFA_413B_A99C_B95CA31A7BFE property. Its value is 'SQLServer2005SQLBrowserUser$WS03'.
MSI (s) (48!D0) [16:02:31:921]: PROPERTY CHANGE: Adding QuotedServiceGroupSQLBrowser.03BE59F9_3DFA_413B_A99C_B95CA31A7BFE property. Its value is 'RIEDER\SQLServer2005SQLBrowserUser$WS03'.
MSI (s) (48!D0) [16:02:31:921]: PROPERTY CHANGE: Adding ServiceGroupSQLBrowser.879C8BDB_884A_4C3C_80C3_3452EA2B8439 property. Its value is 'SQLServer2005SQLBrowserUser$WS03'.
MSI (s) (48!D0) [16:02:31:921]: PROPERTY CHANGE: Adding QuotedServiceGroupSQLBrowser.879C8BDB_884A_4C3C_80C3_3452EA2B8439 property. Its value is 'RIEDER\SQLServer2005SQLBrowserUser$WS03'.
MSI (s) (48!D0) [16:02:31:921]: PROPERTY CHANGE: Adding ServiceGroupADHelper.2C8E638F_C982_4AA5_A173_7148A8E8649D property. Its value is 'SQLServer2005MSSQLServerADHelperUser$WS03'.
MSI (s) (48!D0) [16:02:31:921]: PROPERTY CHANGE: Adding QuotedServiceGroupADHelper.2C8E638F_C982_4AA5_A173_7148A8E8649D property. Its value is 'RIEDER\SQLServer2005MSSQLServerADHelperUser$WS03'.
MSI (s) (48!D0) [16:02:31:921]: PROPERTY CHANGE: Adding InstanceRegKey.2C8E638F_C982_4AA5_A173_7148A8E8649D property. Its value is 'Microsoft SQL Server\MSSQL.1'.
MSI (s) (48!D0) [16:02:31:921]: PROPERTY CHANGE: Adding DataInstanceTxt.EAD22282_F1AF_4119_B1F9_C9F1DCBC62FF property. Its value is 'C:\Archivos de programa\Microsoft SQL Server\MSSQL.1\MSSQL'.
MSI (s) (48!D0) [16:02:31:921]: PROPERTY CHANGE: Adding ServiceNameSQL.EAD22282_F1AF_4119_B1F9_C9F1DCBC62FF property. Its value is 'MSSQLSERVER'.
Using PrevRegRootPath: Software\Microsoft\Microsoft SQL Server\MSSQL.1
GetServiceUserGroup failed for MSSQLSERVER, 5
Error Code: 0x80070534 (1332)
Windows Error Text: No se ha efectuado ninguna asignación entre los nombres de cuenta y los identificadores de seguridad.
Source File Name: sqlca\sqlcax.cpp
Compiler Timestamp: Mon Feb 27 02:04:14 2006
Function Name: SetInstanceProperty
Source Line Number: 1223
MSI (s) (48!D0) [16:02:31:937]: Transforming table Error.
MSI (s) (48!D0) [16:02:31:937]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (48!D0) [16:02:31:937]: Transforming table Error.
MSI (s) (48!D0) [16:02:31:937]: Transforming table Error.
MSI (s) (48!D0) [16:02:31:937]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (48!D0) [16:02:31:937]: Transforming table Error.
MSI (s) (48!D0) [16:02:31:937]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (48!D0) [16:02:31:937]: Transforming table Error.
MSI (s) (48!D0) [16:02:31:937]: Note: 1: 2262 2: Error 3: -2147287038
Error Code: 1332
MSI (s) (48!D0) [16:02:31:952]: Transforming table Error.
MSI (s) (48!D0) [16:02:31:952]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (48!D0) [16:02:31:952]: Transforming table Error.
MSI (s) (48!D0) [16:02:31:952]: Transforming table Error.
MSI (s) (48!D0) [16:02:31:952]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (48!D0) [16:02:31:952]: Transforming table Error.
MSI (s) (48!D0) [16:02:31:952]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (48!D0) [16:02:31:952]: Transforming table Error.
MSI (s) (48!D0) [16:02:31:952]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (48!D0) [16:02:31:952]: Producto: Microsoft SQL Server 2005 -- Error 29528. El programa de instalación ha detectado un error inesperado al Estableciendo propiedades internas. El error es: Error grave durante la instalación.
.
Error 29528. El programa de instalación ha detectado un error inesperado al Estableciendo propiedades internas. El error es: Error grave durante la instalación.
.
<Failure Type='Fatal' Error='1332'>
<EndFunc Name='LaunchFunction' Return='1332' GetLastError='0'>
MSI (s) (48:9C) [16:02:31:952]: Transforming table InstallExecuteSequence.
MSI (s) (48:9C) [16:02:31:952]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (48:9C) [16:02:31:952]: Transforming table InstallExecuteSequence.
MSI (s) (48:9C) [16:02:31:952]: Transforming table InstallExecuteSequence.
MSI (s) (48:9C) [16:02:31:952]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (48:9C) [16:02:31:952]: Transforming table InstallExecuteSequence.
MSI (s) (48:9C) [16:02:31:952]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (48:9C) [16:02:31:952]: Transforming table InstallExecuteSequence.
MSI (s) (48:9C) [16:02:31:952]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
La acción terminó a las 16:02:31: SetInstanceProperty.D20239D7_E87C_40C9_9837_E70B8D4882C2. Valor devuelto: 3.
La acción terminó a las 16:02:31: INSTALL. Valor devuelto: 3.
Property(S): ProductCode = {FD515EB7-E1C3-4278-9EC2-047672A8B718}
Property(S): ProductLanguage = 3082
Property(S): Manufacturer = Microsoft Corporation
Property(S): ProductVersion = 9.1.2047.00
Property(S): MEDIAPACKAGEPATH = \Setup\
Property(S): ALLUSERS = 1
Property(S): NULLGUID = {00000000-0000-0000-0000-000000000000}
Property(S): ASPNetVersion = 2.0.50727
Property(S): ARPHELPLINK = http://go.microsoft.com/fwlink/?LinkId=52152
Property(S): ARPPRODUCTICON = ARPIcon.ico
Property(S): ARPNOREPAIR = 1
Property(S): ARPSYSTEMCOMPONENT = 1
Property(S): MsiHiddenProperties = SQLPASSWORD;AGTPASSWORD;ASPASSWORD;RSPASSWORD;SQLBROWSERPASSWORD;RSSQLPASSWORD;RSSQLPassword;RSSQLPasswordQuoted;RSSETUPPASSWORD;RSSetupPassword;SAPWD;saPWD;UPGRADEPWD;SqlUpgradePwd;SQLPassword;ServicePassword;ADMINPASSWORD;PIDKEY;FTEPassword.68C6D15C_77E0_11D5_8528_00C04F68155C;checksum.7354AFCB_913B_4E9F_B76C_2376101FDE0C;checksum.;DigitalProductID;DPID;Do_sqlScript.D20239D7_E87C_40C9_9837_E70B8D4882C2;Rollback_SqlConnection.D20239D7_E87C_40C9_9837_E70B8D4882C2;Do_XmlSingleNode.D20239D7_E87C_40C9_9837_E70B8D4882C2;Do_RSSetting.D20239D7_E87C_40C9_9837_E70B8D4882C2;PID;ProductID;RSUPGRADEPASSWORD;Do_RSSetSharePointExclusionPath.D20239D7_E87C_40C9_9837_E70B8D4882C2
Property(S): SecureCustomProperties = SQL_SHOWLIC;UPGRADESQL90
Property(S): SqlServerBuild = 1
Property(S): SqlCluster = 0
Property(S): INSTALLLEVEL = 90
Property(S): FXAssemblyVersion = 2.0.0.0
Property(S): VSAssemblyVersion = 8.0.0.0
Property(S): SqlErrorReporting = #0
Property(S): SqlSqmReporting = #0
Property(S): SqlEnableRanu = 0
Property(S): SqlPatchLevel = 9.1.2047
Property(S): ChannelID = 271
Property(S): PIDTemplate = 77656<````=````=````=````=`````>@.@.@.@.@.
Property(S): mpc = 77656
Property(S): OEMRelease = 0
Property(S): PIDKEY = **********
Property(S): ProgramFilesFolder = C:\Archivos de programa\
Property(S): ProductID = **********
Property(S): SqlInstanceName = MSSQLSERVER
Property(S): SqlSecurityMode = SQL
Property(S): SqlClusterSec = 0
Property(S): MDACSXS = 1
Property(S): DefaultUIFont = Tahoma8
Property(S): VersionNT = 502
Property(S): LocalSystemAccount = NT AUTHORITY\SYSTEM
Property(S): DefaultBuiltInAccount = LocalSystemAccount
.....
Thks
Emilio, unfortunately this is a known issue. Here is a snippet from a log I posted previously (from an English log).
The log post reads:
Using PrevRegRootPath: Software\Microsoft\Microsoft SQL Server\MSSQL.1
GetServiceUserGroup failed for MSSQLSERVER, 5
Error Code: 0x80070534 (1332)
Windows Error Text: No mapping between account names and security IDs was done.
We are currently investigating this issue, but my guess is that after RTM, someone deleted the user groups that were created during install. SQL setup creates several user groups that are used during setup. It appears that SP1 is also looking to use these and they no longer exist. The user groups are named in this fashion: SQLServer2005MSSQLUser$<MachineName>$<InstanceName>
We are still looking into it and hope to have a solution soon.
Thanks,
Samuel Lester (MSFT)
Is a solution to this available?
Regards,
Eric Lapham
SQL server uses local group for ACLs. When the server is installed the groups are created and their SIDs are stored in the registry. Somewhere along the way, the SID had to change and the SIDs in the registry were not valid anymore. Try to delete the values for the following values in Setup registry key the instance hive [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.1\Setup]
The registry values are:
AGTGroup
SQLGroup
FTSGroup
ASGroup
Thanks,
Samuel Lester (MSFT)
i deleted the registry value for AGTGroup, SQLGroupF, TSGroup and ASGroup and the setup ended now correct for all product.
Thanks for the help.
Regards,
Emilio
|||
Thank you; SP1 is installed. I found ASGroup in
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.2\Setup]
The fours keys appeared to be recreated by the install of SP1. Regards, Eric Lapham
|||Correct, I should have mentioned that as well. These keys will get recreated correctly during the following SP1 install. Glad to hear it works for you!Samuel Lester (MSFT)|||
Samuel, I am getting ready to install SP1. Would you recommend deleting these values prior to any attempt to install SP1
Regards,
Jon
Nope, no need to do this. This error only occurs if someone has explicitly deleted user groups after installing RTM. We haven't seen much of this happening, but in case it has, this is how to clean it up.
Go ahead and install SP1.
Thanks,
Sam
Hello Samuel,
I experienced the same problem when installing SQL 2005 SP2.
I removed the registry values as you suggested; but I still got the failures.
Here are the partial logs :
Configuring ACL for WMI namespace \\.\root\Microsoft\SqlServer\ComputerManagement
ACL: (A;CI;CCDCLCSWRPWPRCWD;;;BA)(A;CI;CC;;;WD)
<Func Name='SecureWMINamespace'>
No need to protect the namespace security
<EndFunc Name='SecureWMINamespace' Return='0' GetLastError='0'>
<EndFunc Name='Do_WMISecurity' Return='0' GetLastError='0'>
PerfTime Stop: Do_WMISecurity : Tue Jun 05 16:38:04 2007
MSI (s) (48:0C) [16:38:04:855]: Executing op: ActionStart(Name=CAFTEAddCertificate.68C6D15C_77E0_11D5_8528_00C04F68155C,,)
<EndFunc Name='LaunchFunction' Return='0' GetLastError='0'>
MSI (s) (48:0C) [16:38:04:855]: Executing op: CustomActionSchedule(Action=CAFTEAddCertificate.68C6D15C_77E0_11D5_8528_00C04F68155C,ActionType=1089,Source=BinaryData,Target=AddCertificate,CustomActionData=c:\Program Files\Microsoft SQL Server\MSSQL.2\MSSQL\Binn\)
MSI (s) (48:CC) [16:38:04:875]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI596.tmp, Entrypoint: AddCertificate
FTECa.DLL: INFO: FTE: AddCertificate(), Entering...
FTECa.DLL: INFO: FTE: AddCertificate: CustomActionData: c:\Program Files\Microsoft SQL Server\MSSQL.2\MSSQL\Binn\
MSI (s) (48:0C) [16:38:05:416]: Executing op: ActionStart(Name=CAFTEInstallPerfCounters.68C6D15C_77E0_11D5_8528_00C04F68155C,,)
FTECa.DLL: INFO: FTE: AddCertificate: Succeeded. Added Certificate from c:\Program Files\Microsoft SQL Server\MSSQL.2\MSSQL\Binn\msfte.dll
MSI (s) (48:0C) [16:38:05:416]: Executing op: CustomActionSchedule(Action=CAFTEInstallPerfCounters.68C6D15C_77E0_11D5_8528_00C04F68155C,ActionType=1089,Source=BinaryData,Target=InstallPerfCounters,CustomActionData=c:\Program Files\Microsoft SQL Server\MSSQL.2\MSSQL\Binn\
MSI (s) (48
C) [16:38:05:436]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI597.tmp, Entrypoint: InstallPerfCounters
FTECa.DLL: INFO: FTE: InstallPerfCounters(), Entering...
FTECa.DLL: INFO: InstallPerfCounters: CustomActionData: c:\Program Files\Microsoft SQL Server\MSSQL.2\MSSQL\Binn\:
FTECa.DLL: INFO: InstallPerfCounters: Instance name obtained:
FTECa.DLL: INFO: InstallPerfCounters: Instance home path: c:\Program Files\Microsoft SQL Server\MSSQL.2\MSSQL\Binn\
FTECa.DLL: INFO: Setting acls on c:\Program Files\Microsoft SQL Server\MSSQL.2\MSSQL\Binn\msfte.dll
FTECa.DLL: Warning: Failed to get BuiltinPerfMonitoringUsersSid win32error 87, this is only expected to work on w2k3+ systems
FTECa.DLL: INFO: InstallPerfCounters: Patching c:\Program Files\Microsoft SQL Server\MSSQL.2\MSSQL\Binn\fdcntrs.ini -> c:\Program Files\Microsoft SQL Server\MSSQL.2\MSSQL\Binn\ifdcntrs.ini, msftesqlFD -> msftesqlFD, MSFTESQL -> MSFTESQL
FTECa.DLL: INFO: InstallPerfCounters: Patching c:\Program Files\Microsoft SQL Server\MSSQL.2\MSSQL\Binn\ftecntrs.ini -> c:\Program Files\Microsoft SQL Server\MSSQL.2\MSSQL\Binn\iftcntrs.ini, msftesql -> msftesql, MSFTESQL -> MSFTESQL
FTECa.DLL: INFO: InstallPerfCounters: Patching c:\Program Files\Microsoft SQL Server\MSSQL.2\MSSQL\Binn\idxcntrs.ini -> c:\Program Files\Microsoft SQL Server\MSSQL.2\MSSQL\Binn\iindctrs.ini, msftesqlidx -> msftesqlidx, MSFTESQL -> MSFTESQL
FTECa.DLL: INFO: InstallPerfCounters: Perf counters from x "c:\Program Files\Microsoft SQL Server\MSSQL.2\MSSQL\Binn\ifdcntrs.ini have been installed.
FTECa.DLL: INFO: InstallPerfCounters: Perf counters from x "c:\Program Files\Microsoft SQL Server\MSSQL.2\MSSQL\Binn\iftcntrs.ini have been installed.
FTECa.DLL: INFO: InstallPerfCounters: Perf counters from x "c:\Program Files\Microsoft SQL Server\MSSQL.2\MSSQL\Binn\iindctrs.ini have been installed.
MSI (s) (48:0C) [16:38:06:127]: Executing op: ActionStart(Name=CARemoveFTEServiceDependency.68C6D15C_77E0_11D5_8528_00C04F68155C,,)
FTECa.DLL: INFO: FTE: InstallPerfCounters(), Exiting...
MSI (s) (48:0C) [16:38:06:127]: Executing op: CustomActionSchedule(Action=CARemoveFTEServiceDependency.68C6D15C_77E0_11D5_8528_00C04F68155C,ActionType=1025,Source=BinaryData,Target=RemoveFTEServiceDependency,CustomActionData=msftesql)
MSI (s) (48:34) [16:38:06:147]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI598.tmp, Entrypoint: RemoveFTEServiceDependency
FTECa.DLL: INFO: FTE: Enter RemoveFTEServiceDependency()
FTECa.DLL: INFO: FTE: RemoveFTEServiceDependency: Service name obtained: msftesql
MSI (s) (48:0C) [16:38:07:008]: Executing op: ActionStart(Name=CASetLaunchPermissions.68C6D15C_77E0_11D5_8528_00C04F68155C,,)
FTECa.DLL: INFO: FTE: Exit RemoveFTEServiceDependency()
MSI (s) (48:0C) [16:38:07:018]: Executing op: CustomActionSchedule(Action=CASetLaunchPermissions.68C6D15C_77E0_11D5_8528_00C04F68155C,ActionType=1089,Source=BinaryData,Target=SetLaunchPermissions,CustomActionData={68C6D318-77E0-11D5-8528-00C04F68155C}:NT AUTHORITY\SYSTEM)
MSI (s) (48:8C) [16:38:07:038]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI599.tmp, Entrypoint: SetLaunchPermissions
MSI (s) (48:0C) [16:38:07:228]: Executing op: ActionStart(Name=StartServices,Description=Starting services,Template=Service: [1])
MSI (s) (48:0C) [16:38:07:238]: Executing op: ProgressTotal(Total=6,Type=1,ByteEquivalent=1300000)
MSI (s) (48:0C) [16:38:07:238]: Executing op: ServiceControl(,Name=SQLWriter,Action=1,Wait=0,)
MSI (s) (48:0C) [16:38:37:277]: Transforming table Error.
MSI (s) (48:0C) [16:38:37:277]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (48:0C) [16:38:37:397]: Transforming table Error.
MSI (s) (48:0C) [16:38:37:407]: Transforming table Error.
MSI (s) (48:0C) [16:38:37:407]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (48:0C) [16:38:37:407]: Transforming table Error.
MSI (s) (48:0C) [16:38:37:407]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (48:0C) [16:38:37:407]: Transforming table Error.
MSI (s) (48:0C) [16:38:37:407]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (48:0C) [16:38:37:498]: Transforming table Error.
MSI (s) (48:0C) [16:38:37:498]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (48:0C) [16:38:37:528]: Transforming table Error.
MSI (s) (48:0C) [16:38:37:538]: Transforming table Error.
MSI (s) (48:0C) [16:38:37:538]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (48:0C) [16:38:37:538]: Transforming table Error.
MSI (s) (48:0C) [16:38:37:538]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (48:0C) [16:38:37:538]: Transforming table Error.
MSI (s) (48:0C) [16:38:37:538]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (48:0C) [16:38:37:538]: Product: Microsoft SQL Server 2005 -- Error 1920. Service 'SQLWriter' (SQLWriter) failed to start. Verify that you have sufficient privileges to start system services.
Error 1920. Service 'SQLWriter' (SQLWriter) failed to start. Verify that you have sufficient privileges to start system services.
MSI (s) (48:0C) [16:38:37:568]: User policy value 'DisableRollback' is 0
MSI (s) (48:0C) [16:38:37:568]: Machine policy value 'DisableRollback' is 0
Action ended 16:38:37: InstallFinalize. Return value 3.
Any suggestion are much appreciated
Thanks
David Chan
sql
Subscribe to:
Posts (Atom)