MDAC2.71 Service Pack 1 Refresh: mdac_typ.exe ??

Hi all,
I run MDAC Component Check on my SQL Server 2000. None
of the versions of MDAC passed the tests. The closest one
is 2.7 SP1 (2.71.9030.9) with only One error on
msjtes40.dll file
msjtes40.dll,Error,Field 'FileVersion' mismatch:
Expect '4.00.2927.8' Got '4.00.5914.0',Microsoft Jet
Expression
Does this mean that I have to install 2.71 Service
Pack 1 Refresh: mdac_typ.exe ?
What files contain in this mdac_typ.exe? Would
installing this file help on Memory Leak?
Thank you sooooo much!!!
P.S.: I think I install 2.7 SP1 via Windows Update. I
didn't apply SQL Sever 2000 SP3 at all.
AnnieThat file almost always checks different, so don't worry.
normally if the version number is higher compared to the closest match it is
OK.
This normally happens because you installed some software with an newer DLL.
( I am assuming msjtes40.dll is installed by MS Office, since I always see
it being different at work.)
Tim S
"Annie" <piyomeme@.yahoo.com> wrote in message
news:05da01c34d8b$f0e63f00$a101280a@.phx.gbl...
> Hi all,
> I run MDAC Component Check on my SQL Server 2000. None
> of the versions of MDAC passed the tests. The closest one
> is 2.7 SP1 (2.71.9030.9) with only One error on
> msjtes40.dll file
> msjtes40.dll,Error,Field 'FileVersion' mismatch:
> Expect '4.00.2927.8' Got '4.00.5914.0',Microsoft Jet
> Expression
> Does this mean that I have to install 2.71 Service
> Pack 1 Refresh: mdac_typ.exe ?
> What files contain in this mdac_typ.exe? Would
> installing this file help on Memory Leak?
> Thank you sooooo much!!!
> P.S.: I think I install 2.7 SP1 via Windows Update. I
> didn't apply SQL Sever 2000 SP3 at all.
> Annie
>|||Thank you, Tim.
I don't have MS Office installed on Server, but it could
be something else.
That was helpful. Thank you~
Annie
>--Original Message--
>That file almost always checks different, so don't worry.
>normally if the version number is higher compared to the
closest match it is
>OK.
>This normally happens because you installed some software
with an newer DLL.
>( I am assuming msjtes40.dll is installed by MS Office,
since I always see
>it being different at work.)
>Tim S
>
>"Annie" <piyomeme@.yahoo.com> wrote in message
>news:05da01c34d8b$f0e63f00$a101280a@.phx.gbl...
>> Hi all,
>> I run MDAC Component Check on my SQL Server 2000.
None
>> of the versions of MDAC passed the tests. The closest
one
>> is 2.7 SP1 (2.71.9030.9) with only One error on
>> msjtes40.dll file
>> msjtes40.dll,Error,Field 'FileVersion' mismatch:
>> Expect '4.00.2927.8' Got '4.00.5914.0',Microsoft Jet
>> Expression
>> Does this mean that I have to install 2.71 Service
>> Pack 1 Refresh: mdac_typ.exe ?
>> What files contain in this mdac_typ.exe? Would
>> installing this file help on Memory Leak?
>> Thank you sooooo much!!!
>> P.S.: I think I install 2.7 SP1 via Windows Update. I
>> didn't apply SQL Sever 2000 SP3 at all.
>> Annie
>
>.
>

MDAC Upgrade

Please advice.
I have a WIN 2K SP3 ADV Server that runs SQL 2K with MDAC
2.6 SP1.
I would like to upgrade this to MDAC 2.7. Can I simply
run the MDAC 2.7 update or what is the Microsoft way to
do this.
Help Appreciated.SQL Server 2000 Service Pack 3a comes with MDAC 2.7 Service Pack 1a, so the
best way is to install the SQL Server Service Pack.
--
Jacco Schalkwijk
SQL Server MVP
"Olutimi" <anonymous@.discussions.microsoft.com> wrote in message
news:e9c601c3f096$369ceb40$a501280a@.phx.gbl...
> Please advice.
> I have a WIN 2K SP3 ADV Server that runs SQL 2K with MDAC
> 2.6 SP1.
> I would like to upgrade this to MDAC 2.7. Can I simply
> run the MDAC 2.7 update or what is the Microsoft way to
> do this.
> Help Appreciated.|||MDAC 2.8 is also availabe for download from MS site.
Regards
Chip
>--Original Message--
>SQL Server 2000 Service Pack 3a comes with MDAC 2.7
Service Pack 1a, so the
>best way is to install the SQL Server Service Pack.
>--
>Jacco Schalkwijk
>SQL Server MVP
>
>"Olutimi" <anonymous@.discussions.microsoft.com> wrote in
message
>news:e9c601c3f096$369ceb40$a501280a@.phx.gbl...
>> Please advice.
>> I have a WIN 2K SP3 ADV Server that runs SQL 2K with
MDAC
>> 2.6 SP1.
>> I would like to upgrade this to MDAC 2.7. Can I simply
>> run the MDAC 2.7 update or what is the Microsoft way to
>> do this.
>> Help Appreciated.
>
>.
>|||Thanks for your reply.
My configuration is WIN 2k SP3 plus SQL 2K Client tools
with MDAC 2.6 SP1. What is the best course of action to
upgrade to MDAC 2.7
Help Appreciated.
>--Original Message--
>SQL Server 2000 Service Pack 3a comes with MDAC 2.7
Service Pack 1a, so the
>best way is to install the SQL Server Service Pack.
>--
>Jacco Schalkwijk
>SQL Server MVP
>
>"Olutimi" <anonymous@.discussions.microsoft.com> wrote in
message
>news:e9c601c3f096$369ceb40$a501280a@.phx.gbl...
>> Please advice.
>> I have a WIN 2K SP3 ADV Server that runs SQL 2K with
MDAC
>> 2.6 SP1.
>> I would like to upgrade this to MDAC 2.7. Can I simply
>> run the MDAC 2.7 update or what is the Microsoft way to
>> do this.
>> Help Appreciated.
>
>.
>|||Olutimi,
We run Win 2K SP4 and SQL2000 SP2 +. Remember to make sure that the server
MDAC is at least the same level as the client or higher. MDAC can introduce
changes that cause things like DTS, run from the client, to fail.
We upgraded the server to MDAC 2.7SP1A and then the clients. A simple
download and then run the DASETUP.
HTH
Chris Wood
Alberta Department of Energy
CANADA
"Olutimi" <anonymous@.discussions.microsoft.com> wrote in message
news:e17301c3f0b9$9ec87860$a301280a@.phx.gbl...
> Thanks for your reply.
> My configuration is WIN 2k SP3 plus SQL 2K Client tools
> with MDAC 2.6 SP1. What is the best course of action to
> upgrade to MDAC 2.7
> Help Appreciated.
>
> >--Original Message--
> >SQL Server 2000 Service Pack 3a comes with MDAC 2.7
> Service Pack 1a, so the
> >best way is to install the SQL Server Service Pack.
> >
> >--
> >Jacco Schalkwijk
> >SQL Server MVP
> >
> >
> >"Olutimi" <anonymous@.discussions.microsoft.com> wrote in
> message
> >news:e9c601c3f096$369ceb40$a501280a@.phx.gbl...
> >> Please advice.
> >>
> >> I have a WIN 2K SP3 ADV Server that runs SQL 2K with
> MDAC
> >> 2.6 SP1.
> >> I would like to upgrade this to MDAC 2.7. Can I simply
> >> run the MDAC 2.7 update or what is the Microsoft way to
> >> do this.
> >>
> >> Help Appreciated.
> >
> >
> >.
> >

MDAC Upgrade

Please advice.
I have a WIN 2K SP3 ADV Server that runs SQL 2K with MDAC
2.6 SP1.
I would like to upgrade this to MDAC 2.7. Can I simply
run the MDAC 2.7 update or what is the Microsoft way to
do this.
Help Appreciated.SQL Server 2000 Service Pack 3a comes with MDAC 2.7 Service Pack 1a, so the
best way is to install the SQL Server Service Pack.
Jacco Schalkwijk
SQL Server MVP
"Olutimi" <anonymous@.discussions.microsoft.com> wrote in message
news:e9c601c3f096$369ceb40$a501280a@.phx.gbl...
> Please advice.
> I have a WIN 2K SP3 ADV Server that runs SQL 2K with MDAC
> 2.6 SP1.
> I would like to upgrade this to MDAC 2.7. Can I simply
> run the MDAC 2.7 update or what is the Microsoft way to
> do this.
> Help Appreciated.|||MDAC 2.8 is also availabe for download from MS site.
Regards
Chip
>--Original Message--
>SQL Server 2000 Service Pack 3a comes with MDAC 2.7
Service Pack 1a, so the
>best way is to install the SQL Server Service Pack.
>--
>Jacco Schalkwijk
>SQL Server MVP
>
>"Olutimi" <anonymous@.discussions.microsoft.com> wrote in
message
>news:e9c601c3f096$369ceb40$a501280a@.phx.gbl...
MDAC
>
>.
>|||Thanks for your reply.
My configuration is WIN 2k SP3 plus SQL 2K Client tools
with MDAC 2.6 SP1. What is the best course of action to
upgrade to MDAC 2.7
Help Appreciated.

>--Original Message--
>SQL Server 2000 Service Pack 3a comes with MDAC 2.7
Service Pack 1a, so the
>best way is to install the SQL Server Service Pack.
>--
>Jacco Schalkwijk
>SQL Server MVP
>
>"Olutimi" <anonymous@.discussions.microsoft.com> wrote in
message
>news:e9c601c3f096$369ceb40$a501280a@.phx.gbl...
MDAC
>
>.
>|||Olutimi,
We run Win 2K SP4 and SQL2000 SP2 +. Remember to make sure that the server
MDAC is at least the same level as the client or higher. MDAC can introduce
changes that cause things like DTS, run from the client, to fail.
We upgraded the server to MDAC 2.7SP1A and then the clients. A simple
download and then run the DASETUP.
HTH
Chris Wood
Alberta Department of Energy
CANADA
"Olutimi" <anonymous@.discussions.microsoft.com> wrote in message
news:e17301c3f0b9$9ec87860$a301280a@.phx.gbl...
> Thanks for your reply.
> My configuration is WIN 2k SP3 plus SQL 2K Client tools
> with MDAC 2.6 SP1. What is the best course of action to
> upgrade to MDAC 2.7
> Help Appreciated.
>
> Service Pack 1a, so the
> message
> MDAC

MDAC Madness

Greetings,
On my Windows 2000 SP4 Server, the MDAC Component Checker Version 2.0
reports that MDAC 2.8 SP1 on Windows XP SP2 is installed.
MDAC 2.8 SP1 on Windows XP SP2 ... but this is a Windows 2000 SP4
server? Very confusing. Will someone help me get my head around this?
Further, when I set the Component Checker to perform analysis against a
selected version, and target MDAC 2.8 SP1 on Windows XP SP2, only one
inconsistency is reported -- msxml3.dll is at version 8.70.1104.0, but
8.50.2162.0 is expected. Is this also anything to be concerned about?
Thanks,
Tim ==Tim,
You don't mention the level of SQL2000 that you are running? Is it SP4?
Chris Wood
<tim@.tcsys.com> wrote in message
news:1123081469.455549.23850@.f14g2000cwb.googlegroups.com...
> Greetings,
> On my Windows 2000 SP4 Server, the MDAC Component Checker Version 2.0
> reports that MDAC 2.8 SP1 on Windows XP SP2 is installed.
> MDAC 2.8 SP1 on Windows XP SP2 ... but this is a Windows 2000 SP4
> server? Very confusing. Will someone help me get my head around this?
> Further, when I set the Component Checker to perform analysis against a
> selected version, and target MDAC 2.8 SP1 on Windows XP SP2, only one
> inconsistency is reported -- msxml3.dll is at version 8.70.1104.0, but
> 8.50.2162.0 is expected. Is this also anything to be concerned about?
> Thanks,
> Tim ==
>|||Thanks for replying, Chris.
I know almost nothing about SQL server, but, that being said, I'm an
otherwise competent MS net admin.
This particular box has an MSDE engine installed by an not-profit
financial application. The management of this app is hands-off, under
the control of the vendor.
The thing is, the same server is also our Backup Exec box. Backup Exec
was configured to use the same SQL instance as the financial app.
That's not unusual; the use of an existing SQL or MSDE instance on the
same box is the default installation setting for Backup Exec.
But lately we've been having some trouble with Backup Exec. And
wouldn't you know it? Some mismatched MDAC files turned up in the
course of investigation, and now Veritas/Symantec technical support is
insisting upon having the information in the OP before proceeding
further with the case.
So to answer your question: Knowing that this is an MSDE installation,
I was able to Google up this command line...
osql.exe -U administrator -Q "USE master SELECT @.@.version" -p
...but I'm prompted for a password which I do not believe that I
posses.
I've tried running it with the local administrator account and the
domain administrator account. No luck.
Believe me, your continued assistance is appreciated!|||Tim,
If you are using an Windows administrator id I think that use can use the -E
rather than -U parameter. This should not ask for a password.
From the MSDE SP4 readme
1.5 Verify the Version of Microsoft Data Access Components
MSDE 2000 SP4 setup determines whether to upgrade an installed version of
Microsoft Data Access Components (MDAC) to MDAC 2.8 SP1:
a.. Computers that run Windows 2000 are upgraded to MDAC 2.8 SP1.
b.. Computers that run Windows XP or Windows Server 2003 are not upgraded
to MDAC 2.8 SP1. If your system requires any of the fixes included in MDAC
2.8 SP1, upgrade your system to Windows XP SP2 or Windows Server 2003 SP1 to
obtain MDAC 2.8 SP2.
c.. MDAC 2.8 SP1 is not installed on computers that already have installed
an equal or later version of MDAC.
d..
e.. 1.6 Identify the Current Version of MSDE 2000
Before running Setup, identify the version of the MSDE 2000 instance that
is being upgraded. If the version of MSDE 2000 is already at or greater than
SP4, you do not need to install SP4.
To identify the installed version of MSDE 2000:
1.. Execute one of the following queries against an instance of the
database engine by using isql, osql, or Query Analyzer.
a.. SELECT SERVERPROPERTY('ProductLevel')
b.. SELECT @.@.VERSION
c.. SELECT SERVERPROPERTY('ProductVersion')
2.. Find out your version of MSDE by means of the following table. SQL
Server 2000 Version and Level @.@.VERSION Product Level
SQL Server 2000 Original Release 8.00.194 RTM
Desktop Engine SP1 8.00.384 SP1
Desktop Engine SP2 8.00.534 SP2
Desktop Engine SP3, SP3a, or MSDE 2000 Release A. 8.00.760 SP3
MSDE 2000 SP4 8.00.2039 SP4
Chris
<tim@.tcsys.com> wrote in message
news:1123100308.823774.310400@.g49g2000cwa.googlegroups.com...
> Thanks for replying, Chris.
> I know almost nothing about SQL server, but, that being said, I'm an
> otherwise competent MS net admin.
> This particular box has an MSDE engine installed by an not-profit
> financial application. The management of this app is hands-off, under
> the control of the vendor.
> The thing is, the same server is also our Backup Exec box. Backup Exec
> was configured to use the same SQL instance as the financial app.
> That's not unusual; the use of an existing SQL or MSDE instance on the
> same box is the default installation setting for Backup Exec.
> But lately we've been having some trouble with Backup Exec. And
> wouldn't you know it? Some mismatched MDAC files turned up in the
> course of investigation, and now Veritas/Symantec technical support is
> insisting upon having the information in the OP before proceeding
> further with the case.
> So to answer your question: Knowing that this is an MSDE installation,
> I was able to Google up this command line...
> osql.exe -U administrator -Q "USE master SELECT @.@.version" -p
> ...but I'm prompted for a password which I do not believe that I
> posses.
> I've tried running it with the local administrator account and the
> domain administrator account. No luck.
> Believe me, your continued assistance is appreciated!
>|||Tim,
Did you find out the build of MSDE?
Chris
<tim@.tcsys.com> wrote in message
news:1123100308.823774.310400@.g49g2000cwa.googlegroups.com...
> Thanks for replying, Chris.
> I know almost nothing about SQL server, but, that being said, I'm an
> otherwise competent MS net admin.
> This particular box has an MSDE engine installed by an not-profit
> financial application. The management of this app is hands-off, under
> the control of the vendor.
> The thing is, the same server is also our Backup Exec box. Backup Exec
> was configured to use the same SQL instance as the financial app.
> That's not unusual; the use of an existing SQL or MSDE instance on the
> same box is the default installation setting for Backup Exec.
> But lately we've been having some trouble with Backup Exec. And
> wouldn't you know it? Some mismatched MDAC files turned up in the
> course of investigation, and now Veritas/Symantec technical support is
> insisting upon having the information in the OP before proceeding
> further with the case.
> So to answer your question: Knowing that this is an MSDE installation,
> I was able to Google up this command line...
> osql.exe -U administrator -Q "USE master SELECT @.@.version" -p
> ...but I'm prompted for a password which I do not believe that I
> posses.
> I've tried running it with the local administrator account and the
> domain administrator account. No luck.
> Believe me, your continued assistance is appreciated!
>|||Chris,
This thread speaks to a problem I created on our SBS 2003 with MDAC now
having 5 mismatched file versions and a crippled Veritas BackupExec 10, not
to mention the other problems this MDAC issue is causing. I lost RAS
yesterday (related? who knows!) and I can no longer access our Exchange
Server through the Web access for Outlook 2003.
I really messed things up and need help to get the correct MDAC files
restored. I used the cc.exe. Component Checker from MS to test the installed
version against the expected file versions.
Veritas/Symantec will not proceed with assistance until I get MDAC fixed.
HELP!
Chris
"Chris Wood" wrote:

> Tim,
> If you are using an Windows administrator id I think that use can use the
-E
> rather than -U parameter. This should not ask for a password.
> From the MSDE SP4 readme
> 1.5 Verify the Version of Microsoft Data Access Components
> MSDE 2000 SP4 setup determines whether to upgrade an installed version of
> Microsoft Data Access Components (MDAC) to MDAC 2.8 SP1:
> a.. Computers that run Windows 2000 are upgraded to MDAC 2.8 SP1.
>
> b.. Computers that run Windows XP or Windows Server 2003 are not upgrade
d
> to MDAC 2.8 SP1. If your system requires any of the fixes included in MDAC
> 2.8 SP1, upgrade your system to Windows XP SP2 or Windows Server 2003 SP1
to
> obtain MDAC 2.8 SP2.
>
> c.. MDAC 2.8 SP1 is not installed on computers that already have install
ed
> an equal or later version of MDAC.
> d..
> e.. 1.6 Identify the Current Version of MSDE 2000
> Before running Setup, identify the version of the MSDE 2000 instance tha
t
> is being upgraded. If the version of MSDE 2000 is already at or greater th
an
> SP4, you do not need to install SP4.
> To identify the installed version of MSDE 2000:
> 1.. Execute one of the following queries against an instance of the
> database engine by using isql, osql, or Query Analyzer.
> a.. SELECT SERVERPROPERTY('ProductLevel')
>
> b.. SELECT @.@.VERSION
>
> c.. SELECT SERVERPROPERTY('ProductVersion')
> 2.. Find out your version of MSDE by means of the following table. SQL
> Server 2000 Version and Level @.@.VERSION Product Level
> SQL Server 2000 Original Release 8.00.194 RTM
> Desktop Engine SP1 8.00.384 SP1
> Desktop Engine SP2 8.00.534 SP2
> Desktop Engine SP3, SP3a, or MSDE 2000 Release A. 8.00.760 SP3
> MSDE 2000 SP4 8.00.2039 SP4
> Chris
> <tim@.tcsys.com> wrote in message
> news:1123100308.823774.310400@.g49g2000cwa.googlegroups.com...
>
>|||Is this SBS 2003 SP1? It looks like it includes MSDE2000 SP4 unless you have
the Premium edition that includes full blown SQL2000 SP4.
If this is SP1 then my previous note about MDAC applies.
Chris
"Chris Williams" <Chris Williams@.discussions.microsoft.com> wrote in message
news:BE841E75-8D2C-4EE1-B2E7-D4BE9EAD417E@.microsoft.com...[vbcol=seagreen]
> Chris,
> This thread speaks to a problem I created on our SBS 2003 with MDAC now
> having 5 mismatched file versions and a crippled Veritas BackupExec 10,
> not
> to mention the other problems this MDAC issue is causing. I lost RAS
> yesterday (related? who knows!) and I can no longer access our Exchange
> Server through the Web access for Outlook 2003.
> I really messed things up and need help to get the correct MDAC files
> restored. I used the cc.exe. Component Checker from MS to test the
> installed
> version against the expected file versions.
> Veritas/Symantec will not proceed with assistance until I get MDAC fixed.
> HELP!
> Chris
> "Chris Wood" wrote:
>|||Chris (Wood),
Are you asking about my server issue or the one from Tim? We are not at SP1
for our SBS 2003 yet because the server would not allow Windows Update to
properly run much less update it's components. I have all 5 of the Microsoft
specified downloads for SBS 2003 SP1 downloaded as per an article I read on
the SBS MS site. I was planning to do some more reading on this before tryin
g
to apply them and was hoping that would fix my browser issue that kept it
from running Windows Update properly.
Frankly this server was a walking abortion from the get go with the company
that originally installed it doing a very poor job. I band-aided everything
I
could safely do to even get it to run without daily unexpected re-boots. I
know that was putting off the inevidable, but the company needed to get back
to daily operations after 30+ days of dissruption caused by this "other"
outside computer company. We have since severed ties with them.
Anyway, we are running with only the original installation of SBS 2003, some
security patches in place and not much else. I also wanted to update the
exchange server to SP1 (this is part of the process I hope to complete once
I
fix my MDAC issues).
Since I last posted, I tossed in my towel on this and have a engineer coming
in this morning from a group that has been trying to get our business for
some time now. I hope he will know what to do to fix this MDAC problem.
But any input you can offer will be good. Also, we are running the standard
version of SBS 2003, not the premium, thus the SQL is only that MSDE2000,
which I am growing to hate by the minute. I would have ponyed up the money
for the premium if I where actually working here when they were forced to ge
t
a new server back in December 2004. (The old server was a Netware server tha
t
this same outside computer company supported, broke and then said it's bette
r
to scrap that server and replace it with the SBS 2003 they installed - This
Machine. We all know how well a job they did on that too!)
Sorry to rant. It's been a long week and I am stressed out.
Chris W.
"Chris Wood" wrote:

> Is this SBS 2003 SP1? It looks like it includes MSDE2000 SP4 unless you ha
ve
> the Premium edition that includes full blown SQL2000 SP4.
> If this is SP1 then my previous note about MDAC applies.
> Chris
> "Chris Williams" <Chris Williams@.discussions.microsoft.com> wrote in messa
ge
> news:BE841E75-8D2C-4EE1-B2E7-D4BE9EAD417E@.microsoft.com...
>
>

MDAC Madness

Greetings,
On my Windows 2000 SP4 Server, the MDAC Component Checker Version 2.0
reports that MDAC 2.8 SP1 on Windows XP SP2 is installed.
MDAC 2.8 SP1 on Windows XP SP2 ... but this is a Windows 2000 SP4
server? Very confusing. Will someone help me get my head around this?
Further, when I set the Component Checker to perform analysis against a
selected version, and target MDAC 2.8 SP1 on Windows XP SP2, only one
inconsistency is reported -- msxml3.dll is at version 8.70.1104.0, but
8.50.2162.0 is expected. Is this also anything to be concerned about?
Thanks,
Tim ==
Tim,
You don't mention the level of SQL2000 that you are running? Is it SP4?
Chris Wood
<tim@.tcsys.com> wrote in message
news:1123081469.455549.23850@.f14g2000cwb.googlegro ups.com...
> Greetings,
> On my Windows 2000 SP4 Server, the MDAC Component Checker Version 2.0
> reports that MDAC 2.8 SP1 on Windows XP SP2 is installed.
> MDAC 2.8 SP1 on Windows XP SP2 ... but this is a Windows 2000 SP4
> server? Very confusing. Will someone help me get my head around this?
> Further, when I set the Component Checker to perform analysis against a
> selected version, and target MDAC 2.8 SP1 on Windows XP SP2, only one
> inconsistency is reported -- msxml3.dll is at version 8.70.1104.0, but
> 8.50.2162.0 is expected. Is this also anything to be concerned about?
> Thanks,
> Tim ==
>
|||Thanks for replying, Chris.
I know almost nothing about SQL server, but, that being said, I'm an
otherwise competent MS net admin.
This particular box has an MSDE engine installed by an not-profit
financial application. The management of this app is hands-off, under
the control of the vendor.
The thing is, the same server is also our Backup Exec box. Backup Exec
was configured to use the same SQL instance as the financial app.
That's not unusual; the use of an existing SQL or MSDE instance on the
same box is the default installation setting for Backup Exec.
But lately we've been having some trouble with Backup Exec. And
wouldn't you know it? Some mismatched MDAC files turned up in the
course of investigation, and now Veritas/Symantec technical support is
insisting upon having the information in the OP before proceeding
further with the case.
So to answer your question: Knowing that this is an MSDE installation,
I was able to Google up this command line...
osql.exe -U administrator -Q "USE master SELECT @.@.version" -p
...but I'm prompted for a password which I do not believe that I
posses.
I've tried running it with the local administrator account and the
domain administrator account. No luck.
Believe me, your continued assistance is appreciated!
|||Tim,
If you are using an Windows administrator id I think that use can use the -E
rather than -U parameter. This should not ask for a password.
From the MSDE SP4 readme
1.5 Verify the Version of Microsoft Data Access Components
MSDE 2000 SP4 setup determines whether to upgrade an installed version of
Microsoft Data Access Components (MDAC) to MDAC 2.8 SP1:
a.. Computers that run Windows 2000 are upgraded to MDAC 2.8 SP1.
b.. Computers that run Windows XP or Windows Server 2003 are not upgraded
to MDAC 2.8 SP1. If your system requires any of the fixes included in MDAC
2.8 SP1, upgrade your system to Windows XP SP2 or Windows Server 2003 SP1 to
obtain MDAC 2.8 SP2.
c.. MDAC 2.8 SP1 is not installed on computers that already have installed
an equal or later version of MDAC.
d..
e.. 1.6 Identify the Current Version of MSDE 2000
Before running Setup, identify the version of the MSDE 2000 instance that
is being upgraded. If the version of MSDE 2000 is already at or greater than
SP4, you do not need to install SP4.
To identify the installed version of MSDE 2000:
1.. Execute one of the following queries against an instance of the
database engine by using isql, osql, or Query Analyzer.
a.. SELECT SERVERPROPERTY('ProductLevel')
b.. SELECT @.@.VERSION
c.. SELECT SERVERPROPERTY('ProductVersion')
2.. Find out your version of MSDE by means of the following table. SQL
Server 2000 Version and Level @.@.VERSION Product Level
SQL Server 2000 Original Release 8.00.194 RTM
Desktop Engine SP1 8.00.384 SP1
Desktop Engine SP2 8.00.534 SP2
Desktop Engine SP3, SP3a, or MSDE 2000 Release A. 8.00.760 SP3
MSDE 2000 SP4 8.00.2039 SP4
Chris
<tim@.tcsys.com> wrote in message
news:1123100308.823774.310400@.g49g2000cwa.googlegr oups.com...
> Thanks for replying, Chris.
> I know almost nothing about SQL server, but, that being said, I'm an
> otherwise competent MS net admin.
> This particular box has an MSDE engine installed by an not-profit
> financial application. The management of this app is hands-off, under
> the control of the vendor.
> The thing is, the same server is also our Backup Exec box. Backup Exec
> was configured to use the same SQL instance as the financial app.
> That's not unusual; the use of an existing SQL or MSDE instance on the
> same box is the default installation setting for Backup Exec.
> But lately we've been having some trouble with Backup Exec. And
> wouldn't you know it? Some mismatched MDAC files turned up in the
> course of investigation, and now Veritas/Symantec technical support is
> insisting upon having the information in the OP before proceeding
> further with the case.
> So to answer your question: Knowing that this is an MSDE installation,
> I was able to Google up this command line...
> osql.exe -U administrator -Q "USE master SELECT @.@.version" -p
> ...but I'm prompted for a password which I do not believe that I
> posses.
> I've tried running it with the local administrator account and the
> domain administrator account. No luck.
> Believe me, your continued assistance is appreciated!
>
|||Tim,
Did you find out the build of MSDE?
Chris
<tim@.tcsys.com> wrote in message
news:1123100308.823774.310400@.g49g2000cwa.googlegr oups.com...
> Thanks for replying, Chris.
> I know almost nothing about SQL server, but, that being said, I'm an
> otherwise competent MS net admin.
> This particular box has an MSDE engine installed by an not-profit
> financial application. The management of this app is hands-off, under
> the control of the vendor.
> The thing is, the same server is also our Backup Exec box. Backup Exec
> was configured to use the same SQL instance as the financial app.
> That's not unusual; the use of an existing SQL or MSDE instance on the
> same box is the default installation setting for Backup Exec.
> But lately we've been having some trouble with Backup Exec. And
> wouldn't you know it? Some mismatched MDAC files turned up in the
> course of investigation, and now Veritas/Symantec technical support is
> insisting upon having the information in the OP before proceeding
> further with the case.
> So to answer your question: Knowing that this is an MSDE installation,
> I was able to Google up this command line...
> osql.exe -U administrator -Q "USE master SELECT @.@.version" -p
> ...but I'm prompted for a password which I do not believe that I
> posses.
> I've tried running it with the local administrator account and the
> domain administrator account. No luck.
> Believe me, your continued assistance is appreciated!
>
|||Chris,
This thread speaks to a problem I created on our SBS 2003 with MDAC now
having 5 mismatched file versions and a crippled Veritas BackupExec 10, not
to mention the other problems this MDAC issue is causing. I lost RAS
yesterday (related? who knows!) and I can no longer access our Exchange
Server through the Web access for Outlook 2003.
I really messed things up and need help to get the correct MDAC files
restored. I used the cc.exe. Component Checker from MS to test the installed
version against the expected file versions.
Veritas/Symantec will not proceed with assistance until I get MDAC fixed.
HELP!
Chris
"Chris Wood" wrote:

> Tim,
> If you are using an Windows administrator id I think that use can use the -E
> rather than -U parameter. This should not ask for a password.
> From the MSDE SP4 readme
> 1.5 Verify the Version of Microsoft Data Access Components
> MSDE 2000 SP4 setup determines whether to upgrade an installed version of
> Microsoft Data Access Components (MDAC) to MDAC 2.8 SP1:
> a.. Computers that run Windows 2000 are upgraded to MDAC 2.8 SP1.
>
> b.. Computers that run Windows XP or Windows Server 2003 are not upgraded
> to MDAC 2.8 SP1. If your system requires any of the fixes included in MDAC
> 2.8 SP1, upgrade your system to Windows XP SP2 or Windows Server 2003 SP1 to
> obtain MDAC 2.8 SP2.
>
> c.. MDAC 2.8 SP1 is not installed on computers that already have installed
> an equal or later version of MDAC.
> d..
> e.. 1.6 Identify the Current Version of MSDE 2000
> Before running Setup, identify the version of the MSDE 2000 instance that
> is being upgraded. If the version of MSDE 2000 is already at or greater than
> SP4, you do not need to install SP4.
> To identify the installed version of MSDE 2000:
> 1.. Execute one of the following queries against an instance of the
> database engine by using isql, osql, or Query Analyzer.
> a.. SELECT SERVERPROPERTY('ProductLevel')
>
> b.. SELECT @.@.VERSION
>
> c.. SELECT SERVERPROPERTY('ProductVersion')
> 2.. Find out your version of MSDE by means of the following table. SQL
> Server 2000 Version and Level @.@.VERSION Product Level
> SQL Server 2000 Original Release 8.00.194 RTM
> Desktop Engine SP1 8.00.384 SP1
> Desktop Engine SP2 8.00.534 SP2
> Desktop Engine SP3, SP3a, or MSDE 2000 Release A. 8.00.760 SP3
> MSDE 2000 SP4 8.00.2039 SP4
> Chris
> <tim@.tcsys.com> wrote in message
> news:1123100308.823774.310400@.g49g2000cwa.googlegr oups.com...
>
>
|||Is this SBS 2003 SP1? It looks like it includes MSDE2000 SP4 unless you have
the Premium edition that includes full blown SQL2000 SP4.
If this is SP1 then my previous note about MDAC applies.
Chris
"Chris Williams" <Chris Williams@.discussions.microsoft.com> wrote in message
news:BE841E75-8D2C-4EE1-B2E7-D4BE9EAD417E@.microsoft.com...[vbcol=seagreen]
> Chris,
> This thread speaks to a problem I created on our SBS 2003 with MDAC now
> having 5 mismatched file versions and a crippled Veritas BackupExec 10,
> not
> to mention the other problems this MDAC issue is causing. I lost RAS
> yesterday (related? who knows!) and I can no longer access our Exchange
> Server through the Web access for Outlook 2003.
> I really messed things up and need help to get the correct MDAC files
> restored. I used the cc.exe. Component Checker from MS to test the
> installed
> version against the expected file versions.
> Veritas/Symantec will not proceed with assistance until I get MDAC fixed.
> HELP!
> Chris
> "Chris Wood" wrote:
|||Chris (Wood),
Are you asking about my server issue or the one from Tim? We are not at SP1
for our SBS 2003 yet because the server would not allow Windows Update to
properly run much less update it's components. I have all 5 of the Microsoft
specified downloads for SBS 2003 SP1 downloaded as per an article I read on
the SBS MS site. I was planning to do some more reading on this before trying
to apply them and was hoping that would fix my browser issue that kept it
from running Windows Update properly.
Frankly this server was a walking abortion from the get go with the company
that originally installed it doing a very poor job. I band-aided everything I
could safely do to even get it to run without daily unexpected re-boots. I
know that was putting off the inevidable, but the company needed to get back
to daily operations after 30+ days of dissruption caused by this "other"
outside computer company. We have since severed ties with them.
Anyway, we are running with only the original installation of SBS 2003, some
security patches in place and not much else. I also wanted to update the
exchange server to SP1 (this is part of the process I hope to complete once I
fix my MDAC issues).
Since I last posted, I tossed in my towel on this and have a engineer coming
in this morning from a group that has been trying to get our business for
some time now. I hope he will know what to do to fix this MDAC problem.
But any input you can offer will be good. Also, we are running the standard
version of SBS 2003, not the premium, thus the SQL is only that MSDE2000,
which I am growing to hate by the minute. I would have ponyed up the money
for the premium if I where actually working here when they were forced to get
a new server back in December 2004. (The old server was a Netware server that
this same outside computer company supported, broke and then said it's better
to scrap that server and replace it with the SBS 2003 they installed - This
Machine. We all know how well a job they did on that too!)
Sorry to rant. It's been a long week and I am stressed out.
Chris W.
"Chris Wood" wrote:

> Is this SBS 2003 SP1? It looks like it includes MSDE2000 SP4 unless you have
> the Premium edition that includes full blown SQL2000 SP4.
> If this is SP1 then my previous note about MDAC applies.
> Chris
> "Chris Williams" <Chris Williams@.discussions.microsoft.com> wrote in message
> news:BE841E75-8D2C-4EE1-B2E7-D4BE9EAD417E@.microsoft.com...
>
>

MDAC Madness

Greetings,
On my Windows 2000 SP4 Server, the MDAC Component Checker Version 2.0
reports that MDAC 2.8 SP1 on Windows XP SP2 is installed.
MDAC 2.8 SP1 on Windows XP SP2 ... but this is a Windows 2000 SP4
server? Very confusing. Will someone help me get my head around this?
Further, when I set the Component Checker to perform analysis against a
selected version, and target MDAC 2.8 SP1 on Windows XP SP2, only one
inconsistency is reported -- msxml3.dll is at version 8.70.1104.0, but
8.50.2162.0 is expected. Is this also anything to be concerned about?
Thanks,
Tim ==Tim,
You don't mention the level of SQL2000 that you are running? Is it SP4?
Chris Wood
<tim@.tcsys.com> wrote in message
news:1123081469.455549.23850@.f14g2000cwb.googlegroups.com...
> Greetings,
> On my Windows 2000 SP4 Server, the MDAC Component Checker Version 2.0
> reports that MDAC 2.8 SP1 on Windows XP SP2 is installed.
> MDAC 2.8 SP1 on Windows XP SP2 ... but this is a Windows 2000 SP4
> server? Very confusing. Will someone help me get my head around this?
> Further, when I set the Component Checker to perform analysis against a
> selected version, and target MDAC 2.8 SP1 on Windows XP SP2, only one
> inconsistency is reported -- msxml3.dll is at version 8.70.1104.0, but
> 8.50.2162.0 is expected. Is this also anything to be concerned about?
> Thanks,
> Tim ==>|||Thanks for replying, Chris.
I know almost nothing about SQL server, but, that being said, I'm an
otherwise competent MS net admin.
This particular box has an MSDE engine installed by an not-profit
financial application. The management of this app is hands-off, under
the control of the vendor.
The thing is, the same server is also our Backup Exec box. Backup Exec
was configured to use the same SQL instance as the financial app.
That's not unusual; the use of an existing SQL or MSDE instance on the
same box is the default installation setting for Backup Exec.
But lately we've been having some trouble with Backup Exec. And
wouldn't you know it? Some mismatched MDAC files turned up in the
course of investigation, and now Veritas/Symantec technical support is
insisting upon having the information in the OP before proceeding
further with the case.
So to answer your question: Knowing that this is an MSDE installation,
I was able to Google up this command line...
osql.exe -U administrator -Q "USE master SELECT @.@.version" -p
...but I'm prompted for a password which I do not believe that I
posses.
I've tried running it with the local administrator account and the
domain administrator account. No luck.
Believe me, your continued assistance is appreciated!|||Tim,
If you are using an Windows administrator id I think that use can use the -E
rather than -U parameter. This should not ask for a password.
From the MSDE SP4 readme
1.5 Verify the Version of Microsoft Data Access Components
MSDE 2000 SP4 setup determines whether to upgrade an installed version of
Microsoft Data Access Components (MDAC) to MDAC 2.8 SP1:
a.. Computers that run Windows 2000 are upgraded to MDAC 2.8 SP1.
b.. Computers that run Windows XP or Windows Server 2003 are not upgraded
to MDAC 2.8 SP1. If your system requires any of the fixes included in MDAC
2.8 SP1, upgrade your system to Windows XP SP2 or Windows Server 2003 SP1 to
obtain MDAC 2.8 SP2.
c.. MDAC 2.8 SP1 is not installed on computers that already have installed
an equal or later version of MDAC.
d..
e.. 1.6 Identify the Current Version of MSDE 2000
Before running Setup, identify the version of the MSDE 2000 instance that
is being upgraded. If the version of MSDE 2000 is already at or greater than
SP4, you do not need to install SP4.
To identify the installed version of MSDE 2000:
1.. Execute one of the following queries against an instance of the
database engine by using isql, osql, or Query Analyzer.
a.. SELECT SERVERPROPERTY('ProductLevel')
b.. SELECT @.@.VERSION
c.. SELECT SERVERPROPERTY('ProductVersion')
2.. Find out your version of MSDE by means of the following table. SQL
Server 2000 Version and Level @.@.VERSION Product Level
SQL Server 2000 Original Release 8.00.194 RTM
Desktop Engine SP1 8.00.384 SP1
Desktop Engine SP2 8.00.534 SP2
Desktop Engine SP3, SP3a, or MSDE 2000 Release A. 8.00.760 SP3
MSDE 2000 SP4 8.00.2039 SP4
Chris
<tim@.tcsys.com> wrote in message
news:1123100308.823774.310400@.g49g2000cwa.googlegroups.com...
> Thanks for replying, Chris.
> I know almost nothing about SQL server, but, that being said, I'm an
> otherwise competent MS net admin.
> This particular box has an MSDE engine installed by an not-profit
> financial application. The management of this app is hands-off, under
> the control of the vendor.
> The thing is, the same server is also our Backup Exec box. Backup Exec
> was configured to use the same SQL instance as the financial app.
> That's not unusual; the use of an existing SQL or MSDE instance on the
> same box is the default installation setting for Backup Exec.
> But lately we've been having some trouble with Backup Exec. And
> wouldn't you know it? Some mismatched MDAC files turned up in the
> course of investigation, and now Veritas/Symantec technical support is
> insisting upon having the information in the OP before proceeding
> further with the case.
> So to answer your question: Knowing that this is an MSDE installation,
> I was able to Google up this command line...
> osql.exe -U administrator -Q "USE master SELECT @.@.version" -p
> ...but I'm prompted for a password which I do not believe that I
> posses.
> I've tried running it with the local administrator account and the
> domain administrator account. No luck.
> Believe me, your continued assistance is appreciated!
>|||Tim,
Did you find out the build of MSDE?
Chris
<tim@.tcsys.com> wrote in message
news:1123100308.823774.310400@.g49g2000cwa.googlegroups.com...
> Thanks for replying, Chris.
> I know almost nothing about SQL server, but, that being said, I'm an
> otherwise competent MS net admin.
> This particular box has an MSDE engine installed by an not-profit
> financial application. The management of this app is hands-off, under
> the control of the vendor.
> The thing is, the same server is also our Backup Exec box. Backup Exec
> was configured to use the same SQL instance as the financial app.
> That's not unusual; the use of an existing SQL or MSDE instance on the
> same box is the default installation setting for Backup Exec.
> But lately we've been having some trouble with Backup Exec. And
> wouldn't you know it? Some mismatched MDAC files turned up in the
> course of investigation, and now Veritas/Symantec technical support is
> insisting upon having the information in the OP before proceeding
> further with the case.
> So to answer your question: Knowing that this is an MSDE installation,
> I was able to Google up this command line...
> osql.exe -U administrator -Q "USE master SELECT @.@.version" -p
> ...but I'm prompted for a password which I do not believe that I
> posses.
> I've tried running it with the local administrator account and the
> domain administrator account. No luck.
> Believe me, your continued assistance is appreciated!
>|||Chris,
This thread speaks to a problem I created on our SBS 2003 with MDAC now
having 5 mismatched file versions and a crippled Veritas BackupExec 10, not
to mention the other problems this MDAC issue is causing. I lost RAS
yesterday (related? who knows!) and I can no longer access our Exchange
Server through the Web access for Outlook 2003.
I really messed things up and need help to get the correct MDAC files
restored. I used the cc.exe. Component Checker from MS to test the installed
version against the expected file versions.
Veritas/Symantec will not proceed with assistance until I get MDAC fixed.
HELP!
Chris
"Chris Wood" wrote:
> Tim,
> If you are using an Windows administrator id I think that use can use the -E
> rather than -U parameter. This should not ask for a password.
> From the MSDE SP4 readme
> 1.5 Verify the Version of Microsoft Data Access Components
> MSDE 2000 SP4 setup determines whether to upgrade an installed version of
> Microsoft Data Access Components (MDAC) to MDAC 2.8 SP1:
> a.. Computers that run Windows 2000 are upgraded to MDAC 2.8 SP1.
>
> b.. Computers that run Windows XP or Windows Server 2003 are not upgraded
> to MDAC 2.8 SP1. If your system requires any of the fixes included in MDAC
> 2.8 SP1, upgrade your system to Windows XP SP2 or Windows Server 2003 SP1 to
> obtain MDAC 2.8 SP2.
>
> c.. MDAC 2.8 SP1 is not installed on computers that already have installed
> an equal or later version of MDAC.
> d..
> e.. 1.6 Identify the Current Version of MSDE 2000
> Before running Setup, identify the version of the MSDE 2000 instance that
> is being upgraded. If the version of MSDE 2000 is already at or greater than
> SP4, you do not need to install SP4.
> To identify the installed version of MSDE 2000:
> 1.. Execute one of the following queries against an instance of the
> database engine by using isql, osql, or Query Analyzer.
> a.. SELECT SERVERPROPERTY('ProductLevel')
>
> b.. SELECT @.@.VERSION
>
> c.. SELECT SERVERPROPERTY('ProductVersion')
> 2.. Find out your version of MSDE by means of the following table. SQL
> Server 2000 Version and Level @.@.VERSION Product Level
> SQL Server 2000 Original Release 8.00.194 RTM
> Desktop Engine SP1 8.00.384 SP1
> Desktop Engine SP2 8.00.534 SP2
> Desktop Engine SP3, SP3a, or MSDE 2000 Release A. 8.00.760 SP3
> MSDE 2000 SP4 8.00.2039 SP4
> Chris
> <tim@.tcsys.com> wrote in message
> news:1123100308.823774.310400@.g49g2000cwa.googlegroups.com...
> > Thanks for replying, Chris.
> >
> > I know almost nothing about SQL server, but, that being said, I'm an
> > otherwise competent MS net admin.
> >
> > This particular box has an MSDE engine installed by an not-profit
> > financial application. The management of this app is hands-off, under
> > the control of the vendor.
> >
> > The thing is, the same server is also our Backup Exec box. Backup Exec
> > was configured to use the same SQL instance as the financial app.
> > That's not unusual; the use of an existing SQL or MSDE instance on the
> > same box is the default installation setting for Backup Exec.
> >
> > But lately we've been having some trouble with Backup Exec. And
> > wouldn't you know it? Some mismatched MDAC files turned up in the
> > course of investigation, and now Veritas/Symantec technical support is
> > insisting upon having the information in the OP before proceeding
> > further with the case.
> >
> > So to answer your question: Knowing that this is an MSDE installation,
> > I was able to Google up this command line...
> > osql.exe -U administrator -Q "USE master SELECT @.@.version" -p
> > ...but I'm prompted for a password which I do not believe that I
> > posses.
> >
> > I've tried running it with the local administrator account and the
> > domain administrator account. No luck.
> >
> > Believe me, your continued assistance is appreciated!
> >
>
>|||Is this SBS 2003 SP1? It looks like it includes MSDE2000 SP4 unless you have
the Premium edition that includes full blown SQL2000 SP4.
If this is SP1 then my previous note about MDAC applies.
Chris
"Chris Williams" <Chris Williams@.discussions.microsoft.com> wrote in message
news:BE841E75-8D2C-4EE1-B2E7-D4BE9EAD417E@.microsoft.com...
> Chris,
> This thread speaks to a problem I created on our SBS 2003 with MDAC now
> having 5 mismatched file versions and a crippled Veritas BackupExec 10,
> not
> to mention the other problems this MDAC issue is causing. I lost RAS
> yesterday (related? who knows!) and I can no longer access our Exchange
> Server through the Web access for Outlook 2003.
> I really messed things up and need help to get the correct MDAC files
> restored. I used the cc.exe. Component Checker from MS to test the
> installed
> version against the expected file versions.
> Veritas/Symantec will not proceed with assistance until I get MDAC fixed.
> HELP!
> Chris
> "Chris Wood" wrote:
>> Tim,
>> If you are using an Windows administrator id I think that use can use
>> the -E
>> rather than -U parameter. This should not ask for a password.
>> From the MSDE SP4 readme
>> 1.5 Verify the Version of Microsoft Data Access Components
>> MSDE 2000 SP4 setup determines whether to upgrade an installed version of
>> Microsoft Data Access Components (MDAC) to MDAC 2.8 SP1:
>> a.. Computers that run Windows 2000 are upgraded to MDAC 2.8 SP1.
>>
>> b.. Computers that run Windows XP or Windows Server 2003 are not
>> upgraded
>> to MDAC 2.8 SP1. If your system requires any of the fixes included in
>> MDAC
>> 2.8 SP1, upgrade your system to Windows XP SP2 or Windows Server 2003 SP1
>> to
>> obtain MDAC 2.8 SP2.
>>
>> c.. MDAC 2.8 SP1 is not installed on computers that already have
>> installed
>> an equal or later version of MDAC.
>> d..
>> e.. 1.6 Identify the Current Version of MSDE 2000
>> Before running Setup, identify the version of the MSDE 2000 instance
>> that
>> is being upgraded. If the version of MSDE 2000 is already at or greater
>> than
>> SP4, you do not need to install SP4.
>> To identify the installed version of MSDE 2000:
>> 1.. Execute one of the following queries against an instance of the
>> database engine by using isql, osql, or Query Analyzer.
>> a.. SELECT SERVERPROPERTY('ProductLevel')
>>
>> b.. SELECT @.@.VERSION
>>
>> c.. SELECT SERVERPROPERTY('ProductVersion')
>> 2.. Find out your version of MSDE by means of the following table.
>> SQL
>> Server 2000 Version and Level @.@.VERSION Product Level
>> SQL Server 2000 Original Release 8.00.194 RTM
>> Desktop Engine SP1 8.00.384 SP1
>> Desktop Engine SP2 8.00.534 SP2
>> Desktop Engine SP3, SP3a, or MSDE 2000 Release A. 8.00.760 SP3
>> MSDE 2000 SP4 8.00.2039 SP4
>> Chris
>> <tim@.tcsys.com> wrote in message
>> news:1123100308.823774.310400@.g49g2000cwa.googlegroups.com...
>> > Thanks for replying, Chris.
>> >
>> > I know almost nothing about SQL server, but, that being said, I'm an
>> > otherwise competent MS net admin.
>> >
>> > This particular box has an MSDE engine installed by an not-profit
>> > financial application. The management of this app is hands-off, under
>> > the control of the vendor.
>> >
>> > The thing is, the same server is also our Backup Exec box. Backup Exec
>> > was configured to use the same SQL instance as the financial app.
>> > That's not unusual; the use of an existing SQL or MSDE instance on the
>> > same box is the default installation setting for Backup Exec.
>> >
>> > But lately we've been having some trouble with Backup Exec. And
>> > wouldn't you know it? Some mismatched MDAC files turned up in the
>> > course of investigation, and now Veritas/Symantec technical support is
>> > insisting upon having the information in the OP before proceeding
>> > further with the case.
>> >
>> > So to answer your question: Knowing that this is an MSDE installation,
>> > I was able to Google up this command line...
>> > osql.exe -U administrator -Q "USE master SELECT @.@.version" -p
>> > ...but I'm prompted for a password which I do not believe that I
>> > posses.
>> >
>> > I've tried running it with the local administrator account and the
>> > domain administrator account. No luck.
>> >
>> > Believe me, your continued assistance is appreciated!
>> >
>>|||Chris (Wood),
Are you asking about my server issue or the one from Tim? We are not at SP1
for our SBS 2003 yet because the server would not allow Windows Update to
properly run much less update it's components. I have all 5 of the Microsoft
specified downloads for SBS 2003 SP1 downloaded as per an article I read on
the SBS MS site. I was planning to do some more reading on this before trying
to apply them and was hoping that would fix my browser issue that kept it
from running Windows Update properly.
Frankly this server was a walking abortion from the get go with the company
that originally installed it doing a very poor job. I band-aided everything I
could safely do to even get it to run without daily unexpected re-boots. I
know that was putting off the inevidable, but the company needed to get back
to daily operations after 30+ days of dissruption caused by this "other"
outside computer company. We have since severed ties with them.
Anyway, we are running with only the original installation of SBS 2003, some
security patches in place and not much else. I also wanted to update the
exchange server to SP1 (this is part of the process I hope to complete once I
fix my MDAC issues).
Since I last posted, I tossed in my towel on this and have a engineer coming
in this morning from a group that has been trying to get our business for
some time now. I hope he will know what to do to fix this MDAC problem.
But any input you can offer will be good. Also, we are running the standard
version of SBS 2003, not the premium, thus the SQL is only that MSDE2000,
which I am growing to hate by the minute. I would have ponyed up the money
for the premium if I where actually working here when they were forced to get
a new server back in December 2004. (The old server was a Netware server that
this same outside computer company supported, broke and then said it's better
to scrap that server and replace it with the SBS 2003 they installed - This
Machine. We all know how well a job they did on that too!)
Sorry to rant. It's been a long week and I am stressed out.
Chris W.
"Chris Wood" wrote:
> Is this SBS 2003 SP1? It looks like it includes MSDE2000 SP4 unless you have
> the Premium edition that includes full blown SQL2000 SP4.
> If this is SP1 then my previous note about MDAC applies.
> Chris
> "Chris Williams" <Chris Williams@.discussions.microsoft.com> wrote in message
> news:BE841E75-8D2C-4EE1-B2E7-D4BE9EAD417E@.microsoft.com...
> > Chris,
> >
> > This thread speaks to a problem I created on our SBS 2003 with MDAC now
> > having 5 mismatched file versions and a crippled Veritas BackupExec 10,
> > not
> > to mention the other problems this MDAC issue is causing. I lost RAS
> > yesterday (related? who knows!) and I can no longer access our Exchange
> > Server through the Web access for Outlook 2003.
> >
> > I really messed things up and need help to get the correct MDAC files
> > restored. I used the cc.exe. Component Checker from MS to test the
> > installed
> > version against the expected file versions.
> >
> > Veritas/Symantec will not proceed with assistance until I get MDAC fixed.
> >
> > HELP!
> >
> > Chris
> >
> > "Chris Wood" wrote:
> >
> >> Tim,
> >>
> >> If you are using an Windows administrator id I think that use can use
> >> the -E
> >> rather than -U parameter. This should not ask for a password.
> >>
> >> From the MSDE SP4 readme
> >>
> >> 1.5 Verify the Version of Microsoft Data Access Components
> >> MSDE 2000 SP4 setup determines whether to upgrade an installed version of
> >> Microsoft Data Access Components (MDAC) to MDAC 2.8 SP1:
> >>
> >> a.. Computers that run Windows 2000 are upgraded to MDAC 2.8 SP1.
> >>
> >>
> >> b.. Computers that run Windows XP or Windows Server 2003 are not
> >> upgraded
> >> to MDAC 2.8 SP1. If your system requires any of the fixes included in
> >> MDAC
> >> 2.8 SP1, upgrade your system to Windows XP SP2 or Windows Server 2003 SP1
> >> to
> >> obtain MDAC 2.8 SP2.
> >>
> >>
> >> c.. MDAC 2.8 SP1 is not installed on computers that already have
> >> installed
> >> an equal or later version of MDAC.
> >> d..
> >> e.. 1.6 Identify the Current Version of MSDE 2000
> >> Before running Setup, identify the version of the MSDE 2000 instance
> >> that
> >> is being upgraded. If the version of MSDE 2000 is already at or greater
> >> than
> >> SP4, you do not need to install SP4.
> >>
> >> To identify the installed version of MSDE 2000:
> >>
> >> 1.. Execute one of the following queries against an instance of the
> >> database engine by using isql, osql, or Query Analyzer.
> >> a.. SELECT SERVERPROPERTY('ProductLevel')
> >>
> >>
> >> b.. SELECT @.@.VERSION
> >>
> >>
> >> c.. SELECT SERVERPROPERTY('ProductVersion')
> >> 2.. Find out your version of MSDE by means of the following table.
> >> SQL
> >> Server 2000 Version and Level @.@.VERSION Product Level
> >> SQL Server 2000 Original Release 8.00.194 RTM
> >> Desktop Engine SP1 8.00.384 SP1
> >> Desktop Engine SP2 8.00.534 SP2
> >> Desktop Engine SP3, SP3a, or MSDE 2000 Release A. 8.00.760 SP3
> >> MSDE 2000 SP4 8.00.2039 SP4
> >>
> >> Chris
> >> <tim@.tcsys.com> wrote in message
> >> news:1123100308.823774.310400@.g49g2000cwa.googlegroups.com...
> >> > Thanks for replying, Chris.
> >> >
> >> > I know almost nothing about SQL server, but, that being said, I'm an
> >> > otherwise competent MS net admin.
> >> >
> >> > This particular box has an MSDE engine installed by an not-profit
> >> > financial application. The management of this app is hands-off, under
> >> > the control of the vendor.
> >> >
> >> > The thing is, the same server is also our Backup Exec box. Backup Exec
> >> > was configured to use the same SQL instance as the financial app.
> >> > That's not unusual; the use of an existing SQL or MSDE instance on the
> >> > same box is the default installation setting for Backup Exec.
> >> >
> >> > But lately we've been having some trouble with Backup Exec. And
> >> > wouldn't you know it? Some mismatched MDAC files turned up in the
> >> > course of investigation, and now Veritas/Symantec technical support is
> >> > insisting upon having the information in the OP before proceeding
> >> > further with the case.
> >> >
> >> > So to answer your question: Knowing that this is an MSDE installation,
> >> > I was able to Google up this command line...
> >> > osql.exe -U administrator -Q "USE master SELECT @.@.version" -p
> >> > ...but I'm prompted for a password which I do not believe that I
> >> > posses.
> >> >
> >> > I've tried running it with the local administrator account and the
> >> > domain administrator account. No luck.
> >> >
> >> > Believe me, your continued assistance is appreciated!
> >> >
> >>
> >>
> >>
>
>sql

MDAC error

I have upgraded MDAC to vers 2.7 SP1(winXP).

On checking via the MDAC Cmponent Checker that one file has an error or maybe currupt.

I have tried to reinstall with no joy. The error description is as follows:

Item Name,Item Type,ErrorString,Status
oledb32.dll,File,Field 'FileVersion' mismatch: Expect '2.71.9030.0 built by: Lab06_N(dagbuild)' Got '2.71.9031.4 built by: Lab06_N(dagbuild)',Error

Could you shed any light on what might be the problem is?

Cheers PetermJust uninstall everything related to MDAC and remove registry keys, reboot the box.

For information on MDAC issues refer to this Article (http://www.8wire.com/articles/index.asp?AID=2318) and this KBA (http://support.microsoft.com/default.aspx?scid=kb;EN-US;324520).

Make sure to install latest MDAC and SP from MS.

MDAC 2.8 vs MDAC 2.7 SQL Server Driver - causing deadlocks

I have two computers, a Windows XP machine with MDAC 2.7 SP1 (sqlsrv32.dll
version 2000.81.9042.0) and a Windows Server 2003 machine with MDAC 2.8 SP2
for Server 2003 (sqlsrv32.dll version 2000.86.1830.0) as confirmed by MDAC
Component Checker.
They are both connecting to the same machine with SQL Server 2000 with SP4.
I am submitting the several SQL commands through .NET OleDb (Framework 1.1)
to a JET DB (Access 2003) with a linked table to SQL Server. I have also
connected to JET through ODBC in the past as well with the same results.
I am inserting a record into a linked table called "Events" with one
autonumbered IDENTITY column called EventKey.
I have started a transaction through the BeginTransaction .NET methods. I
submit the following SQL commands (.NET pseudo-code'ish):
ExecuteNonQuery("INSERT INTO Events (EventMember) VALUES (6)")
var key = ExecuteScalar("SELECT @.@.IDENTITY")
ExecuteQuery("SELECT * FROM Events WHERE EventKey = " & key)
The first two commands run successfully, but the third command fails with
the following error: "System.Data.OleDb.OleDbException: ODBC--call failed."
after about a minute timeout.
Upon checking SQL Enterprise Manager, there are two processes (one blocking,
one blocked). The blocking process last executed the "SELECT @.@.IDENTITY",
the blocked process executed the "select * from..." query. After a lock
timeout, the SELECT * query returns with that error.
My question is: why are TWO connections being made to SQL Server for the
same transaction? Since all three queries are coming from the same source
JET connection, of course that second connection to SQL server while the
first connection has that inserted record locked will fail to read it.
This works perfectly from MDAC 2.7, but fails every time with MDAC 2.8. I
have tried to go through the "List of bug fixes" KB articles, but nothing wa
s
listed about a fix that I would think may break this idea other than
asynchronous fetching?
Any ideas - our application heavily uses this approach to insert new records
through ADO.NET and then select the records back during the same transaction
.
Thanks,
Mike Dearman
Lead Software EngineerI used the ODBC trace feature to obtain the following log. It definitely
shows the ODBC driver disconnecting then reconnecting between the SELECT
@.@.IDENTIY and the SELECT * commands. The weird thing is that it does a
SQLExecDirectW, then a fetch, then a getdata that all appears to be
successful. Then it does another fetch with return code 100
(SQL_NO_DATA_FOUND). After that, it seems to free the statement, and procee
d
to call SQLAllocConnect again.
Here is the complete ODBC trace log for the three SQL commands (cleaned up a
bit though - log too long):
ENTER SQLAllocEnv
HENV * 0C0FE7B8
EXIT SQLAllocEnv with return code 0 (SQL_SUCCESS)
HENV * 0x0C0FE7B8 ( 0x0f881788)
ENTER SQLAllocConnect
HENV 0F881788
HDBC * 0C0FE8C8
EXIT SQLAllocConnect with return code 0 (SQL_SUCCESS)
HENV 0F881788
HDBC * 0x0C0FE8C8 ( 0x0f881830)
ENTER SQLSetConnectOption
HDBC 0F881830
SQLINTEGER 103 <SQL_LOGIN_TIMEOUT>
SQLPOINTER 0x00000014
EXIT SQLSetConnectOption with return code 0 (SQL_SUCCESS)
HDBC 0F881830
SQLINTEGER 103 <SQL_LOGIN_TIMEOUT>
SQLPOINTER 0x00000014 (BADMEM)
ENTER SQLSetConnectAttrW
SQLHDBC 0F881830
SQLINTEGER 30002 <unknown>
SQLPOINTER [Unknown attribute 30002]
SQLINTEGER -3
EXIT SQLSetConnectAttrW with return code 0 (SQL_SUCCESS)
SQLHDBC 0F881830
SQLINTEGER 30002 <unknown>
SQLPOINTER [Unknown attribute 30002]
SQLINTEGER -3
ENTER SQLDriverConnectW
HDBC 0F881830
HWND 00000000
WCHAR * 0x4BF78088 [ -3] "******\ 0"
SWORD -3
WCHAR * 0x4BF78088
SWORD 2
SWORD * 0x00000000
UWORD 0 <SQL_DRIVER_NOPROMPT>
EXIT SQLDriverConnectW with return code 1 (SQL_SUCCESS_WITH_INFO)
HDBC 0F881830
HWND 00000000
WCHAR * 0x4BF78088 [ -3] "******\ 0"
SWORD -3
WCHAR * 0x4BF78088
SWORD 2
SWORD * 0x00000000
UWORD 0 <SQL_DRIVER_NOPROMPT>
DIAG [IM006] [Microsoft][ODBC Driver Manager] Driver's SQLSetCon
nectAttr
failed (0)
DIAG [01000] [Microsoft][ODBC SQL Server Driver][SQL Server]
Changed
database context to 'UAA'. (5701)
DIAG [01000] [Microsoft][ODBC SQL Server Driver][SQL Server]
Changed
language setting to us_english. (5703)
ENTER SQLGetInfoW
HDBC 0F881830
UWORD 9 <SQL_ODBC_API_CONFORMANCE>
PTR 0x0C0FE8EC
SWORD 2
SWORD * 0x0C0FE8E4
EXIT SQLGetInfoW with return code 0 (SQL_SUCCESS)
HDBC 0F881830
UWORD 9 <SQL_ODBC_API_CONFORMANCE>
PTR 0x0C0FE8EC (2)
SWORD 2
SWORD * 0x0C0FE8E4 (2)
ENTER SQLGetInfoW
HDBC 0F881830
UWORD 6 <SQL_DRIVER_NAME>
PTR 0x0C0FE7FC
SWORD 200
SWORD * 0x0C0FE8E4
EXIT SQLGetInfoW with return code 0 (SQL_SUCCESS)
HDBC 0F881830
UWORD 6 <SQL_DRIVER_NAME>
PTR 0x0C0FE7FC [ 24] "SQLSRV32.DLL"
SWORD 200
SWORD * 0x0C0FE8E4 (24)
ENTER SQLGetInfoW
HDBC 0F881830
UWORD 46 <SQL_TXN_CAPABLE>
PTR 0x0C0FE7C6
SWORD 2
SWORD * 0x0C0FE398
EXIT SQLGetInfoW with return code 0 (SQL_SUCCESS)
HDBC 0F881830
UWORD 46 <SQL_TXN_CAPABLE>
PTR 0x0C0FE7C6 (2)
SWORD 2
SWORD * 0x0C0FE398 (2)
ENTER SQLGetInfoW
HDBC 0F881830
UWORD 23 <SQL_CURSOR_COMMIT_BEHAVIOR>
PTR 0x0E029928
SWORD 2
SWORD * 0x0C0FE398
EXIT SQLGetInfoW with return code 0 (SQL_SUCCESS)
HDBC 0F881830
UWORD 23 <SQL_CURSOR_COMMIT_BEHAVIOR>
PTR 0x0E029928 (1)
SWORD 2
SWORD * 0x0C0FE398 (2)
ENTER SQLGetInfoW
HDBC 0F881830
UWORD 24 <SQL_CURSOR_ROLLBACK_BEHAVIOR>
PTR 0x0E02992A
SWORD 2
SWORD * 0x0C0FE398
EXIT SQLGetInfoW with return code 0 (SQL_SUCCESS)
HDBC 0F881830
UWORD 24 <SQL_CURSOR_ROLLBACK_BEHAVIOR>
PTR 0x0E02992A (1)
SWORD 2
SWORD * 0x0C0FE398 (2)
ENTER SQLGetInfoW
HDBC 0F881830
UWORD 1 <SQL_ACTIVE_STATEMENTS>
PTR 0x0C0FE7CC
SWORD 2
SWORD * 0x0C0FE7B2
EXIT SQLGetInfoW with return code 0 (SQL_SUCCESS)
HDBC 0F881830
UWORD 1 <SQL_ACTIVE_STATEMENTS>
PTR 0x0C0FE7CC (1)
SWORD 2
SWORD * 0x0C0FE7B2 (2)
ENTER SQLSetConnectOption
HDBC 0F881830
SQLINTEGER 101 <SQL_ACCESS_MODE>
SQLPOINTER 0x00000000
EXIT SQLSetConnectOption with return code 0 (SQL_SUCCESS)
HDBC 0F881830
SQLINTEGER 101 <SQL_ACCESS_MODE>
SQLPOINTER 0x00000000
ENTER SQLAllocStmt
HDBC 0F881830
HSTMT * 0C0FE390
EXIT SQLAllocStmt with return code 0 (SQL_SUCCESS)
HDBC 0F881830
HSTMT * 0x0C0FE390 ( 0x0f8820f0)
ENTER SQLGetStmtOption
HSTMT 0F8820F0
UWORD 0
PTR 0x0C0FE33C
EXIT SQLGetStmtOption with return code 0 (SQL_SUCCESS)
HSTMT 0F8820F0
UWORD 0
PTR 0x0C0FE33C
ENTER SQLSetStmtOption
HSTMT 0F8820F0
UWORD 0 <SQL_QUERY_TIMEOUT>
SQLPOINTER 0x0000003C
EXIT SQLSetStmtOption with return code 0 (SQL_SUCCESS)
HSTMT 0F8820F0
UWORD 0 <SQL_QUERY_TIMEOUT>
SQLPOINTER 0x0000003C (BADMEM)
ENTER SQLExecDirectW
HSTMT 0F8820F0
WCHAR * 0x1B074AA0 [ -3] "SELECT Config, nValue FROM
MSysConf\ 0"
SDWORD -3
EXIT SQLExecDirectW with return code -1 (SQL_ERROR)
HSTMT 0F8820F0
WCHAR * 0x1B074AA0 [ -3] "SELECT Config, nValue FROM
MSysConf\ 0"
SDWORD -3
DIAG [S0002] [Microsoft][ODBC SQL Server Driver][SQL Server]
Invalid object
name 'MSysConf'. (208)
ENTER SQLErrorW
HENV 0F881788
HDBC 0F881830
HSTMT 0F8820F0
WCHAR * 0x0C0FE2D0 (NYI)
SDWORD * 0x0C0FE31C
WCHAR * 0x0DFD0048
SWORD 4095
SWORD * 0x0C0FE308
EXIT SQLErrorW with return code 0 (SQL_SUCCESS)
HENV 0F881788
HDBC 0F881830
HSTMT 0F8820F0
WCHAR * 0x0C0FE2D0 (NYI)
SDWORD * 0x0C0FE31C (208)
WCHAR * 0x0DFD0048 [ 78] "[Microsoft][ODBC SQL
Server
Driver][SQL Server]Invalid object name 'MSysConf'."
SWORD 4095
SWORD * 0x0C0FE308 (78)
ENTER SQLErrorW
HENV 0F881788
HDBC 0F881830
HSTMT 0F8820F0
WCHAR * 0x0C0FE2D0 (NYI)
SDWORD * 0x0C0FE31C
WCHAR * 0x0DFD00FA
SWORD 4006
SWORD * 0x0C0FE308
EXIT SQLErrorW with return code 100 (SQL_NO_DATA_FOUND)
HENV 0F881788
HDBC 0F881830
HSTMT 0F8820F0
WCHAR * 0x0C0FE2D0 (NYI)
SDWORD * 0x0C0FE31C
WCHAR * 0x0DFD00FA
SWORD 4006
SWORD * 0x0C0FE308
ENTER SQLFreeStmt
HSTMT 0F8820F0
UWORD 1 <SQL_DROP>
EXIT SQLFreeStmt with return code 0 (SQL_SUCCESS)
HSTMT 0F8820F0
UWORD 1 <SQL_DROP>
ENTER SQLGetInfoW
HDBC 0F881830
UWORD 17 <SQL_DBMS_NAME>
PTR 0x0C0FDFC4
SWORD 200
SWORD * 0x0C0FE08E
EXIT SQLGetInfoW with return code 0 (SQL_SUCCESS)
HDBC 0F881830
UWORD 17 <SQL_DBMS_NAME>
PTR 0x0C0FDFC4 [ 40] "Microsoft SQL Server"
SWORD 200
SWORD * 0x0C0FE08E (40)
ENTER SQLGetInfoW
HDBC 0F881830
UWORD 0 <SQL_ACTIVE_CONNECTIONS>
PTR 0x0C0FE0D2
SWORD 2
SWORD * 0x0C0FE0E0
EXIT SQLGetInfoW with return code 0 (SQL_SUCCESS)
HDBC 0F881830
UWORD 0 <SQL_ACTIVE_CONNECTIONS>
PTR 0x0C0FE0D2 (0)
SWORD 2
SWORD * 0x0C0FE0E0 (2)
ENTER SQLGetInfoW
HDBC 0F881830
UWORD 25 <SQL_DATA_SOURCE_READ_ONLY>
PTR 0x0C0FE0B8
SWORD 20
SWORD * 0x0C0FE0E0
EXIT SQLGetInfoW with return code 0 (SQL_SUCCESS)
HDBC 0F881830
UWORD 25 <SQL_DATA_SOURCE_READ_ONLY>
PTR 0x0C0FE0B8 [ 2] "N"
SWORD 20
SWORD * 0x0C0FE0E0 (2)
ENTER SQLGetInfoW
HDBC 0F881830
UWORD 46 <SQL_TXN_CAPABLE>
PTR 0x0C0FE0D0
SWORD 2
SWORD * 0x0C0FE0A0
EXIT SQLGetInfoW with return code 0 (SQL_SUCCESS)
HDBC 0F881830
UWORD 46 <SQL_TXN_CAPABLE>
PTR 0x0C0FE0D0 (2)
SWORD 2
SWORD * 0x0C0FE0A0 (2)
ENTER SQLGetInfoW
HDBC 0F881830
UWORD 23 <SQL_CURSOR_COMMIT_BEHAVIOR>
PTR 0x0C0FE0CC
SWORD 2
SWORD * 0x0C0FE0A0
EXIT SQLGetInfoW with return code 0 (SQL_SUCCESS)
HDBC 0F881830
UWORD 23 <SQL_CURSOR_COMMIT_BEHAVIOR>
PTR 0x0C0FE0CC (1)
SWORD 2
SWORD * 0x0C0FE0A0 (2)
ENTER SQLGetInfoW
HDBC 0F881830
UWORD 24 <SQL_CURSOR_ROLLBACK_BEHAVIOR>
PTR 0x0C0FE0CE
SWORD 2
SWORD * 0x0C0FE0A0
EXIT SQLGetInfoW with return code 0 (SQL_SUCCESS)
HDBC 0F881830
UWORD 24 <SQL_CURSOR_ROLLBACK_BEHAVIOR>
PTR 0x0C0FE0CE (1)
SWORD 2
SWORD * 0x0C0FE0A0 (2)
ENTER SQLGetInfoW
HDBC 0F881830
UWORD 29 <SQL_IDENTIFIER_QUOTE_CHAR>
PTR 0x0C0FE0B8
SWORD 20
SWORD * 0x0C0FE0E0
EXIT SQLGetInfoW with return code 0 (SQL_SUCCESS)
HDBC 0F881830
UWORD 29 <SQL_IDENTIFIER_QUOTE_CHAR>
PTR 0x0C0FE0B8 [ 2] """
SWORD 20
SWORD * 0x0C0FE0E0 (2)
ENTER SQLSetConnectOption
HDBC 0F881830
SQLINTEGER 102 <SQL_AUTOCOMMIT>
SQLPOINTER 0x00000000
EXIT SQLSetConnectOption with return code 0 (SQL_SUCCESS)
HDBC 0F881830
SQLINTEGER 102 <SQL_AUTOCOMMIT>
SQLPOINTER 0x00000000
ENTER SQLAllocStmt
HDBC 0F881830
HSTMT * 0C0FEBD8
EXIT SQLAllocStmt with return code 0 (SQL_SUCCESS)
HDBC 0F881830
HSTMT * 0x0C0FEBD8 ( 0x0f8820f0)
ENTER SQLGetStmtOption
HSTMT 0F8820F0
UWORD 0
PTR 0x0C0FE718
EXIT SQLGetStmtOption with return code 0 (SQL_SUCCESS)
HSTMT 0F8820F0
UWORD 0
PTR 0x0C0FE718
ENTER SQLSetStmtOption
HSTMT 0F8820F0
UWORD 0 <SQL_QUERY_TIMEOUT>
SQLPOINTER 0x0000003C
EXIT SQLSetStmtOption with return code 0 (SQL_SUCCESS)
HSTMT 0F8820F0
UWORD 0 <SQL_QUERY_TIMEOUT>
SQLPOINTER 0x0000003C (BADMEM)
ENTER SQLBindParameter
HSTMT 0F8820F0
UWORD 1
SWORD 1 <SQL_PARAM_INPUT>
SWORD 4 <SQL_C_LONG>
SWORD 4 <SQL_INTEGER>
SQLULEN 10
SWORD 0
PTR 0x2DFD41A4
SQLLEN 0
SQLLEN * 0x2DFD41A0
EXIT SQLBindParameter with return code 0 (SQL_SUCCESS)
HSTMT 0F8820F0
UWORD 1
SWORD 1 <SQL_PARAM_INPUT>
SWORD 4 <SQL_C_LONG>
SWORD 4 <SQL_INTEGER>
SQLULEN 10
SWORD 0
PTR 0x2DFD41A4
SQLLEN 0
SQLLEN * 0x2DFD41A0 (4)
ENTER SQLExecDirectW
HSTMT 0F8820F0
WCHAR * 0x2DFD61A8 [ -3] "INSERT INTO "dbo"."Events"
("EventMember") VALUES (?)\ 0"
SDWORD -3
EXIT SQLExecDirectW with return code 0 (SQL_SUCCESS)
HSTMT 0F8820F0
WCHAR * 0x2DFD61A8 [ -3] "INSERT INTO "dbo"."Events"
("EventMember") VALUES (?)\ 0"
SDWORD -3
ENTER SQLFreeStmt
HSTMT 0F8820F0
UWORD 3 <SQL_RESET_PARAMS>
EXIT SQLFreeStmt with return code 0 (SQL_SUCCESS)
HSTMT 0F8820F0
UWORD 3 <SQL_RESET_PARAMS>
ENTER SQLRowCount
HSTMT 0F8820F0
SQLLEN * 0x0C0FEBAC
EXIT SQLRowCount with return code 0 (SQL_SUCCESS)
HSTMT 0F8820F0
SQLLEN * 0x0C0FEBAC (1)
ENTER SQLFreeStmt
HSTMT 0F8820F0
UWORD 1 <SQL_DROP>
EXIT SQLFreeStmt with return code 0 (SQL_SUCCESS)
HSTMT 0F8820F0
UWORD 1 <SQL_DROP>
ENTER SQLAllocStmt
HDBC 0F881830
HSTMT * 0C0FE744
EXIT SQLAllocStmt with return code 0 (SQL_SUCCESS)
HDBC 0F881830
HSTMT * 0x0C0FE744 ( 0x0f8820f0)
ENTER SQLGetStmtOption
HSTMT 0F8820F0
UWORD 0
PTR 0x0C0FE6EC
EXIT SQLGetStmtOption with return code 0 (SQL_SUCCESS)
HSTMT 0F8820F0
UWORD 0
PTR 0x0C0FE6EC
ENTER SQLSetStmtOption
HSTMT 0F8820F0
UWORD 0 <SQL_QUERY_TIMEOUT>
SQLPOINTER 0x0000003C
EXIT SQLSetStmtOption with return code 0 (SQL_SUCCESS)
HSTMT 0F8820F0
UWORD 0 <SQL_QUERY_TIMEOUT>
SQLPOINTER 0x0000003C (BADMEM)
ENTER SQLExecDirectW
HSTMT 0F8820F0
WCHAR * 0x1B075CE0 [ -3] "SELECT @.@.IDENTITY\ 0"
SDWORD -3
EXIT SQLExecDirectW with return code 0 (SQL_SUCCESS)
HSTMT 0F8820F0
WCHAR * 0x1B075CE0 [ -3] "SELECT @.@.IDENTITY\ 0"
SDWORD -3
ENTER SQLFetch
HSTMT 0F8820F0
EXIT SQLFetch with return code 0 (SQL_SUCCESS)
HSTMT 0F8820F0
ENTER SQLGetData
HSTMT 0F8820F0
UWORD 1
SWORD 4 <SQL_C_LONG>
PTR <unknown type>
SQLLEN 4
SQLLEN * 0x0C0FE738
EXIT SQLGetData with return code 0 (SQL_SUCCESS)
HSTMT 0F8820F0
UWORD 1
SWORD 4 <SQL_C_LONG>
PTR <unknown type>
SQLLEN 4
SQLLEN * 0x0C0FE738 (4)
ENTER SQLFetch
HSTMT 0F8820F0
EXIT SQLFetch with return code 100 (SQL_NO_DATA_FOUND)
HSTMT 0F8820F0
ENTER SQLFreeStmt
HSTMT 0F8820F0
UWORD 0 <SQL_CLOSE>
EXIT SQLFreeStmt with return code 0 (SQL_SUCCESS)
HSTMT 0F8820F0
UWORD 0 <SQL_CLOSE>
ENTER SQLFreeStmt
HSTMT 0F8820F0
UWORD 1 <SQL_DROP>
EXIT SQLFreeStmt with return code 0 (SQL_SUCCESS)
HSTMT 0F8820F0
UWORD 1 <SQL_DROP>
ENTER SQLAllocConnect
HENV 0F881788
HDBC * 0C0FEBF0
EXIT SQLAllocConnect with return code 0 (SQL_SUCCESS)
HENV 0F881788
HDBC * 0x0C0FEBF0 ( 0x0f882af0)
ENTER SQLSetConnectOption
HDBC 0F882AF0
SQLINTEGER 103 <SQL_LOGIN_TIMEOUT>
SQLPOINTER 0x00000014
EXIT SQLSetConnectOption with return code 0 (SQL_SUCCESS)
HDBC 0F882AF0
SQLINTEGER 103 <SQL_LOGIN_TIMEOUT>
SQLPOINTER 0x00000014 (BADMEM)
ENTER SQLSetConnectAttrW
SQLHDBC 0F882AF0
SQLINTEGER 30002 <unknown>
SQLPOINTER [Unknown attribute 30002]
SQLINTEGER -3
EXIT SQLSetConnectAttrW with return code 0 (SQL_SUCCESS)
SQLHDBC 0F882AF0
SQLINTEGER 30002 <unknown>
SQLPOINTER [Unknown attribute 30002]
SQLINTEGER -3
ENTER SQLDriverConnectW
HDBC 0F882AF0
HWND 00000000
WCHAR * 0x4BF78088 [ -3] "******\ 0"
SWORD -3
WCHAR * 0x4BF78088
SWORD 2
SWORD * 0x00000000
UWORD 0 <SQL_DRIVER_NOPROMPT>
EXIT SQLDriverConnectW with return code 1 (SQL_SUCCESS_WITH_INFO)
HDBC 0F882AF0
HWND 00000000
WCHAR * 0x4BF78088 [ -3] "******\ 0"
SWORD -3
WCHAR * 0x4BF78088
SWORD 2
SWORD * 0x00000000
UWORD 0 <SQL_DRIVER_NOPROMPT>
DIAG [IM006] [Microsoft][ODBC Driver Manager] Driver's SQLSetCon
nectAttr
failed (0)
DIAG [01000] [Microsoft][ODBC SQL Server Driver][SQL Server]
Changed
database context to 'UAA'. (5701)
DIAG [01000] [Microsoft][ODBC SQL Server Driver][SQL Server]
Changed
language setting to us_english. (5703)
ENTER SQLGetInfoW
HDBC 0F882AF0
UWORD 9 <SQL_ODBC_API_CONFORMANCE>
PTR 0x0C0FEC14
SWORD 2
SWORD * 0x0C0FEC0C
EXIT SQLGetInfoW with return code 0 (SQL_SUCCESS)
HDBC 0F882AF0
UWORD 9 <SQL_ODBC_API_CONFORMANCE>
PTR 0x0C0FEC14 (2)
SWORD 2
SWORD * 0x0C0FEC0C (2)
ENTER SQLGetInfoW
HDBC 0F882AF0
UWORD 6 <SQL_DRIVER_NAME>
PTR 0x0C0FEB24
SWORD 200
SWORD * 0x0C0FEC0C
EXIT SQLGetInfoW with return code 0 (SQL_SUCCESS)
HDBC 0F882AF0
UWORD 6 <SQL_DRIVER_NAME>
PTR 0x0C0FEB24 [ 24] "SQLSRV32.DLL"
SWORD 200
SWORD * 0x0C0FEC0C (24)
ENTER SQLGetInfoW
HDBC 0F882AF0
UWORD 46 <SQL_TXN_CAPABLE>
PTR 0x0C0FEAEE
SWORD 2
SWORD * 0x0C0FE6C0
EXIT SQLGetInfoW with return code 0 (SQL_SUCCESS)
HDBC 0F882AF0
UWORD 46 <SQL_TXN_CAPABLE>
PTR 0x0C0FEAEE (2)
SWORD 2
SWORD * 0x0C0FE6C0 (2)
ENTER SQLGetInfoW
HDBC 0F882AF0
UWORD 23 <SQL_CURSOR_COMMIT_BEHAVIOR>
PTR 0x0E029C58
SWORD 2
SWORD * 0x0C0FE6C0
EXIT SQLGetInfoW with return code 0 (SQL_SUCCESS)
HDBC 0F882AF0
UWORD 23 <SQL_CURSOR_COMMIT_BEHAVIOR>
PTR 0x0E029C58 (1)
SWORD 2
SWORD * 0x0C0FE6C0 (2)
ENTER SQLGetInfoW
HDBC 0F882AF0
UWORD 24 <SQL_CURSOR_ROLLBACK_BEHAVIOR>
PTR 0x0E029C5A
SWORD 2
SWORD * 0x0C0FE6C0
EXIT SQLGetInfoW with return code 0 (SQL_SUCCESS)
HDBC 0F882AF0
UWORD 24 <SQL_CURSOR_ROLLBACK_BEHAVIOR>
PTR 0x0E029C5A (1)
SWORD 2
SWORD * 0x0C0FE6C0 (2)
ENTER SQLGetInfoW
HDBC 0F882AF0
UWORD 1 <SQL_ACTIVE_STATEMENTS>
PTR 0x0C0FEAF4
SWORD 2
SWORD * 0x0C0FEADA
EXIT SQLGetInfoW with return code 0 (SQL_SUCCESS)
HDBC 0F882AF0
UWORD 1 <SQL_ACTIVE_STATEMENTS>
PTR 0x0C0FEAF4 (1)
SWORD 2
SWORD * 0x0C0FEADA (2)
ENTER SQLSetConnectOption
HDBC 0F882AF0
SQLINTEGER 101 <SQL_ACCESS_MODE>
SQLPOINTER 0x00000001
EXIT SQLSetConnectOption with return code 0 (SQL_SUCCESS)
HDBC 0F882AF0
SQLINTEGER 101 <SQL_ACCESS_MODE>
SQLPOINTER 0x00000001 (BADMEM)
ENTER SQLGetInfoW
HDBC 0F882AF0
UWORD 17 <SQL_DBMS_NAME>
PTR 0x0C0FEB58
SWORD 200
SWORD * 0x0C0FEC22
EXIT SQLGetInfoW with return code 0 (SQL_SUCCESS)
HDBC 0F882AF0
UWORD 17 <SQL_DBMS_NAME>
PTR 0x0C0FEB58 [ 40] "Microsoft SQL Server"
SWORD 200
SWORD * 0x0C0FEC22 (40)
ENTER SQLSetConnectOption
HDBC 0F882AF0
SQLINTEGER 101 <SQL_ACCESS_MODE>
SQLPOINTER 0x00000001
EXIT SQLSetConnectOption with return code 0 (SQL_SUCCESS)
HDBC 0F882AF0
SQLINTEGER 101 <SQL_ACCESS_MODE>
SQLPOINTER 0x00000001 (BADMEM)
ENTER SQLSetConnectOption
HDBC 0F882AF0
SQLINTEGER 102 <SQL_AUTOCOMMIT>
SQLPOINTER 0x00000000
EXIT SQLSetConnectOption with return code 0 (SQL_SUCCESS)
HDBC 0F882AF0
SQLINTEGER 102 <SQL_AUTOCOMMIT>
SQLPOINTER 0x00000000
ENTER SQLAllocStmt
HDBC 0F882AF0
HSTMT * 320D2174
EXIT SQLAllocStmt with return code 0 (SQL_SUCCESS)
HDBC 0F882AF0
HSTMT * 0x320D2174 ( 0x0f8820f0)
ENTER SQLGetStmtOption
HSTMT 0F8820F0
UWORD 0
PTR 0x0C0FEB7C
EXIT SQLGetStmtOption with return code 0 (SQL_SUCCESS)
HSTMT 0F8820F0
UWORD 0
PTR 0x0C0FEB7C
ENTER SQLSetStmtOption
HSTMT 0F8820F0
UWORD 0 <SQL_QUERY_TIMEOUT>
SQLPOINTER 0x0000003C
EXIT SQLSetStmtOption with return code 0 (SQL_SUCCESS)
HSTMT 0F8820F0
UWORD 0 <SQL_QUERY_TIMEOUT>
SQLPOINTER 0x0000003C (BADMEM)
ENTER SQLGetStmtOption
HSTMT 0F8820F0
UWORD 3
PTR 0x0C0FEB7C
EXIT SQLGetStmtOption with return code 0 (SQL_SUCCESS)
HSTMT 0F8820F0
UWORD 3
PTR 0x0C0FEB7C
ENTER SQLSetStmtOption
HSTMT 0F8820F0
UWORD 3 <SQL_MAX_LENGTH>
SQLPOINTER 0x7FFFFFFF
EXIT SQLSetStmtOption with return code 0 (SQL_SUCCESS)
HSTMT 0F8820F0
UWORD 3 <SQL_MAX_LENGTH>
SQLPOINTER 0x7FFFFFFF (BADMEM)
ENTER SQLExecDirectW
HSTMT 0F8820F0
WCHAR * 0x320D2690 [ -3] "SELECT "EventKey" ,"EventMemb
er"
,"EventDateFrom" ,"EventDateTo" ,"EventType" ,"EventName" ,"EventDetails"
,"EventAttendanceHere" ,"EventAttendanceOut" ,"EventAttendanceNight"
,"EventCost" ,"EventCostHere" ,"EventCostOut" ,"EventRevenue"
,"EventRevenueIn" ,"EventColIn" ,"EventFamilies" ,"EventContactHrs"
,"EventMeals" ,"EventOtherOrg1" ,"EventOtherOrg2" ,"EventOtherOrg3"
,"EventOtherOrg4" ,"EventOtherOrg5" ,"EventVolunteers" ,"EventVolHrs"
,"EventOutcomeMeasure" ,"EventOutcomeWeight" ,"EventOutcomeNarrative" FROM
"dbo"."Events" WHERE ("EventKey" = 591 ) \ 0"
SDWORD -3
EXIT SQLExecDirectW with return code -1 (SQL_ERROR)
HSTMT 0F8820F0
WCHAR * 0x320D2690 [ -3] "SELECT "EventKey" ,"EventMemb
er"
,"EventDateFrom" ,"EventDateTo" ,"EventType" ,"EventName" ,"EventDetails"
,"EventAttendanceHere" ,"EventAttendanceOut" ,"EventAttendanceNight"
,"EventCost" ,"EventCostHere" ,"EventCostOut" ,"EventRevenue"
,"EventRevenueIn" ,"EventColIn" ,"EventFamilies" ,"EventContactHrs"
,"EventMeals" ,"EventOtherOrg1" ,"EventOtherOrg2" ,"EventOtherOrg3"
,"EventOtherOrg4" ,"EventOtherOrg5" ,"EventVolunteers" ,"EventVolHrs"
,"EventOutcomeMeasure" ,"EventOutcomeWeight" ,"EventOutcomeNarrative" FROM
"dbo"."Events" WHERE ("EventKey" = 591 ) \ 0"
SDWORD -3
DIAG [S1T00] [Microsoft][ODBC SQL Server Driver]Timeout expired
(0)
ENTER SQLErrorW
HENV 0F881788
HDBC 0F882AF0
HSTMT 0F8820F0
WCHAR * 0x0C0FEAE8 (NYI)
SDWORD * 0x0C0FEB34
WCHAR * 0x0DFD0048
SWORD 4095
SWORD * 0x0C0FEB20
EXIT SQLErrorW with return code 0 (SQL_SUCCESS)
HENV 0F881788
HDBC 0F882AF0
HSTMT 0F8820F0
WCHAR * 0x0C0FEAE8 (NYI)
SDWORD * 0x0C0FEB34 (0)
WCHAR * 0x0DFD0048 [ 50] "[Microsoft][ODBC SQL
Server
Driver]Timeout expired"
SWORD 4095
SWORD * 0x0C0FEB20 (50)
ENTER SQLErrorW
HENV 0F881788
HDBC 0F882AF0
HSTMT 0F8820F0
WCHAR * 0x0C0FEAE8 (NYI)
SDWORD * 0x0C0FEB34
WCHAR * 0x0DFD00BE
SWORD 4036
SWORD * 0x0C0FEB20
EXIT SQLErrorW with return code 100 (SQL_NO_DATA_FOUND)
HENV 0F881788
HDBC 0F882AF0
HSTMT 0F8820F0
WCHAR * 0x0C0FEAE8 (NYI)
SDWORD * 0x0C0FEB34
WCHAR * 0x0DFD00BE
SWORD 4036
SWORD * 0x0C0FEB20
ENTER SQLFreeStmt
HSTMT 0F8820F0
UWORD 1 <SQL_DROP>
EXIT SQLFreeStmt with return code 0 (SQL_SUCCESS)
HSTMT 0F8820F0
UWORD 1 <SQL_DROP>
ENTER SQLTransact
HENV 0F881788
HDBC 0F882AF0
UWORD 1 <SQL_ROLLBACK>
EXIT SQLTransact with return code 0 (SQL_SUCCESS)
HENV 0F881788
HDBC 0F882AF0
UWORD 1 <SQL_ROLLBACK>
ENTER SQLSetConnectOption
HDBC 0F882AF0
SQLINTEGER 102 <SQL_AUTOCOMMIT>
SQLPOINTER 0x00000001
EXIT SQLSetConnectOption with return code 0 (SQL_SUCCESS)
HDBC 0F882AF0
SQLINTEGER 102 <SQL_AUTOCOMMIT>
SQLPOINTER 0x00000001 (BADMEM)
ENTER SQLTransact
HENV 0F881788
HDBC 0F881830
UWORD 1 <SQL_ROLLBACK>
EXIT SQLTransact with return code 0 (SQL_SUCCESS)
HENV 0F881788
HDBC 0F881830
UWORD 1 <SQL_ROLLBACK>
ENTER SQLSetConnectOption
HDBC 0F881830
SQLINTEGER 102 <SQL_AUTOCOMMIT>
SQLPOINTER 0x00000001
EXIT SQLSetConnectOption with return code 0 (SQL_SUCCESS)
HDBC 0F881830
SQLINTEGER 102 <SQL_AUTOCOMMIT>
SQLPOINTER 0x00000001 (BADMEM)

MDAC 2.8 vs MDAC 2.7 SQL Server Driver - causing deadlocks

I have two computers, a Windows XP machine with MDAC 2.7 SP1 (sqlsrv32.dll
version 2000.81.9042.0) and a Windows Server 2003 machine with MDAC 2.8 SP2
for Server 2003 (sqlsrv32.dll version 2000.86.1830.0) as confirmed by MDAC
Component Checker.
They are both connecting to the same machine with SQL Server 2000 with SP4.
I am submitting the several SQL commands through .NET OleDb (Framework 1.1)
to a JET DB (Access 2003) with a linked table to SQL Server. I have also
connected to JET through ODBC in the past as well with the same results.
I am inserting a record into a linked table called "Events" with one
autonumbered IDENTITY column called EventKey.
I have started a transaction through the BeginTransaction .NET methods. I
submit the following SQL commands (.NET pseudo-code'ish):
ExecuteNonQuery("INSERT INTO Events (EventMember) VALUES (6)")
var key = ExecuteScalar("SELECT @.@.IDENTITY")
ExecuteQuery("SELECT * FROM Events WHERE EventKey = " & key)
The first two commands run successfully, but the third command fails with
the following error: "System.Data.OleDb.OleDbException: ODBC--call failed."
after about a minute timeout.
Upon checking SQL Enterprise Manager, there are two processes (one blocking,
one blocked). The blocking process last executed the "SELECT @.@.IDENTITY",
the blocked process executed the "select * from..." query. After a lock
timeout, the SELECT * query returns with that error.
My question is: why are TWO connections being made to SQL Server for the
same transaction? Since all three queries are coming from the same source
JET connection, of course that second connection to SQL server while the
first connection has that inserted record locked will fail to read it.
This works perfectly from MDAC 2.7, but fails every time with MDAC 2.8. I
have tried to go through the "List of bug fixes" KB articles, but nothing was
listed about a fix that I would think may break this idea other than
asynchronous fetching?
Any ideas - our application heavily uses this approach to insert new records
through ADO.NET and then select the records back during the same transaction.
Thanks,
Mike Dearman
Lead Software Engineer
I used the ODBC trace feature to obtain the following log. It definitely
shows the ODBC driver disconnecting then reconnecting between the SELECT
@.@.IDENTIY and the SELECT * commands. The weird thing is that it does a
SQLExecDirectW, then a fetch, then a getdata that all appears to be
successful. Then it does another fetch with return code 100
(SQL_NO_DATA_FOUND). After that, it seems to free the statement, and proceed
to call SQLAllocConnect again.
Here is the complete ODBC trace log for the three SQL commands (cleaned up a
bit though - log too long):
ENTER SQLAllocEnv
HENV * 0C0FE7B8
EXIT SQLAllocEnv with return code 0 (SQL_SUCCESS)
HENV * 0x0C0FE7B8 ( 0x0f881788)
ENTER SQLAllocConnect
HENV 0F881788
HDBC * 0C0FE8C8
EXIT SQLAllocConnect with return code 0 (SQL_SUCCESS)
HENV 0F881788
HDBC * 0x0C0FE8C8 ( 0x0f881830)
ENTER SQLSetConnectOption
HDBC 0F881830
SQLINTEGER 103 <SQL_LOGIN_TIMEOUT>
SQLPOINTER 0x00000014
EXIT SQLSetConnectOption with return code 0 (SQL_SUCCESS)
HDBC 0F881830
SQLINTEGER 103 <SQL_LOGIN_TIMEOUT>
SQLPOINTER 0x00000014 (BADMEM)
ENTER SQLSetConnectAttrW
SQLHDBC 0F881830
SQLINTEGER 30002 <unknown>
SQLPOINTER [Unknown attribute 30002]
SQLINTEGER -3
EXIT SQLSetConnectAttrW with return code 0 (SQL_SUCCESS)
SQLHDBC 0F881830
SQLINTEGER 30002 <unknown>
SQLPOINTER [Unknown attribute 30002]
SQLINTEGER -3
ENTER SQLDriverConnectW
HDBC 0F881830
HWND 00000000
WCHAR * 0x4BF78088 [ -3] "******\ 0"
SWORD -3
WCHAR * 0x4BF78088
SWORD 2
SWORD * 0x00000000
UWORD 0 <SQL_DRIVER_NOPROMPT>
EXIT SQLDriverConnectW with return code 1 (SQL_SUCCESS_WITH_INFO)
HDBC 0F881830
HWND 00000000
WCHAR * 0x4BF78088 [ -3] "******\ 0"
SWORD -3
WCHAR * 0x4BF78088
SWORD 2
SWORD * 0x00000000
UWORD 0 <SQL_DRIVER_NOPROMPT>
DIAG [IM006] [Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr
failed (0)
DIAG [01000] [Microsoft][ODBC SQL Server Driver][SQL Server]Changed
database context to 'UAA'. (5701)
DIAG [01000] [Microsoft][ODBC SQL Server Driver][SQL Server]Changed
language setting to us_english. (5703)
ENTER SQLGetInfoW
HDBC 0F881830
UWORD 9 <SQL_ODBC_API_CONFORMANCE>
PTR 0x0C0FE8EC
SWORD 2
SWORD * 0x0C0FE8E4
EXIT SQLGetInfoW with return code 0 (SQL_SUCCESS)
HDBC 0F881830
UWORD 9 <SQL_ODBC_API_CONFORMANCE>
PTR 0x0C0FE8EC (2)
SWORD 2
SWORD * 0x0C0FE8E4 (2)
ENTER SQLGetInfoW
HDBC 0F881830
UWORD 6 <SQL_DRIVER_NAME>
PTR 0x0C0FE7FC
SWORD 200
SWORD * 0x0C0FE8E4
EXIT SQLGetInfoW with return code 0 (SQL_SUCCESS)
HDBC 0F881830
UWORD 6 <SQL_DRIVER_NAME>
PTR 0x0C0FE7FC [ 24] "SQLSRV32.DLL"
SWORD 200
SWORD * 0x0C0FE8E4 (24)
ENTER SQLGetInfoW
HDBC 0F881830
UWORD 46 <SQL_TXN_CAPABLE>
PTR 0x0C0FE7C6
SWORD 2
SWORD * 0x0C0FE398
EXIT SQLGetInfoW with return code 0 (SQL_SUCCESS)
HDBC 0F881830
UWORD 46 <SQL_TXN_CAPABLE>
PTR 0x0C0FE7C6 (2)
SWORD 2
SWORD * 0x0C0FE398 (2)
ENTER SQLGetInfoW
HDBC 0F881830
UWORD 23 <SQL_CURSOR_COMMIT_BEHAVIOR>
PTR 0x0E029928
SWORD 2
SWORD * 0x0C0FE398
EXIT SQLGetInfoW with return code 0 (SQL_SUCCESS)
HDBC 0F881830
UWORD 23 <SQL_CURSOR_COMMIT_BEHAVIOR>
PTR 0x0E029928 (1)
SWORD 2
SWORD * 0x0C0FE398 (2)
ENTER SQLGetInfoW
HDBC 0F881830
UWORD 24 <SQL_CURSOR_ROLLBACK_BEHAVIOR>
PTR 0x0E02992A
SWORD 2
SWORD * 0x0C0FE398
EXIT SQLGetInfoW with return code 0 (SQL_SUCCESS)
HDBC 0F881830
UWORD 24 <SQL_CURSOR_ROLLBACK_BEHAVIOR>
PTR 0x0E02992A (1)
SWORD 2
SWORD * 0x0C0FE398 (2)
ENTER SQLGetInfoW
HDBC 0F881830
UWORD 1 <SQL_ACTIVE_STATEMENTS>
PTR 0x0C0FE7CC
SWORD 2
SWORD * 0x0C0FE7B2
EXIT SQLGetInfoW with return code 0 (SQL_SUCCESS)
HDBC 0F881830
UWORD 1 <SQL_ACTIVE_STATEMENTS>
PTR 0x0C0FE7CC (1)
SWORD 2
SWORD * 0x0C0FE7B2 (2)
ENTER SQLSetConnectOption
HDBC 0F881830
SQLINTEGER 101 <SQL_ACCESS_MODE>
SQLPOINTER 0x00000000
EXIT SQLSetConnectOption with return code 0 (SQL_SUCCESS)
HDBC 0F881830
SQLINTEGER 101 <SQL_ACCESS_MODE>
SQLPOINTER 0x00000000
ENTER SQLAllocStmt
HDBC 0F881830
HSTMT * 0C0FE390
EXIT SQLAllocStmt with return code 0 (SQL_SUCCESS)
HDBC 0F881830
HSTMT * 0x0C0FE390 ( 0x0f8820f0)
ENTER SQLGetStmtOption
HSTMT 0F8820F0
UWORD 0
PTR 0x0C0FE33C
EXIT SQLGetStmtOption with return code 0 (SQL_SUCCESS)
HSTMT 0F8820F0
UWORD 0
PTR 0x0C0FE33C
ENTER SQLSetStmtOption
HSTMT 0F8820F0
UWORD 0 <SQL_QUERY_TIMEOUT>
SQLPOINTER 0x0000003C
EXIT SQLSetStmtOption with return code 0 (SQL_SUCCESS)
HSTMT 0F8820F0
UWORD 0 <SQL_QUERY_TIMEOUT>
SQLPOINTER 0x0000003C (BADMEM)
ENTER SQLExecDirectW
HSTMT 0F8820F0
WCHAR * 0x1B074AA0 [ -3] "SELECT Config, nValue FROM
MSysConf\ 0"
SDWORD -3
EXIT SQLExecDirectW with return code -1 (SQL_ERROR)
HSTMT 0F8820F0
WCHAR * 0x1B074AA0 [ -3] "SELECT Config, nValue FROM
MSysConf\ 0"
SDWORD -3
DIAG [S0002] [Microsoft][ODBC SQL Server Driver][SQL Server]Invalid object
name 'MSysConf'. (208)
ENTER SQLErrorW
HENV 0F881788
HDBC 0F881830
HSTMT 0F8820F0
WCHAR * 0x0C0FE2D0 (NYI)
SDWORD * 0x0C0FE31C
WCHAR * 0x0DFD0048
SWORD 4095
SWORD * 0x0C0FE308
EXIT SQLErrorW with return code 0 (SQL_SUCCESS)
HENV 0F881788
HDBC 0F881830
HSTMT 0F8820F0
WCHAR * 0x0C0FE2D0 (NYI)
SDWORD * 0x0C0FE31C (208)
WCHAR * 0x0DFD0048 [ 78] "[Microsoft][ODBC SQL Server
Driver][SQL Server]Invalid object name 'MSysConf'."
SWORD 4095
SWORD * 0x0C0FE308 (78)
ENTER SQLErrorW
HENV 0F881788
HDBC 0F881830
HSTMT 0F8820F0
WCHAR * 0x0C0FE2D0 (NYI)
SDWORD * 0x0C0FE31C
WCHAR * 0x0DFD00FA
SWORD 4006
SWORD * 0x0C0FE308
EXIT SQLErrorW with return code 100 (SQL_NO_DATA_FOUND)
HENV 0F881788
HDBC 0F881830
HSTMT 0F8820F0
WCHAR * 0x0C0FE2D0 (NYI)
SDWORD * 0x0C0FE31C
WCHAR * 0x0DFD00FA
SWORD 4006
SWORD * 0x0C0FE308
ENTER SQLFreeStmt
HSTMT 0F8820F0
UWORD 1 <SQL_DROP>
EXIT SQLFreeStmt with return code 0 (SQL_SUCCESS)
HSTMT 0F8820F0
UWORD 1 <SQL_DROP>
ENTER SQLGetInfoW
HDBC 0F881830
UWORD 17 <SQL_DBMS_NAME>
PTR 0x0C0FDFC4
SWORD 200
SWORD * 0x0C0FE08E
EXIT SQLGetInfoW with return code 0 (SQL_SUCCESS)
HDBC 0F881830
UWORD 17 <SQL_DBMS_NAME>
PTR 0x0C0FDFC4 [ 40] "Microsoft SQL Server"
SWORD 200
SWORD * 0x0C0FE08E (40)
ENTER SQLGetInfoW
HDBC 0F881830
UWORD 0 <SQL_ACTIVE_CONNECTIONS>
PTR 0x0C0FE0D2
SWORD 2
SWORD * 0x0C0FE0E0
EXIT SQLGetInfoW with return code 0 (SQL_SUCCESS)
HDBC 0F881830
UWORD 0 <SQL_ACTIVE_CONNECTIONS>
PTR 0x0C0FE0D2 (0)
SWORD 2
SWORD * 0x0C0FE0E0 (2)
ENTER SQLGetInfoW
HDBC 0F881830
UWORD 25 <SQL_DATA_SOURCE_READ_ONLY>
PTR 0x0C0FE0B8
SWORD 20
SWORD * 0x0C0FE0E0
EXIT SQLGetInfoW with return code 0 (SQL_SUCCESS)
HDBC 0F881830
UWORD 25 <SQL_DATA_SOURCE_READ_ONLY>
PTR 0x0C0FE0B8 [ 2] "N"
SWORD 20
SWORD * 0x0C0FE0E0 (2)
ENTER SQLGetInfoW
HDBC 0F881830
UWORD 46 <SQL_TXN_CAPABLE>
PTR 0x0C0FE0D0
SWORD 2
SWORD * 0x0C0FE0A0
EXIT SQLGetInfoW with return code 0 (SQL_SUCCESS)
HDBC 0F881830
UWORD 46 <SQL_TXN_CAPABLE>
PTR 0x0C0FE0D0 (2)
SWORD 2
SWORD * 0x0C0FE0A0 (2)
ENTER SQLGetInfoW
HDBC 0F881830
UWORD 23 <SQL_CURSOR_COMMIT_BEHAVIOR>
PTR 0x0C0FE0CC
SWORD 2
SWORD * 0x0C0FE0A0
EXIT SQLGetInfoW with return code 0 (SQL_SUCCESS)
HDBC 0F881830
UWORD 23 <SQL_CURSOR_COMMIT_BEHAVIOR>
PTR 0x0C0FE0CC (1)
SWORD 2
SWORD * 0x0C0FE0A0 (2)
ENTER SQLGetInfoW
HDBC 0F881830
UWORD 24 <SQL_CURSOR_ROLLBACK_BEHAVIOR>
PTR 0x0C0FE0CE
SWORD 2
SWORD * 0x0C0FE0A0
EXIT SQLGetInfoW with return code 0 (SQL_SUCCESS)
HDBC 0F881830
UWORD 24 <SQL_CURSOR_ROLLBACK_BEHAVIOR>
PTR 0x0C0FE0CE (1)
SWORD 2
SWORD * 0x0C0FE0A0 (2)
ENTER SQLGetInfoW
HDBC 0F881830
UWORD 29 <SQL_IDENTIFIER_QUOTE_CHAR>
PTR 0x0C0FE0B8
SWORD 20
SWORD * 0x0C0FE0E0
EXIT SQLGetInfoW with return code 0 (SQL_SUCCESS)
HDBC 0F881830
UWORD 29 <SQL_IDENTIFIER_QUOTE_CHAR>
PTR 0x0C0FE0B8 [ 2] """
SWORD 20
SWORD * 0x0C0FE0E0 (2)
ENTER SQLSetConnectOption
HDBC 0F881830
SQLINTEGER 102 <SQL_AUTOCOMMIT>
SQLPOINTER 0x00000000
EXIT SQLSetConnectOption with return code 0 (SQL_SUCCESS)
HDBC 0F881830
SQLINTEGER 102 <SQL_AUTOCOMMIT>
SQLPOINTER 0x00000000
ENTER SQLAllocStmt
HDBC 0F881830
HSTMT * 0C0FEBD8
EXIT SQLAllocStmt with return code 0 (SQL_SUCCESS)
HDBC 0F881830
HSTMT * 0x0C0FEBD8 ( 0x0f8820f0)
ENTER SQLGetStmtOption
HSTMT 0F8820F0
UWORD 0
PTR 0x0C0FE718
EXIT SQLGetStmtOption with return code 0 (SQL_SUCCESS)
HSTMT 0F8820F0
UWORD 0
PTR 0x0C0FE718
ENTER SQLSetStmtOption
HSTMT 0F8820F0
UWORD 0 <SQL_QUERY_TIMEOUT>
SQLPOINTER 0x0000003C
EXIT SQLSetStmtOption with return code 0 (SQL_SUCCESS)
HSTMT 0F8820F0
UWORD 0 <SQL_QUERY_TIMEOUT>
SQLPOINTER 0x0000003C (BADMEM)
ENTER SQLBindParameter
HSTMT 0F8820F0
UWORD 1
SWORD 1 <SQL_PARAM_INPUT>
SWORD 4 <SQL_C_LONG>
SWORD 4 <SQL_INTEGER>
SQLULEN 10
SWORD 0
PTR 0x2DFD41A4
SQLLEN 0
SQLLEN * 0x2DFD41A0
EXIT SQLBindParameter with return code 0 (SQL_SUCCESS)
HSTMT 0F8820F0
UWORD 1
SWORD 1 <SQL_PARAM_INPUT>
SWORD 4 <SQL_C_LONG>
SWORD 4 <SQL_INTEGER>
SQLULEN 10
SWORD 0
PTR 0x2DFD41A4
SQLLEN 0
SQLLEN * 0x2DFD41A0 (4)
ENTER SQLExecDirectW
HSTMT 0F8820F0
WCHAR * 0x2DFD61A8 [ -3] "INSERT INTO "dbo"."Events"
("EventMember") VALUES (?)\ 0"
SDWORD -3
EXIT SQLExecDirectW with return code 0 (SQL_SUCCESS)
HSTMT 0F8820F0
WCHAR * 0x2DFD61A8 [ -3] "INSERT INTO "dbo"."Events"
("EventMember") VALUES (?)\ 0"
SDWORD -3
ENTER SQLFreeStmt
HSTMT 0F8820F0
UWORD 3 <SQL_RESET_PARAMS>
EXIT SQLFreeStmt with return code 0 (SQL_SUCCESS)
HSTMT 0F8820F0
UWORD 3 <SQL_RESET_PARAMS>
ENTER SQLRowCount
HSTMT 0F8820F0
SQLLEN * 0x0C0FEBAC
EXIT SQLRowCount with return code 0 (SQL_SUCCESS)
HSTMT 0F8820F0
SQLLEN * 0x0C0FEBAC (1)
ENTER SQLFreeStmt
HSTMT 0F8820F0
UWORD 1 <SQL_DROP>
EXIT SQLFreeStmt with return code 0 (SQL_SUCCESS)
HSTMT 0F8820F0
UWORD 1 <SQL_DROP>
ENTER SQLAllocStmt
HDBC 0F881830
HSTMT * 0C0FE744
EXIT SQLAllocStmt with return code 0 (SQL_SUCCESS)
HDBC 0F881830
HSTMT * 0x0C0FE744 ( 0x0f8820f0)
ENTER SQLGetStmtOption
HSTMT 0F8820F0
UWORD 0
PTR 0x0C0FE6EC
EXIT SQLGetStmtOption with return code 0 (SQL_SUCCESS)
HSTMT 0F8820F0
UWORD 0
PTR 0x0C0FE6EC
ENTER SQLSetStmtOption
HSTMT 0F8820F0
UWORD 0 <SQL_QUERY_TIMEOUT>
SQLPOINTER 0x0000003C
EXIT SQLSetStmtOption with return code 0 (SQL_SUCCESS)
HSTMT 0F8820F0
UWORD 0 <SQL_QUERY_TIMEOUT>
SQLPOINTER 0x0000003C (BADMEM)
ENTER SQLExecDirectW
HSTMT 0F8820F0
WCHAR * 0x1B075CE0 [ -3] "SELECT @.@.IDENTITY\ 0"
SDWORD -3
EXIT SQLExecDirectW with return code 0 (SQL_SUCCESS)
HSTMT 0F8820F0
WCHAR * 0x1B075CE0 [ -3] "SELECT @.@.IDENTITY\ 0"
SDWORD -3
ENTER SQLFetch
HSTMT 0F8820F0
EXIT SQLFetch with return code 0 (SQL_SUCCESS)
HSTMT 0F8820F0
ENTER SQLGetData
HSTMT 0F8820F0
UWORD 1
SWORD 4 <SQL_C_LONG>
PTR <unknown type>
SQLLEN 4
SQLLEN * 0x0C0FE738
EXIT SQLGetData with return code 0 (SQL_SUCCESS)
HSTMT 0F8820F0
UWORD 1
SWORD 4 <SQL_C_LONG>
PTR <unknown type>
SQLLEN 4
SQLLEN * 0x0C0FE738 (4)
ENTER SQLFetch
HSTMT 0F8820F0
EXIT SQLFetch with return code 100 (SQL_NO_DATA_FOUND)
HSTMT 0F8820F0
ENTER SQLFreeStmt
HSTMT 0F8820F0
UWORD 0 <SQL_CLOSE>
EXIT SQLFreeStmt with return code 0 (SQL_SUCCESS)
HSTMT 0F8820F0
UWORD 0 <SQL_CLOSE>
ENTER SQLFreeStmt
HSTMT 0F8820F0
UWORD 1 <SQL_DROP>
EXIT SQLFreeStmt with return code 0 (SQL_SUCCESS)
HSTMT 0F8820F0
UWORD 1 <SQL_DROP>
ENTER SQLAllocConnect
HENV 0F881788
HDBC * 0C0FEBF0
EXIT SQLAllocConnect with return code 0 (SQL_SUCCESS)
HENV 0F881788
HDBC * 0x0C0FEBF0 ( 0x0f882af0)
ENTER SQLSetConnectOption
HDBC 0F882AF0
SQLINTEGER 103 <SQL_LOGIN_TIMEOUT>
SQLPOINTER 0x00000014
EXIT SQLSetConnectOption with return code 0 (SQL_SUCCESS)
HDBC 0F882AF0
SQLINTEGER 103 <SQL_LOGIN_TIMEOUT>
SQLPOINTER 0x00000014 (BADMEM)
ENTER SQLSetConnectAttrW
SQLHDBC 0F882AF0
SQLINTEGER 30002 <unknown>
SQLPOINTER [Unknown attribute 30002]
SQLINTEGER -3
EXIT SQLSetConnectAttrW with return code 0 (SQL_SUCCESS)
SQLHDBC 0F882AF0
SQLINTEGER 30002 <unknown>
SQLPOINTER [Unknown attribute 30002]
SQLINTEGER -3
ENTER SQLDriverConnectW
HDBC 0F882AF0
HWND 00000000
WCHAR * 0x4BF78088 [ -3] "******\ 0"
SWORD -3
WCHAR * 0x4BF78088
SWORD 2
SWORD * 0x00000000
UWORD 0 <SQL_DRIVER_NOPROMPT>
EXIT SQLDriverConnectW with return code 1 (SQL_SUCCESS_WITH_INFO)
HDBC 0F882AF0
HWND 00000000
WCHAR * 0x4BF78088 [ -3] "******\ 0"
SWORD -3
WCHAR * 0x4BF78088
SWORD 2
SWORD * 0x00000000
UWORD 0 <SQL_DRIVER_NOPROMPT>
DIAG [IM006] [Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr
failed (0)
DIAG [01000] [Microsoft][ODBC SQL Server Driver][SQL Server]Changed
database context to 'UAA'. (5701)
DIAG [01000] [Microsoft][ODBC SQL Server Driver][SQL Server]Changed
language setting to us_english. (5703)
ENTER SQLGetInfoW
HDBC 0F882AF0
UWORD 9 <SQL_ODBC_API_CONFORMANCE>
PTR 0x0C0FEC14
SWORD 2
SWORD * 0x0C0FEC0C
EXIT SQLGetInfoW with return code 0 (SQL_SUCCESS)
HDBC 0F882AF0
UWORD 9 <SQL_ODBC_API_CONFORMANCE>
PTR 0x0C0FEC14 (2)
SWORD 2
SWORD * 0x0C0FEC0C (2)
ENTER SQLGetInfoW
HDBC 0F882AF0
UWORD 6 <SQL_DRIVER_NAME>
PTR 0x0C0FEB24
SWORD 200
SWORD * 0x0C0FEC0C
EXIT SQLGetInfoW with return code 0 (SQL_SUCCESS)
HDBC 0F882AF0
UWORD 6 <SQL_DRIVER_NAME>
PTR 0x0C0FEB24 [ 24] "SQLSRV32.DLL"
SWORD 200
SWORD * 0x0C0FEC0C (24)
ENTER SQLGetInfoW
HDBC 0F882AF0
UWORD 46 <SQL_TXN_CAPABLE>
PTR 0x0C0FEAEE
SWORD 2
SWORD * 0x0C0FE6C0
EXIT SQLGetInfoW with return code 0 (SQL_SUCCESS)
HDBC 0F882AF0
UWORD 46 <SQL_TXN_CAPABLE>
PTR 0x0C0FEAEE (2)
SWORD 2
SWORD * 0x0C0FE6C0 (2)
ENTER SQLGetInfoW
HDBC 0F882AF0
UWORD 23 <SQL_CURSOR_COMMIT_BEHAVIOR>
PTR 0x0E029C58
SWORD 2
SWORD * 0x0C0FE6C0
EXIT SQLGetInfoW with return code 0 (SQL_SUCCESS)
HDBC 0F882AF0
UWORD 23 <SQL_CURSOR_COMMIT_BEHAVIOR>
PTR 0x0E029C58 (1)
SWORD 2
SWORD * 0x0C0FE6C0 (2)
ENTER SQLGetInfoW
HDBC 0F882AF0
UWORD 24 <SQL_CURSOR_ROLLBACK_BEHAVIOR>
PTR 0x0E029C5A
SWORD 2
SWORD * 0x0C0FE6C0
EXIT SQLGetInfoW with return code 0 (SQL_SUCCESS)
HDBC 0F882AF0
UWORD 24 <SQL_CURSOR_ROLLBACK_BEHAVIOR>
PTR 0x0E029C5A (1)
SWORD 2
SWORD * 0x0C0FE6C0 (2)
ENTER SQLGetInfoW
HDBC 0F882AF0
UWORD 1 <SQL_ACTIVE_STATEMENTS>
PTR 0x0C0FEAF4
SWORD 2
SWORD * 0x0C0FEADA
EXIT SQLGetInfoW with return code 0 (SQL_SUCCESS)
HDBC 0F882AF0
UWORD 1 <SQL_ACTIVE_STATEMENTS>
PTR 0x0C0FEAF4 (1)
SWORD 2
SWORD * 0x0C0FEADA (2)
ENTER SQLSetConnectOption
HDBC 0F882AF0
SQLINTEGER 101 <SQL_ACCESS_MODE>
SQLPOINTER 0x00000001
EXIT SQLSetConnectOption with return code 0 (SQL_SUCCESS)
HDBC 0F882AF0
SQLINTEGER 101 <SQL_ACCESS_MODE>
SQLPOINTER 0x00000001 (BADMEM)
ENTER SQLGetInfoW
HDBC 0F882AF0
UWORD 17 <SQL_DBMS_NAME>
PTR 0x0C0FEB58
SWORD 200
SWORD * 0x0C0FEC22
EXIT SQLGetInfoW with return code 0 (SQL_SUCCESS)
HDBC 0F882AF0
UWORD 17 <SQL_DBMS_NAME>
PTR 0x0C0FEB58 [ 40] "Microsoft SQL Server"
SWORD 200
SWORD * 0x0C0FEC22 (40)
ENTER SQLSetConnectOption
HDBC 0F882AF0
SQLINTEGER 101 <SQL_ACCESS_MODE>
SQLPOINTER 0x00000001
EXIT SQLSetConnectOption with return code 0 (SQL_SUCCESS)
HDBC 0F882AF0
SQLINTEGER 101 <SQL_ACCESS_MODE>
SQLPOINTER 0x00000001 (BADMEM)
ENTER SQLSetConnectOption
HDBC 0F882AF0
SQLINTEGER 102 <SQL_AUTOCOMMIT>
SQLPOINTER 0x00000000
EXIT SQLSetConnectOption with return code 0 (SQL_SUCCESS)
HDBC 0F882AF0
SQLINTEGER 102 <SQL_AUTOCOMMIT>
SQLPOINTER 0x00000000
ENTER SQLAllocStmt
HDBC 0F882AF0
HSTMT * 320D2174
EXIT SQLAllocStmt with return code 0 (SQL_SUCCESS)
HDBC 0F882AF0
HSTMT * 0x320D2174 ( 0x0f8820f0)
ENTER SQLGetStmtOption
HSTMT 0F8820F0
UWORD 0
PTR 0x0C0FEB7C
EXIT SQLGetStmtOption with return code 0 (SQL_SUCCESS)
HSTMT 0F8820F0
UWORD 0
PTR 0x0C0FEB7C
ENTER SQLSetStmtOption
HSTMT 0F8820F0
UWORD 0 <SQL_QUERY_TIMEOUT>
SQLPOINTER 0x0000003C
EXIT SQLSetStmtOption with return code 0 (SQL_SUCCESS)
HSTMT 0F8820F0
UWORD 0 <SQL_QUERY_TIMEOUT>
SQLPOINTER 0x0000003C (BADMEM)
ENTER SQLGetStmtOption
HSTMT 0F8820F0
UWORD 3
PTR 0x0C0FEB7C
EXIT SQLGetStmtOption with return code 0 (SQL_SUCCESS)
HSTMT 0F8820F0
UWORD 3
PTR 0x0C0FEB7C
ENTER SQLSetStmtOption
HSTMT 0F8820F0
UWORD 3 <SQL_MAX_LENGTH>
SQLPOINTER 0x7FFFFFFF
EXIT SQLSetStmtOption with return code 0 (SQL_SUCCESS)
HSTMT 0F8820F0
UWORD 3 <SQL_MAX_LENGTH>
SQLPOINTER 0x7FFFFFFF (BADMEM)
ENTER SQLExecDirectW
HSTMT 0F8820F0
WCHAR * 0x320D2690 [ -3] "SELECT "EventKey" ,"EventMember"
,"EventDateFrom" ,"EventDateTo" ,"EventType" ,"EventName" ,"EventDetails"
,"EventAttendanceHere" ,"EventAttendanceOut" ,"EventAttendanceNight"
,"EventCost" ,"EventCostHere" ,"EventCostOut" ,"EventRevenue"
,"EventRevenueIn" ,"EventColIn" ,"EventFamilies" ,"EventContactHrs"
,"EventMeals" ,"EventOtherOrg1" ,"EventOtherOrg2" ,"EventOtherOrg3"
,"EventOtherOrg4" ,"EventOtherOrg5" ,"EventVolunteers" ,"EventVolHrs"
,"EventOutcomeMeasure" ,"EventOutcomeWeight" ,"EventOutcomeNarrative" FROM
"dbo"."Events" WHERE ("EventKey" = 591 ) \ 0"
SDWORD -3
EXIT SQLExecDirectW with return code -1 (SQL_ERROR)
HSTMT 0F8820F0
WCHAR * 0x320D2690 [ -3] "SELECT "EventKey" ,"EventMember"
,"EventDateFrom" ,"EventDateTo" ,"EventType" ,"EventName" ,"EventDetails"
,"EventAttendanceHere" ,"EventAttendanceOut" ,"EventAttendanceNight"
,"EventCost" ,"EventCostHere" ,"EventCostOut" ,"EventRevenue"
,"EventRevenueIn" ,"EventColIn" ,"EventFamilies" ,"EventContactHrs"
,"EventMeals" ,"EventOtherOrg1" ,"EventOtherOrg2" ,"EventOtherOrg3"
,"EventOtherOrg4" ,"EventOtherOrg5" ,"EventVolunteers" ,"EventVolHrs"
,"EventOutcomeMeasure" ,"EventOutcomeWeight" ,"EventOutcomeNarrative" FROM
"dbo"."Events" WHERE ("EventKey" = 591 ) \ 0"
SDWORD -3
DIAG [S1T00] [Microsoft][ODBC SQL Server Driver]Timeout expired (0)
ENTER SQLErrorW
HENV 0F881788
HDBC 0F882AF0
HSTMT 0F8820F0
WCHAR * 0x0C0FEAE8 (NYI)
SDWORD * 0x0C0FEB34
WCHAR * 0x0DFD0048
SWORD 4095
SWORD * 0x0C0FEB20
EXIT SQLErrorW with return code 0 (SQL_SUCCESS)
HENV 0F881788
HDBC 0F882AF0
HSTMT 0F8820F0
WCHAR * 0x0C0FEAE8 (NYI)
SDWORD * 0x0C0FEB34 (0)
WCHAR * 0x0DFD0048 [ 50] "[Microsoft][ODBC SQL Server
Driver]Timeout expired"
SWORD 4095
SWORD * 0x0C0FEB20 (50)
ENTER SQLErrorW
HENV 0F881788
HDBC 0F882AF0
HSTMT 0F8820F0
WCHAR * 0x0C0FEAE8 (NYI)
SDWORD * 0x0C0FEB34
WCHAR * 0x0DFD00BE
SWORD 4036
SWORD * 0x0C0FEB20
EXIT SQLErrorW with return code 100 (SQL_NO_DATA_FOUND)
HENV 0F881788
HDBC 0F882AF0
HSTMT 0F8820F0
WCHAR * 0x0C0FEAE8 (NYI)
SDWORD * 0x0C0FEB34
WCHAR * 0x0DFD00BE
SWORD 4036
SWORD * 0x0C0FEB20
ENTER SQLFreeStmt
HSTMT 0F8820F0
UWORD 1 <SQL_DROP>
EXIT SQLFreeStmt with return code 0 (SQL_SUCCESS)
HSTMT 0F8820F0
UWORD 1 <SQL_DROP>
ENTER SQLTransact
HENV 0F881788
HDBC 0F882AF0
UWORD 1 <SQL_ROLLBACK>
EXIT SQLTransact with return code 0 (SQL_SUCCESS)
HENV 0F881788
HDBC 0F882AF0
UWORD 1 <SQL_ROLLBACK>
ENTER SQLSetConnectOption
HDBC 0F882AF0
SQLINTEGER 102 <SQL_AUTOCOMMIT>
SQLPOINTER 0x00000001
EXIT SQLSetConnectOption with return code 0 (SQL_SUCCESS)
HDBC 0F882AF0
SQLINTEGER 102 <SQL_AUTOCOMMIT>
SQLPOINTER 0x00000001 (BADMEM)
ENTER SQLTransact
HENV 0F881788
HDBC 0F881830
UWORD 1 <SQL_ROLLBACK>
EXIT SQLTransact with return code 0 (SQL_SUCCESS)
HENV 0F881788
HDBC 0F881830
UWORD 1 <SQL_ROLLBACK>
ENTER SQLSetConnectOption
HDBC 0F881830
SQLINTEGER 102 <SQL_AUTOCOMMIT>
SQLPOINTER 0x00000001
EXIT SQLSetConnectOption with return code 0 (SQL_SUCCESS)
HDBC 0F881830
SQLINTEGER 102 <SQL_AUTOCOMMIT>
SQLPOINTER 0x00000001 (BADMEM)
sql