MDAC Component Checker

I am on a win 2003 server and have run the component
checker and found 2 errors. The files obdcbcp.dll and
sqlsrv32.dll have mismatch errors. There errors say
expecting version 2000.85.1022.0; but the problem is that
I have 2000.85.1025.0
How can I fix this?
Thanks in advance,
Stewart
It sounds like you have installed MS04-003 to thsi system. The sqlsrv32.dll
and odbcbcp.dll from that patch are version 2000.85.1025.0.
Rand
This posting is provided "as is" with no warranties and confers no rights.
|||Stewart,
I have exactly same problem, what did you do to fix it?
Thanks
Regards
Kasba

MDAC Component Checker

I am on a win 2003 server and have run the component
checker and found 2 errors. The files obdcbcp.dll and
sqlsrv32.dll have mismatch errors. There errors say
expecting version 2000.85.1022.0; but the problem is that
I have 2000.85.1025.0
How can I fix this?
Thanks in advance,
StewartIt sounds like you have installed MS04-003 to thsi system. The sqlsrv32.dll
and odbcbcp.dll from that patch are version 2000.85.1025.0.
Rand
This posting is provided "as is" with no warranties and confers no rights.|||Stewart,
I have exactly same problem, what did you do to fix it?
Thanks
Regards
Kasba
vkasba
---
Posted via http://www.mcse.ms
---
View this thread: http://www.mcse.ms/message744871.html

MCP Tests Off MCDBA CD Have Script Errors!

I decided to become MCDBA certified and bought a book (70-228) that
will help me study for the first test. I pop in one of the CD's it
came with and install the test questions. When I launch the program I
get this: http://img154.imageshack.us/img154/7...pterror2zm.jpg
Okay, I click yes, and it loads the program. I then click start test
and I get another one of those messages. I click ok and then I get a
blank screen. I figure maybe it has something to do with the fact that
I have Firefox as my default browser, so I set IE as my default browser
and have the same problem. I tried lowering the security settings all
the way with no luck as well as making sure anything related to scripts
under the advanced tab in IE settings is checked or allowed to run. I
reboot, still nothing. I install it on my laptop with XP SP2 as well,
same thing.
Has anyone run across this problem before? Are these tests not
compatible with XP SP2? I've already emailed Microsoft about it, but
I'm pretty sure I'll be certified before I get a response. Being able
to use these tests is what lead me to purchase the book in the first
place.
Edit-My friend bought the same book earlier in the year and I had him
try to install it on his XP laptop and he has the same problem.
*Bump
|||Turns out there is a patch for the program. Apparently a security fix
in SP2 breaks the program. http://support.microsoft.com/kb/885674/en-us

MCP Tests Off MCDBA CD Have Script Errors!

I decided to become MCDBA certified and bought a book (70-228) that
will help me study for the first test. I pop in one of the CD's it
came with and install the test questions. When I launch the program I
get this: http://img154.imageshack.us/img154/...ipterror2zm.jpg
Okay, I click yes, and it loads the program. I then click start test
and I get another one of those messages. I click ok and then I get a
blank screen. I figure maybe it has something to do with the fact that
I have Firefox as my default browser, so I set IE as my default browser
and have the same problem. I tried lowering the security settings all
the way with no luck as well as making sure anything related to scripts
under the advanced tab in IE settings is checked or allowed to run. I
reboot, still nothing. I install it on my laptop with XP SP2 as well,
same thing.
Has anyone run across this problem before? Are these tests not
compatible with XP SP2? I've already emailed Microsoft about it, but
I'm pretty sure I'll be certified before I get a response. Being able
to use these tests is what lead me to purchase the book in the first
place.
Edit-My friend bought the same book earlier in the year and I had him
try to install it on his XP laptop and he has the same problem.*Bump|||Turns out there is a patch for the program. Apparently a security fix
in SP2 breaks the program. http://support.microsoft.com/kb/885674/en-us

MCP Tests Off MCDBA CD Have Script Errors!

I decided to become MCDBA certified and bought a book (70-228) that
will help me study for the first test. I pop in one of the CD's it
came with and install the test questions. When I launch the program I
get this: http://img154.imageshack.us/img154/7994/scripterror2zm.jpg
Okay, I click yes, and it loads the program. I then click start test
and I get another one of those messages. I click ok and then I get a
blank screen. I figure maybe it has something to do with the fact that
I have Firefox as my default browser, so I set IE as my default browser
and have the same problem. I tried lowering the security settings all
the way with no luck as well as making sure anything related to scripts
under the advanced tab in IE settings is checked or allowed to run. I
reboot, still nothing. I install it on my laptop with XP SP2 as well,
same thing.
Has anyone run across this problem before? Are these tests not
compatible with XP SP2? I've already emailed Microsoft about it, but
I'm pretty sure I'll be certified before I get a response. Being able
to use these tests is what lead me to purchase the book in the first
place.
Edit-My friend bought the same book earlier in the year and I had him
try to install it on his XP laptop and he has the same problem.*Bump|||Turns out there is a patch for the program. Apparently a security fix
in SP2 breaks the program. http://support.microsoft.com/kb/885674/en-us

Maybe this explains the issue I am finding with SQLMail

http://support.microsoft.com/default.aspx?scid=3Dkb;EN-US;313969
I don't get those errors from SQL Server. I get an error from Microsoft = Outlook 2003 that 'the folders cannot be created' if I allow SQL Server = Agent to start at boot in Windows 2000 SP3 and then try to open = Microsoft Outlook 2003. We have to use the same profile in SQL Mail as = we use in Microsoft Outlook 2003 because if we don't the SQL Mail will = never be sent. Therefore SQL Mail and Microsoft Outlook 2003 are both = using the same pst.
Hmmm...
If SQL Server Agent starts at boot ( a little problem here) then = Microsoft Outlook 2003 will not start. So don't allow SQL Server Agent = to start at boot and use a different profile for SQL Mail then I use to = start Microsoft Outlook 2003. Then SQL Mail will not be able to send = the mail until I close down Microsoft Outlook 2003 in my main profile = and open it in the profile I have SQL Mail set to. But of course I also = have to close down SQL Server Agent to do this. Man what a humdinger.
-- George Hester
__________________________________Try xp_smtp_sendmail from www.sqldev.net.
It works and is very stable. It is not a drop-in replacement, but it can do
most of the functions of SQLMail with a little extra work on your part.
--
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
"George Hester" <hesterloli@.hotmail.com> wrote in message
news:u$zN$SS4DHA.2332@.TK2MSFTNGP10.phx.gbl...
http://support.microsoft.com/default.aspx?scid=kb;EN-US;313969
I don't get those errors from SQL Server. I get an error from Microsoft
Outlook 2003 that 'the folders cannot be created' if I allow SQL Server
Agent to start at boot in Windows 2000 SP3 and then try to open Microsoft
Outlook 2003. We have to use the same profile in SQL Mail as we use in
Microsoft Outlook 2003 because if we don't the SQL Mail will never be sent.
Therefore SQL Mail and Microsoft Outlook 2003 are both using the same pst.
Hmmm...
If SQL Server Agent starts at boot ( a little problem here) then Microsoft
Outlook 2003 will not start. So don't allow SQL Server Agent to start at
boot and use a different profile for SQL Mail then I use to start Microsoft
Outlook 2003. Then SQL Mail will not be able to send the mail until I close
down Microsoft Outlook 2003 in my main profile and open it in the profile I
have SQL Mail set to. But of course I also have to close down SQL Server
Agent to do this. Man what a humdinger.
--
George Hester
__________________________________|||I had similar problems with OutlookXP & it not being able to send mail
messages unless the pst file was open. I solved this by installing Outlook
2000 on the Server, which I believe SQL Mail was originally designed for.
Since then it was worked perfectly...
Cheers,
James Goodman MCSE, MCDBA
http://www.angelfire.com/sports/f1pictures|||Hi Geoff. Oh I have that and it works great. But my issue still =exists.
-- George Hester
__________________________________
"Geoff N. Hiten" <SRDBA@.Careerbuilder.com> wrote in message =news:#R5NxDT4DHA.1504@.TK2MSFTNGP12.phx.gbl...
> Try xp_smtp_sendmail from www.sqldev.net.
> > It works and is very stable. It is not a drop-in replacement, but it =can do
> most of the functions of SQLMail with a little extra work on your =part.
> > -- > Geoff N. Hiten
> Microsoft SQL Server MVP
> Senior Database Administrator
> Careerbuilder.com
> > > > > "George Hester" <hesterloli@.hotmail.com> wrote in message
> news:u$zN$SS4DHA.2332@.TK2MSFTNGP10.phx.gbl...
> http://support.microsoft.com/default.aspx?scid=3Dkb;EN-US;313969
> > I don't get those errors from SQL Server. I get an error from =Microsoft
> Outlook 2003 that 'the folders cannot be created' if I allow SQL =Server
> Agent to start at boot in Windows 2000 SP3 and then try to open =Microsoft
> Outlook 2003. We have to use the same profile in SQL Mail as we use =in
> Microsoft Outlook 2003 because if we don't the SQL Mail will never be =sent.
> Therefore SQL Mail and Microsoft Outlook 2003 are both using the same =pst.
> > Hmmm...
> > If SQL Server Agent starts at boot ( a little problem here) then =Microsoft
> Outlook 2003 will not start. So don't allow SQL Server Agent to start =at
> boot and use a different profile for SQL Mail then I use to start =Microsoft
> Outlook 2003. Then SQL Mail will not be able to send the mail until I =close
> down Microsoft Outlook 2003 in my main profile and open it in the =profile I
> have SQL Mail set to. But of course I also have to close down SQL =Server
> Agent to do this. Man what a humdinger.
> > -- > George Hester
> __________________________________
> >|||Yes James. That is what I am seeing too.
-- George Hester
__________________________________
"James Goodman" <j a m e s@.norton-associates.co.u k> wrote in message =news:buqp6h$ppe$1@.hercules.btinternet.com...
> I had similar problems with OutlookXP & it not being able to send mail
> messages unless the pst file was open. I solved this by installing =Outlook
> 2000 on the Server, which I believe SQL Mail was originally designed =for.
> Since then it was worked perfectly...
> > > > -- > Cheers,
> > James Goodman MCSE, MCDBA
> http://www.angelfire.com/sports/f1pictures
> >

Maybe this explains the issue I am finding with SQLMail

http://support.microsoft.com/defaul...kb;EN-US;313969
I don't get those errors from SQL Server. I get an error from Microsoft =
Outlook 2003 that 'the folders cannot be created' if I allow SQL Server =
Agent to start at boot in Windows 2000 SP3 and then try to open =
Microsoft Outlook 2003. We have to use the same profile in SQL Mail as =
we use in Microsoft Outlook 2003 because if we don't the SQL Mail will =
never be sent. Therefore SQL Mail and Microsoft Outlook 2003 are both =
using the same pst.
Hmmm...
If SQL Server Agent starts at boot ( a little problem here) then =
Microsoft Outlook 2003 will not start. So don't allow SQL Server Agent =
to start at boot and use a different profile for SQL Mail then I use to =
start Microsoft Outlook 2003. Then SQL Mail will not be able to send =
the mail until I close down Microsoft Outlook 2003 in my main profile =
and open it in the profile I have SQL Mail set to. But of course I also =
have to close down SQL Server Agent to do this. Man what a humdinger.
--=20
George Hester
__________________________________Try xp_smtp_sendmail from www.sqldev.net.
It works and is very stable. It is not a drop-in replacement, but it can do
most of the functions of SQLMail with a little extra work on your part.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
"George Hester" <hesterloli@.hotmail.com> wrote in message
news:u$zN$SS4DHA.2332@.TK2MSFTNGP10.phx.gbl...
http://support.microsoft.com/defaul...kb;EN-US;313969
I don't get those errors from SQL Server. I get an error from Microsoft
Outlook 2003 that 'the folders cannot be created' if I allow SQL Server
Agent to start at boot in Windows 2000 SP3 and then try to open Microsoft
Outlook 2003. We have to use the same profile in SQL Mail as we use in
Microsoft Outlook 2003 because if we don't the SQL Mail will never be sent.
Therefore SQL Mail and Microsoft Outlook 2003 are both using the same pst.
Hmmm...
If SQL Server Agent starts at boot ( a little problem here) then Microsoft
Outlook 2003 will not start. So don't allow SQL Server Agent to start at
boot and use a different profile for SQL Mail then I use to start Microsoft
Outlook 2003. Then SQL Mail will not be able to send the mail until I close
down Microsoft Outlook 2003 in my main profile and open it in the profile I
have SQL Mail set to. But of course I also have to close down SQL Server
Agent to do this. Man what a humdinger.
George Hester
__________________________________|||I had similar problems with OutlookXP & it not being able to send mail
messages unless the pst file was open. I solved this by installing Outlook
2000 on the Server, which I believe SQL Mail was originally designed for.
Since then it was worked perfectly...
Cheers,
James Goodman MCSE, MCDBA
http://www.angelfire.com/sports/f1pictures|||Hi Geoff. Oh I have that and it works great. But my issue still =
exists.
--=20
George Hester
__________________________________
"Geoff N. Hiten" <SRDBA@.Careerbuilder.com> wrote in message =
news:#R5NxDT4DHA.1504@.TK2MSFTNGP12.phx.gbl...

quote:

---

> Try xp_smtp_sendmail from www.sqldev.net.
>=20
> It works and is very stable. It is not a drop-in replacement, but it =

---

can do

quote:

---

> most of the functions of SQLMail with a little extra work on your =

---

part.

quote:

---

>=20
> --=20
> Geoff N. Hiten
> Microsoft SQL Server MVP
> Senior Database Administrator
> Careerbuilder.com
>=20
>=20
>=20
>=20
> "George Hester" <hesterloli@.hotmail.com> wrote in message
> news:u$zN$SS4DHA.2332@.TK2MSFTNGP10.phx.gbl...
> http://support.microsoft.com/defaul...kb;EN-US;313969
>=20
> I don't get those errors from SQL Server. I get an error from =

---

Microsoft

quote:

---

> Outlook 2003 that 'the folders cannot be created' if I allow SQL =

---

Server

quote:

---

> Agent to start at boot in Windows 2000 SP3 and then try to open =

---

Microsoft

quote:

---

> Outlook 2003. We have to use the same profile in SQL Mail as we use =

---

in

quote:

---

> Microsoft Outlook 2003 because if we don't the SQL Mail will never be =

---

sent.

quote:

---

> Therefore SQL Mail and Microsoft Outlook 2003 are both using the same =

---

pst.

quote:

---

>=20
> Hmmm...
>=20
> If SQL Server Agent starts at boot ( a little problem here) then =

---

Microsoft

quote:

---

> Outlook 2003 will not start. So don't allow SQL Server Agent to start =

---

at

quote:

---

> boot and use a different profile for SQL Mail then I use to start =

---

Microsoft

quote:

---

> Outlook 2003. Then SQL Mail will not be able to send the mail until I =

---

close

quote:

---

> down Microsoft Outlook 2003 in my main profile and open it in the =

---

profile I

quote:

---

> have SQL Mail set to. But of course I also have to close down SQL =

---

Server

quote:

---

> Agent to do this. Man what a humdinger.
>=20
> --=20
> George Hester
> __________________________________
>=20
>

---

|||Yes James. That is what I am seeing too.
--=20
George Hester
__________________________________
"James Goodman" <j a m e s@.norton-associates.co.u k> wrote in message =
news:buqp6h$ppe$1@.hercules.btinternet.com...

quote:

---

> I had similar problems with OutlookXP & it not being able to send mail
> messages unless the pst file was open. I solved this by installing =

---

Outlook

quote:

---

> 2000 on the Server, which I believe SQL Mail was originally designed =

---

for.

quote:

---

> Since then it was worked perfectly...
>=20
>=20
>=20
> --=20
> Cheers,
>=20
> James Goodman MCSE, MCDBA
> http://www.angelfire.com/sports/f1pictures
>=20
>

---

MaximunErrorCount issue

Hi,

I need to launch a SSIS process that has several errors (the most common is insert records with a PK that already exists in the destination table). My process may continue to the end despite these errors, in order to see them in the log when the process has finished.

I have set "MaximunErrorCount" to 999999 , but the process stop the first time i attempt to write a duplaicate PK.

I have also set MaximunErrorCount of every Data flow taks to this value...

What's going wrong?

Thanks!

Hi Alberttoim,

I am not sure of this.

But there is a better solution, If you want to get unique rows finally in to your destination table:

- First output to a Staging Table whose structure is same as your Destination table and dedupe them.

Thanks

Subhash Subramanyam

|||

Hi Subhash,

The thing is the source table is huge, and doing this is so expensive... in addition to this i want to know how to manage errors since this is not the only error i can find in a future.

I have try to "omit error" but in this case the error is not recorded in the log.

I theory , if i set MaximumErrorCount to a high value the process should continue executing ,is'nt it? What is going worng?

|||Albertoim,
Have you read through this thread? http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1211340&SiteID=1|||

Yes, i have read it. I do a lookup before insert the record, the problem is that i am not using a for each bucle, i am treating a bunch of rows.. thats why the lookup transformation doesnt find any record with this PK because it actually doesnt already exists fisically in the database.

Anyway, i need to know how to manage errors, how to make the process continue executing in spite of errors.

|||You can redirect errors out of the OLE DB Destination component. That will allow you to redirect them (or even ignore if you want) without raising a package error.|||And a lookup would work if your destination is failing because of primary key violations. If you are expecting the lookup to refresh with each inserted record from the data flow, you can setup the lookup to not cache it's lookup results, which means that every time a new records gets inserted, the next record through the lookup could find it.|||

Thanks Phil,

I have been doing this to prove that the whole package works ok, but now i am trying to use the other solution because the flow is quite big and i have to redirect errors in so many places... the package becomes too confusing.

The question is, can't i allow the package continue executing when this error happens and record it in the log?

If i use an event handler, can i send to it any info (columns of the duplicate record for example)... when the event is triggered the task stop executing?

Thanks

|||

Phil, regarding your second solution...

Thats the situation: Source table has info that already exists in the destination... i have to update/add records in the destination deppending if the record already exists or not.

If i disable cache and in the source table two records have the same PK, in the destination , in the first round the record will be inserted, and in the second will be updated... no error but i cant detect what is happening. I need to detect these errors to advice the user to correct it, i can't touch the source table...

In addition to this, i think disabling cache of lookup transformations that manage a great amount of info will produce a low performance.. am i wrong?

I simply need to allow the process to support continue executing in spite of errors and record them on a log...

|||

Albertoim wrote:

Phil, regarding your second solution...

Thats the situation: Source table has info that already exists in the destination... i have to update/add records in the destination deppending if the record already exists or not.

If i disable cache and in the source table two records have the same PK, in the destination , the first round the record will be inserted, and in the second will be updated... no error but i cant detect what is happening. I need to detect these errors to advice the user to correct it, i can't touch the source table...

In addition to this, i think disabling cache of lookup transformations that manage a great amount of info will produce a low performance.. am i wrong?

I simply need to allow the process to support continue executing in spite of errors and record them on a log...

Why can't you redirect the errors as is the appropriate solution?|||I can do that, but i am trying to find the other way to do that because introducing a lot of redirections makes the flow so confusing (i have to introduce them in many places)... the question is if i can ignore errors, continue executing but record them on the log (i supposed MaximumErrorCount property is for that purpose).|||

Albertoim wrote:

I can do that, but i am trying to find the other way to do that because introducing a lot of redirections makes the flow so confusing (i have to introduce them in many places)... the question is if i can ignore errors, continue executing but record them on the log (i supposed MaximumErrorCount property is for that purpose).

It's the "record them on the log" that's causing you problems. You want to continue processing, yet capture the error rows, but do not want to redirect them. I fail to see how you can do this without redirecting the errors.

Do you want to know which rows were in error, or just the error message?|||

Phil,

The main problem i have is a cant let the proccess continue when the error happens... despite i set MaximumErrorCount value to 10000 the process stop.

Once i solve it i would see how to get the row that produce the error: maybe with a custom log, creating an event handler... whatever... but firstly i would like to solve the other issue regardless of knowing which row is duplicated... just see the error message in the log.

Thank youuu

|||Make sure that FailPackageOnFailure and FailParentOnFailure aren't set to TRUE for the data flow.|||

Both properties are set to False... any other hint?

Thanks you very much for your help Phil...

Edit: i've been doing tests in a crappy package and the same problem... execution stops when this specific error happens. MaximunErrorCount set to 100, FailPackageOnFailure = False and failParentOnFailure = False. I have seen the problem is not the whole package stops, its the Dataflow that contains the error what is sttoping, only it...

|||You should set the MaximumErrorNumber to zero of the parent task. It's better than setting a high value. I Hope it helps.sql

MAXERRORS in BCP Does'nt work

Hi,
I'm trying to use MAXERRORS option (-m switch) to force loading to continue
even though errors occur, but the load stop at the first error occur, all
batch is commited and no error is logged in error file (-e hint)
here is the commande I'm using :
exec master.dbo.xp_cmdshell 'bcp "DBName.dbo.TableName" in
"Path\FileName.tab" -m1000 -e"Path\ErrorFile" -T -E -n -q -S"ServerName"'
Is there any people successfuly use MAXERRORS option ?
Thanks for your helpMark (sauvemark@.yahoo.com) writes:
> I'm trying to use MAXERRORS option (-m switch) to force loading to
> continue even though errors occur, but the load stop at the first error
> occur, all batch is commited and no error is logged in error file (-e
> hint)
> here is the commande I'm using :
> exec master.dbo.xp_cmdshell 'bcp "DBName.dbo.TableName" in
> "Path\FileName.tab" -m1000 -e"Path\ErrorFile" -T -E -n -q -S"ServerName"'
> Is there any people successfuly use MAXERRORS option ?
Yes, I've used it successfully. But it depends on what sort of error you
get. What is the exact output you get?
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx|||> Yes, I've used it successfully
Glad to here this, I thought this a bug

> What is the exact output you get?
Error = [Microsoft][ODBC SQL Server Driver][SQL Server]Violation of PRIMARY
KEY constraint
I apreciate your help
"Erland Sommarskog" <esquel@.sommarskog.se> wrote in message
news:Xns97E969C5660BYazorman@.127.0.0.1...
> Mark (sauvemark@.yahoo.com) writes:
"Path\FileName.tab" -m1000 -e"Path\ErrorFile" -T -E -n -q -S"ServerName"'
> Yes, I've used it successfully. But it depends on what sort of error you
> get. What is the exact output you get?
>
> --
> Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
> Books Online for SQL Server 2005 at
> http://www.microsoft.com/technet/pr...oads/books.mspx
> Books Online for SQL Server 2000 at
> http://www.microsoft.com/sql/prodin...ions/books.mspx|||Mark (sauvemark@.yahoo.com) writes:
> Glad to here this, I thought this a bug
>
> Error = [Microsoft][ODBC SQL Server Driver][SQL Server]Violation of
> PRIMARY KEY constraint
OK, so the errors that MAXERRORS control are conversion errors within the
file. That is, you are supposed to provide a decimal value, but the
valiue BCP finds is not decimal, so it cannot convert.
This is a pure SQL error, and for a PK violation the standard rule
applies: the entire statement is rolled back. That is, the entire BCP.
Unless you set a batch size. Then only the batch(es) with the violating
key are dropped. (At least I believe that BCP will continue, but I
have not tested, and now the hour is late.)
Setting a batchsize of 1, would give you all rows that does not violate
the PK, but that is likely to be effecient. Better is probably to use
a staging table, and then clean up the data in SQL Server.
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx