Showing posts with label installed. Show all posts

Friday, March 30, 2012

Mdac Xp 2000

My Development machine is Win XP Pro.
I have MDAC 2.7, Visual Studio 6.0 SP3 Installed.

I am running into some issues where a vb program i wrote runs perfectly fine (Using ADO) when connecting to sql server but only runs fine on half of the windows 2000 machines i tested on.

Anyone have any suggestions? even stranger is that the versions of the odbc driver on the 2000 box are newer than the versions on my xp box with MDAC 2.7 SP1 installed.

All machines have DSN's set up exactly the same. I even tested with a DSN'less connection just to be sure (same result).Refer to event viewer logs for any kind of information in this regard.

MDAC version

Hi
How can I find out what version of MDAC is installed on a Machine.
And would there be any problem with me installing both MDAC 2.7 and 2.8 on
the same machine
Ian
> How can I find out what version of MDAC is installed on a Machine.
http://www.aspfaq.com/2057

> And would there be any problem with me installing both MDAC 2.7 and 2.8 on
> the same machine
Installing 2.8 should upgrade 2.7 to 2.8.
http://www.aspfaq.com/
(Reverse address to reply.)
|||Thanks Aaron
But i was reading that MDAC 2.8 does not have the JET drivers and my
application needs them as well as the MS SQL drivers.
So do i install both?
Ian
"Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
news:ub99mydiEHA.1344@.TK2MSFTNGP11.phx.gbl...[vbcol=seagreen]
> http://www.aspfaq.com/2057
on
> Installing 2.8 should upgrade 2.7 to 2.8.
> --
> http://www.aspfaq.com/
> (Reverse address to reply.)
>
|||No, you don't need to install 2.7 and 2.8. You need to install MDAC 2.8 and
then install newer jet drivers separately.
http://www.aspfaq.com/2342
http://www.aspfaq.com/
(Reverse address to reply.)
"Ian" <ian@.NoWhere.com> wrote in message
news:uotFj7diEHA.384@.TK2MSFTNGP10.phx.gbl...
> Thanks Aaron
> But i was reading that MDAC 2.8 does not have the JET drivers and my
> application needs them as well as the MS SQL drivers.
>
> So do i install both?
|||Ian wrote:

> Hi
> How can I find out what version of MDAC is installed on a Machine.
> And would there be any problem with me installing both MDAC 2.7 and 2.8 on
> the same machine
> Ian
I use this approach:
Private Sub mnuHelpMDAC_Click()
Dim ans As String
ans = GetAdoVersion
If ans = "0" Then
MsgBox "MDAC is not Installed" & _
"Please Install MDAC from the DBAdmin CD", _
vbCritical, "Missing Important Component"
Else
MsgBox "MDAC version " & ans & " Is Installed on this System"
End If
End Sub
Function GetAdoVersion() As String
'Retrieve ADO (MDAC) version - see if it installed
'Returns an empty string is ADO is not installed
Dim o As Object
On Error Resume Next
GetAdoVersion = "0"
Set o = CreateObject("ADODB.Connection")
If Err.Number = 0 Then GetAdoVersion = o.Version
Set o = Nothing
End Function
|||MDAC 2.7 doesn't have the Jet drivers either: MDAC 2.5 was the last version
that did.
In any case, Aaron gave you the correct answer
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no e-mails, please!)
"Ian" <ian@.NoWhere.com> wrote in message
news:uotFj7diEHA.384@.TK2MSFTNGP10.phx.gbl...[vbcol=seagreen]
> Thanks Aaron
> But i was reading that MDAC 2.8 does not have the JET drivers and my
> application needs them as well as the MS SQL drivers.
>
> So do i install both?
> Ian
>
>
> "Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
> news:ub99mydiEHA.1344@.TK2MSFTNGP11.phx.gbl...
2.8
> on
>
|||Thank you all
For the advice.
"Ian" <ian@.NoWhere.com> wrote in message
news:u4iDeidiEHA.3016@.tk2msftngp13.phx.gbl...
> Hi
> How can I find out what version of MDAC is installed on a Machine.
> And would there be any problem with me installing both MDAC 2.7 and 2.8 on
> the same machine
> Ian
>
|||And to offer some more advice, unless there is a compelling reason to use
ADO 2.6 or greater, just reference ADO 2.5 and redistribute MDAC 2.5. That
way, the Jet components are included and, if not present, should get
installed even if MDAC 2.6 or greater is already installed. At least, I'm
pretty sure about that. I'm sure someone will correct me if I'm wrong.
Mike
"Douglas J. Steele" <NOSPAM_djsteele@.NOSPAM_canada.com> wrote in message
news:untEKfiiEHA.1104@.TK2MSFTNGP10.phx.gbl...
> MDAC 2.7 doesn't have the Jet drivers either: MDAC 2.5 was the last
version
> that did.
> In any case, Aaron gave you the correct answer
> --
> Doug Steele, Microsoft Access MVP
> http://I.Am/DougSteele
> (no e-mails, please!)
>
> "Ian" <ian@.NoWhere.com> wrote in message
> news:uotFj7diEHA.384@.TK2MSFTNGP10.phx.gbl...
> 2.8
>

MDAC version

Hi
How can I find out what version of MDAC is installed on a Machine.
And would there be any problem with me installing both MDAC 2.7 and 2.8 on
the same machine
Ian> How can I find out what version of MDAC is installed on a Machine.
http://www.aspfaq.com/2057

> And would there be any problem with me installing both MDAC 2.7 and 2.8 on
> the same machine
Installing 2.8 should upgrade 2.7 to 2.8.
http://www.aspfaq.com/
(Reverse address to reply.)|||Thanks Aaron
But i was reading that MDAC 2.8 does not have the JET drivers and my
application needs them as well as the MS SQL drivers.
So do i install both?
Ian
"Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
news:ub99mydiEHA.1344@.TK2MSFTNGP11.phx.gbl...
> http://www.aspfaq.com/2057
>
on[vbcol=seagreen]
> Installing 2.8 should upgrade 2.7 to 2.8.
> --
> http://www.aspfaq.com/
> (Reverse address to reply.)
>|||No, you don't need to install 2.7 and 2.8. You need to install MDAC 2.8 and
then install newer jet drivers separately.
http://www.aspfaq.com/2342
http://www.aspfaq.com/
(Reverse address to reply.)
"Ian" <ian@.NoWhere.com> wrote in message
news:uotFj7diEHA.384@.TK2MSFTNGP10.phx.gbl...
> Thanks Aaron
> But i was reading that MDAC 2.8 does not have the JET drivers and my
> application needs them as well as the MS SQL drivers.
>
> So do i install both?|||Ian wrote:

> Hi
> How can I find out what version of MDAC is installed on a Machine.
> And would there be any problem with me installing both MDAC 2.7 and 2.8 on
> the same machine
> Ian
I use this approach:
Private Sub mnuHelpMDAC_Click()
Dim ans As String
ans = GetAdoVersion
If ans = "0" Then
MsgBox "MDAC is not Installed" & _
"Please Install MDAC from the DBAdmin CD", _
vbCritical, "Missing Important Component"
Else
MsgBox "MDAC version " & ans & " Is Installed on this System"
End If
End Sub
Function GetAdoVersion() As String
'Retrieve ADO (MDAC) version - see if it installed
'Returns an empty string is ADO is not installed
Dim o As Object
On Error Resume Next
GetAdoVersion = "0"
Set o = CreateObject("ADODB.Connection")
If Err.Number = 0 Then GetAdoVersion = o.Version
Set o = Nothing
End Function|||MDAC 2.7 doesn't have the Jet drivers either: MDAC 2.5 was the last version
that did.
In any case, Aaron gave you the correct answer
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no e-mails, please!)
"Ian" <ian@.NoWhere.com> wrote in message
news:uotFj7diEHA.384@.TK2MSFTNGP10.phx.gbl...
> Thanks Aaron
> But i was reading that MDAC 2.8 does not have the JET drivers and my
> application needs them as well as the MS SQL drivers.
>
> So do i install both?
> Ian
>
>
> "Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
> news:ub99mydiEHA.1344@.TK2MSFTNGP11.phx.gbl...
2.8[vbcol=seagreen]
> on
>|||Thank you all
For the advice.
"Ian" <ian@.NoWhere.com> wrote in message
news:u4iDeidiEHA.3016@.tk2msftngp13.phx.gbl...
> Hi
> How can I find out what version of MDAC is installed on a Machine.
> And would there be any problem with me installing both MDAC 2.7 and 2.8 on
> the same machine
> Ian
>|||And to offer some more advice, unless there is a compelling reason to use
ADO 2.6 or greater, just reference ADO 2.5 and redistribute MDAC 2.5. That
way, the Jet components are included and, if not present, should get
installed even if MDAC 2.6 or greater is already installed. At least, I'm
pretty sure about that. I'm sure someone will correct me if I'm wrong.
Mike
"Douglas J. Steele" <NOSPAM_djsteele@.NOSPAM_canada.com> wrote in message
news:untEKfiiEHA.1104@.TK2MSFTNGP10.phx.gbl...
> MDAC 2.7 doesn't have the Jet drivers either: MDAC 2.5 was the last
version
> that did.
> In any case, Aaron gave you the correct answer
> --
> Doug Steele, Microsoft Access MVP
> http://I.Am/DougSteele
> (no e-mails, please!)
>
> "Ian" <ian@.NoWhere.com> wrote in message
> news:uotFj7diEHA.384@.TK2MSFTNGP10.phx.gbl...
> 2.8
>

MDAC version

Hi
How can I find out what version of MDAC is installed on a Machine.
And would there be any problem with me installing both MDAC 2.7 and 2.8 on
the same machine
Ian> How can I find out what version of MDAC is installed on a Machine.
http://www.aspfaq.com/2057
> And would there be any problem with me installing both MDAC 2.7 and 2.8 on
> the same machine
Installing 2.8 should upgrade 2.7 to 2.8.
--
http://www.aspfaq.com/
(Reverse address to reply.)|||Thanks Aaron
But i was reading that MDAC 2.8 does not have the JET drivers and my
application needs them as well as the MS SQL drivers.
So do i install both?
Ian
"Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
news:ub99mydiEHA.1344@.TK2MSFTNGP11.phx.gbl...
> > How can I find out what version of MDAC is installed on a Machine.
> http://www.aspfaq.com/2057
> > And would there be any problem with me installing both MDAC 2.7 and 2.8
on
> > the same machine
> Installing 2.8 should upgrade 2.7 to 2.8.
> --
> http://www.aspfaq.com/
> (Reverse address to reply.)
>|||No, you don't need to install 2.7 and 2.8. You need to install MDAC 2.8 and
then install newer jet drivers separately.
http://www.aspfaq.com/2342
--
http://www.aspfaq.com/
(Reverse address to reply.)
"Ian" <ian@.NoWhere.com> wrote in message
news:uotFj7diEHA.384@.TK2MSFTNGP10.phx.gbl...
> Thanks Aaron
> But i was reading that MDAC 2.8 does not have the JET drivers and my
> application needs them as well as the MS SQL drivers.
>
> So do i install both?|||Ian wrote:
> Hi
> How can I find out what version of MDAC is installed on a Machine.
> And would there be any problem with me installing both MDAC 2.7 and 2.8 on
> the same machine
> Ian
I use this approach:
Private Sub mnuHelpMDAC_Click()
Dim ans As String
ans = GetAdoVersion
If ans = "0" Then
MsgBox "MDAC is not Installed" & _
"Please Install MDAC from the DBAdmin CD", _
vbCritical, "Missing Important Component"
Else
MsgBox "MDAC version " & ans & " Is Installed on this System"
End If
End Sub
Function GetAdoVersion() As String
'Retrieve ADO (MDAC) version - see if it installed
'Returns an empty string is ADO is not installed
Dim o As Object
On Error Resume Next
GetAdoVersion = "0"
Set o = CreateObject("ADODB.Connection")
If Err.Number = 0 Then GetAdoVersion = o.Version
Set o = Nothing
End Function|||MDAC 2.7 doesn't have the Jet drivers either: MDAC 2.5 was the last version
that did.
In any case, Aaron gave you the correct answer
--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no e-mails, please!)
"Ian" <ian@.NoWhere.com> wrote in message
news:uotFj7diEHA.384@.TK2MSFTNGP10.phx.gbl...
> Thanks Aaron
> But i was reading that MDAC 2.8 does not have the JET drivers and my
> application needs them as well as the MS SQL drivers.
>
> So do i install both?
> Ian
>
>
> "Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
> news:ub99mydiEHA.1344@.TK2MSFTNGP11.phx.gbl...
> > > How can I find out what version of MDAC is installed on a Machine.
> >
> > http://www.aspfaq.com/2057
> >
> > > And would there be any problem with me installing both MDAC 2.7 and
2.8
> on
> > > the same machine
> >
> > Installing 2.8 should upgrade 2.7 to 2.8.
> >
> > --
> > http://www.aspfaq.com/
> > (Reverse address to reply.)
> >
> >
>|||Thank you all
For the advice.
"Ian" <ian@.NoWhere.com> wrote in message
news:u4iDeidiEHA.3016@.tk2msftngp13.phx.gbl...
> Hi
> How can I find out what version of MDAC is installed on a Machine.
> And would there be any problem with me installing both MDAC 2.7 and 2.8 on
> the same machine
> Ian
>|||And to offer some more advice, unless there is a compelling reason to use
ADO 2.6 or greater, just reference ADO 2.5 and redistribute MDAC 2.5. That
way, the Jet components are included and, if not present, should get
installed even if MDAC 2.6 or greater is already installed. At least, I'm
pretty sure about that. I'm sure someone will correct me if I'm wrong.
Mike
"Douglas J. Steele" <NOSPAM_djsteele@.NOSPAM_canada.com> wrote in message
news:untEKfiiEHA.1104@.TK2MSFTNGP10.phx.gbl...
> MDAC 2.7 doesn't have the Jet drivers either: MDAC 2.5 was the last
version
> that did.
> In any case, Aaron gave you the correct answer
> --
> Doug Steele, Microsoft Access MVP
> http://I.Am/DougSteele
> (no e-mails, please!)
>
> "Ian" <ian@.NoWhere.com> wrote in message
> news:uotFj7diEHA.384@.TK2MSFTNGP10.phx.gbl...
> > Thanks Aaron
> >
> > But i was reading that MDAC 2.8 does not have the JET drivers and my
> > application needs them as well as the MS SQL drivers.
> >
> >
> > So do i install both?
> >
> > Ian
> >
> >
> >
> >
> > "Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
> > news:ub99mydiEHA.1344@.TK2MSFTNGP11.phx.gbl...
> > > > How can I find out what version of MDAC is installed on a Machine.
> > >
> > > http://www.aspfaq.com/2057
> > >
> > > > And would there be any problem with me installing both MDAC 2.7 and
> 2.8
> > on
> > > > the same machine
> > >
> > > Installing 2.8 should upgrade 2.7 to 2.8.
> > >
> > > --
> > > http://www.aspfaq.com/
> > > (Reverse address to reply.)
> > >
> > >
> >
> >
>

MDAC upgrade problem CompCheck reports 2.5 instead of 2.8

I am running SQL server on a Windows 2000 server with sp4 installed. After installing SQL service pack 4 on the machine my applications began complaining that MDAC was version 2.5 sure enough CompChecker reports version 2.5. I have tried to install the latest version of MDAC (2.8) on the machine but no matter what I do CompChecker reports 2.5.

I've tried reinstalling the SQL service pack I had no luck with that. Any help with this issue would be greatly appreciated.

WHen was the Windows service pack4 was applied, is it after SQL SP4 or before?

Check this KBA http://support.microsoft.com/kb/823939 for informaiton, ifyou need then you have to install MDAC 2.8 seperately.

|||The service pack was applied before the upgrade.|||I don't know if this helps but I think the issue is with the Windows File Protection. If I attempt to rename one of the dlls the server will automatically replace the file on the server with the 2.5 version. Is there some way to overcome this?|||Did you try to install the MDAC 2.8 separately like Satya proposed ? The file cannot be changed as the Windows FileProtextion is enabled for them (as you already noticed). if you already tried to install the MDAC 2.8, did you get an error or did the install run through ? Did you restart the system afterwards ?

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de

|||

I finally figured this out. It turns out that there were certain registry settings that were incorrectly set when SP4 was applied to SQL Server 2000. I don't want to get into the exact registry settings that need to be changed but that is where the answer lies.

Thanks to all for your assistance.

MDAC Madness

Wednesday, March 28, 2012

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 and odbc

Hi,
I have installed a mdac 2.6 on my client's Windows XP PC, but the ODBC seems
to be the same.
What do I need to do so the ODBC will be changed to the ODBC comes up with
the MDAC?
Thanks for help.
Jason
Yes...MDAC 2.6 wouldn't have done anything if you are on XP
SP2.
I'm not real clear on what you are trying to accomplish or
what in particular you want changed. If you need to verify
the installation of MDAC and what versions of what pieces
are on there, you can use the component checker. I'm
guessing that's probably what you need to do first anyway.
You can download the component checker from:
http://msdn.microsoft.com/data/ref/mdac/downloads/
-Sue
On Thu, 12 Oct 2006 15:05:15 +0800, "Jason Huang"
<JasonHuang8888@.hotmail.com> wrote:

>Hi,
>I have installed a mdac 2.6 on my client's Windows XP PC, but the ODBC seems
>to be the same.
>What do I need to do so the ODBC will be changed to the ODBC comes up with
>the MDAC?
>Thanks for help.
>
>Jason
>
sql

mdac and odbc

Hi,
I have installed a mdac 2.6 on my client's Windows XP PC, but the ODBC seems
to be the same.
What do I need to do so the ODBC will be changed to the ODBC comes up with
the MDAC?
Thanks for help.
JasonYes...MDAC 2.6 wouldn't have done anything if you are on XP
SP2.
I'm not real clear on what you are trying to accomplish or
what in particular you want changed. If you need to verify
the installation of MDAC and what versions of what pieces
are on there, you can use the component checker. I'm
guessing that's probably what you need to do first anyway.
You can download the component checker from:
http://msdn.microsoft.com/data/ref/mdac/downloads/
-Sue
On Thu, 12 Oct 2006 15:05:15 +0800, "Jason Huang"
<JasonHuang8888@.hotmail.com> wrote:

>Hi,
>I have installed a mdac 2.6 on my client's Windows XP PC, but the ODBC seem
s
>to be the same.
>What do I need to do so the ODBC will be changed to the ODBC comes up with
>the MDAC?
>Thanks for help.
>
>Jason
>

MDAC 2.8 on SQL 2000 Sp3a

Any reason why MDAC 2.8 should NOT be installed on the above server? A
colleague has an error linking a Excel spreadsheet (linked server) and the
MS site suggests Jet 4 SP8. However it claims I do not have Jet 4 SP3 yet
and that is the minimum required to add SP8! I thought MDAC 2.8 would get me
bang up to date with Jet.
Thanks for any input.
Simon
Jet is no longer included with MDAC. For Jet updates see
http://www.aspfaq.com/2342
http://www.aspfaq.com/
(Reverse address to reply.)
"Simon" <simoncar@.NotThisBittotalise.co.uk> wrote in message
news:#7j$g7RXEHA.4064@.TK2MSFTNGP11.phx.gbl...
> Any reason why MDAC 2.8 should NOT be installed on the above server? A
> colleague has an error linking a Excel spreadsheet (linked server) and the
> MS site suggests Jet 4 SP8. However it claims I do not have Jet 4 SP3 yet
> and that is the minimum required to add SP8! I thought MDAC 2.8 would get
me
> bang up to date with Jet.
> Thanks for any input.
> Simon
>
|||Jet is no longer included with MDAC. For Jet updates see
http://www.aspfaq.com/2342
http://www.aspfaq.com/
(Reverse address to reply.)
"Simon" <simoncar@.NotThisBittotalise.co.uk> wrote in message
news:#7j$g7RXEHA.4064@.TK2MSFTNGP11.phx.gbl...
> Any reason why MDAC 2.8 should NOT be installed on the above server? A
> colleague has an error linking a Excel spreadsheet (linked server) and the
> MS site suggests Jet 4 SP8. However it claims I do not have Jet 4 SP3 yet
> and that is the minimum required to add SP8! I thought MDAC 2.8 would get
me
> bang up to date with Jet.
> Thanks for any input.
> Simon
>

MDAC 2.8 on SQL 2000 Sp3a

MDAC 2.8

how to find which MDAC version is installed on SQL Server
thanks
KalyanYou can download and run the MDAC component checker:
4332ef092c9&displaylang=en" target="_blank">http://www.microsoft.com/downloads/...&displaylang=en
Hope this helps.
Dan Guzman
SQL Server MVP
"Kalyan" <Kalyan@.discussions.microsoft.com> wrote in message
news:D9E6F3E5-08F9-4065-A29C-F1618E8EBABA@.microsoft.com...
> how to find which MDAC version is installed on SQL Server
>
> thanks
> Kalyan
>|||Or
EXEC master..xp_regread
N'HKEY_LOCAL_MACHINE',
N'Software\Microsoft\DataAccess',
N'Version'
"Kalyan" <Kalyan@.discussions.microsoft.com> wrote in message
news:D9E6F3E5-08F9-4065-A29C-F1618E8EBABA@.microsoft.com...
> how to find which MDAC version is installed on SQL Server
>
> thanks
> Kalyan
>|||or
search for msado15.dll......then select properties and version
"Kalyan" wrote:

> how to find which MDAC version is installed on SQL Server
>
> thanks
> Kalyan
>sql

MDAC 2.8

how to find which MDAC version is installed on SQL Server
thanks
Kalyan
You can download and run the MDAC component checker:
http://www.microsoft.com/downloads/d...displaylang=en
Hope this helps.
Dan Guzman
SQL Server MVP
"Kalyan" <Kalyan@.discussions.microsoft.com> wrote in message
news:D9E6F3E5-08F9-4065-A29C-F1618E8EBABA@.microsoft.com...
> how to find which MDAC version is installed on SQL Server
>
> thanks
> Kalyan
>
|||Or
EXEC master..xp_regread
N'HKEY_LOCAL_MACHINE',
N'Software\Microsoft\DataAccess',
N'Version'
"Kalyan" <Kalyan@.discussions.microsoft.com> wrote in message
news:D9E6F3E5-08F9-4065-A29C-F1618E8EBABA@.microsoft.com...
> how to find which MDAC version is installed on SQL Server
>
> thanks
> Kalyan
>
|||or
search for msado15.dll......then select properties and version
"Kalyan" wrote:

> how to find which MDAC version is installed on SQL Server
>
> thanks
> Kalyan
>

Monday, March 26, 2012

MDAC 2.8

how to find which MDAC version is installed on SQL Server
thanks
KalyanYou can download and run the MDAC component checker:
http://www.microsoft.com/downloads/details.aspx?familyid=8f0a8df6-4a21-4b43-bf53-14332ef092c9&displaylang=en
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Kalyan" <Kalyan@.discussions.microsoft.com> wrote in message
news:D9E6F3E5-08F9-4065-A29C-F1618E8EBABA@.microsoft.com...
> how to find which MDAC version is installed on SQL Server
>
> thanks
> Kalyan
>|||Or
EXEC master..xp_regread
N'HKEY_LOCAL_MACHINE',
N'Software\Microsoft\DataAccess',
N'Version'
"Kalyan" <Kalyan@.discussions.microsoft.com> wrote in message
news:D9E6F3E5-08F9-4065-A29C-F1618E8EBABA@.microsoft.com...
> how to find which MDAC version is installed on SQL Server
>
> thanks
> Kalyan
>|||or
search for msado15.dll......then select properties and version
"Kalyan" wrote:
> how to find which MDAC version is installed on SQL Server
>
> thanks
> Kalyan
>

MDAC 2.6 with SQL Server 7 clustered (delay in connect)

After I installed the MDAC 2.6 in COM+ Server, I'd a problem with a long delay to connect the COM+ with SQL 7 clustered.

I had some tests, explained below:

* COM+ in server 1
* SQL Server in server 2

1) Try COM+ connect in SQL Server with thrust authentication
ConnectionString: "Provider=SQLOLEDB;Server=SERVER1;Database=master;P ersist Security Info=False;Integrated Security=SSPI"

(this SQL Server is Sort Order 52)
--> connect in 10 seconds

2) try COM+ connect in SQL Server with SQL authentication
ConnectionString: "Provider=SQLOLEDB;Server=SERVER1;Database=master;P ersist Security Info=False"

--> connect in 0,1 seconds

3) Try COM+ connect in SQL Server with thrust authentication
ConnectionString: "Provider=SQLOLEDB;Server=SERVER2;Database=master;P ersist Security Info=False;Integrated Security=SSPI"

(this SQL Server is Sort Order 54)
--> connect in 0,1 seconds

CODE:

Dim cnnData As ADODB.Connection

Set cnnData = New ADODB.Connection

Trace "Before cnnData.Open"

cnnData.Open "Provider=SQLOLEDB;" _
& "Server=SERVER1;" _
& "Database=master;" _
& "Persist Security Info=False;" _
& "Integrated Security=SSPI"

Trace "After cnnData.Open"

cnnData.Close
set cnnData = Nothing

All answers will be welcome.
Thanks,
SushiAny errors or information from SQL error log?|||no message in ERRORLOG or EventViewer :-(

MDAC

Where do I check for what version of MDAC is installed.
--
BeaversWithin SQL Server:
EXEC master..xp_regread
N'HKEY_LOCAL_MACHINE',
N'Software\Microsoft\DataAccess',
N'Version'
Or use the MDAC Checker from Microsoft.
HTH, Jens Suessmeyer.
--
http://www.sqlserver2005.de
--
"Beavers" <score@.beavers.mail> schrieb im Newsbeitrag
news:92B07BAD-87D5-433A-91AA-06090592F45B@.microsoft.com...
> Where do I check for what version of MDAC is installed.
> --
> Beavers
>|||> Where do I check for what version of MDAC is installed.
http://www.aspfaq.com/2057|||Thanks, guys that shld do it for me!
"Jens SÃ¼Ã?meyer" wrote:
> Within SQL Server:
> EXEC master..xp_regread
> N'HKEY_LOCAL_MACHINE',
> N'Software\Microsoft\DataAccess',
> N'Version'
> Or use the MDAC Checker from Microsoft.
>
> HTH, Jens Suessmeyer.
> --
> http://www.sqlserver2005.de
> --
> "Beavers" <score@.beavers.mail> schrieb im Newsbeitrag
> news:92B07BAD-87D5-433A-91AA-06090592F45B@.microsoft.com...
> > Where do I check for what version of MDAC is installed.
> > --
> > Beavers
> >
>
>

Wednesday, March 21, 2012

Maybe it's just Vista that has the problem?!?

So I installed a second instance of Report Server since the default instance couldn't find any default directories and I got this error message with started my saga Friday. I actually chose to follow MS's advise and do solution 1). That is when Report Server first lost track of it's directories and caused me to reinstall everything.

Does anyone know what this means?

Server Error in Application "Default Web Site/ReportServer$Two"

HTTP Error 500.0 - Internal Server Error

Description: This application is running in an application pool that uses the Integrated .NET mode. This is the preferred mode for running ASP.NET applications on the current and future version of IIS.

In this mode, the application should not specify ASP.NET handler mappings in the <system.web>/<httpHandlers> configuration section. Instead, it should use the <system.webServer>/<handlers> configuration section to configure ASP.NET handler mappings. You have the following options:

1) Migrate the application to work with the Integrated .NET mode (PREFERRED).

You can migrate the application configuration, including the contents of the <httpHandlers> configuration section, by using the following from a command line window (the window must be running as Administrator):

%systemroot%\system32\inetsrv\APPCMD.EXE migrate config "Default Web Site/ReportServer$Two"

After you migrate your application, it will run in both Classic and Integrated .NET modes, as well as on downlevel platforms.

2) Move this application to an application pool using the Classic .NET mode.

You can move the application to an application pool that uses the Classic .NET mode by using the following from a command line window (the window must be running as Administrator):

%systemroot%\system32\inetsrv\APPCMD.EXE set app "Default Web Site/ReportServer$Two" /applicationPool:"Classic .NET AppPool"

Alternatively, you can use any other application pool on your system that is running in the Classic .NET mode. You can also use the IIS Administration tool to move this application to another application pool.

It is preferred that you migrate this application by using option 1 to take advantage of the benefits provided by the Integrated .NET mode.

Error Code: 0x80070032

Notification: BeginRequest

Module: ConfigurationValidationModule

Requested URL: http://jc:80/ReportServer$Two

Physical Path: C:\Program Files\Microsoft SQL Server\MSSQL.6\Reporting Services\ReportServer

Logon User: Not yet determined

Logon Method: Not yet determined

Handler: AboMapperCustom-43870

Most likely causes: IIS received the request; however, an internal error occurred during the processing of the request. The root cause of this error depends on which module handles the request and what was happening in the worker process when this error occurred. IIS was not able to access the web.config file for the Web site or application. This can occur if the NTFS permissions are set incorrectly. IIS was not able to process configuration for the Web site or application. The authenticated user does not have permission to use this DLL. The request is mapped to a managed handler but the .NET Extensibility Feature is not installed.

What you can try: Ensure that the NTFS permissions for the web.config file are correct and allow access to the Web server's machine account. Check the event logs to see if any additional information was logged. Verify the permissions for the DLL. Install the .NET Extensibility feature if the request is mapped to a managed handler. Create a tracing rule to track failed requests for this HTTP status code. For more information about creating a tracing rule for failed requests, click here.

More Information... This error means that there was a problem while processing the request. The request was received by the Web server, but during processing a fatal error occurred, causing the 500 error.

Microsoft Knowledge Base Articles: 294807

Server Version Information: Internet Information Services 7.0.Could be. I heard that SQL has some problems with Vista. Check on the Microsoft site and make sure you have the new update for Vista and VS 2005 SP1. You'll have to download SP1 though. Or maybe check for some SQL updates for Vista.

Friday, March 30, 2012

Mdac Xp 2000

MDAC version

MDAC version

MDAC version

MDAC version

MDAC upgrade problem CompCheck reports 2.5 instead of 2.8

MDAC Madness

MDAC Madness

Wednesday, March 28, 2012

MDAC Madness

mdac and odbc

mdac and odbc

MDAC 2.8 on SQL 2000 Sp3a

MDAC 2.8 on SQL 2000 Sp3a

MDAC 2.8 on SQL 2000 Sp3a

MDAC 2.8

MDAC 2.8

Monday, March 26, 2012

MDAC 2.8

MDAC 2.6 with SQL Server 7 clustered (delay in connect)

MDAC

Wednesday, March 21, 2012

Maybe it's just Vista that has the problem?!?

Server Error in Application "Default Web Site/ReportServer$Two"

HTTP Error 500.0 - Internal Server Error

1) Migrate the application to work with the Integrated .NET mode (PREFERRED).

2) Move this application to an application pool using the Classic .NET mode.

MAX and DATEDIFF

Blog Archive

About Me