db datatypes: windows

Showing posts with label windows. Show all posts

Friday, March 30, 2012

Problem With Login Null

Hi,
I have a problem. My web server is a Windows 2k Server and my database
server a Windows 2003. I use windows authentication to login at SQL Server,
but when I access from a client machine that uses Win 2k Professional I
always receive this message: "[Microsoft][ODBC SQL Server Driver][SQL
Server]Login failed for user '(null)'. Reason: Not associated with a trusted
SQL Server connection.".
When I access from a client machine that uses Windows XP everything its
ok.
This problem only occurs at the web site. When I try to access the Query
Analyzer or the Enterprise Manager I still have the connection.
Can anyone help me?!
Thanks,
Riane Santos
riane@.cpunet.com.br
I've seen this error when a local security policy was in place preventing
access from the network. But, I don't see how that could be your problem
since it works from some machines.
"Riane de Oliveira Torres Santos" <riane@.cpunet.com.br> wrote in message
news:eI4Ehr1jEHA.2788@.tk2msftngp13.phx.gbl...
> Hi,
> I have a problem. My web server is a Windows 2k Server and my database
> server a Windows 2003. I use windows authentication to login at SQL
Server,
> but when I access from a client machine that uses Win 2k Professional I
> always receive this message: "[Microsoft][ODBC SQL Server Driver][SQL
> Server]Login failed for user '(null)'. Reason: Not associated with a
trusted
> SQL Server connection.".
> When I access from a client machine that uses Windows XP everything its
> ok.
> This problem only occurs at the web site. When I try to access the Query
> Analyzer or the Enterprise Manager I still have the connection.
> Can anyone help me?!
> Thanks,
> Riane Santos
> riane@.cpunet.com.br
>
sql

Problem With Login null

Monday, March 26, 2012

Problem with installing SQL Server 2000

Help me

I am installing SQL Server 2000 on Windows 2000 and It ends up with the error showing :
"Setup failed to Configure Server. Please refer to C:\Winnt\Sqlstp.log for detail"
I checked sqlstp.log and found that
driver={sql server};server=MyServer;UID=sa;PWD=;database=....,
[Microsoft][ODBC SQL Server Driver] Connection broken

Thanks in advance.

Is that Windows 2000 server or workstation? And what edition of SQL Server are you installing?

Also - at what point in the installation is it failing?

|||

http://support.microsoft.com/default.aspx?scid=KB;EN-US;Q317328

HTH

Problem with installing SQL Server

Hi All,

I'm running into a problem when trying to install SQL Server onto my laptop that is running Windows XP. The error message that is displayed is:

"An error occurred while creating one or more registry entries. Please see
C:\Windows\sqlstp.log for details. The problem could be caused by a low
registry quota condition."

Does anyone know how to solve this?? Any help would be appreciated.

Thanks,

Pete

Seems to be a complex issue, may need sqlstp.log for trouble-shooting. For a quick check, please take a look at this link, which also mentioned an issue of installing SQL on WinXp:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=182716&SiteId=1

|||Typically this type of error (which isn't SQL Server specific) can/will happen if the account you are using can't access the registry to write/update new entries... or if there aren't enough empty 'slots' available.

Were you running/installing this as admin? (or were you trying to throw this instance on to a DC, etc?)

Try this link as well:
http://www.mcse.ms/archive82-2004-12-1281012.html

problem with installation of sqlserver 2000

I have a problem with installation of sqlserver 2000.
I have a pc at home, my pc is not in a network. The
operative system installed is Windows XP professional.
When I try to install sqlserver I receive the following
message: " sqlserver 2000 enterprise edition component is
not supported in this operative system. You can install
only client components"; so I install only client
components.
I must use Query Analizer, but when I try to connect to
my computer (local server) I get this error message: "
Unable to connect to server (my pc) Msg 17, level 16,
[Microsoft][odbc sqlserver driver][Shared Memory]
sqlserver does not exist or access denied".
I cannot change system operative and I must use Query
Analizer. How can I do? Please help me!Hi,
Since you have not installed a SQL server , you can not connect Query
Analyser with out having access to a server.
In Windows XP try installing SQL 2K Personal Edition.
Thanks
Hari
MCDBA
"Giulia" <giulia74z@.libero.it> wrote in message
news:050701c3cadd$dca77110$a101280a@.phx.gbl...

quote:

> I have a problem with installation of sqlserver 2000.
> I have a pc at home, my pc is not in a network. The
> operative system installed is Windows XP professional.
> When I try to install sqlserver I receive the following
> message: " sqlserver 2000 enterprise edition component is
> not supported in this operative system. You can install
> only client components"; so I install only client
> components.
> I must use Query Analizer, but when I try to connect to
> my computer (local server) I get this error message: "
> Unable to connect to server (my pc) Msg 17, level 16,
> [Microsoft][odbc sqlserver driver][Shared Memory]
> sqlserver does not exist or access denied".
> I cannot change system operative and I must use Query
> Analizer. How can I do? Please help me!
>

|||Giulia (giulia74z@.libero.it) writes:

quote:

> I have a problem with installation of sqlserver 2000.
> I have a pc at home, my pc is not in a network. The
> operative system installed is Windows XP professional.
> When I try to install sqlserver I receive the following
> message: " sqlserver 2000 enterprise edition component is
> not supported in this operative system. You can install
> only client components"; so I install only client
> components.

This is because on Windows XP you can only install Deverloper Edition,
Personal Edition, Evaulation Edition and MSDE. You cannot install
Standard Edition and Enterprise Edition. These two edition require
a server operating system.

quote:

> I must use Query Analizer, but when I try to connect to
> my computer (local server) I get this error message: "
> Unable to connect to server (my pc) Msg 17, level 16,
> [Microsoft][odbc sqlserver driver][Shared Memory]
> sqlserver does not exist or access denied".
> I cannot change system operative and I must use Query
> Analizer. How can I do? Please help me!

Since you did not install server components, there is no local server
to connect to. So either you need to connect to network where there
is an SQL Server available, install an edition of SQL Server that
runs on XP.
Erland Sommarskog, SQL Server MVP, sommar@.algonet.se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||Thank you for help!
I installed MSDE from Office 2000 and client components
of sqlserver 2000.
Then I started sql server service manager, in this way I
can connect to local server from Query Analizer!
thank you another

quote:

>--Original Message--
>Giulia (giulia74z@.libero.it) writes:
following[QUOTE]
is[QUOTE]
install[QUOTE]
>This is because on Windows XP you can only install

Deverloper Edition,

quote:

>Personal Edition, Evaulation Edition and MSDE. You

cannot install

quote:

>Standard Edition and Enterprise Edition. These two

edition require

quote:

>a server operating system.
>
to[QUOTE]
>Since you did not install server components, there is no

local server

quote:

>to connect to. So either you need to connect to network

where there

quote:

>is an SQL Server available, install an edition of SQL

Server that

quote:

>runs on XP.
>
>--
>Erland Sommarskog, SQL Server MVP, sommar@.algonet.se
>Books Online for SQL Server SP3 at
>http://www.microsoft.com/sql/techin...uctdoc/2000/boo

ks.asp

quote:

>.
>

|||Thank you for help!
I installed MSDE from Office 2000 and client components
of sqlserver 2000.
Then I started sql server service manager, in this way I
can connect to local server from Query Analizer!

quote:

>--Original Message--
>Hi,
>Since you have not installed a SQL server , you can not

connect Query

quote:

>Analyser with out having access to a server.
>In Windows XP try installing SQL 2K Personal Edition.
>Thanks
>Hari
>MCDBA
>"Giulia" <giulia74z@.libero.it> wrote in message
>news:050701c3cadd$dca77110$a101280a@.phx.gbl...
is[QUOTE]
>
>.
>

problem with installation of RDA...

Hello,

We have a server with 64bit Windows 2003 Server. I installed sqlce30setupen.msi and started to configure it. I get an error during virtual directory creating process which says "server tools must be installed first"....but I installed sqlce30setupen.msi already...Doesn't it the server tools that the error message says about?

The server tools are not supported on 64 bit Windows (for now) - sadly!|||

Hello,

Is it possible to install the server components to a pc(1) and install sql server to another pc(2) and connect to (2) via (1) using RDA method. I need this because the sql server is in 64bit windows 2003 server,so server tools can not be installed to it. I want to install server tools to another pc and access sql server via it.

How can I do that?

|||

Yes, this scenario is absolutely supported, so you must run 32 bit Windows on the web server, and can run 64 bit Windows on the DB server. See the SQL CE Books Onlie topic: Multiple Server Environment at http://msdn2.microsoft.com/en-us/library/ms172937.aspx

Problem with installation

Hi
I'm having problems installing MS SQL 2000 (Developer edition) Server on a
Windows XP SP2 computer.
It's a clean Windows XP installation, and it is not the first time the we
install SQL 2k on a WinXP computer,so it's quite strange becasue quite at
the end of the installation when I try to configure SQL server installation
fails.
I included a log-file that was generating during the installation.
Any help or tips how to resolve this would be appriciated.
Thank you all in advance
Best regards
Miha
begin 666 sqlstp.log
M,3(Z,S,Z-3@.@.0F5G:6X@.4V5T=7 -"C$R.C,S.C4X(#@.N,# N,3DT#0HQ,CHS
M,SHU."!-;V1E(#T@.3F]R;6%L#0HQ,CHS,SHU."!-;V1E5'EP92 ]($Y/4DU!
M3 T*,3(Z,S,Z-3D@.1V5T1&5F:6YI=&EO;D5X(')E='5R;F5D.B P+"!%>'1E
M;F1E9#H@.,'@.P#0HQ,CHS,SHU.2!686QU94944R!R971U<FYE9 #H@.,0T*,3(Z
M,S,Z-3D@.5F%L=650240@.<F5T=7)N960Z(#$-"C$R.C,S.C4Y(%9A;'5E3&EC
M(')E='5R;F5D.B P#0HQ,CHS,SHU.2!3>7-T96TZ(%=I;F1O=W,@.3E0@.5V]R
M:U-T871I;VX-"C$R.C,S.C4Y(%-13"!397)V97(@.4')O9'5C=%1Y<&4Z($1E
M=F5L;W!E<B!%9&ET:6]N(%LP>#-=#0HQ,CHS,SHU.2!"96=I;B!!8W1I;VXZ
M(%-E='5P26YI=&EA;&EZ92 -"C$R.C,S.C4Y($5N9"!!8W1I;VX@.4V5T=7!)
M;FET:6%L:7IE#0HQ,CHS,SHU.2!"96=I;B!!8W1I;VXZ("!39 71U<$EN<W1A
M;&P-"C$R.C,S.C4Y(%)E861I;F<@.4V]F='=A<F5<36EC<F]S;V9T7%=I;F1O
M=W-<0W5R<F5N=%9E<G-I;VY<0V]M;6]N1FEL97-$:7(@.+BXN#0HQ,CHS,SHU
M.2!#;VUM;VY&:6QE<T1I<CU#.EQ0<F]G<F%M($9I;&5S7$-O;6UO;B!&:6QE
M<PT*,3(Z,S,Z-3D@.5VEN9&]W<R!$:7)E8W1O<GD]0SI<5TE.1$]74UP-"C$R
M.C,S.C4Y(%!R;V=R86T@.1FEL97,]0SI<4')O9W)A;2!&:6QE<UP-"C$R.C,S
M.C4Y(%1%35!$25(]0SI<5TE.1$]74UQ414U07 T*,3(Z,S,Z-3D@.0F5G:6X@.
M06-T:6]N.B @.4V5T=7!);G-T86QL#0HQ,CHS,SHU.2!D:6=P:60@.<VEZ92 Z
M(#(U-@.T*,3(Z,S,Z-3D@.9&EG<&ED('-I>F4@..B Q-C0-"C$R.C,S.C4Y($)E
M9VEN($%C=&EO;CH@.($-H96-K1FEX961297%U:7)E;65N=',-"C$R.C,S.C4Y
M(%!L871F;W)M($E$.B P>&8P,# P,# -"C$R.C,S.C4Y(%9E<G-I;VXZ(#4N
M,2XR-C P#0HQ,CHS,SHU.2!&:6QE(%9E<G-I;VX@.+2!#.EQ724Y$3U=37'-Y
M<W1E;3,R7'-H9&]C=G<N9&QL.B V+C N,CDP,"XR-3$X#0HQ,CHS,SHU.2!%
M;F0@.06-T:6]N.B @.0VAE8VM&:7AE9%)E<75I<F5M96YT<PT*,3(Z,S,Z-3D@.
M0F5G:6X@.06-T:6]N.B @.4VAO=T1I86QO9W,-"C$R.C,S.C4Y($EN:71I86P@.
M1&EA;&]G($UA<VLZ(#!X.#,P,#!F-RP@.1&ES86)L92!"86-K/3!X,0T*,3(Z
M,S,Z-3D@.0F5G:6X@.06-T:6]N(%-H;W=$:6%L;V=S2&QP<CH@.,'@.Q#0HQ,CHS
M,SHU.2!"96=I;B!!8W1I;VXZ("!$:6%L;V=3:&]W4V1796QC;VUE#0HQ,CHS
M-#HP,2!%;F0@.06-T:6]N("!$:6%L;V=3:&]W4V1796QC;VUE#0HQ,CHS-#HP
M,2!$:6%L;V<@.,'@.Q(')E='5R;F5D.B Q#0HQ,CHS-#HP,2!%;F0@.06-T:6]N
M(%-H;W=$:6%L;V=S2&QP<@.T*,3(Z,S0Z,#$@.4VAO=T1I86QO9W-'971$:6%L
M;V<@.<F5T=7)N960Z(&Y#=7)R96YT/3!X,BQI;F1E>#TQ#0HQ,CHS-#HP,2!"
M96=I;B!!8W1I;VX@.4VAO=T1I86QO9W-(;'!R.B P>#(-"C$R.C,T.C Q($)E
M9VEN($%C=&EO;CH@.($1I86QO9U-H;W=39$UA8VAI;F5.86UE#0HQ,CHS-#HP
M,B!3:&]W1&QG36%C:&EN92!R971U<FYE9#H@.,0T*,3(Z,S0Z,#(@.3F%M9 2 ]
M($%34$E213$S,# L(%1Y<&4@./2 P>#$-"C$R.C,T.C R($)E9VEN($%C=&EO
M;CH@.($-H96-K4F5Q=6ER96UE;G1S#0HQ,CHS-#HP,B!0<F]C97-S;W(@.07)C
M:&ET96-T=7)E.B!X.#8@.*%!E;G1I=6TI#0HQ,CHS-#HP,B!397)V:6-E(%!A
M8VLZ(" U,3(-"C$R.C,T.C R($-O;7!U=&5R3F%M93H@.05-025)%,3,P, T*
M,3(Z,S0Z,#(@.57-E<B!.86UE.B!)+4%R;6EC#0HQ,CHS-#HP,B!)<T%L;$%C
M8V5S<T%L;&]W960@.<F5T=7)N960Z(#$-"C$R.C,T.C R($]3($QA;F=U86=E
M.B P>#0R- T*,3(Z,S0Z,#(@.16YD($%C=&EO;B!#:&5C:U)E<75I<F5M96YT
M<PT*,3(Z,S0Z,#(@.5&AI<R!C;VUB:6YA=&EO;B!O9B!086-K86=E(&%N9"!/
M<&5R871I;F<@.4WES=&5M(&%L;&]W<R!A(&9U;&P@.<')O9'5C="!I;G-T86QL
M+@.T*,3(Z,S0Z,#(@.0W)E871E4V5T=7!4;W!O;&]G>2A!4U!)4D4Q,S P*2P@.
M2&%N9&QE(#H@.,'@.Q-3,T,&$X+"!R971U<FYE9" Z(# -"C$R.C,T.C R($-R
M96%T95-E='5P5&]P;VQO9WD@.<F5T=7)N960@..B P+"!(86YD;&4@..B P>#$U
M,S0P83@.-"C$R.C,T.C R(%1O<&]L;V=Y(%1Y<&4@..B Q+"!2971U<FX@.5F%L
M=64@..B P#0HQ,CHS-#HP,B!35%]'9710:'ES:6-A;$YO9&4@.<F5T=7)N960@.
M.B P+"!03DAA;F1L92 Z(#!X,34S-#!F. T*,3(Z,S0Z,#(@.4$Y?16YU;65R
M871E17@.@.<F5T=7)N960@..B P#0HQ,CHS-#HP,B!03E]'971344Q3=&%T97,@.
M<F5T=7)N960@..B P+"!3<6Q3=&%T97,@..B P># -"C$R.C,T.C R(%!.7U-T
M87)T4V-A;B!;,'@.Q-3,T,&8X72!R971U<FYE9" Z(# -"C$R.C,T.C R(%!.
M7T=E=$YE>'0@.6S!X,34S-#!F.%T@.<F5T=7)N960@..B Q."P@.2&%N9&QE.B!;
M,'@.P70T*,3(Z,S0Z,#(@.3F\@.;6]R92!I=&5M<R!I;B!E;G5M97)A=&EO;BX-
M"C$R.C,T.C R(%)E;&5A<V53971U<%1O<&]L;V=Y#0HQ,CHS-#HP,B!.86UE
M9"!I;G-T86YC92!L:6UI=#H@.,3 P+"!Q=6]T83H@., T*,3(Z,S0Z,#(@.16YD
M($%C=&EO;B @.1&EA;&]G4VAO=U-D36%C:&EN94YA;64-"C$R.C,T.C R(&)E
M9VEN(%-H;W=$:6%L;V=S57!D871E36%S:PT*,3(Z,S0Z,#(@.;D9U;&Q-87-K
M(#T@.,'@.X,S P,&8W+"!N0W5R<F5N=" ](#!X,BP@.;D1I<F5C=&EO;B ](# -
M"C$R.C,T.C R(%5P9&%T960@.1&EA;&]G($UA<VLZ(#!X8F8P,# S-RP@.1&ES
M86)L92!"86-K(#T@.,'@.Q#0HQ,CHS-#HP,B!$:6%L;V<@.,'@.R(')E='5R;F5D
M.B P#0HQ,CHS-#HP,B!%;F0@.06-T:6]N(%-H;W=$:6%L;V=S2&QP<@.T*,3(Z
M,S0Z,#(@.4VAO=T1I86QO9W-'971$:6%L;V<@.<F5T=7)N960Z(&Y#=7)R96YT
M/3!X-"QI;F1E>#TR#0HQ,CHS-#HP,B!"96=I;B!!8W1I;VX@.4VAO=T1I86QO
M9W-(;'!R.B P>#0-"C$R.C,T.C R($)E9VEN($%C=&EO;CH@.($1I86QO9U-H
M;W=39$EN<W1A;&Q-;V1E#0HQ,CHS-#HP,R!3:&]W1&QG26YS=&%L;$UO9&4@.
M<F5T=7)N960Z(#$-"C$R.C,T.C S($EN<W1A;&Q-;V1E(#H@.,'@.Q#0HQ,CHS
M-#HP,R!%;F0@.06-T:6]N("!$:6%L;V=3:&]W4V1);G-T86QL36]D90T*,3(Z
M,S0Z,#,@.8F5G:6X@.4VAO=T1I86QO9W-5<&1A=&5-87-K#0HQ,CHS-#HP,R!N
M1G5L;$UA<VL@./2 P>&)F,# P,S<L(&Y#=7)R96YT(#T@.,'@.T+"!N1&ER96-T
M:6]N(#T@.,0T*,3(Z,S0Z,#,@.57!D871E9"!$:6%L;V<@.36%S:SH@., 'AB9C0P
M,#,W+"!$:7-A8FQE($)A8VL@./2 P>#$-"C$R.C,T.C S($1I86QO9R P>#0@.
M<F5T=7)N960Z(#$-"C$R.C,T.C S($5N9"!!8W1I;VX@.4VAO=T1I86QO9W-(
M;'!R#0HQ,CHS-#HP,R!3:&]W1&EA;&]G<T=E=$1I86QO9R!R971U<FYE9#H@.
M;D-U<G)E;G0],'@.Q,"QI;F1E>#TT#0HQ,CHS-#HP,R!"96=I;B!!8W1I;VX@.
M4VAO=T1I86QO9W-(;'!R.B P>#$P#0HQ,CHS-#HP,R!"96=I;B!!8W1I;VXZ
M("!$:6%L;V=3:&]W4V1296=I<W1E<E5S97)%> T*,3(Z,S0Z,#4@.16YD($%C
M=&EO;B!$:6%L;V=3:&]W4V1296=I<W1E<E5S97)%> T*,3(Z,S0Z,#4@.1&EA
M;&]G(#!X,3 @.<F5T=7)N960Z(#$-"C$R.C,T.C U($5N9"!!8W1I;VX@.4VAO
M=T1I86QO9W-(;'!R#0HQ,CHS-#HP-2!3:&]W1&EA;&]G<T=E=$1I86QO9R!R
M971U<FYE9#H@.;D-U<G)E;G0],'@.R,"QI;F1E>#TU#0HQ,CHS-#HP-2!"96=I
M;B!!8W1I;VX@.4VAO=T1I86QO9W-(;'!R.B P>#(P#0HQ,CHS-#HP-2!"96=I
M;B!!8W1I;VXZ("!$:6%L;V=3:&]W4V1,:6-E;G-E#0HQ,CHS-#HP-B!%;F0@.
M06-T:6]N($1I86QO9U-H;W=39$QI8V5N<V4-"C$R.C,T.C V($1I86QO9R P
M>#(P(')E='5R;F5D.B Q#0HQ,CHS-#HP-B!%;F0@.06-T:6]N(%-H;W=$:6%L
M;V=S2&QP<@.T*,3(Z,S0Z,#8@.4VAO=T1I86QO9W-'971$:6%L;V<@.<F5T=7)N
M960Z(&Y#=7)R96YT/3!X-# P,# L:6YD97@.],3@.-"C$R.C,T.C V($)E9VEN
M($%C=&EO;B!3:&]W1&EA;&]G<TAL<'(Z(#!X-# P,# -"C$R.C,T.C V($)E
M9VEN($%C=&EO;CH@.($1I86QO9U-H;W=39$-L:5-V<@.T*,3(Z,S0Z,#8@.1&ES
M<&QA>5-Y<W1E;5!R95)E<0T*,3(Z,S0Z,#<@.4VAO=T1L9T-L:65N=%-E<G9E
M<E-E;&5C="!R971U<FYE9#H@.,0T*,3(Z,S0Z,#<@.5'EP92 Z(#!X,@.T*,3(Z
M,S0Z,#<@.16YD($%C=&EO;B @.1&EA;&]G4VAO=U-D0VQI4W9R#0HQ,CHS-#HP
M-R!B96=I;B!3:&]W1&EA;&]G<U5P9&%T94UA<VL-"C$R.C,T.C W(&Y&=6QL
M36%S:R ](#!X8F8T,# S-RP@.;D-U<G)E;G0@./2 P>#0P,# P+"!N1&ER96-T
M:6]N(#T@.,0T*,3(Z,S0Z,#<@.57!D871E9"!$:6%L;V<@.36%S:SH@., 'AB9F,P
M,#,W+"!$:7-A8FQE($)A8VL@./2 P>#$-"C$R.C,T.C W($1I86QO9R P>#0P
M,# P(')E='5R;F5D.B Q#0HQ,CHS-#HP-R!%;F0@.06-T:6]N(%-H;W=$:6%L
M;V=S2&QP<@.T*,3(Z,S0Z,#<@.4VAO=T1I86QO9W-'971$:6%L;V<@.<F5T=7)N
M960Z(&Y#=7)R96YT/3!X.# P,# L:6YD97@.],3D-"C$R.C,T.C W($)E9VEN
M($%C=&EO;B!3:&]W1&EA;&]G<TAL<'(Z(#!X.# P,# -"C$R.C,T.C W($)E
M9VEN($%C=&EO;CH@.($1I86QO9U-H;W=39$EN<W1A;F-E3F%M90T*,3(Z,S0Z
M,#<@.0F5G:6X@.06-T:6]N.B!3:&]W1&QG26YS=&%N8V5.86UE#0HQ,CHS-#HP
M."!%;F0@.06-T:6]N.B!3:&]W1&QG26YS=&%N8V5.86UE#0HQ,CHS-#HP."!3
M:&]W1&QG26YS=&%N8V5.86UE(')E='5R;F5D(#H@.,0T*,3(Z,S0Z, #@.@.26YS
M=&%N8V5.86UE(#H@.35-344Q315)615(-"C$R.C,T.C X($-R96%T95-E='5P
M5&]P;VQO9WDH05-025)%,3,P,"DL($AA;F1L92 Z(#!X,34S-#8W,"P@.<F5T
M=7)N960@..B P#0HQ,CHS-#HP."!#<F5A=&53971U<%1O<&]L;V=Y(')E='5R
M;F5D(#H@.,"P@.2&%N9&QE(#H@.,'@.Q-3,T-C<P#0HQ,CHS-#HP."!4;W!O;&]G
M>2!4>7!E(#H@.,2P@.4F5T=7)N(%9A;'5E(#H@., T*,3(Z,S0Z,#@.@.4U1?1V5T
M4&AY<VEC86Q.;V1E(')E='5R;F5D(#H@.,"P@.4$Y(86YD;&4@.. B P>#$U,S0P
M9C@.-"C$R.C,T.C X(%!.7T5N=6UE<F%T945X(')E='5R;F5D(#H@., T*,3(Z
M,S0Z,#@.@.4$Y?1V5T4U%,4W1A=&5S(')E='5R;F5D(#H@.,"P@.4 W%L4W1A=&5S
M(#H@.,'@.P#0HQ,CHS-#HP."!03E]3=&%R=%-C86X@.6S!X,34S-#!F.%T@.<F5T
M=7)N960@..B P#0HQ,CHS-#HP."!03E]'971.97AT(%LP>#$U,S0P9CA=(')E
M='5R;F5D(#H@.,3@.L($AA;F1L93H@.6S!X,%T-"C$R.C,T.C X($YO(&UO<F4@.
M:71E;7,@.:6X@.96YU;65R871I;VXN#0HQ,CHS-#HP."!296QE87-E4V5T=7!4
M;W!O;&]G>0T*,3(Z,S0Z,#@.@.16YD($%C=&EO;B @.1&EA;&]G4VAO=U-D26YS
M=&%N8V5.86UE#0HQ,CHS-#HP."!B96=I;B!3:&]W1&EA;&]G<U5P9&%T94UA
M<VL-"C$R.C,T.C X(&Y&=6QL36%S:R ](#!X8F9C,# S-RP@.;D-U<G)E;G0@.
M/2 P>#@.P,# P+"!N1&ER96-T:6]N(#T@.,0T*,3(Z,S0Z,#@.@.57!D871E9"!$
M:6%L;V<@.36%S:SH@.,'AB9F,P,#,W+"!$:7-A8FQE($)A8VL@./2 P>#$-"C$R
M.C,T.C X($1I86QO9R P>#@.P,# P(')E='5R;F5D.B Q#0HQ,CHS-#HP."!%
M;F0@.06-T:6]N(%-H;W=$:6%L;V=S2&QP<@.T*,3(Z,S0Z,#@.@.4VAO=T1I86QO
M9W-'971$:6%L;V<@.<F5T=7)N960Z(&Y#=7)R96YT/3!X,3 P,# P+&EN9&5X
M/3(P#0HQ,CHS-#HP."!"96=I;B!!8W1I;VX@.4VAO=T1I86QO9W-(;'!R.B P
M>#$P,# P, T*,3(Z,S0Z,#@.@.0F5G:6X@.06-T:6]N.B @.1&EA;&]G4VAO=U-D
M4V5T=7!4>7!E#0HQ,CHS-#HP.2!"96=I;B!!8W1I;VXZ(%-E='5P(%1Y<&4-
M"C$R.C,T.C$P(%-13"!P<F]G<F%M(&9O;&1E<CH@.0SI<4')O9W)A;2!&:6QE
M<UQ-:6-R;W-O9G0@.4U%,(%-E<G9E<@.T*,3(Z,S0Z,3 @.4U%,(&1A=&$@.9F]L
M9&5R.B!#.EQ0<F]G<F%M($9I;&5S7$UI8W)O<V]F="!344P@.4V5R=F5R#0HQ
M,CHS-#HQ,"!7:6YD;W=S('-Y<W1E;2!F;VQD97(Z($,Z7%=)3D1/5U-<<WES
M=&5M,S)<#0HQ,CHS-#HQ,"!0<F]G(')E<3H@.,S@.P-S,L($1A=&$@.<F5Q.B S
M-#0S,BP@.4WES(')E<3H@.,34X-CDT#0HQ,CHS-#HQ,"!0<F]G(&%V86EL.B Q
M,#(W-S U-BP@.1&%T82!A=F%I;#H@.,3 R-S<P-38L(%-Y<R!A=F%I;#H@.,3 R
M-S<P-38-"C$R.C,T.C$P(%!R;V<@.<F5Q('9S+B!A=F%I;"P@.,C,Q,3DY+" Q
M,#(W-S U-@.T*,3(Z,S0Z,3 @.1&%T82!R97$@.=G,N(&%V86EL+" S-#0S,BP@.
M,3 R-S<P-38-"C$R.C,T.C$P(%-Y<R!R97$@.=G,N(&%V86EL+" Q.3,Q,C8L
M(#$P,C<W,#4V#0HQ,CHS-#HQ,"!$:7-P;&%Y4WES=&5M4')E4F5Q#0HQ,CHS
M-#HQ,"!;4V5T=7!4>7!E4U%,70T*,3(Z,S0Z,3 @.<WI$:7(@./2!#.EQ0<F]G
M<F%M($9I;&5S7$UI8W)O<V]F="!344P@.4V5R=F5R#0HQ,CHS-#HQ,"!S>D1I
M<B ]("504D]'4D%-1DE,15,E7$UI8W)O<V]F="!344P@.4V5R=F5R#0HQ,CHS
M-#HQ,"!297-U;'0@./2 S,#$-"C$R.C,T.C$P('-Z1&%T841I<B ]($,Z7%!R
M;V=R86T@.1FEL97-<36EC<F]S;V9T(%-13"!397)V97(-"C$R.C,T.C$P('-Z
M1&%T841I<B ]("504D]'4D%-1DE,15,E7$UI8W)O<V]F="!344P@.4V5R=F5R
M#0HQ,CHS-#HQ,2!%;F0@.06-T:6]N.B!3971U<"!4>7!E#0HQ,CHS-#HQ,2!3
M971U<"!4>7!E.B!4>7!I8V%L("@.S,#$I#0HQ,CHS-#HQ,2!%;F0@.06-T:6]N
M("!$:6%L;V=3:&]W4V13971U<%1Y<&4-"C$R.C,T.C$Q(&)E9VEN(%-H;W=$
M:6%L;V=S57!D871E36%S:PT*,3(Z,S0Z,3$@.;D9U;&Q-87-K(#T@.,'AB9F,P
M,#,W+"!N0W5R<F5N=" ](#!X,3 P,# P+"!N1&ER96-T:6]N(#T@.,S Q#0HQ
M,CHS-#HQ,2!5<&1A=&5D($1I86QO9R!-87-K.B P>&)D8S P,S<L($1I<V%B
M;&4@.0F%C:R ](#!X,0T*,3(Z,S0Z,3$@.1&EA;&]G(#!X,3 P,# P(')E='5R
M;F5D.B S,#$-"C$R.C,T.C$Q($5N9"!!8W1I;VX@.4VAO=T1I86QO9W-(;'!R
M#0HQ,CHS-#HQ,2!3:&]W1&EA;&]G<T=E=$1I86QO9R!R971U<FYE9#H@.;D-U
M<G)E;G0],'@.T,# P,# L:6YD97@.],C(-"C$R.C,T.C$Q($)E9VEN($%C=&EO
M;B!3:&]W1&EA;&]G<TAL<'(Z(#!X-# P,# P#0HQ,CHS-#HQ,2!"96=I;B!!
M8W1I;VXZ("!$;&=397)V:6-E<PT*,3(Z,S0Z,30@.4VAO=T1L9U-E<G9I8V5S
M(')E='5R;F5D.B Q#0HQ,CHS-#HQ-"!;1&QG4V5R=FEC97-=#0HQ,CHS-#HQ
M-"!,;V-A;"U$;VUA:6X)/2 S.#4U#0HQ,CHS-#HQ-"!!=71O4W1A<G0)"3T@.
M,34-"C$R.C,T.C$T(%)E<W5L= D](#$-"C$R.C,T.C$T($5N9"!!8W1I;VX@.
M1&QG4V5R=FEC97,-"C$R.C,T.C$T(&)E9VEN(%-H;W=$:6%L;V=S57!D871E
M36%S:PT*,3(Z,S0Z,30@.;D9U;&Q-87-K(#T@.,'AB9&,P,#,W+"!N0W5R<F5N
M=" ](#!X-# P,# P+"!N1&ER96-T:6]N(#T@.,0T*,3(Z,S0Z,30@.57!D871E
M9"!$:6%L;V<@.36%S:SH@.,'AB9&,P,#,W+"!$:7-A8FQE($)A8VL@./2 P>#$-
M"C$R.C,T.C$T($1I86QO9R P>#0P,# P,"!R971U<FYE9#H@.,0T*,3(Z,S0Z
M,30@.16YD($%C=&EO;B!3:&]W1&EA;&]G<TAL<'(-"C$R.C,T.C$T(%-H;W=$
M:6%L;V=S1V5T1&EA;&]G(')E='5R;F5D.B!N0W5R<F5N=#TP>#@.P,# P,"QI
M;F1E>#TR,PT*,3(Z,S0Z,30@.0F5G:6X@.06-T:6]N(%-H;W=$:6%L;V=S2&QP
M<CH@.,'@.X,# P,# -"C$R.C,T.C$T($)E9VEN($%C=&EO;CH@.($1L9U-13%-E
M8W5R:71Y#0HQ,CHS-#HQ."!3:&]W1&QG4U%,4V5C=7)I='D@.<F5T=7)N960Z
M(#$-"C$R.C,T.C$X($QO9VEN36]D92 ](#(L<WI0=V0-"C$R.C,T.C$X($5N
M9"!!8W1I;VX@.1&QG4U%,4V5C=7)I='D-"C$R.C,T.C$X(&)E9VEN(%-H;W=$
M:6%L;V=S57!D871E36%S:PT*,3(Z,S0Z,3@.@.;D9U;&Q-87-K(#T@.,'AB9&,P
M,#,W+"!N0W5R<F5N=" ](#!X.# P,# P+"!N1&ER96-T:6]N(#T@.,0T*,3(Z
M,S0Z,3@.@.57!D871E9"!$:6%L;V<@.36%S:SH@.,'AB9&,P,#,W+ "!$:7-A8FQE
M($)A8VL@./2 P>#$-"C$R.C,T.C$X($1I86QO9R P>#@.P,# P,"!R971U<FYE
M9#H@.,0T*,3(Z,S0Z,3@.@.16YD($%C=&EO;B!3:&]W1&EA;&]G<TAL<'(-"C$R
M.C,T.C$X(%-H;W=$:6%L;V=S1V5T1&EA;&]G(')E='5R;F5D.B!N0W5R<F5N
M=#TP>#$P,# P,# L:6YD97@.],C0-"C$R.C,T.C$X($)E9VEN($%C=&EO;B!3
M:&]W1&EA;&]G<TAL<'(Z(#!X,3 P,# P, T*,3(Z,S0Z,3@.@.0F5G:6X@.06-T
M:6]N.B @.1&QG0V]L;&%T:6]N#0HQ,CHS-#HQ."!3:&]W1&QG0V]L;&%T:6]N
M(')E='5R;F5D.B Q#0HQ,CHS-#HQ."!C;VQL871I;VY?;F%M92 ](%-L;W9E
M;FEA;E]#25]!4RQL;V-A;&5?;F%M92 ](%-L;W9E;FEA;BQL8VED(#T@.,'@.T
M,C0L4V]R=$ED(#T@.,"QD=T-O;7!&;&%G<R ](#!X,S P,#$-"C$R.C,T.C$X
M($5N9"!!8W1I;VX@.1&QG0V]L;&%T:6]N#0HQ,CHS-#HQ."!B96=I;B!3:&]W
M1&EA;&]G<U5P9&%T94UA<VL-"C$R.C,T.C$X(&Y&=6QL36%S:R ](#!X8F1C
M,# S-RP@.;D-U<G)E;G0@./2 P>#$P,# P,# L(&Y$:7)E8W1I;VX@./2 Q#0HQ
M,CHS-#HQ.2!5<&1A=&5D($1I86QO9R!-87-K.B P>&)D8S P,S<L($1I<V%B
M;&4@.0F%C:R ](#!X,0T*,3(Z,S0Z,3D@.1&EA;&]G(#!X,3 P,# P,"!R971U
M<FYE9#H@.,0T*,3(Z,S0Z,3D@.16YD($%C=&EO;B!3:&]W1&EA;&]G<TAL<'(-
M"C$R.C,T.C$Y(%-H;W=$:6%L;V=S1V5T1&EA;&]G(')E='5R;F5D.B!N0W5R
M<F5N=#TP>#(P,# P,# L:6YD97@.],C4-"C$R.C,T.C$Y($)E9VEN($%C=&EO
M;B!3:&]W1&EA;&]G<TAL<'(Z(#!X,C P,# P, T*,3(Z,S0Z,3D@.0F5G:6X@.
M06-T:6]N.B @.1&QG3F5T=V]R:PT*,3(Z,S0Z,3D@.4VAO=T1L9TYE='=O<FL@.
M<F5T=7)N960Z(#$-"C$R.C,T.C$Y(%M$;&=397)V97).971W;W)K70T*,3(Z
M,S0Z,3D@.3F5T=V]R:TQI8G,@./2 R-34-"C$R.C,T.C$Y(%1#4%!O<G0@./2 Q
M-#,S#0HQ,CHS-#HQ.2!40U!0<GAY(#T@.1&5F875L= T*,3(Z,S0Z,3D@.3DU0
M4&EP94YA;64@./2!<7"Y<<&EP95QS<6Q<<75E<GD-"C$R.C,T.C$Y(%)E<W5L
M=" ](#$-"C$R.C,T.C$Y($5N9"!!8W1I;VX@.1&QG3F5T=V]R:PT*,3(Z,S0Z
M,3D@.8F5G:6X@.4VAO=T1I86QO9W-5<&1A=&5-87-K#0HQ,CHS-#HQ.2!N1G5L
M;$UA<VL@./2 P>&)D8S P,S<L(&Y#=7)R96YT(#T@.,'@.R,# P,# P+"!N1&ER
M96-T:6]N(#T@.,0T*,3(Z,S0Z,3D@.57!D871E9"!$:6%L;V<@.36%S:SH@., 'AB
M9&,P,#,W+"!$:7-A8FQE($)A8VL@./2 P>#$-"C$R.C,T.C$Y($1I86QO9R P
M>#(P,# P,# @.<F5T=7)N960Z(#$-"C$R.C,T.C$Y($5N9"!!8W1I;VX@.4VAO
M=T1I86QO9W-(;'!R#0HQ,CHS-#HQ.2!3:&]W1&EA;&]G<T=E=$1I86QO9R!R
M971U<FYE9#H@.;D-U<G)E;G0],'@.X,# P,# P+&EN9&5X/3(W#0HQ,CHS-#HQ
M.2!"96=I;B!!8W1I;VX@.4VAO=T1I86QO9W-(;'!R.B P>#@.P,# P,# -"C$R
M.C,T.C$Y($)E9VEN($%C=&EO;CH@.($1I86QO9U-H;W=39%-T87)T0V]P>0T*
M,3(Z,S0Z,3D@.16YD($%C=&EO;B!$:6%L;V=3:&]W4V13=&%R=$-O<'D-"C$R
M.C,T.C$Y(&)E9VEN(%-H;W=$:6%L;V=S57!D871E36%S:PT*,3(Z,S0Z,3D@.
M;D9U;&Q-87-K(#T@.,'AB9&,P,#,W+"!N0W5R<F5N=" ](#!X.# P,# P,"P@.
M;D1I<F5C=&EO;B ](#$-"C$R.C,T.C$Y(%5P9&%T960@.1&EA;&]G($UA<VLZ
M(#!X8F1C,# S-RP@.1&ES86)L92!"86-K(#T@.,'@.Q#0HQ,CHS-#HQ.2!$:6%L
M;V<@.,'@.X,# P,# P(')E='5R;F5D.B Q#0HQ,CHS-#HQ.2!%;F0@.06-T:6]N
M(%-H;W=$:6%L;V=S2&QP<@.T*,3(Z,S0Z,3D@.4VAO=T1I86QO9W-'971$:6%L
M;V<@.<F5T=7)N960Z(&Y#=7)R96YT/3!X,"QI;F1E>#TP#0HQ,CHS-#HQ.2!%
M;F0@.06-T:6]N(%-H;W=$:6%L;V=S#0HQ,CHS-#HR,"!"96=I;B!!8W1I;VX@.
M4')O8V5S<T)E9F]R941A=&%-;W9E.@.T*,3(Z,S0Z,C @.1&5I;G-T86QL4W1A
M<G0@.<F5T=7)N960@.*$,Z7%!R;V=R86T@.1FEL97-<36EC<F]S;V9T(%-13"!3
M97)V97)<35-344PI.B P#0HQ,CHS-#HR,"!%;F0@.06-T:6]N(" @.4')O8V5S
M<T)E9F]R941A=&%-;W9E.@.T*,3(Z,S0Z,C @.0F5G:6X@.06-T:6]N(%-E=%1O
M;VQS0V]M<&]N96YT4V5L96-T:6]N.@.T*,3(Z,S0Z,C @.16YD($%C=&EO;B!3
M9714;V]L<T-O;7!O;F5N=%-E;&5C=&EO;CH-"C$R.C,T.C(P($)E9VEN($%C
M=&EO;B!0<F]C97-S0V]M<&]N96YT4V5L96-T:6]N.@.T*,3(Z,S0Z,C @.16YD
M($%C=&EO;B!0<F]C97-S0V]M<&]N96YT4V5L96-T:6]N#0HQ,CHS-#HR,"!"
M96=I;B!!8W1I;VX@.3&]G4V5L96-T961#;VUP;VYE;G1S.@.T*,3(Z,S0Z,C @.
M4U%,4')O9PT*,3(Z,S0Z,C @.4U%,4')O9UQ344Q397)V<@.T*,3(Z,S0Z,C @.
M4U%,4')O9UQ344Q397)V<EQ(96QP#0HQ,CHS-#HR,"!344Q0<F]G7%-13%-E
M<G9R7%-#341E=@.T*,3(Z,S0Z,C @.4U%,4')O9UQ344Q397)V<EQ30TU$979<
M4T--: T*,3(Z,S0Z,C @.4U%,4')O9UQ344Q397)V<EQ30TU$979<4T--6#@.V
M3&(-"C$R.C,T.C(P(%-13%!R;V=<4U%,4V5R=G)<4T--1&5V7%-#34%,8@.T*
M,3(Z,S0Z,C @.4U%,4')O9UQ344Q397)V<EQ2<S$P,S,-"C$R.C,T.C(P(%-1
M3%!R;V=<4U%,4V5R=G)<4G-);G1L#0HQ,CHS-#HR,"!344Q0<F]G7%-13%-E
M<G9R7$%C=&EV95@.-"C$R.C,T.C(P(%-13%!R;V=<4U%,4V5R=G)<4WES=&5M
M#0HQ,CHS-#HR,"!344Q0<F]G7%5P9U1O;VQS#0HQ,CHS-#HR,"!344Q0<F]G
M7%5P9U1O;VQS7%5P9U-Y<PT*,3(Z,S0Z,C @.4U%,4')O9UQ5<&=4;V]L<UQ!
M8W1I=F58#0HQ,CHS-#HR,"!344Q0<F]G7%5P9U1O;VQS7%)E<S$P,S,-"C$R
M.C,T.C(P(%-13%!R;V=<57!G5&]O;'-<4F5S3W1H97(-"C$R.C,T.C(P(%-1
M3%!R;V=<57!G5&]O;'-<4F5S;&0-"C$R.C,T.C(P(%-13%!R;V=<4F5P;%-U
M<' -"C$R.C,T.C(P(%-13%!R;V=<4F5P;%-U<'!<4F5P;$1A= T*,3(Z,S0Z
M,C @.4U%,4')O9UQ297!L4W5P<%Q297!#;VUM#0HQ,CHS-#HR,"!344Q0<F]G
M7%)E<&Q3=7!P7%)E<$YO1&L-"C$R.C,T.C(P(%-13%!R;V=<4F5P;%-U<'!<
M06-T:79E6 T*,3(Z,S0Z,C @.4U%,4')O9UQ);G-T86QL#0HQ,CHS-#HR,"!3
M44Q0<F]G7%-Y<W1E;0T*,3(Z,S0Z,C @.4U%,4')O9UQ3=G)%>'0-"C$R.C,T
M.C(P(%-13%!R;V=<4W9R17AT7$AE;' -"C$R.C,T.C(P(%-13%!R;V=<4W9R
M17AT7%-V<D5X=%)S#0HQ,CHS-#HR,"!344Q0<F]G7%-V<D5X=%Q297-);G1L
M#0HQ,CHS-#HR,"!344Q0<F]G7$1A= T*,3(Z,S0Z,C @.4U%,4')O9UQ$8713
M;7!L#0HQ,CHS-#HR,"!344Q0<F]G7$)A<V53>7,-"C$R.C,T.C(P(%-13%!R
M;V=<0F%S94)I;FX-"C$R.C,T.C(P(%-13%!R;V=<0F%S94EN<W0-"C$R.C,T
M.C(P(%-13%!R;V=<4WEM8F]L<PT*,3(Z,S0Z,C @.4U%,4')O9UQ3>6UB;VQS
M7$5810T*,3(Z,S0Z,C @.4U%,4')O9UQ3>6UB;VQS7$1,3 T*,3(Z,S0Z,C @.
M4U%,4')O9UQ097)F;6]N#0HQ,CHS-#HR,"!344Q0<F]G7%!E<F9M;VY<4WES
M=&5M#0HQ,CHS-#HR,"!344Q0<F]G7%)O;W0-"C$R.C,T.C(P($UG=%1O;VP-
M"C$R.C,T.C(P($UG=%1O;VQ<4T5-#0HQ,CHS-#HR,"!-9W14;V]L7%-%35Q(
M5$U,#0HQ,CHS-#HR,"!-9W14;V]L7%-%35Q-4T0Y. T*,3(Z,S0Z,C @.36=T
M5&]O;%Q314U<35-$.3A365,-"C$R.C,T.C(P($UG=%1O;VQ<4T5-7$U31#DX
M4F5S#0HQ,CHS-#HR,"!-9W14;V]L7%-%35Q-4T0Y.$AL< T*,3(Z,S0Z,C @.
M36=T5&]O;%Q314U<2&5L< T*,3(Z,S0Z,C @.36=T5&]O;%Q314U<4F5S,3 S
M,PT*,3(Z,S0Z,C @.36=T5&]O;%Q314U<4F5S26YT; T*,3(Z,S0Z,C @.36=T
M5&]O;%Q314U<35-$.3A2<TD-"C$R.C,T.C(P($UG=%1O;VQ<4T5-7$%C=&EV
M95@.-"C$R.C,T.C(P($UG=%1O;VQ<4T5-7$%C=&EV95A<4F5S,3 S,PT*,3(Z
M,S0Z,C @.36=T5&]O;%Q314U<06-T:79E6%Q297-);G1L#0HQ,CHS-#HR,"!-
M9W14;V]L7%-%35Q38W)I<'1S#0HQ,CHS-#HR,"!-9W14;V]L7%-%35Q/3$5$
M0@.T*,3(Z,S0Z,C @.36=T5&]O;%Q314U<3TQ%1$)<4F5S,3 S,PT*,3(Z,S0Z
M,C @.36=T5&]O;%Q314U<3TQ%1$)<4F5S26YT; T*,3(Z,S0Z,C @.36=T5&]O
M;%Q0<F]F:6QE<@.T*,3(Z,S0Z,C @.36=T5&]O;%Q0<F]F:6QE<EQ(96QP#0HQ
M,CHS-#HR,"!-9W14;V]L7%!R;V9I;&5R7%)E<S$P,S,-"C$R.C,T.C(P($UG
M=%1O;VQ<4')O9FEL97)<4F5S26YT; T*,3(Z,S0Z,C @.36=T5&]O;%Q1<GEA
M;FQZ#0HQ,CHS-#HR,"!-9W14;V]L7%%R>6%N;'I<2&5L< T*,3(Z,S0Z,C @.
M36=T5&]O;%Q1<GEA;FQZ7%)E<S$P,S,-"C$R.C,T.C(P($UG=%1O;VQ<47)Y
M86YL>EQ297-);G1L#0HQ,CHS-#HR,"!-9W14;V]L7$140T-,:0T*,3(Z,S0Z
M,C @.36=T5&]O;%Q7>F-N9FQC= T*,3(Z,S0Z,C @.36=T5&]O;%Q7>F-N9FQC
M=%Q7>F-N2&QP#0HQ,CHS-#HR,"!-9W14;V]L7%=Z8VYF;&-T7%=Z8VXQ,#,S
M#0HQ,CHS-#HR,"!-9W14;V]L7%=Z8VYF;&-T7%=Z8VY/=&AR#0HQ,CHS-#HR
M,"!-9W14;V]L7%=Z8VYF;&-T7%=Z8VY#;6X-"C$R.C,T.C(P($UG=%1O;VQ<
M571I;%-Y<PT*,3(Z,S0Z,C @.36=T5&]O;%Q5=&EL0FEN;@.T*,3(Z,S0Z,C @.
M0V]N;F5C= T*,3(Z,S0Z,C @.0V]N;F5C=%Q#;VYN4WES#0HQ,CHS-#HR,"!"
M;V]K<PT*,3(Z,S0Z,C @.0F]O:W-<0F]O:W-O#0HQ,CHS-#HR,"!";V]K<UQ"
M;V]K<V]<571I;',-"C$R.C,T.C(P($1E=E1O;VQS#0HQ,CHS-#HR,"!$9794
M;V]L<UQ$8F<@.26YT#0HQ,CHS-#HR,"!$9794;V]L<UQ$8F<@.26YT7$1B9R!)
M;G0@.0V]M;6]N#0HQ,CHS-#HR,"!$9794;V]L<UQ$8F<@.26YT7$5810T*,3(Z
M,S0Z,C @.0V]R95)E<&P-"C$R.C,T.C(P($-O<F5297!L7%)E<S$P,S,-"C$R
M.C,T.C(P($-O<F5297!L7%)E<TEN=&P-"C$R.C,T.C(P($-O<F4-"C$R.C,T
M.C(P($-O<F5<4F5S,3 S,PT*,3(Z,S0Z,C @.0V]R95Q297-/=&AE<@.T*,3(Z
M,S0Z,C @.4F5P;W-T<GD-"C$R.C,T.C(P(%)E<&]S=')Y7%)E<'-T4WES#0HQ
M,CHS-#HR,"!297!O<W1R>5Q297,Q,#,S#0HQ,CHS-#HR,"!297!O<W1R>5Q2
M97-);G1L#0HQ,CHS-#HR,"!#;W)E36ES8PT*,3(Z,S0Z,C @.0V]R94UI<V-<
M06-T:79E6 T*,3(Z,S0Z,C @.0V]R94UI<V-<06-T:79E6%Q297,Q,#,S#0HQ
M,CHS-#HR,"!#;W)E36ES8UQ!8W1I=F587%)E<TEN=&P-"C$R.C,T.C(P($-O
M<F5-:7-C7%)E<S$P,S,-"C$R.C,T.C(P($UO;F%R8V@.-"C$R.C,T.C(P($UO
M;F%R8VA<36]N<C$P,S,-"C$R.C,T.C(P($UO;F%R8VA<36]N<DEN=&P-"C$R
M.C,T.C(P($IE= T*,3(Z,S0Z,C @.0V]R94EN<W0-"C$R.C,T.C(P($-O<F5#
M3TT-"C$R.C,T.C(P($-O<F5#3TU<4F5S,3 S,PT*,3(Z,S0Z,C @.0V]R94-/
M35Q297-);G1L#0HQ,CHS-#HR,"!#;W)E5&]O; T*,3(Z,S0Z,C @.0V]R951O
M;VQ<4F5S,3 S,PT*,3(Z,S0Z,C @.0V]R951O;VQ<4F5S3W1H97(-"C$R.C,T
M.C(P($1"3&EB0VQI#0HQ,CHS-#HR,"!31D5X= T*,3(Z,S0Z,C @.4T9%>'1<
M06-T:79E6 T*,3(Z,S0Z,C @.4T9%>'1<06-T:79E6%Q297,Q,#,S#0HQ,CHS
M-#HR,"!31D5X=%Q!8W1I=F587%)E<TEN=&P-"C$R.C,T.C(P(%-&17AT7%)E
M<S$P,S,-"C$R.C,T.C(P(%-&17AT7%)E<TEN=&P-"C$R.C,T.C(P(%1R86-E
M#0HQ,CHS-#HR,"!4<F%C95Q297,Q,#,S#0HQ,CHS-#HR,"!4<F%C95Q297-/
M=&AE<@.T*,3(Z,S0Z,C @.36ES8T-O<F4-"C$R.C,T.C(P($U##0HQ,CHS-#HR
M,"!-0UQ-0S$P,S,-"C$R.C,T.C(P($U#7$U#26YT; T*,3(Z,S0Z,C @.34-<
M2&5L< T*,3(Z,S0Z,C @.4U%,36=R#0HQ,CHS-#HR,"!344Q-9W)<4F5S,3 S
M,PT*,3(Z,S0Z,C @.4U%,36=R7%)E<TEN=&P-"C$R.C,T.C(P(%-V<E1O;VP-
M"C$R.C,T.C(P(%-V<E1O;VQ<4F5S,3 S,PT*,3(Z,S0Z,C @.4W9R5&]O;%Q2
M97-);G1L#0HQ,CHS-#HR,"!$5%-520T*,3(Z,S0Z,C @.1%1354E<4F5S,3 S
M,PT*,3(Z,S0Z,C @.1%1354E<4F5S26YT; T*,3(Z,S0Z,C @.35-/;&%P#0HQ
M,CHS-#HR,"!-4T]L87!<4F5S,3 S,PT*,3(Z,S0Z,C @.35-/;&%P7%)E<TEN
M=&P-"C$R.C,T.C(P($%43 T*,3(Z,S0Z,C @.051,7'=I;FYT#0HQ,CHS-#HR
M,"!!5$Q<=VEN.7@.-"C$R.C,T.C(P($U&0S0R50T*,3(Z,S0Z,C @.5D,-"C$R
M.C,T.C(P(%9"#0HQ,CHS-#HR,"!/0U@.Q#0HQ,CHS-#HR,"!344Q!9$AL< T*
M,3(Z,S0Z,C @.4U%,061(;'!<4F5S,3 S,PT*,3(Z,S0Z,C @.4U%,061(;'!<
M4F5S3W1H97(-"C$R.C,T.C(P('M%,#=&1$1"12TU03(Q+3$Q9#(M.41!1" TP
M,$,P-$8W.40T,S1]#0HQ,CHS-#HR,"![13 W1D1$0S<M-4$R,2TQ,60R+3E$
M040M,#!#,#1&-SE$-#,T?0T*,3(Z,S0Z,C @.>T4P-T9$1$,P+35!,C$M,3%D
M,BTY1$%$+3 P0S T1C<Y1#0S-'T-"C$R.C,T.C(P('M%,#=&1$1"1BTU03(Q
M+3$Q9#(M.41!1"TP,$,P-$8W.40T,S1]#0HQ,CHS-#HR,"!%;F0@.06-T:6]N
M($QO9U-E;&5C=&5D0V]M<&]N96YT<PT*,3(Z,S0Z,C @.0F5G:6X@.06-T:6]N
M($EN<W1A;&Q0:V=S.@.T*,3(Z,S0Z,C @.0F5G:6X@.06-T:6]N.B!,;V-K960@.
M0V]N;F5C=&EV:71Y($9I;&5S($-H96-K#0HQ,CHS-#HR,2!#;VYN96-T:79I
M='E,;V-K960@.<F5T=7)N960Z(# -"C$R.C,T.C(Q(%1H92!O<&5R871I;VX@.
M8V]M<&QE=&5D('-U8V-E<W-F=6QL>2X-"@.T*,3(Z,S0Z,C$@.16YD($%C=&EO
M;CH@.3&]C:V5D($-O;FYE8W1I=FET>2!&:6QE<R!#:&5C:PT*,3(Z,S0Z,C$@.
M4V5T=7 @.:7,@.:6YS=&%L;&EN9R!-:6-R;W-O9G0@.1&%T82!!8V-E<W,@.0V]M
M<&]N96YT<R H341!0RD@.+BXN#0HQ,CHS-#HR,2!$.EQX.#9<3W1H97)<<W%L
M<F5D:7,N97AE("]Q.F$@.+T,Z(G-E='5P<F4N97AE(%=!4DX],2 M<R M4TU3
M(@.T*,3(Z,S0Z-#D@.17AI=$-O9&4Z(# -"C$R.C,T.C0Y(%-E='5P(&ES(&EN
M<W1A;&QI;F<@.36EC<F]S;V9T($1I<W1R:6)U=&5D(%1R86YS86-T:6]N($-O
M;W)D:6YA=&]R("A-4T140RD@.+BXN#0HQ,CHS-#HT.2 @.0SI<5TE.1$]74UQ4
M14U07%-Q;%-E='5P7$)I;EQC;&1T8W-T<"YE>&4@.+5-U<'!O<G1$:7(@.(D,Z
M7%=)3D1/5U-<5$5-4%Q3<6Q3971U<%Q":6XB("U$5$-0:V<@.(D0Z7'@.X-EQ/
M=&AE<EQD=&-S971U<"YE>&4B("U,;V=&:6QE(")#.EQ724Y$3U=37'-Q;'-T
M<"YL;V<B#0HQ,CHS-#HU,2!0<F]C97-S($5X:70@.0V]D93H@.*# I( T*,3(Z
M,S0Z-3$@.("]1.D$@.+U0Z0SI<5TE.1$]74UQ414U07&EX<# P,2YT;7 -"C$R
M.C,T.C4Q(%-E='5P(&ES(&EN<W1A;&QI;F<@.2%1-3"!(96QP("XN+@.T*,3(Z
M,S0Z-3(@.2%1-3"!(96QP(&EN<W1A;&QE<B!E>&ET(&-O9&4Z(# -"C$R.C,U
M.C$U($5N9"!!8W1I;VX@.26YS=&%L;%!K9W,-"C$R.C,U.C$U($)E9VEN($%C
M=&EO;B!-;W9E1FEL941A=&$Z#0HQ,CHS-3HQ-2!%;F%B;&5D(%-%3$9214=)
M4U1%4D)!5$-(#0HQ,CHS-3HQ-2!%;F%B;&5D($-/4D5#3TU03TY%3E1(04Y$
M3$E.1PT*,3(Z,S<Z,C<@.0F5G:6X@.06-T:6]N.B @.36]V949I;&5$871A4W!E
M8VEA; T*,3(Z,S<Z,C@.@.16YD($%C=&EO;CH@.($UO=F5&:6QE1&%T85-P96-I
M86P-"C$R.C,W.C(X($5N9"!!8W1I;VX@.("!-;W9E1FEL941A=&$-"C$R.C,W
M.C(X($)E9VEN($%C=&EO;B!0<F]C97-S069T97)$871A36]V93H-"C$R.C,W
M.C(Y($0Z7'@.X-EQ":6YN7&AH8V]L+F5X92!#.EQ0<F]G<F%M($9I;&5S7$UI
M8W)O<V]F="!344P@.4V5R=F5R7#@.P7%1O;VQS7$)O;VMS#0HQ,CHS-SHS,2!%
M;F0@.06-T:6]N(" @.4')O8V5S<T%F=&5R1&%T84UO=F4-"C$R.C,W.C,Q($)E
M9VEN($%C=&EO;B!"=6EL9%-E<G9E<CH-"C$R.C,W.C,Q($,Z7%=)3D1/5U-<
M5$5-4%Q3<6Q3971U<%Q":6Y<<V-M+F5X92 @.+5-I;&5N=" Q("U!8W1I;VX@.
M-2 M17AE4&%T:" B0SI<4')O9W)A;2!&:6QE<UQ-:6-R;W-O9G0@.4U%,(%-E
M<G9E<EQ-4U-13%QB:6YN7'-Q;'-E<G9R+F5X92(@.+5-E<G9I8V4@.(DU34U%,
M4T525D52(@.T*,3(Z,S<Z,S(@.4')O8V5S<R!%>&ET($-O9&4Z("@.P*2 -"C$R
M.C,W.C,R($)E9VEN($%C=&EO;CH@.0W)E871E4F5G:7-T<GE3971344P-"C$R
M.C,W.C,R($5N9"!!8W1I;VXZ($-R96%T95)E9VES=')Y4V5T4U%,#0HQ,CHS
M-SHS,B!"96=I;B!!8W1I;VXZ(%)E9U=R:71E4V5T=7!%;G1R>0T *,3(Z,S<Z
M,S(@.16YD($%C=&EO;CH@.4F5G5W)I=&53971U<$5N=')Y#0HQ, CHS-SHS,B!"
M96=I;B!!8W1I;VXZ($-R96%T95-E<@.T*,3(Z,S<Z,S(@.16YD($%C=&EO;CH@.
M0W)E871E4V5R#0HQ,CHS-SHS,B!"96=I;B!!8W1I;VXZ(%-K=4ET#0HQ,CHS
M-SHS,B!%;F0@.06-T:6]N.B!3:W5)= T*,3(Z,S<Z,S(@.4V5T1FEL95-E8W5R
M:71Y4U%,06YD061M:6X@.9F]R($,Z7%!R;V=R86T@.1FEL97-<36EC<F]S;V9T
M(%-13"!397)V97)<35-344P@.<F5T=7)N960Z(#$S-3 L(#$S-3 -"C$R.C,W
M.C,S(%-E=%)E9U-E8W5R:71Y4U%,06YD061M:6X@.9F]R(%-O9G1W87)E7$UI
M8W)O<V]F=%Q-4U-13%-E<G9E<EQ-4U-13%-E<G9E<B!R971U<FYE9#H@.,"P@.
M, T*,3(Z,S<Z,S,@.0F5G:6X@.06-T:6]N.B!5<&1A=&53>7-T96U0871H#0HQ
M,CHS-SHS,R!0871H('-U8V-E<W-F=6QL>2!U<&1A=&5D+@.T*,3(Z,S<Z,S,@.
M)5-94U1%35)/3U0E7%-94U1%33,R.R5365-414U23T]4)3LE4UE35$5-4D]/
M5"5<4UE35$5-,S)<5T)%33M#.EQ04D]'4D%-($9)3$537%)!5$E/3D%,7$-/
M34U/3CM#.EQ04D]'4D%-($9)3$537%)!5$E/3D%,7$-,14%20T%315Q"24X[
M0SI<4')O9W)A;2!&:6QE<UQ086YD82!3;V9T=V%R95Q086YD8 2!!;G1I=FER
M=7,@.4&QA=&EN=6T[0SI<4')O9W)A;2!&:6QE<UQ-:6-R;W-O9G0@.4U%,(%-E
M<G9E<EPX,%Q4;V]L<UQ"24Y..T,Z7%!R;V=R86T@.1FEL97-<37E344Q<37E3
M44P@.4V5R=F5R(#0N,5QB:6X[#0HQ,CHS-SHS,R!%;F0@.06-T:6]N.B!5<&1A
M=&53>7-T96U0871H#0HQ,CHS-SHS-"!#.EQ0<F]G<F%M($9I;&5S7$UI8W)O
M<V]F="!344P@.4V5R=F5R7#@.P7%1O;VQS7$)I;FY<8VYF9W-V<BYE>&4@.("U&
M(")#.EQ724Y$3U=37'-Q;'-T<"YL;V<B("U)($U34U%,4T525D52("U6(#$@.
M+4T@.," M42 B4VQO=F5N:6%N7T-)7T%3(B M2" V-3@.Y-" M52!S82 M4" -
M"B,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C( R,C(R,C(R,C
M(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,-"@.T*#0I3=&%R
M=&EN9R!397)V:6-E("XN+@.T*#0I3;&]V96YI86Y?0TE?05,-"@.T*+6T@.+5$@.
M+50T,#(R("U4,S8U.0T*#0I#;VYN96-T:6YG('1O(%-E<G9E<B N+BX-"@.T*
M9')I=F5R/7MS<6P@.<V5R=F5R?3MS97)V97(]05-025)%,3,P,#M5240]<V$[
M4%=$/3MD871A8F%S93UM87-T97(-"@.T*6TUI8W)O<V]F=%U;3T1"0R!344P@.
M4V5R=F5R($1R:79E<EU;3F%M960@.4&EP97-=0V]N;F5C=&EO;B!B<F]K96XN
M#0H-"EM-:6-R;W-O9G1=6T]$0D,@.4U%,(%-E<G9E<B!$<FEV97)=6TYA;65D
M(%!I<&5S74-O;FYE8W1I;VY296%D("A'971/=F5R3&%P<&5D4F5S=6QT*"DI
M+@.T*#0ID<FEV97(]>W-Q;"!S97)V97)].W-E<G9E<CU!4U!)4D4Q,S P.U5)
M1#US83M05T0].V1A=&%B87-E/6UA<W1E<@.T*#0I;36EC<F]S;V9T75M/1$)#
M(%-13"!397)V97(@.1')I=F5R75M.86UE9"!0:7!E<UU#;VYN96-T:6]N(&)R
M;VME;BX-"@.T*6TUI8W)O<V]F=%U;3T1"0R!344P@.4V5R=F5R($1R:79E<EU;
M3F%M960@.4&EP97-=0V]N;F5C=&EO;E)E860@.*$=E=$]V97),87!P961297-U
M;'0H*2DN#0H-"F1R:79E<CU[<W%L('-E<G9E<GT[<V5R=F5R/4%34$E213$S
M,# [54E$/7-A.U!71#T[9&%T86)A<V4];6%S=&5R#0H-"EM-:6-R;W-O9G1=
M6T]$0D,@.4U%,(%-E<G9E<B!$<FEV97)=6TYA;65D(%!I<&5S74-O;FYE8W1I
M;VX@.8G)O:V5N+@.T*#0I;36EC<F]S;V9T75M/1$)#(%-13"!397)V97(@.1')I
M=F5R75M.86UE9"!0:7!E<UU#;VYN96-T:6]N4F5A9" H4F5A9$9I;&4H*2DN
M#0H-"E-13"!397)V97(@.8V]N9FEG=7)A=&EO;B!F86EL960N#0H-"B,C(R,C
M(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C( R,C(R,C(R,C
M(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,-"@.T*,3(Z,S@.Z,C(@.4')O
M8V5S<R!%>&ET($-O9&4Z("@.M,2D@.#0HQ,CHS.3HQ.2!3971U<"!F86EL960@.
M=&\@.8V]N9FEG=7)E('1H92!S97)V97(N(" @.4F5F97(@.=&\@.=&AE('-E<G9E
M<B!E<G)O<B!L;V=S(&%N9"!#.EQ724Y$3U=37'-Q;'-T<"YL;V<@.9F]R(&UO
M<F4@.:6YF;W)M871I;VXN#0HQ,CHS.3HR,R!!8W1I;VX@.17AI= "!(86YD;&5R
M.@.T*,3(Z,SDZ-3<@.06-T:6]N($-L96%N57!);G-T86QL.@.T*,3(Z,SDZ-3<@.
M0SI<5TE.1$]74UQ414U07%-Q;%-E='5P7$)I;EQS8VTN97AE(" M4VEL96YT
M(#$@.+4%C=&EO;B T("U397)V:6-E(%-13%-%4E9%4D%'14Y4#0HQ,CHS.3HU
M-R!0<F]C97-S($5X:70@.0V]D93H@.*#$P-C I(%1H92!S<&5C:69I960@.<V5R
M=FEC92!D;V5S(&YO="!E>&ES="!A<R!A;B!I;G-T86QL960@.<V5R=FEC92X-
M"@.T*,3(Z,SDZ-3<@.0SI<5TE.1$]74UQ414U07%-Q;%-E='5P7$)I;EQS8VTN
M97AE(" M4VEL96YT(#$@.+4%C=&EO;B T("U397)V:6-E($U34U%,4T525D52
M#0HQ,CHS.3HU-R!0<F]C97-S($5X:70@.0V]D93H@.*# I( T*,3(Z,SDZ-3<@.
M4W1A='-'96YE<F%T92!R971U<FYE9#H@.,@.T*,3(Z,SDZ-3<@.4W1A='-'96YE
M<F%T92 H,'@.P+#!X,2PP>&8P,# P,# L,'@.R,# L,3 S,RPS,#,L,'@.P+#!X
M,2PP+# L, T*,3(Z,SDZ-3<@.4W1A='-'96YE<F%T92 M,2Q)+4%R;6EC*0T*
?,3(Z,SDZ-3<@.26YS=&%L;&%T:6]N($9A:6QE9"X-"@.``
`
end
Miha,
The following KB link may help
http://support.microsoft.com/default...;en-us;841249. According
to the log (near the end), the connection is being broken when trying to
access the SQL Server. The Windows Firewall that was introduced with Windows
XP SP2 may be causing the problem. The link will provides directions on
configuring the firewall to allow SQL Server 2000 to operate. Hope this
helps. Thanks.
William Hutchison [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.
"Miha" <miha.bernik@.isg.si> wrote in message
news:O$BtUGC9EHA.1204@.TK2MSFTNGP10.phx.gbl...
> Hi
> I'm having problems installing MS SQL 2000 (Developer edition) Server on a
> Windows XP SP2 computer.
> It's a clean Windows XP installation, and it is not the first time the we
> install SQL 2k on a WinXP computer,so it's quite strange becasue quite at
> the end of the installation when I try to configure SQL server
> installation fails.
> I included a log-file that was generating during the installation.
> Any help or tips how to resolve this would be appriciated.
> Thank you all in advance
> Best regards
> Miha
>
>
|||Hi,
I installed SQL 2k over WinXP SP1, and then, I upgraded to SP2...Any
problem...SQL Server is working very well.
You can try to install SQL Server SP3a...may be, this solve your problem.
Richard_SQL
DBA
"William Hutchison [MSFT]" wrote:

> Miha,
> The following KB link may help
> http://support.microsoft.com/default...;en-us;841249. According
> to the log (near the end), the connection is being broken when trying to
> access the SQL Server. The Windows Firewall that was introduced with Windows
> XP SP2 may be causing the problem. The link will provides directions on
> configuring the firewall to allow SQL Server 2000 to operate. Hope this
> helps. Thanks.
> --
> William Hutchison [MSFT]
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Miha" <miha.bernik@.isg.si> wrote in message
> news:O$BtUGC9EHA.1204@.TK2MSFTNGP10.phx.gbl...
>
>

Problem with Install of MSSQL 2005 Standard x64 on two node cluster

Hi:
I'm trying to install MS SQL 2005 Standard x64 to a two node Windows Server
2003 R2 SP2 cluster.
I've setup the cluster as per MS requirements and tested failover, The
cluster seems to be working well.
When I go through the Install and select failover clustering for the
Database and Analysis services, all seems to go well until it gets to the
end, I get a failure on the second (passive) node.
On the passive node I find that there is a Task Scheduler job set, SQL
Server Remote Setup.job that is reporting this error:
"SQL Server Remote Setup .job" (setup.exe) 12/4/2007 12:40:14 PM ** ERROR
**
Unable to start task.
The specific error is:
0x80070005: Access is denied.
Try using the Task page Browse button to locate the application.
The only MS info, I've found is not to be in RDP on the second node. I've
tried that and even did an install from the console on the first node (No
Remote Desktop sessions at all). Same error.
I've made sure that the account used is part of the local administrators
group on both nodes and has the following rights:
Act as part of operating system
Logon as a batch job
Logon as a Service
I have been going around on this for several days and cannot come to a
solution.
Is it that the second node doesn't have access to the setup files? I tried
installing from the DVD on the primary node and copied the files to a
directory on the primary and shared it. Same error.
Thanks
Usually, the last thing you tried, moving the setup files, fixes this type
of issue.
Have you tried running the cluster install but only for the first node, then
adding the node via add/remove programs? I sometimes find mirroring the
regular cluster setup logic (build a single-node cluster and add on) helps.
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP
"Paul Hons" <Paul.Hons@.unt.edu> wrote in message
news:4755520A.B695.00E7.0@.unt.edu...
> Hi:
> I'm trying to install MS SQL 2005 Standard x64 to a two node Windows
> Server
> 2003 R2 SP2 cluster.
> I've setup the cluster as per MS requirements and tested failover, The
> cluster seems to be working well.
> When I go through the Install and select failover clustering for the
> Database and Analysis services, all seems to go well until it gets to the
> end, I get a failure on the second (passive) node.
> On the passive node I find that there is a Task Scheduler job set, SQL
> Server Remote Setup.job that is reporting this error:
> "SQL Server Remote Setup .job" (setup.exe) 12/4/2007 12:40:14 PM ** ERROR
> **
> Unable to start task.
> The specific error is:
> 0x80070005: Access is denied.
> Try using the Task page Browse button to locate the application.
> The only MS info, I've found is not to be in RDP on the second node. I've
> tried that and even did an install from the console on the first node (No
> Remote Desktop sessions at all). Same error.
> I've made sure that the account used is part of the local administrators
> group on both nodes and has the following rights:
> Act as part of operating system
> Logon as a batch job
> Logon as a Service
> I have been going around on this for several days and cannot come to a
> solution.
> Is it that the second node doesn't have access to the setup files? I tried
> installing from the DVD on the primary node and copied the files to a
> directory on the primary and shared it. Same error.
> Thanks
>
>
|||Geoff N. Hiten wrote:
> Usually, the last thing you tried, moving the setup files, fixes this
> type of issue.
> Have you tried running the cluster install but only for the first
> node, then adding the node via add/remove programs? I sometimes find
> mirroring the regular cluster setup logic (build a single-node cluster
> and add on) helps.
>
One other thing to try - which I had to do to get around this issue.
Have you logged into both systems with the service account that you will
be using to run SQL Server? If not, make sure you log into both
machines with that account to create the user profile. For whatever
reason - without the user profile the task scheduler jobs cannot be started.
At least that is what worked for me.
BTW - before you restart your install make sure you uninstall the setup
files or you will get another error.
Jeff

Friday, March 23, 2012

problem with insert into in scheduled job pleas help ASAP

Hello MSDN

I am using SQL 2005 and trying to INSTERT data in to a table

When I am using my command from SQL query windows it works fine,

INSERT INTO "tbl.FTPuploads" ("FTPFile_Names", "FTPGS", "FTPST", "FTPJOB", "FTPDN", "FTPSTATUS", "FTPDATE", "FTPTIME")

SELECT "FTPFile_Names", "FTPGS", "FTPST", "FTPJOB", "FTPDN", "FTPSTATUS", "FTPDATE", "FTPTIME"

FROM OpenDataSource( 'Microsoft.Jet.OLEDB.4.0',

'Data Source="G:\DATA\EDItoDB";Extended properties=Text')...uploaded#txt

But when I am trying to put that command in to a scheduled job I get this error

Executed as user: GW\fmnlasa. Incorrect syntax near 'tbl.FTPuploads'. [SQLSTATE 42000] (Error 102).The step failed.

I have changed the command to this, I have removed the quotes from the table name.

INSERT INTO tbl.FTPuploads ("FTPFile_Names", "FTPGS", "FTPST", "FTPJOB", "FTPDN", "FTPSTATUS", "FTPDATE", "FTPTIME")

SELECT "FTPFile_Names", "FTPGS", "FTPST", "FTPJOB", "FTPDN", "FTPSTATUS", "FTPDATE", "FTPTIME"

FROM OpenDataSource( 'Microsoft.Jet.OLEDB.4.0',

'Data Source="G:\DATA\EDItoDB";Extended properties=Text')...uploaded#txt

And now I get this error

Executed as user: GW\fmnlasa. Access to the remote server is denied because the current security context is not trusted. [SQLSTATE 42000] (Error 15274).The step failed.

When you execute from the query, it will use your credential to connect the remote server. But the scheduled query might use the ServiceAccount. Check which service account used in the current context & give the required permission on the remote server. Or change the service account context to NT Credential.|||

Bascially the issues is of Security Context under which the Job run. Check these links

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1012759&SiteID=1

http://www.sqlmonster.com/Uwe/Forum.aspx/sql-server/44111/Access-to-the-remote-server-is-denied-because-the-current-security

Madhu

|||

Thank you, for such a quick reply

I was using the same account in Job to as I was using in Query window

I am not sure but I think that the problem was in my table and column names

I have created new table with the name tblFTPuploads the old one was tbl.FTPuploads

After that I got erros for may column names so I have changed the first column name to FTPFileNames the old one was FTPfile_name

And the last step I did was to remove the quotes from the table and column names.

So the end script is like this

INSERT INTO tblFTPuploads (FTPFileNames, FTPGS, FTPST, FTPJOB, FTPDN, FTPSTATUS, FTPDATE, FTPTIME)

SELECT FTPFileNames, FTPGS, FTPST, FTPJOB, FTPDN, FTPSTATUS, FTPDATE, FTPTIME

FROM OpenDataSource( 'Microsoft.Jet.OLEDB.4.0',

'Data Source="G:\DATA\EDItoDB";Extended properties=Text')...uploaded#txt

And it is working now no problems.

Thanks again for a quick reply

Best regards,

Artavazd ASLANYAN

Network Administrator

Tuesday, March 20, 2012

Problem with Form Authentication Example

I installed the Microsoft Forms Authentication in Report Services example in
a VPC running Windows 2003, Active Directory, SQl Server Enterprise and SQL
Reporting Servcie Enterprise Edition.
I registered user "john" and modified RSReportServer.config and added and
changed the value for <UserName> tag to be "john".
Stepping through the debugger the demo fails on GetWebResponse because
cookie is null.
I have tried FQDN in RSWebApplication.config but problem persist.
Any idea what is going wrong causing GetWebResponse to fail?I'm using a solution that's primarily based on the Forms Auth sample and I
can say that it does work. Double-check your web.config modifications for
the ReportServer and ReportManager webs according to the instructions in the
sample.
Adrian M.
"John Amason" <jamason@.ics-associates.com> wrote in message
news:uH%23y30Q$EHA.2580@.TK2MSFTNGP15.phx.gbl...
>I installed the Microsoft Forms Authentication in Report Services example
>in
> a VPC running Windows 2003, Active Directory, SQl Server Enterprise and
> SQL
> Reporting Servcie Enterprise Edition.
> I registered user "john" and modified RSReportServer.config and added and
> changed the value for <UserName> tag to be "john".
> Stepping through the debugger the demo fails on GetWebResponse because
> cookie is null.
> I have tried FQDN in RSWebApplication.config but problem persist.
> Any idea what is going wrong causing GetWebResponse to fail?
>

Problem with Forecasting with Excel 2007 DM Add-in using drill-through data from SSAS 2005!

I’m having a problem with Excel 2007 DM and SQL 2005 and I hope someone out there has a solution.

Consider the following environment:

Windows XP SP2 or Windows Vista, Excel 2007, Data Mining Add-in, SSAS 2005 (with session mining models enabled, an AdventureWorksDW cube deployed and drill-through actions available).

Now take the following steps:

1. In Excel 2007 set up a connection to SSAS

2. Connect to the cube and create a new pivot table report (drag and drop whatever you like)

3. Right-click on one of the cell values in the data region and either select a drill-through action, or, select Show Details in the context menu

4. Ensure that you have at least 10 detailed records that are generated on a new worksheet page; you should have a time-based column in your detailed records

5. Select the table of detailed data, then select the Analyze tab (within the Table Tools grouping) which appears in the topmost menu above the ribbon

6. Click the Forecast button in the ribbon and choose both the field which you want to predict as well as the time-based column (from step 4) as well as the number of time periods to forecast

7. Finally click OK.

1. Having followed these steps on both WinXP SP2 and Vista, I keep coming across the exception: HResult:0x800A03EC. Any ideas as to why this exception pops up? If I was using a normal table of data (which was not generated from a Show Details or drill-through action), then the Forecast button works fine.

I googled it and thought the localization settings for SSAS 2005 and Excel 2007 needed to be the same (initially they weren’t). I’ve tried removing the auto-filters which appear atop each column in the detailed data table prior to clicking the Forecast button, and, I’ve also tested for a series of data across a number of time periods with the same result.

Also, a colleague of mine discovered that the column headers that appear by default from a drill-through start with "$[", and, in removing them the Forecast function appears to work.

I would have thought there would be a seamless transition in Excel 2007 between data retrieved from a cube and the DM Add-in featueres (or at the very least, a more meaningful exception message than the one presented).

Is there something I’ve missed, or, is there a KB article I haven’t come across yet? As I know for a fact that the problem is reproducible, is there a fix to this problem on its way to us? Is there a useful workaround that doesn't require manual intervention?

Thanks,

Thanks for the detailed repro - we'll look into it.|||

We have fixed this for future versions of the add-in.

To workaround the bug, please remove [ and ] from the column names.

Thanks a lot for the detailed repro.

Problem with Forecasting with Excel 2007 DM Add-in using drill-through data from SSAS 2005!

I’m having a problem with Excel 2007 DM and SQL 2005 and I hope someone out there has a solution.

Consider the following environment:

Windows XP SP2 or Windows Vista, Excel 2007, Data Mining Add-in, SSAS 2005 (with session mining models enabled, an AdventureWorksDW cube deployed and drill-through actions available).

Now take the following steps:

1. In Excel 2007 set up a connection to SSAS

2. Connect to the cube and create a new pivot table report (drag and drop whatever you like)

3. Right-click on one of the cell values in the data region and either select a drill-through action, or, select Show Details in the context menu

4. Ensure that you have at least 10 detailed records that are generated on a new worksheet page; you should have a time-based column in your detailed records

5. Select the table of detailed data, then select the Analyze tab (within the Table Tools grouping) which appears in the topmost menu above the ribbon

6. Click the Forecast button in the ribbon and choose both the field which you want to predict as well as the time-based column (from step 4) as well as the number of time periods to forecast

7. Finally click OK.

Also, a colleague of mine discovered that the column headers that appear by default from a drill-through start with "$[", and, in removing them the Forecast function appears to work.

Thanks,

Thanks for the detailed repro - we'll look into it.|||

We have fixed this for future versions of the add-in.

To workaround the bug, please remove [ and ] from the column names.

Thanks a lot for the detailed repro.

Problem with Forecasting with Excel 2007 DM Add-in using drill-through data from SSAS 2005!

I’m having a problem with Excel 2007 DM and SQL 2005 and I hope someone out there has a solution.

Consider the following environment:

Windows XP SP2 or Windows Vista, Excel 2007, Data Mining Add-in, SSAS 2005 (with session mining models enabled, an AdventureWorksDW cube deployed and drill-through actions available).

Now take the following steps:

1. In Excel 2007 set up a connection to SSAS

2. Connect to the cube and create a new pivot table report (drag and drop whatever you like)

3. Right-click on one of the cell values in the data region and either select a drill-through action, or, select Show Details in the context menu

4. Ensure that you have at least 10 detailed records that are generated on a new worksheet page; you should have a time-based column in your detailed records

5. Select the table of detailed data, then select the Analyze tab (within the Table Tools grouping) which appears in the topmost menu above the ribbon

6. Click the Forecast button in the ribbon and choose both the field which you want to predict as well as the time-based column (from step 4) as well as the number of time periods to forecast

7. Finally click OK.

Also, a colleague of mine discovered that the column headers that appear by default from a drill-through start with "$[", and, in removing them the Forecast function appears to work.

Thanks,

Thanks for the detailed repro - we'll look into it.|||

We have fixed this for future versions of the add-in.

To workaround the bug, please remove [ and ] from the column names.

Thanks a lot for the detailed repro.

Friday, March 9, 2012

Problem with DTS

Hi there.
I have the following environment:
Windows 2000 Server SP4, SQL Server 2000 Sp3.
There are some DTS which have been creating some time ago. They are
scheduled are have been runngin until now. Now the jobs fail. Can't say
what has been changed. Haven't been responsible for those systems and
those who are say they didnt change anything (same story as always ;)
...)
The DTS have been created when connecting with an Windows Domain
Account. When I connect with this Windows Account I can open and run
those DTS. But when login as local Admin directly on the server and open
Enterprise Manager with the local Admin User and try to open the DTS I
get an error:
Error Source : Microsfot OLE DB Provider for SQL Server
Error Description: [DBNETLIB]ConnectionOpen(Connect()).]SQL Server does
not exist or access is denied.
The DTS is a Local Package (I have some Meta Data Service Packages ...
same there).
The simlest DTS has two SQL Server connection using a SQL User. First a
Delete on the first connection is made, then some data is copied from
connection2 to connection1.
As I said, when I login with Domain User Account I can open it, edit it,
run it .. no problems. But with the local Admin of the SQL Server ...
error.
SQL Server and SQL Agent are running as local System Accounts.
Why am I getting this error? I think it cant be the Connections in the
DTS, because there SQL Users are used which exists and work.
The Local Administartor is also a SQL System Admin, as are the Domain
Admins.
Any hints? Anyone knows where I could investigate further?
--
mfg
Marc EggenbergerSomeone removed the BUILTIN\Administrators login from SQL Server, as they
should have, and have replaced it with the [NT AUTHORITY\SYSTEM] group;
however, they should have followed proper Change Control policies. I'm
surprised you haven't been having more problems.
At the VERY least, you should be running the MSSQL and SQLAGENT service
under local accounts, NOT SYSTEM. And, if you can, run the services under a
Domain Account.
So you know, SYSTEM = [NT AUTHORITY]\SYSTEM and is not a Local User but a
GLOBAL AD GROUP. The members of this group are all the <Machine Name>$
server accounts that are created whenever you add a server as a Domain Member.
Next, if you use a Domain Account for the services, you can grant explicit
privleges to those accounts on other server network shares.
As you know, DTS runs in the process space and under the security context of
the user that executes the DTSRun command. When the package runs as a job,
it uses the server's memory space and the SYSTEM account because that is what
the SQLAgent is running as and where it is running.
You can not log in as SYSTEM and SYSTEM and Local Administrator are two
different security contexts. Another good reason to have an explicitly
defined account to run the SQL Server services under: you can log in to the
server as that user and "see" what the services would see when they log in.
Sincerely,
Anthony Thomas
"Marc Eggenberger" wrote:
> Hi there.
> I have the following environment:
> Windows 2000 Server SP4, SQL Server 2000 Sp3.
> There are some DTS which have been creating some time ago. They are
> scheduled are have been runngin until now. Now the jobs fail. Can't say
> what has been changed. Haven't been responsible for those systems and
> those who are say they didnt change anything (same story as always ;)
> ...)
> The DTS have been created when connecting with an Windows Domain
> Account. When I connect with this Windows Account I can open and run
> those DTS. But when login as local Admin directly on the server and open
> Enterprise Manager with the local Admin User and try to open the DTS I
> get an error:
> Error Source : Microsfot OLE DB Provider for SQL Server
> Error Description: [DBNETLIB]ConnectionOpen(Connect()).]SQL Server does
> not exist or access is denied.
> The DTS is a Local Package (I have some Meta Data Service Packages ...
> same there).
> The simlest DTS has two SQL Server connection using a SQL User. First a
> Delete on the first connection is made, then some data is copied from
> connection2 to connection1.
> As I said, when I login with Domain User Account I can open it, edit it,
> run it .. no problems. But with the local Admin of the SQL Server ...
> error.
> SQL Server and SQL Agent are running as local System Accounts.
> Why am I getting this error? I think it cant be the Connections in the
> DTS, because there SQL Users are used which exists and work.
> The Local Administartor is also a SQL System Admin, as are the Domain
> Admins.
> Any hints? Anyone knows where I could investigate further?
>
> --
> mfg
> Marc Eggenberger
>

Wednesday, March 7, 2012

Problem with delete, lock and transaction log

Saturday, February 25, 2012

Problem with delete, lock and transaction log

we have problem with SQL Server 2000 SP3 / Windows 2003 EE
we have 10 huge tables, I have a procedure which deletes data from
these tables each day.
1. The deletes are very slow, it takes 20 min to delete 400,000
records. It does use index when it deletes, i have seen the plan
2. i am running the database in simple mode but still the transaction
log grows bigger and bigger during the delete process. I have used
checkpoint after every table delete but it didnt help. is there a way
we can avoid writing to transaction log so that i can solve this
problem and improve the delete performance too
3. If i stop the job then everything gets rolled back that is been done
by procedure. does it not commit table by table within the procedure?
is it waiting for the procedure to finish before it commits?
Can any one please help me ASAP
Thanks
RaghuAnswer for you questions:-
1. Disable the foreign key if you can do the house keeping after shutdown
the application [ See Alter table command]
2. No you can not avoid to log the transaction. The easy way is shrink the
transaction log fter delete [See DBCC SHRINKFILE]
3. That depends up the way you handle the transaction.. If its a single
delete statement inside the procedure and if you kill the job;
then automatically every thing pertaning to that delete will be rolled back
Thanks
Hari
SQL Server MVP
"raghu" <raghu.burju@.gmail.com> wrote in message
news:1154641875.483366.120510@.75g2000cwc.googlegroups.com...
> we have problem with SQL Server 2000 SP3 / Windows 2003 EE
> we have 10 huge tables, I have a procedure which deletes data from
> these tables each day.
> 1. The deletes are very slow, it takes 20 min to delete 400,000
> records. It does use index when it deletes, i have seen the plan
> 2. i am running the database in simple mode but still the transaction
> log grows bigger and bigger during the delete process. I have used
> checkpoint after every table delete but it didnt help. is there a way
> we can avoid writing to transaction log so that i can solve this
> problem and improve the delete performance too
> 3. If i stop the job then everything gets rolled back that is been done
> by procedure. does it not commit table by table within the procedure?
> is it waiting for the procedure to finish before it commits?
> Can any one please help me ASAP
> Thanks
> Raghu
>|||Thanks hari for the quick response.
I have no foreign keys on these tables. All i have is indexes to of
them one is for delete based on timestamp and other is for select which
includes 3 more columns.
DBCC SHRINKFILE is only after i do the delete, even before the delete
is finished my 100 GB transaction log is getting filled and stopping
all other application to either insert or delete data.
I have 10 delete statements so this mean that everything that it has
tried till that time is rolledback. I can do some kind of commit which
will clear the log as well as prevent the rollback if any problem
occurs. The begin and end transaction locks the table and wont allow to
make selects till it is commited, i want where selects can work when
delete is going on
Raghu
Hari Prasad wrote:
> Answer for you questions:-
> 1. Disable the foreign key if you can do the house keeping after shutdown
> the application [ See Alter table command]
> 2. No you can not avoid to log the transaction. The easy way is shrink the
> transaction log fter delete [See DBCC SHRINKFILE]
> 3. That depends up the way you handle the transaction.. If its a single
> delete statement inside the procedure and if you kill the job;
> then automatically every thing pertaning to that delete will be rolled back
> Thanks
> Hari
> SQL Server MVP
>
>
> "raghu" <raghu.burju@.gmail.com> wrote in message
> news:1154641875.483366.120510@.75g2000cwc.googlegroups.com...
> > we have problem with SQL Server 2000 SP3 / Windows 2003 EE
> > we have 10 huge tables, I have a procedure which deletes data from
> > these tables each day.
> >
> > 1. The deletes are very slow, it takes 20 min to delete 400,000
> > records. It does use index when it deletes, i have seen the plan
> >
> > 2. i am running the database in simple mode but still the transaction
> > log grows bigger and bigger during the delete process. I have used
> > checkpoint after every table delete but it didnt help. is there a way
> > we can avoid writing to transaction log so that i can solve this
> > problem and improve the delete performance too
> >
> > 3. If i stop the job then everything gets rolled back that is been done
> > by procedure. does it not commit table by table within the procedure?
> > is it waiting for the procedure to finish before it commits?
> >
> > Can any one please help me ASAP
> >
> > Thanks
> > Raghu
> >|||raghu wrote:
> we have problem with SQL Server 2000 SP3 / Windows 2003 EE
> we have 10 huge tables, I have a procedure which deletes data from
> these tables each day.
> 1. The deletes are very slow, it takes 20 min to delete 400,000
> records. It does use index when it deletes, i have seen the plan
> 2. i am running the database in simple mode but still the transaction
> log grows bigger and bigger during the delete process. I have used
> checkpoint after every table delete but it didnt help. is there a way
> we can avoid writing to transaction log so that i can solve this
> problem and improve the delete performance too
> 3. If i stop the job then everything gets rolled back that is been done
> by procedure. does it not commit table by table within the procedure?
> is it waiting for the procedure to finish before it commits?
> Can any one please help me ASAP
> Thanks
> Raghu
>
You could use TRUNCATE TABLE, which is non-logged. Be sure to read the
Books Online entry first, there are some caveats to using this vs. DELETE.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Tracy
Truncate table would clean the entire table. I am just trying to clean
old data that is 15 days old and this is a job which does this each day
Raghu
Tracy McKibben wrote:
> raghu wrote:
> > we have problem with SQL Server 2000 SP3 / Windows 2003 EE
> > we have 10 huge tables, I have a procedure which deletes data from
> > these tables each day.
> >
> > 1. The deletes are very slow, it takes 20 min to delete 400,000
> > records. It does use index when it deletes, i have seen the plan
> >
> > 2. i am running the database in simple mode but still the transaction
> > log grows bigger and bigger during the delete process. I have used
> > checkpoint after every table delete but it didnt help. is there a way
> > we can avoid writing to transaction log so that i can solve this
> > problem and improve the delete performance too
> >
> > 3. If i stop the job then everything gets rolled back that is been done
> > by procedure. does it not commit table by table within the procedure?
> > is it waiting for the procedure to finish before it commits?
> >
> > Can any one please help me ASAP
> >
> > Thanks
> > Raghu
> >
> You could use TRUNCATE TABLE, which is non-logged. Be sure to read the
> Books Online entry first, there are some caveats to using this vs. DELETE.
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com|||raghu wrote:
> Tracy
> Truncate table would clean the entire table. I am just trying to clean
> old data that is 15 days old and this is a job which does this each day
>
I guess I missed that in your original post...
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||I have resolved one problem by splitting the job of delete into 2
different procedures where in the transaction log doesn't grow big now.
The performance of delete is still not improved it does take same
amount of time as mentioned. can anyone have any idea FYI
The deletes are too slow. it takes 20 min to delete 400000 records.
Raghu
raghu wrote:
> Thanks hari for the quick response.
> I have no foreign keys on these tables. All i have is indexes to of
> them one is for delete based on timestamp and other is for select which
> includes 3 more columns.
> DBCC SHRINKFILE is only after i do the delete, even before the delete
> is finished my 100 GB transaction log is getting filled and stopping
> all other application to either insert or delete data.
> I have 10 delete statements so this mean that everything that it has
> tried till that time is rolledback. I can do some kind of commit which
> will clear the log as well as prevent the rollback if any problem
> occurs. The begin and end transaction locks the table and wont allow to
> make selects till it is commited, i want where selects can work when
> delete is going on
> Raghu
> Hari Prasad wrote:
> > Answer for you questions:-
> >
> > 1. Disable the foreign key if you can do the house keeping after shutdown
> > the application [ See Alter table command]
> >
> > 2. No you can not avoid to log the transaction. The easy way is shrink the
> > transaction log fter delete [See DBCC SHRINKFILE]
> >
> > 3. That depends up the way you handle the transaction.. If its a single
> > delete statement inside the procedure and if you kill the job;
> > then automatically every thing pertaning to that delete will be rolled back
> >
> > Thanks
> > Hari
> > SQL Server MVP
> >
> >
> >
> >
> > "raghu" <raghu.burju@.gmail.com> wrote in message
> > news:1154641875.483366.120510@.75g2000cwc.googlegroups.com...
> > > we have problem with SQL Server 2000 SP3 / Windows 2003 EE
> > > we have 10 huge tables, I have a procedure which deletes data from
> > > these tables each day.
> > >
> > > 1. The deletes are very slow, it takes 20 min to delete 400,000
> > > records. It does use index when it deletes, i have seen the plan
> > >
> > > 2. i am running the database in simple mode but still the transaction
> > > log grows bigger and bigger during the delete process. I have used
> > > checkpoint after every table delete but it didnt help. is there a way
> > > we can avoid writing to transaction log so that i can solve this
> > > problem and improve the delete performance too
> > >
> > > 3. If i stop the job then everything gets rolled back that is been done
> > > by procedure. does it not commit table by table within the procedure?
> > > is it waiting for the procedure to finish before it commits?
> > >
> > > Can any one please help me ASAP
> > >
> > > Thanks
> > > Raghu
> > >

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.

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

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 ?

Friday, March 30, 2012

Problem With Login Null

Problem With Login null

Monday, March 26, 2012

Problem with installing SQL Server 2000

Problem with installing SQL Server

problem with installation of sqlserver 2000

problem with installation of RDA...

Problem with installation

Problem with Install of MSSQL 2005 Standard x64 on two node cluster

Friday, March 23, 2012

problem with insert into in scheduled job pleas help ASAP

Tuesday, March 20, 2012

Problem with Form Authentication Example

Problem with Forecasting with Excel 2007 DM Add-in using drill-through data from SSAS 2005!

Problem with Forecasting with Excel 2007 DM Add-in using drill-through data from SSAS 2005!

Problem with Forecasting with Excel 2007 DM Add-in using drill-through data from SSAS 2005!

Friday, March 9, 2012

Problem with DTS

Wednesday, March 7, 2012

Problem with delete, lock and transaction log

Saturday, February 25, 2012

Problem with delete, lock and transaction log

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

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

db datatypes

Blog Archive

About Me