[INSTALL SQL SERVER] GOT A WARNING MESSAGE

[Microsoft SQL server 2000 standard edition server component is not
supported ont this operation system
Only client components will be avaiable for installation ]
my OS is winXP professional edition.
Anything wrong ?
please help
It is not possible to install SQL Server (the server edition) on to a =
desktop OS such as XP Pro. =20
You do have a few options if you need the DBMS installed on your =
computer (for example for development/testing). You can install the =
Personal Edition or the Developer Edition of SQL Server to your desktop =
machine.
--=20
Keith
"Agnes" <agnes@.dynamictech.com.hk> wrote in message =
news:eJd9rxOPEHA.1340@.TK2MSFTNGP12.phx.gbl...
> [Microsoft SQL server 2000 standard edition server component is not
> supported ont this operation system
> Only client components will be avaiable for installation ]
>=20
> my OS is winXP professional edition.
> Anything wrong ?
> please help
>=20
>
|||That's mean I can install to window server2000 but not XP Pro ?
"Keith Kratochvil" <sqlguy.back2u@.comcast.net> ?
news:OCgeK4OPEHA.3124@.TK2MSFTNGP12.phx.gbl ?...
It is not possible to install SQL Server (the server edition) on to a
desktop OS such as XP Pro.
You do have a few options if you need the DBMS installed on your computer
(for example for development/testing). You can install the Personal Edition
or the Developer Edition of SQL Server to your desktop machine.
Keith
"Agnes" <agnes@.dynamictech.com.hk> wrote in message
news:eJd9rxOPEHA.1340@.TK2MSFTNGP12.phx.gbl...
> [Microsoft SQL server 2000 standard edition server component is not
> supported ont this operation system
> Only client components will be avaiable for installation ]
> my OS is winXP professional edition.
> Anything wrong ?
> please help
>
|||> That's mean I can install to window server2000 but not XP Pro ?
That is the expected (and correct) behavior.

> [Microsoft SQL server 2000 standard edition server component is not
> supported ont this operation system
This is a true statement

> Only client components will be avaiable for installation ]
Also a true statement

> my OS is winXP professional edition.
This is your problem. The server editions (Standard and Enterprise) of =
SQL Server do not install on to desktop operating systems. If you want =
to install SQL Server onto your desktop operating system you will need =
to install the Personal Edition, the Developer Edition, or a trial =
edition.

> Anything wrong ?
You are trying to install SQL Server onto an operating system that it =
does not install on.
--=20
Keith
"Agnes" <agnes@.dynamictech.com.hk> wrote in message =
news:%23b76DCPPEHA.3128@.TK2MSFTNGP10.phx.gbl...
> That's mean I can install to window server2000 but not XP Pro ?
>=20
> "Keith Kratochvil" <sqlguy.back2u@.comcast.net> ?
> news:OCgeK4OPEHA.3124@.TK2MSFTNGP12.phx.gbl ?...
> It is not possible to install SQL Server (the server edition) on to a
> desktop OS such as XP Pro.
>=20
> You do have a few options if you need the DBMS installed on your =
computer
> (for example for development/testing). You can install the Personal =
Edition
> or the Developer Edition of SQL Server to your desktop machine.
>=20
> --=20
> Keith
>=20
>=20
> "Agnes" <agnes@.dynamictech.com.hk> wrote in message
> news:eJd9rxOPEHA.1340@.TK2MSFTNGP12.phx.gbl...
>=20
>

[INSTALL SQL SERVER] GOT A WARNING MESSAGE

[Microsoft SQL server 2000 standard edition server component is not
supported ont this operation system
Only client components will be avaiable for installation ]
my OS is winXP professional edition.
Anything wrong '
please helpIt is not possible to install SQL Server (the server edition) on to a =
desktop OS such as XP Pro. =20
You do have a few options if you need the DBMS installed on your =
computer (for example for development/testing). You can install the =
Personal Edition or the Developer Edition of SQL Server to your desktop =
machine.
--=20
Keith
"Agnes" <agnes@.dynamictech.com.hk> wrote in message =
news:eJd9rxOPEHA.1340@.TK2MSFTNGP12.phx.gbl...
> [Microsoft SQL server 2000 standard edition server component is not
> supported ont this operation system
> Only client components will be avaiable for installation ]
>=20
> my OS is winXP professional edition.
> Anything wrong '
> please help
>=20
>|||That's mean I can install to window server2000 but not XP Pro '
"Keith Kratochvil" <sqlguy.back2u@.comcast.net> ?
news:OCgeK4OPEHA.3124@.TK2MSFTNGP12.phx.gbl ?...
It is not possible to install SQL Server (the server edition) on to a
desktop OS such as XP Pro.
You do have a few options if you need the DBMS installed on your computer
(for example for development/testing). You can install the Personal Edition
or the Developer Edition of SQL Server to your desktop machine.
Keith
"Agnes" <agnes@.dynamictech.com.hk> wrote in message
news:eJd9rxOPEHA.1340@.TK2MSFTNGP12.phx.gbl...
> [Microsoft SQL server 2000 standard edition server component is not
> supported ont this operation system
> Only client components will be avaiable for installation ]
> my OS is winXP professional edition.
> Anything wrong '
> please help
>|||> That's mean I can install to window server2000 but not XP Pro '
That is the expected (and correct) behavior.

> [Microsoft SQL server 2000 standard edition server component is not
> supported ont this operation system
This is a true statement

> Only client components will be avaiable for installation ]
Also a true statement

> my OS is winXP professional edition.
This is your problem. The server editions (Standard and Enterprise) of =
SQL Server do not install on to desktop operating systems. If you want =
to install SQL Server onto your desktop operating system you will need =
to install the Personal Edition, the Developer Edition, or a trial =
edition.

> Anything wrong '
You are trying to install SQL Server onto an operating system that it =
does not install on.
--=20
Keith
"Agnes" <agnes@.dynamictech.com.hk> wrote in message =
news:%23b76DCPPEHA.3128@.TK2MSFTNGP10.phx.gbl...
> That's mean I can install to window server2000 but not XP Pro '
>=20
> "Keith Kratochvil" <sqlguy.back2u@.comcast.net> ?
> news:OCgeK4OPEHA.3124@.TK2MSFTNGP12.phx.gbl ?...
> It is not possible to install SQL Server (the server edition) on to a
> desktop OS such as XP Pro.
>=20
> You do have a few options if you need the DBMS installed on your =
computer
> (for example for development/testing). You can install the Personal =
Edition
> or the Developer Edition of SQL Server to your desktop machine.
>=20
> --=20
> Keith
>=20
>=20
> "Agnes" <agnes@.dynamictech.com.hk> wrote in message
> news:eJd9rxOPEHA.1340@.TK2MSFTNGP12.phx.gbl...
>=20
>

[INSTALL SQL SERVER] GOT A WARNING MESSAGE

[Microsoft SQL server 2000 standard edition server component is not
supported ont this operation system
Only client components will be avaiable for installation ]
my OS is winXP professional edition.
Anything wrong '
please helpIt is not possible to install SQL Server (the server edition) on to a =desktop OS such as XP Pro.
You do have a few options if you need the DBMS installed on your =computer (for example for development/testing). You can install the =Personal Edition or the Developer Edition of SQL Server to your desktop =machine.
-- Keith
"Agnes" <agnes@.dynamictech.com.hk> wrote in message =news:eJd9rxOPEHA.1340@.TK2MSFTNGP12.phx.gbl...
> [Microsoft SQL server 2000 standard edition server component is not
> supported ont this operation system
> Only client components will be avaiable for installation ]
> > my OS is winXP professional edition.
> Anything wrong '
> please help
> >|||That's mean I can install to window server2000 but not XP Pro '
"Keith Kratochvil" <sqlguy.back2u@.comcast.net> ?
news:OCgeK4OPEHA.3124@.TK2MSFTNGP12.phx.gbl ?...
It is not possible to install SQL Server (the server edition) on to a
desktop OS such as XP Pro.
You do have a few options if you need the DBMS installed on your computer
(for example for development/testing). You can install the Personal Edition
or the Developer Edition of SQL Server to your desktop machine.
--
Keith
"Agnes" <agnes@.dynamictech.com.hk> wrote in message
news:eJd9rxOPEHA.1340@.TK2MSFTNGP12.phx.gbl...
> [Microsoft SQL server 2000 standard edition server component is not
> supported ont this operation system
> Only client components will be avaiable for installation ]
> my OS is winXP professional edition.
> Anything wrong '
> please help
>|||> That's mean I can install to window server2000 but not XP Pro '
That is the expected (and correct) behavior.
> [Microsoft SQL server 2000 standard edition server component is not
> supported ont this operation system
This is a true statement
> Only client components will be avaiable for installation ]
Also a true statement
> my OS is winXP professional edition.
This is your problem. The server editions (Standard and Enterprise) of =SQL Server do not install on to desktop operating systems. If you want =to install SQL Server onto your desktop operating system you will need =to install the Personal Edition, the Developer Edition, or a trial =edition.
> Anything wrong '
You are trying to install SQL Server onto an operating system that it =does not install on.
-- Keith
"Agnes" <agnes@.dynamictech.com.hk> wrote in message =news:%23b76DCPPEHA.3128@.TK2MSFTNGP10.phx.gbl...
> That's mean I can install to window server2000 but not XP Pro '
> > "Keith Kratochvil" <sqlguy.back2u@.comcast.net> ?
> news:OCgeK4OPEHA.3124@.TK2MSFTNGP12.phx.gbl ?...
> It is not possible to install SQL Server (the server edition) on to a
> desktop OS such as XP Pro.
> > You do have a few options if you need the DBMS installed on your =computer
> (for example for development/testing). You can install the Personal =Edition
> or the Developer Edition of SQL Server to your desktop machine.
> > -- > Keith
> > > "Agnes" <agnes@.dynamictech.com.hk> wrote in message
> news:eJd9rxOPEHA.1340@.TK2MSFTNGP12.phx.gbl...
> > [Microsoft SQL server 2000 standard edition server component is not
> > supported ont this operation system
> > Only client components will be avaiable for installation ]
> >
> > my OS is winXP professional edition.
> > Anything wrong '
> > please help
> >
> >
> >

[DTS.Pipeline] Warning: The output column "Column 5" (1038) on output "Flat File

[DTS.Pipeline] Warning: The output column "Column 5" (1038) on output "Flat File Source Output" (2) and component "Flat File Source" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.

what the heck does this mean?

More or less what it says - you have a column that is not used by downstream component.

So the data flow issues a warning that it might be better to just remove this column to save buffer space. Of course it is just optimization warning and can be ignored, but if you want maximum performance do pay attention to such warnings.

[ActiveX Script Task] Error: Retrieving the file name for a component failed with error code 0x0

This error occurs when the ActiveX task tries to execute:

[ActiveX Script Task] Error: Retrieving the file name for a component failed with error code 0x001B6438.

Anybody know how to troubleshoot these errors? I can't find anything on this error code. The same script works in DTS.

I have got the same error, the code is different but couldn't figure out what to do...|||

Hi Igor,

This isn't much of an answer but it is true: you should try to move away from the ActiveX Script Task and use the Script Task instead.

Hope this helps,
Andy

|||Script Task does mean that there is a different scripting language?

I tryed a different thing: I moved all the script from a SSIS task to a SQL Server job (a job with one "activeX script" step).

It sounds great, but I have a different error in the step that says that
"The command script does not destroy all the objects that it creates. Revise the command script. (Microsoft SQL Server, Error: 14277)"

I am not a VB programmer, so I think I have to ask someone to revise the script.

Thanks for the help|||

ActiveX scripts in SQL Jobs (all versions) appear to have a major bug in that they report Error: 14277 whenever the string "createobject(" appears more than once anywhere in the script. It does not matter whether the string is just part of a character expression such as: sTemp = "..... createobject( ...."; whether it appears in a comment or whether it is used to actually create an object. Any combination of the above that puts "createobject(" in the script more than once will cause the 14277 error to appear when you try to close the Job modifier.

There is a trick that I have found to overcome this. That is, to create any and all objects in a single common subroutine. Even in this subroutine, you have to trick the system into thinking that you have just destroyed the object that you are trying to create.

The subroutine is cobj. It takes the variable that will become the object and a string that defines the activex control. The "set ... = Nothing" that appears after the "Exit Sub" is the trick that makes the system think that the object is destroyed within the scope of cobj. Note: be sure to destroy the object in the scope where the object variable was defined.

Here is a code sample that sends an email using ASPMAIL, which contains data from an ADO SQL query.

'*********************************************
' ActiveX Script - no 14277 error
'*********************************************
MailMe readSQL(1006), "mymail@.mail.com"

Sub cobj(newobj, ax)
Set newobj = createobject(ax) ' only appears once, here
exit sub
Set newobj = Nothing ' never executed but tricks checker
End Sub

sub MailMe (sMsg, sAddress)
dim Mailer, vRet
if instr(sAddress,"@.")<1 then exit sub

cobj Mailer, "SMTPsvg.Mailer"

Mailer.FromName = "ASP_Debug"
Mailer.FromAddress = sAddress
Mailer.RemoteHost = "127.0.0.1"
Mailer.AddRecipient "", sAddress
Mailer.Subject = "Debug ActiveX Script - 14277 Error"
Mailer.BodyText = sMsg
Mailer.SendMail
Set Mailer=Nothing
end sub

Function readSQL(ndx)
Dim SQL, sConn, oRst
readSQL = "No Record"
SQL = "SELECT Note FROM NoteTable WHERE [ID]=" & CStr(ndx)
sConn = "Provider=SQLOLEDB.1;Initial Catalog=xx;Data Source=zz"

cobj oRst, "ADODB.Recordset"

oRst.Open SQL, sConn
If oRst.State = 1 Then
readSQL = oRst(0)
oRst.Close
End If
Set oRst = Nothing
End Function

[ActiveX Script Task] Error: Retrieving the file name for a component failed with error code 0x0

This error occurs when the ActiveX task tries to execute:

[ActiveX Script Task] Error: Retrieving the file name for a component failed with error code 0x001B6438.

Anybody know how to troubleshoot these errors? I can't find anything on this error code. The same script works in DTS.

I have got the same error, the code is different but couldn't figure out what to do...|||

Hi Igor,

This isn't much of an answer but it is true: you should try to move away from the ActiveX Script Task and use the Script Task instead.

Hope this helps,
Andy

|||Script Task does mean that there is a different scripting language?

I tryed a different thing: I moved all the script from a SSIS task to a SQL Server job (a job with one "activeX script" step).

It sounds great, but I have a different error in the step that says that
"The command script does not destroy all the objects that it creates. Revise the command script. (Microsoft SQL Server, Error: 14277)"

I am not a VB programmer, so I think I have to ask someone to revise the script.

Thanks for the help|||

ActiveX scripts in SQL Jobs (all versions) appear to have a major bug in that they report Error: 14277 whenever the string "createobject(" appears more than once anywhere in the script. It does not matter whether the string is just part of a character expression such as: sTemp = "..... createobject( ...."; whether it appears in a comment or whether it is used to actually create an object. Any combination of the above that puts "createobject(" in the script more than once will cause the 14277 error to appear when you try to close the Job modifier.

There is a trick that I have found to overcome this. That is, to create any and all objects in a single common subroutine. Even in this subroutine, you have to trick the system into thinking that you have just destroyed the object that you are trying to create.

The subroutine is cobj. It takes the variable that will become the object and a string that defines the activex control. The "set ... = Nothing" that appears after the "Exit Sub" is the trick that makes the system think that the object is destroyed within the scope of cobj. Note: be sure to destroy the object in the scope where the object variable was defined.

Here is a code sample that sends an email using ASPMAIL, which contains data from an ADO SQL query.

'*********************************************
' ActiveX Script - no 14277 error
'*********************************************
MailMe readSQL(1006), "mymail@.mail.com"

Sub cobj(newobj, ax)
Set newobj = createobject(ax) ' only appears once, here
exit sub
Set newobj = Nothing ' never executed but tricks checker
End Sub

sub MailMe (sMsg, sAddress)
dim Mailer, vRet
if instr(sAddress,"@.")<1 then exit sub

cobj Mailer, "SMTPsvg.Mailer"

Mailer.FromName = "ASP_Debug"
Mailer.FromAddress = sAddress
Mailer.RemoteHost = "127.0.0.1"
Mailer.AddRecipient "", sAddress
Mailer.Subject = "Debug ActiveX Script - 14277 Error"
Mailer.BodyText = sMsg
Mailer.SendMail
Set Mailer=Nothing
end sub

Function readSQL(ndx)
Dim SQL, sConn, oRst
readSQL = "No Record"
SQL = "SELECT Note FROM NoteTable WHERE [ID]=" & CStr(ndx)
sConn = "Provider=SQLOLEDB.1;Initial Catalog=xx;Data Source=zz"

cobj oRst, "ADODB.Recordset"

oRst.Open SQL, sConn
If oRst.State = 1 Then
readSQL = oRst(0)
oRst.Close
End If
Set oRst = Nothing
End Function

[ActiveX Script Task] Error: Retrieving the file name for a component failed with error code 0x0

This error occurs when the ActiveX task tries to execute:

[ActiveX Script Task] Error: Retrieving the file name for a component failed with error code 0x001B6438.

Anybody know how to troubleshoot these errors? I can't find anything on this error code. The same script works in DTS.

I have got the same error, the code is different but couldn't figure out what to do...|||

Hi Igor,

This isn't much of an answer but it is true: you should try to move away from the ActiveX Script Task and use the Script Task instead.

Hope this helps,
Andy

|||Script Task does mean that there is a different scripting language?

I tryed a different thing: I moved all the script from a SSIS task to a SQL Server job (a job with one "activeX script" step).

It sounds great, but I have a different error in the step that says that
"The command script does not destroy all the objects that it creates. Revise the command script. (Microsoft SQL Server, Error: 14277)"

I am not a VB programmer, so I think I have to ask someone to revise the script.

Thanks for the help|||

ActiveX scripts in SQL Jobs (all versions) appear to have a major bug in that they report Error: 14277 whenever the string "createobject(" appears more than once anywhere in the script. It does not matter whether the string is just part of a character expression such as: sTemp = "..... createobject( ...."; whether it appears in a comment or whether it is used to actually create an object. Any combination of the above that puts "createobject(" in the script more than once will cause the 14277 error to appear when you try to close the Job modifier.

There is a trick that I have found to overcome this. That is, to create any and all objects in a single common subroutine. Even in this subroutine, you have to trick the system into thinking that you have just destroyed the object that you are trying to create.

The subroutine is cobj. It takes the variable that will become the object and a string that defines the activex control. The "set ... = Nothing" that appears after the "Exit Sub" is the trick that makes the system think that the object is destroyed within the scope of cobj. Note: be sure to destroy the object in the scope where the object variable was defined.

Here is a code sample that sends an email using ASPMAIL, which contains data from an ADO SQL query.

'*********************************************
' ActiveX Script - no 14277 error
'*********************************************
MailMe readSQL(1006), "mymail@.mail.com"

Sub cobj(newobj, ax)
Set newobj = createobject(ax) ' only appears once, here
exit sub
Set newobj = Nothing ' never executed but tricks checker
End Sub

sub MailMe (sMsg, sAddress)
dim Mailer, vRet
if instr(sAddress,"@.")<1 then exit sub

cobj Mailer, "SMTPsvg.Mailer"

Mailer.FromName = "ASP_Debug"
Mailer.FromAddress = sAddress
Mailer.RemoteHost = "127.0.0.1"
Mailer.AddRecipient "", sAddress
Mailer.Subject = "Debug ActiveX Script - 14277 Error"
Mailer.BodyText = sMsg
Mailer.SendMail
Set Mailer=Nothing
end sub

Function readSQL(ndx)
Dim SQL, sConn, oRst
readSQL = "No Record"
SQL = "SELECT Note FROM NoteTable WHERE [ID]=" & CStr(ndx)
sConn = "Provider=SQLOLEDB.1;Initial Catalog=xx;Data Source=zz"

cobj oRst, "ADODB.Recordset"

oRst.Open SQL, sConn
If oRst.State = 1 Then
readSQL = oRst(0)
oRst.Close
End If
Set oRst = Nothing
End Function

[ActiveX Script Task] Error: Retrieving the file name for a component failed with error code 0x0

This error occurs when the ActiveX task tries to execute:

[ActiveX Script Task] Error: Retrieving the file name for a component failed with error code 0x001B6438.

Anybody know how to troubleshoot these errors? I can't find anything on this error code. The same script works in DTS.

I have got the same error, the code is different but couldn't figure out what to do...|||

Hi Igor,

This isn't much of an answer but it is true: you should try to move away from the ActiveX Script Task and use the Script Task instead.

Hope this helps,
Andy

|||Script Task does mean that there is a different scripting language?

I tryed a different thing: I moved all the script from a SSIS task to a SQL Server job (a job with one "activeX script" step).

It sounds great, but I have a different error in the step that says that
"The command script does not destroy all the objects that it creates. Revise the command script. (Microsoft SQL Server, Error: 14277)"

I am not a VB programmer, so I think I have to ask someone to revise the script.

Thanks for the help|||

ActiveX scripts in SQL Jobs (all versions) appear to have a major bug in that they report Error: 14277 whenever the string "createobject(" appears more than once anywhere in the script. It does not matter whether the string is just part of a character expression such as: sTemp = "..... createobject( ...."; whether it appears in a comment or whether it is used to actually create an object. Any combination of the above that puts "createobject(" in the script more than once will cause the 14277 error to appear when you try to close the Job modifier.

There is a trick that I have found to overcome this. That is, to create any and all objects in a single common subroutine. Even in this subroutine, you have to trick the system into thinking that you have just destroyed the object that you are trying to create.

The subroutine is cobj. It takes the variable that will become the object and a string that defines the activex control. The "set ... = Nothing" that appears after the "Exit Sub" is the trick that makes the system think that the object is destroyed within the scope of cobj. Note: be sure to destroy the object in the scope where the object variable was defined.

Here is a code sample that sends an email using ASPMAIL, which contains data from an ADO SQL query.

'*********************************************
' ActiveX Script - no 14277 error
'*********************************************
MailMe readSQL(1006), "mymail@.mail.com"

Sub cobj(newobj, ax)
Set newobj = createobject(ax) ' only appears once, here
exit sub
Set newobj = Nothing ' never executed but tricks checker
End Sub

sub MailMe (sMsg, sAddress)
dim Mailer, vRet
if instr(sAddress,"@.")<1 then exit sub

cobj Mailer, "SMTPsvg.Mailer"

Mailer.FromName = "ASP_Debug"
Mailer.FromAddress = sAddress
Mailer.RemoteHost = "127.0.0.1"
Mailer.AddRecipient "", sAddress
Mailer.Subject = "Debug ActiveX Script - 14277 Error"
Mailer.BodyText = sMsg
Mailer.SendMail
Set Mailer=Nothing
end sub

Function readSQL(ndx)
Dim SQL, sConn, oRst
readSQL = "No Record"
SQL = "SELECT Note FROM NoteTable WHERE [ID]=" & CStr(ndx)
sConn = "Provider=SQLOLEDB.1;Initial Catalog=xx;Data Source=zz"

cobj oRst, "ADODB.Recordset"

oRst.Open SQL, sConn
If oRst.State = 1 Then
readSQL = oRst(0)
oRst.Close
End If
Set oRst = Nothing
End Function