Problem with getting up to date MSDE version using Service Pack 3a

I removed (as far as I can tell) all versions of MSDE from my
computer. This was confirmed when I examined the installed programs on
the 'Add or remove programs' screen
If I then use the files from my SP3a disk (installed on my D drive) to
apparently successfully install a new default instance of MSDE and I
subsequently check the version I get the following details:
Microsoft SQL Server 2000 - 8.00.760 (Intel X86) Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation Desktop Engine on
Windows NT 5.1 (Build 2600: Service Pack 1)
In other words I do not seem to have the up to date Service Pack 3
version installed.
My questions are:
1. Is this message misleading or does it mean that I have failed to
install the SP3a package for some reason?
2. I am using SELECT @.@.Version to get the version details- is this
appropriate?
3. Is there any other way I can check whether I have SP3a properly
installed?
(The command line instruction I am using is
setup SAPWD=Abc/def/ghk1 SECURITYMODE=SQL
I have tried to update it further using the command line
setup /upgradesp sqlrun SECURITYMODE=SQL UPGRADEUSER=sa
UPGRADEPWD=Abc/def/ghk1 DISABLENETWORKPROTOCOLS=1
This also seems to work to the extent that a screen is opened up and
it finishes properly. But again when the same version details are
obtained, no sign of it being upgraded to SP3a
Best wishes, John Morgan
hi John
"John Morgan" <jfm@.XXwoodlander.co.uk> ha scritto nel messaggio
news:lti6s0lcurtnlu681ph9s454i54omut69d@.4ax.com
> I removed (as far as I can tell) all versions of MSDE from my
> computer. This was confirmed when I examined the installed programs on
> the 'Add or remove programs' screen
> If I then use the files from my SP3a disk (installed on my D drive) to
> apparently successfully install a new default instance of MSDE and I
> subsequently check the version I get the following details:
> Microsoft SQL Server 2000 - 8.00.760 (Intel X86) Dec 17 2002 14:22:05
> Copyright (c) 1988-2003 Microsoft Corporation Desktop Engine on
> Windows NT 5.1 (Build 2600: Service Pack 1)
> In other words I do not seem to have the up to date Service Pack 3
> version installed.
> My questions are:
> 1. Is this message misleading or does it mean that I have failed to
> install the SP3a package for some reason?
>
the message is correct, but you are failing in reading it..
it says
> Microsoft SQL Server 2000 - 8.00.760 (Intel X86) Dec 17 2002 14:22:05
and 8.00.760 is service pack 3 and/or 3a build, so you are in order with
that... then it says

> Copyright (c) 1988-2003 Microsoft Corporation Desktop Engine on
> Windows NT 5.1 (Build 2600: Service Pack 1)
and this is about your Operating System... you are running on WinXP sp1

> 2. I am using SELECT @.@.Version to get the version details- is this
> appropriate?
it is, but you have to read it correctly... unfortunately Books On Line is
not very clear about it's result..
you can verify all this by running
SET NOCOUNT ON
SELECT SERVERPROPERTY('ProductLevel') AS [Service Pack],
SERVERPROPERTY('ProductVersion') AS [Build]
that will output
Service Pack Build
-- --
SP3 8.00.760
as you can check again comparing software builds (ie at
http://www.aspfaq.com/show.asp?id=2160) , again, 8.00.760 is service pack 3

> 3. Is there any other way I can check whether I have SP3a properly
> installed?
you are in order with that... but you can go on further, to chek if you are
running service pack 3a, checking the registry key CSDVersion, value is
"8.00.760" for MSDE SP3 and "8.00.761" fro MSDE SP3a:
(HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\C urrentVersion , CSDVersion
key) or, more, look at the version number of the Net-Library file,
Ssnetlib.dll. If the version number of this file is 2000.80.760.0, you have
SP3; if the version number of this file is 2000.80.766.0, you have SP3a.
but you do not need it... the package you installed is updated at service
pack 3a level
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Thank you Andrea for interpreting the version for me.
I verified it by running the SQL as well and you were right!
Much thanks , John Morgan
On Sat, 18 Dec 2004 00:40:45 +0100, "Andrea Montanari"
<andrea.sqlDMO@.virgilio.it> wrote:

>hi John
>"John Morgan" <jfm@.XXwoodlander.co.uk> ha scritto nel messaggio
>news:lti6s0lcurtnlu681ph9s454i54omut69d@.4ax.com
>the message is correct, but you are failing in reading it..
>it says
>and 8.00.760 is service pack 3 and/or 3a build, so you are in order with
>that... then it says
>and this is about your Operating System... you are running on WinXP sp1
>
>it is, but you have to read it correctly... unfortunately Books On Line is
>not very clear about it's result..
>you can verify all this by running
>SET NOCOUNT ON
>SELECT SERVERPROPERTY('ProductLevel') AS [Service Pack],
>SERVERPROPERTY('ProductVersion') AS [Build]
>that will output
>Service Pack Build
>-- --
>SP3 8.00.760
>as you can check again comparing software builds (ie at
>http://www.aspfaq.com/show.asp?id=2160) , again, 8.00.760 is service pack 3
>
>you are in order with that... but you can go on further, to chek if you are
>running service pack 3a, checking the registry key CSDVersion, value is
>"8.00.760" for MSDE SP3 and "8.00.761" fro MSDE SP3a:
>(HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\ CurrentVersion , CSDVersion
>key) or, more, look at the version number of the Net-Library file,
>Ssnetlib.dll. If the version number of this file is 2000.80.760.0, you have
>SP3; if the version number of this file is 2000.80.766.0, you have SP3a.
>but you do not need it... the package you installed is updated at service
>pack 3a level

Problem with debugging SSIS 2005 (32bit) component under Windows Vista ultimate

Hi,

I have a problem when i want to debug an ssis component under visual studio 2005.

I'm using sql 2005 with service pack 2 and i have already install patch for visual studio under vista.

When i put a breakpoint for exemple in the method "public override void PreExecute()" or in the other method. "public override void ProcessInput(int inputID, PipelineBuffer buffer)" and i execute the pgm.

however when i begin debugging,it's always skip breakpoint

However when i put a break point in the Validate method "public override DTSValidationStatus Validate()" it function.

When execute the the package it works fine.

I use this debug parametres :

Start external program :

C:\Program Files\Microsoft SQL Server\90\DTS\Binn\DTExec.exe

Command line arguments

/FILE "D:\Projects\Integration Services Project1\Integration Services Project1\TestXmlParserPipe.dtsx" /MAXCONCURRENT " -1 " /CHECKPOINTING OFF /REPORTING EWCDI

I execute visual studio 2005 as Administrator

Please, can some one help me!

It must be some sort of those trivial problems. Are you sure the execution goes through those two methods? Try to check using some kind of checkpoint logging (i. e. MessageBox).

A few additional troubleshooting tips:

- Make sure you are building the debug version of your component.

- Check if the proper module gets loaded.

- Double-check the function signatures.

HTH.

|||

Hi,

thanks for your answer.

I'm sure, i'm was building the debug version.

I notice that if i put a messagebox in the script component and i run the package.

The message box appear, so i go to my ssis component code under visual studio2005 and then i put a breakpoint in

PreExecute() method (for example), after this i attached the process DtsDebugHost.exe (this process is visible in the process list only when the package ssis is running ). I came back to the message box i click ok and finally it work i can see the yellow line hilight the method.

What can i do to let de debugger work fine under vista ultimate? In my work, we have Windows XP professional and i don't have to use complicated procedure each time i want to debug my custom component.

so it will be so nice if some one know the solution for that.

Thanks in advance.

|||

Can you confirm one thing? Are you debugging your custom component using DTExec or BIDS?

Thanks,

Bob

|||

Hi,

I debug the my custom component using DTExec :

On Start action \start external program I use :

C:\Program Files\Microsoft SQL Server\90\DTS\Binn\DTExec.exe

I'm using the following command line arguments on start option:

/FILE "..\TestXmlParserPipe.dtsx" /MAXCONCURRENT " -1 " /CHECKPOINTING OFF /REPORTING EWCDI

Please help with Windows Vista Ultimate ?

|||

Always start investigating debugging/breakpoints problems by checking if VS finds the symbols for your assembly. Go to Modules window, find your assembly, check if the symbols are loaded. If not, try to load the symbols manually.

Do you install a custom component (run gacutil /if ...) as part of VS post-build step?

What often happens is that if you don't do this, VS would build a new version of the component before starting debugging session; but the binary used by DTEXEC comes from GAC and it is different from the new version build by VS, so VS can't match the symbols and can't use the breakpoints.

Problem with debugging SSIS 2005 (32bit) component under Windows Vista ultimate

Hi,

I have a problem when i want to debug an ssis component under visual studio 2005.

I'm using sql 2005 with service pack 2 and i have already install patch for visual studio under vista.

When i put a breakpoint for exemple in the method "public override void PreExecute()" or in the other method. "public override void ProcessInput(int inputID, PipelineBuffer buffer)" and i execute the pgm.

however when i begin debugging,it's always skip breakpoint

However when i put a break point in the Validate method "public override DTSValidationStatus Validate()" it function.

When execute the the package it works fine.

I use this debug parametres :

Start external program :

C:\Program Files\Microsoft SQL Server\90\DTS\Binn\DTExec.exe

Command line arguments

/FILE "D:\Projects\Integration Services Project1\Integration Services Project1\TestXmlParserPipe.dtsx" /MAXCONCURRENT " -1 " /CHECKPOINTING OFF /REPORTING EWCDI

I execute visual studio 2005 as Administrator

Please, can some one help me!

It must be some sort of those trivial problems. Are you sure the execution goes through those two methods? Try to check using some kind of checkpoint logging (i. e. MessageBox).

A few additional troubleshooting tips:

- Make sure you are building the debug version of your component.

- Check if the proper module gets loaded.

- Double-check the function signatures.

HTH.

|||

Hi,

thanks for your answer.

I'm sure, i'm was building the debug version.

I notice that if i put a messagebox in the script component and i run the package.

The message box appear, so i go to my ssis component code under visual studio2005 and then i put a breakpoint in

PreExecute() method (for example), after this i attached the process DtsDebugHost.exe (this process is visible in the process list only when the package ssis is running ). I came back to the message box i click ok and finally it work i can see the yellow line hilight the method.

What can i do to let de debugger work fine under vista ultimate? In my work, we have Windows XP professional and i don't have to use complicated procedure each time i want to debug my custom component.

so it will be so nice if some one know the solution for that.

Thanks in advance.

|||

Can you confirm one thing? Are you debugging your custom component using DTExec or BIDS?

Thanks,

Bob

|||

Hi,

I debug the my custom component using DTExec :

On Start action \start external program I use :

C:\Program Files\Microsoft SQL Server\90\DTS\Binn\DTExec.exe

I'm using the following command line arguments on start option:

/FILE "..\TestXmlParserPipe.dtsx" /MAXCONCURRENT " -1 " /CHECKPOINTING OFF /REPORTING EWCDI

Please help with Windows Vista Ultimate ?

Problem with debugging SSIS 2005 (32bit) component under Windows Vista ultimate

Hi,

I have a problem when i want to debug an ssis component under visual studio 2005.

I'm using sql 2005 with service pack 2 and i have already install patch for visual studio under vista.

When i put a breakpoint for exemple in the method "public override void PreExecute()" or in the other method. "public override void ProcessInput(int inputID, PipelineBuffer buffer)" and i execute the pgm.

however when i begin debugging,it's always skip breakpoint

However when i put a break point in the Validate method "public override DTSValidationStatus Validate()" it function.

When execute the the package it works fine.

I use this debug parametres :

Start external program :

C:\Program Files\Microsoft SQL Server\90\DTS\Binn\DTExec.exe

Command line arguments

/FILE "D:\Projects\Integration Services Project1\Integration Services Project1\TestXmlParserPipe.dtsx" /MAXCONCURRENT " -1 " /CHECKPOINTING OFF /REPORTING EWCDI

I execute visual studio 2005 as Administrator

Please, can some one help me!

It must be some sort of those trivial problems. Are you sure the execution goes through those two methods? Try to check using some kind of checkpoint logging (i. e. MessageBox).

A few additional troubleshooting tips:

- Make sure you are building the debug version of your component.

- Check if the proper module gets loaded.

- Double-check the function signatures.

HTH.

|||

Hi,

thanks for your answer.

I'm sure, i'm was building the debug version.

I notice that if i put a messagebox in the script component and i run the package.

The message box appear, so i go to my ssis component code under visual studio2005 and then i put a breakpoint in

PreExecute() method (for example), after this i attached the process DtsDebugHost.exe (this process is visible in the process list only when the package ssis is running ). I came back to the message box i click ok and finally it work i can see the yellow line hilight the method.

What can i do to let de debugger work fine under vista ultimate? In my work, we have Windows XP professional and i don't have to use complicated procedure each time i want to debug my custom component.

so it will be so nice if some one know the solution for that.

Thanks in advance.

|||

Can you confirm one thing? Are you debugging your custom component using DTExec or BIDS?

Thanks,

Bob

|||

Hi,

I debug the my custom component using DTExec :

On Start action \start external program I use :

C:\Program Files\Microsoft SQL Server\90\DTS\Binn\DTExec.exe

I'm using the following command line arguments on start option:

/FILE "..\TestXmlParserPipe.dtsx" /MAXCONCURRENT " -1 " /CHECKPOINTING OFF /REPORTING EWCDI

Please help with Windows Vista Ultimate ?

|||

Always start investigating debugging/breakpoints problems by checking if VS finds the symbols for your assembly. Go to Modules window, find your assembly, check if the symbols are loaded. If not, try to load the symbols manually.

Do you install a custom component (run gacutil /if ...) as part of VS post-build step?

What often happens is that if you don't do this, VS would build a new version of the component before starting debugging session; but the binary used by DTEXEC comes from GAC and it is different from the new version build by VS, so VS can't match the symbols and can't use the breakpoints.

Problem with debugging SSIS 2005 (32bit) component under Windows Vista ultimate

Hi,

I have a problem when i want to debug an ssis component under visual studio 2005.

I'm using sql 2005 with service pack 2 and i have already install patch for visual studio under vista.

When i put a breakpoint for exemple in the method "public override void PreExecute()" or in the other method. "public override void ProcessInput(int inputID, PipelineBuffer buffer)" and i execute the pgm.

however when i begin debugging,it's always skip breakpoint

However when i put a break point in the Validate method "public override DTSValidationStatus Validate()" it function.

When execute the the package it works fine.

I use this debug parametres :

Start external program :

C:\Program Files\Microsoft SQL Server\90\DTS\Binn\DTExec.exe

Command line arguments

/FILE "D:\Projects\Integration Services Project1\Integration Services Project1\TestXmlParserPipe.dtsx" /MAXCONCURRENT " -1 " /CHECKPOINTING OFF /REPORTING EWCDI

I execute visual studio 2005 as Administrator

Please, can some one help me!

It must be some sort of those trivial problems. Are you sure the execution goes through those two methods? Try to check using some kind of checkpoint logging (i. e. MessageBox).

A few additional troubleshooting tips:

- Make sure you are building the debug version of your component.

- Check if the proper module gets loaded.

- Double-check the function signatures.

HTH.

|||

Hi,

thanks for your answer.

I'm sure, i'm was building the debug version.

I notice that if i put a messagebox in the script component and i run the package.

The message box appear, so i go to my ssis component code under visual studio2005 and then i put a breakpoint in

PreExecute() method (for example), after this i attached the process DtsDebugHost.exe (this process is visible in the process list only when the package ssis is running ). I came back to the message box i click ok and finally it work i can see the yellow line hilight the method.

What can i do to let de debugger work fine under vista ultimate? In my work, we have Windows XP professional and i don't have to use complicated procedure each time i want to debug my custom component.

so it will be so nice if some one know the solution for that.

Thanks in advance.

|||

Can you confirm one thing? Are you debugging your custom component using DTExec or BIDS?

Thanks,

Bob

|||

Hi,

I debug the my custom component using DTExec :

On Start action \start external program I use :

C:\Program Files\Microsoft SQL Server\90\DTS\Binn\DTExec.exe

I'm using the following command line arguments on start option:

/FILE "..\TestXmlParserPipe.dtsx" /MAXCONCURRENT " -1 " /CHECKPOINTING OFF /REPORTING EWCDI

Please help with Windows Vista Ultimate ?

|||

Always start investigating debugging/breakpoints problems by checking if VS finds the symbols for your assembly. Go to Modules window, find your assembly, check if the symbols are loaded. If not, try to load the symbols manually.

Do you install a custom component (run gacutil /if ...) as part of VS post-build step?

What often happens is that if you don't do this, VS would build a new version of the component before starting debugging session; but the binary used by DTEXEC comes from GAC and it is different from the new version build by VS, so VS can't match the symbols and can't use the breakpoints.