Showing posts with label error. Show all posts

Friday, March 30, 2012

MDAC version error

Hi,
I have a problem to install SQL Server 2000 Development Edition onto my
Windows 2000 professional P.,I have a check of my MDAC version using the
Component Checker, it tells that the version of my MDAC is 2.53.6202.0 which
should be 2.53.6200.0.
Does anybody know why this happened and how to solve it?
Thanks in advance
FrankThe Component Checker you are using likely had not been updated for the
security patch you have installed. If you get a newer version of the
Component Checker
(http://msdn.microsoft.com/library/default.asp?url=/downloads/list/dataacces
s.asp) it should report 2.53.6202.
Shawn Aebi
Microsoft
This posting is provided "AS IS" with no warranties, and confers no rights.

Wednesday, March 28, 2012

MDAC error on VFP linked server

I have a linked server pointing to a folder where foxpro tables exist.
The tables are listed when I click on the linked server/tables.
However I get this error when in query analyer I say: select * from
vfplinked...clients
Server: Msg 7313, Level 16, State 1, Line 1
Invalid schema or catalog specified for provider 'MSDASQL'.
OLE DB error trace [Non-interface error: Invalid schema or catalog
specified for the provider.].
Any help? What am I missing? I got this working before.
This is on SQLServer 2000
Thanks everyone!Hi Michael,
Have you tried using the latest Visual FoxPro OLE DB data provider? It's
downloadable from
http://msdn.microsoft.com/vfoxpro/d...es/default.aspx and works
with all versions of FoxPro tables.
Cindy Winegarden MCSD, Microsoft Visual FoxPro MVP
cindy_winegarden@.msn.com www.cindywinegarden.com
"Michael" <Michael.Rodriguez@.nospam> wrote in message
news:etkRi$bBFHA.2180@.TK2MSFTNGP10.phx.gbl...
> I have a linked server pointing to a folder where foxpro tables exist.
> The tables are listed when I click on the linked server/tables.
> However I get this error when in query analyer I say: select * from
> vfplinked...clients
> Server: Msg 7313, Level 16, State 1, Line 1
> Invalid schema or catalog specified for provider 'MSDASQL'.
> OLE DB error trace [Non-interface error: Invalid schema or catalog
> specified for the provider.].
>
> Any help? What am I missing? I got this working before.
> This is on SQLServer 2000
> Thanks everyone!
>

MDAC error on VFP linked server

I have a linked server pointing to a folder where foxpro tables exist.
The tables are listed when I click on the linked server/tables.
However I get this error when in query analyer I say: select * from
vfplinked...clients
Server: Msg 7313, Level 16, State 1, Line 1
Invalid schema or catalog specified for provider 'MSDASQL'.
OLE DB error trace [Non-interface error: Invalid schema or catalog
specified for the provider.].
Any help? What am I missing? I got this working before.
This is on SQLServer 2000
Thanks everyone!
Hi Michael,
Have you tried using the latest Visual FoxPro OLE DB data provider? It's
downloadable from
http://msdn.microsoft.com/vfoxpro/do...s/default.aspx and works
with all versions of FoxPro tables.
Cindy Winegarden MCSD, Microsoft Visual FoxPro MVP
cindy_winegarden@.msn.com www.cindywinegarden.com
"Michael" <Michael.Rodriguez@.nospam> wrote in message
news:etkRi$bBFHA.2180@.TK2MSFTNGP10.phx.gbl...
> I have a linked server pointing to a folder where foxpro tables exist.
> The tables are listed when I click on the linked server/tables.
> However I get this error when in query analyer I say: select * from
> vfplinked...clients
> Server: Msg 7313, Level 16, State 1, Line 1
> Invalid schema or catalog specified for provider 'MSDASQL'.
> OLE DB error trace [Non-interface error: Invalid schema or catalog
> specified for the provider.].
>
> Any help? What am I missing? I got this working before.
> This is on SQLServer 2000
> Thanks everyone!
>
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 error

Hi,

I have updated my Win98 SE with MDAC 2.7 program and checked
it with component checker (cc.exe) from Microsoft website. Found a warning
that is as following:

Item Name,Item Type,ErrorString,Status
MSADCO.DLL,COM,Unknown Class ID =
{9381d8f1-0288-11d0-9501-00aa00b911a5},Warning

And I attached the screen. Please tell me the impact and any solution?
Thanks.

SupernovaThat dll may be a browser related ADO component?? are you having some kind of issue with web applications (that interface to your database) on the workstation?|||Originally posted by DBA
That dll may be a browser related ADO component?? are you having some kind of issue with web applications (that interface to your database) on the workstation?

Actually not web application. It's a ODBC/SQL server application running at workstation.|||Have you tried running comcheck with switch 'd' (this is a reconfiguration option) ? Have you noticed any problems ? The screen attachment never made it.

MDAC 2.8 Update Causes Problems

Hello,
I have a 2000 server hosting a site using SQL Server 7. I have been having
problems accessing the database and I kept getting an error 80004005 Data
source name not found and no default driver specified. I went to the
Microsoft site and found the white paper and followed a link to download an
MDAC 2.8 update that was compatible with Windows 2000. However now my site
doesn't work at all and I get:
Error Type:
Microsoft OLE DB Provider for ODBC Drivers (0x80040E4D)
[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user 'sa'.
Reason: Not associated with a trusted SQL Server connection.
/includes/i_shop.asp, line 87
I've been searching, but I still can't find exactly what I need and
suggestions would be greatly appreciated.
Thanks for any help,
Med103 wrote:
> Hello,
> I have a 2000 server hosting a site using SQL Server 7. I have been
> having problems accessing the database and I kept getting an error
> 80004005 Data source name not found and no default driver specified.
> I went to the Microsoft site and found the white paper and followed a
> link to download an MDAC 2.8 update that was compatible with Windows
> 2000. However now my site doesn't work at all and I get:
> Error Type:
> Microsoft OLE DB Provider for ODBC Drivers (0x80040E4D)
> [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user
> 'sa'. Reason: Not associated with a trusted SQL Server connection.
> /includes/i_shop.asp, line 87
> I've been searching, but I still can't find exactly what I need and
> suggestions would be greatly appreciated.
> Thanks for any help,
It looks like you are telling ADO to connect using a trusted connection,
but it's picking up "sa" as the user name (or are you passing that in?)
Do you want to be using ODBC with ADO? You're not using the ADO drivers
according to that error. Post your connection string and also try
connecting using SQL Server security from your app if you have it
enabled.
David Gugick
Imceda Software
www.imceda.com
|||I went through and used the component checker and there is one unknown file
sqlsrv32.dll version 2000.85.1025.0 according to the Microsoft site the file
that is supposed to be included is sqlsrv32.dll version 2000.85.1022.0. Would
it be advisable to download the right file and replace it? The connection
string and everything else hasn't changed and it all worked for years. The
only change was the 2.8 update. Should I look at the i_shop.asp page for
clues? Why is it listed.
Thanks for any help,
Mike
"David Gugick" wrote:

> Med103 wrote:
> It looks like you are telling ADO to connect using a trusted connection,
> but it's picking up "sa" as the user name (or are you passing that in?)
> Do you want to be using ODBC with ADO? You're not using the ADO drivers
> according to that error. Post your connection string and also try
> connecting using SQL Server security from your app if you have it
> enabled.
> --
> David Gugick
> Imceda Software
> www.imceda.com
>
|||Med103 wrote:
> I went through and used the component checker and there is one
> unknown file sqlsrv32.dll version 2000.85.1025.0 according to the
> Microsoft site the file that is supposed to be included is
> sqlsrv32.dll version 2000.85.1022.0. Would it be advisable to
> download the right file and replace it? The connection string and
> everything else hasn't changed and it all worked for years. The only
> change was the 2.8 update. Should I look at the i_shop.asp page for
> clues? Why is it listed.
> Thanks for any help,
> Mike
You should post the connection string anyway. Just because MDAC < 2.8
allowed a malformed connection string to pass through doesn't mean 2.8
will. You want to use ODBC in this case, i assume. No?
I wouldn't worry about the file version issue right now.
David Gugick
Imceda Software
www.imceda.com
|||I didn't create this site and the only connection string I could find was in
the siteserver console DSN=pl_commerce;UID=sa;PWD=dbsa;. Is this the one I
need to worry about?
Thnaks again,
Mike
"David Gugick" wrote:

> Med103 wrote:
> You should post the connection string anyway. Just because MDAC < 2.8
> allowed a malformed connection string to pass through doesn't mean 2.8
> will. You want to use ODBC in this case, i assume. No?
> I wouldn't worry about the file version issue right now.
>
> --
> David Gugick
> Imceda Software
> www.imceda.com
>
|||Med103 wrote:
> I didn't create this site and the only connection string I could find
> was in the siteserver console DSN=pl_commerce;UID=sa;PWD=dbsa;. Is
> this the one I need to worry about?
> Thnaks again,
> Mike
>
Well, the first thing you need to do is change the password on the "sa"
account (because you posted it to the group).
Then, you should change the connection to use some other user that has
limited, but sufficient, rights to the underlying database. Better to
use integrated security in this case instead of SQL Security.
You are using a DSN, which means you are connecting using ODBC (not the
fastest). It's better to use the native ADO driver for SQL Server.
Go to the server in question and test the ODBC connection from the ODBC
Control Panel Applet and make sure it works. maybe someone already
changed the password or the server name changed.
David Gugick
Imceda Software
www.imceda.com
|||Oops I was kind of wondering about that . It doesn't work anyway, but when I
try to use the ODBC Control Panel I get the same error posted above. I also
tried changing users, but it kept giving me an error message Invalid
connection string; connection failed.. Can I just create a new database user
in the enterprise manager and see if I can change it in the connection
string?
Thanks,
"David Gugick" wrote:

> Med103 wrote:
> Well, the first thing you need to do is change the password on the "sa"
> account (because you posted it to the group).
> Then, you should change the connection to use some other user that has
> limited, but sufficient, rights to the underlying database. Better to
> use integrated security in this case instead of SQL Security.
> You are using a DSN, which means you are connecting using ODBC (not the
> fastest). It's better to use the native ADO driver for SQL Server.
> Go to the server in question and test the ODBC connection from the ODBC
> Control Panel Applet and make sure it works. maybe someone already
> changed the password or the server name changed.
>
> --
> David Gugick
> Imceda Software
> www.imceda.com
>
|||Med103 wrote:
> Oops I was kind of wondering about that . It doesn't work anyway,
> but when I try to use the ODBC Control Panel I get the same error
> posted above. I also tried changing users, but it kept giving me an
> error message Invalid connection string; connection failed.. Can I
> just create a new database user in the enterprise manager and see if
> I can change it in the connection string?
Sure can. Give that a shot. Once you get it working in the ODBC control
panel applet, you should be good to go.
David Gugick
Imceda Software
www.imceda.com

MDAC 2.8 Update Causes Problems

Hello,
I have a 2000 server hosting a site using SQL Server 7. I have been having
problems accessing the database and I kept getting an error 80004005 Data
source name not found and no default driver specified. I went to the
Microsoft site and found the white paper and followed a link to download an
MDAC 2.8 update that was compatible with Windows 2000. However now my site
doesn't work at all and I get:
Error Type:
Microsoft OLE DB Provider for ODBC Drivers (0x80040E4D)
[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user 'sa'.
Reason: Not associated with a trusted SQL Server connection.
/includes/i_shop.asp, line 87
I've been searching, but I still can't find exactly what I need and
suggestions would be greatly appreciated.
Thanks for any help,Med103 wrote:
> Hello,
> I have a 2000 server hosting a site using SQL Server 7. I have been
> having problems accessing the database and I kept getting an error
> 80004005 Data source name not found and no default driver specified.
> I went to the Microsoft site and found the white paper and followed a
> link to download an MDAC 2.8 update that was compatible with Windows
> 2000. However now my site doesn't work at all and I get:
> Error Type:
> Microsoft OLE DB Provider for ODBC Drivers (0x80040E4D)
> [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user
> 'sa'. Reason: Not associated with a trusted SQL Server connection.
> /includes/i_shop.asp, line 87
> I've been searching, but I still can't find exactly what I need and
> suggestions would be greatly appreciated.
> Thanks for any help,
It looks like you are telling ADO to connect using a trusted connection,
but it's picking up "sa" as the user name (or are you passing that in?)
Do you want to be using ODBC with ADO? You're not using the ADO drivers
according to that error. Post your connection string and also try
connecting using SQL Server security from your app if you have it
enabled.
--
David Gugick
Imceda Software
www.imceda.com|||I went through and used the component checker and there is one unknown file
sqlsrv32.dll version 2000.85.1025.0 according to the Microsoft site the file
that is supposed to be included is sqlsrv32.dll version 2000.85.1022.0. Would
it be advisable to download the right file and replace it? The connection
string and everything else hasn't changed and it all worked for years. The
only change was the 2.8 update. Should I look at the i_shop.asp page for
clues? Why is it listed.
Thanks for any help,
Mike
"David Gugick" wrote:
> Med103 wrote:
> > Hello,
> > I have a 2000 server hosting a site using SQL Server 7. I have been
> > having problems accessing the database and I kept getting an error
> > 80004005 Data source name not found and no default driver specified.
> > I went to the Microsoft site and found the white paper and followed a
> > link to download an MDAC 2.8 update that was compatible with Windows
> > 2000. However now my site doesn't work at all and I get:
> >
> > Error Type:
> > Microsoft OLE DB Provider for ODBC Drivers (0x80040E4D)
> > [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user
> > 'sa'. Reason: Not associated with a trusted SQL Server connection.
> > /includes/i_shop.asp, line 87
> >
> > I've been searching, but I still can't find exactly what I need and
> > suggestions would be greatly appreciated.
> >
> > Thanks for any help,
> It looks like you are telling ADO to connect using a trusted connection,
> but it's picking up "sa" as the user name (or are you passing that in?)
> Do you want to be using ODBC with ADO? You're not using the ADO drivers
> according to that error. Post your connection string and also try
> connecting using SQL Server security from your app if you have it
> enabled.
> --
> David Gugick
> Imceda Software
> www.imceda.com
>|||Med103 wrote:
> I went through and used the component checker and there is one
> unknown file sqlsrv32.dll version 2000.85.1025.0 according to the
> Microsoft site the file that is supposed to be included is
> sqlsrv32.dll version 2000.85.1022.0. Would it be advisable to
> download the right file and replace it? The connection string and
> everything else hasn't changed and it all worked for years. The only
> change was the 2.8 update. Should I look at the i_shop.asp page for
> clues? Why is it listed.
> Thanks for any help,
> Mike
You should post the connection string anyway. Just because MDAC < 2.8
allowed a malformed connection string to pass through doesn't mean 2.8
will. You want to use ODBC in this case, i assume. No?
I wouldn't worry about the file version issue right now.
David Gugick
Imceda Software
www.imceda.com|||I didn't create this site and the only connection string I could find was in
the siteserver console DSN=pl_commerce;UID=sa;PWD=dbsa;. Is this the one I
need to worry about?
Thnaks again,
Mike
"David Gugick" wrote:
> Med103 wrote:
> > I went through and used the component checker and there is one
> > unknown file sqlsrv32.dll version 2000.85.1025.0 according to the
> > Microsoft site the file that is supposed to be included is
> > sqlsrv32.dll version 2000.85.1022.0. Would it be advisable to
> > download the right file and replace it? The connection string and
> > everything else hasn't changed and it all worked for years. The only
> > change was the 2.8 update. Should I look at the i_shop.asp page for
> > clues? Why is it listed.
> > Thanks for any help,
> > Mike
> You should post the connection string anyway. Just because MDAC < 2.8
> allowed a malformed connection string to pass through doesn't mean 2.8
> will. You want to use ODBC in this case, i assume. No?
> I wouldn't worry about the file version issue right now.
>
> --
> David Gugick
> Imceda Software
> www.imceda.com
>|||Med103 wrote:
> I didn't create this site and the only connection string I could find
> was in the siteserver console DSN=pl_commerce;UID=sa;PWD=dbsa;. Is
> this the one I need to worry about?
> Thnaks again,
> Mike
>
Well, the first thing you need to do is change the password on the "sa"
account (because you posted it to the group).
Then, you should change the connection to use some other user that has
limited, but sufficient, rights to the underlying database. Better to
use integrated security in this case instead of SQL Security.
You are using a DSN, which means you are connecting using ODBC (not the
fastest). It's better to use the native ADO driver for SQL Server.
Go to the server in question and test the ODBC connection from the ODBC
Control Panel Applet and make sure it works. maybe someone already
changed the password or the server name changed.
David Gugick
Imceda Software
www.imceda.com|||Oops I was kind of wondering about that . It doesn't work anyway, but when I
try to use the ODBC Control Panel I get the same error posted above. I also
tried changing users, but it kept giving me an error message Invalid
connection string; connection failed.. Can I just create a new database user
in the enterprise manager and see if I can change it in the connection
string?
Thanks,
"David Gugick" wrote:
> Med103 wrote:
> > I didn't create this site and the only connection string I could find
> > was in the siteserver console DSN=pl_commerce;UID=sa;PWD=dbsa;. Is
> > this the one I need to worry about?
> > Thnaks again,
> > Mike
> >
> Well, the first thing you need to do is change the password on the "sa"
> account (because you posted it to the group).
> Then, you should change the connection to use some other user that has
> limited, but sufficient, rights to the underlying database. Better to
> use integrated security in this case instead of SQL Security.
> You are using a DSN, which means you are connecting using ODBC (not the
> fastest). It's better to use the native ADO driver for SQL Server.
> Go to the server in question and test the ODBC connection from the ODBC
> Control Panel Applet and make sure it works. maybe someone already
> changed the password or the server name changed.
>
> --
> David Gugick
> Imceda Software
> www.imceda.com
>|||Med103 wrote:
> Oops I was kind of wondering about that . It doesn't work anyway,
> but when I try to use the ODBC Control Panel I get the same error
> posted above. I also tried changing users, but it kept giving me an
> error message Invalid connection string; connection failed.. Can I
> just create a new database user in the enterprise manager and see if
> I can change it in the connection string?
Sure can. Give that a shot. Once you get it working in the ODBC control
panel applet, you should be good to go.
--
David Gugick
Imceda Software
www.imceda.com

MDAC 2.8 Update Causes Problems

Hello,
I have a 2000 server hosting a site using SQL Server 7. I have been having
problems accessing the database and I kept getting an error 80004005 Data
source name not found and no default driver specified. I went to the
Microsoft site and found the white paper and followed a link to download an
MDAC 2.8 update that was compatible with Windows 2000. However now my site
doesn't work at all and I get:
Error Type:
Microsoft OLE DB Provider for ODBC Drivers (0x80040E4D)
[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for
user 'sa'.
Reason: Not associated with a trusted SQL Server connection.
/includes/i_shop.asp, line 87
I've been searching, but I still can't find exactly what I need and
suggestions would be greatly appreciated.
Thanks for any help,Med103 wrote:
> Hello,
> I have a 2000 server hosting a site using SQL Server 7. I have been
> having problems accessing the database and I kept getting an error
> 80004005 Data source name not found and no default driver specified.
> I went to the Microsoft site and found the white paper and followed a
> link to download an MDAC 2.8 update that was compatible with Windows
> 2000. However now my site doesn't work at all and I get:
> Error Type:
> Microsoft OLE DB Provider for ODBC Drivers (0x80040E4D)
> [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed fo
r user
> 'sa'. Reason: Not associated with a trusted SQL Server connection.
> /includes/i_shop.asp, line 87
> I've been searching, but I still can't find exactly what I need and
> suggestions would be greatly appreciated.
> Thanks for any help,
It looks like you are telling ADO to connect using a trusted connection,
but it's picking up "sa" as the user name (or are you passing that in?)
Do you want to be using ODBC with ADO? You're not using the ADO drivers
according to that error. Post your connection string and also try
connecting using SQL Server security from your app if you have it
enabled.
David Gugick
Imceda Software
www.imceda.com|||I went through and used the component checker and there is one unknown file
sqlsrv32.dll version 2000.85.1025.0 according to the Microsoft site the file
that is supposed to be included is sqlsrv32.dll version 2000.85.1022.0. Woul
d
it be advisable to download the right file and replace it? The connection
string and everything else hasn't changed and it all worked for years. The
only change was the 2.8 update. Should I look at the i_shop.asp page for
clues? Why is it listed.
Thanks for any help,
Mike
"David Gugick" wrote:

> Med103 wrote:
> It looks like you are telling ADO to connect using a trusted connection,
> but it's picking up "sa" as the user name (or are you passing that in?)
> Do you want to be using ODBC with ADO? You're not using the ADO drivers
> according to that error. Post your connection string and also try
> connecting using SQL Server security from your app if you have it
> enabled.
> --
> David Gugick
> Imceda Software
> www.imceda.com
>|||Med103 wrote:
> I went through and used the component checker and there is one
> unknown file sqlsrv32.dll version 2000.85.1025.0 according to the
> Microsoft site the file that is supposed to be included is
> sqlsrv32.dll version 2000.85.1022.0. Would it be advisable to
> download the right file and replace it? The connection string and
> everything else hasn't changed and it all worked for years. The only
> change was the 2.8 update. Should I look at the i_shop.asp page for
> clues? Why is it listed.
> Thanks for any help,
> Mike
You should post the connection string anyway. Just because MDAC < 2.8
allowed a malformed connection string to pass through doesn't mean 2.8
will. You want to use ODBC in this case, i assume. No?
I wouldn't worry about the file version issue right now.
David Gugick
Imceda Software
www.imceda.com|||I didn't create this site and the only connection string I could find was in
the siteserver console DSN=pl_commerce;UID=sa;PWD=dbsa;. Is this the one I
need to worry about?
Thnaks again,
Mike
"David Gugick" wrote:

> Med103 wrote:
> You should post the connection string anyway. Just because MDAC < 2.8
> allowed a malformed connection string to pass through doesn't mean 2.8
> will. You want to use ODBC in this case, i assume. No?
> I wouldn't worry about the file version issue right now.
>
> --
> David Gugick
> Imceda Software
> www.imceda.com
>|||Med103 wrote:
> I didn't create this site and the only connection string I could find
> was in the siteserver console DSN=pl_commerce;UID=sa;PWD=dbsa;. Is
> this the one I need to worry about?
> Thnaks again,
> Mike
>
Well, the first thing you need to do is change the password on the "sa"
account (because you posted it to the group).
Then, you should change the connection to use some other user that has
limited, but sufficient, rights to the underlying database. Better to
use integrated security in this case instead of SQL Security.
You are using a DSN, which means you are connecting using ODBC (not the
fastest). It's better to use the native ADO driver for SQL Server.
Go to the server in question and test the ODBC connection from the ODBC
Control Panel Applet and make sure it works. maybe someone already
changed the password or the server name changed.
David Gugick
Imceda Software
www.imceda.com|||Oops I was kind of wondering about that . It doesn't work anyway, but when
I
try to use the ODBC Control Panel I get the same error posted above. I also
tried changing users, but it kept giving me an error message Invalid
connection string; connection failed.. Can I just create a new database user
in the enterprise manager and see if I can change it in the connection
string?
Thanks,
"David Gugick" wrote:

> Med103 wrote:
> Well, the first thing you need to do is change the password on the "sa"
> account (because you posted it to the group).
> Then, you should change the connection to use some other user that has
> limited, but sufficient, rights to the underlying database. Better to
> use integrated security in this case instead of SQL Security.
> You are using a DSN, which means you are connecting using ODBC (not the
> fastest). It's better to use the native ADO driver for SQL Server.
> Go to the server in question and test the ODBC connection from the ODBC
> Control Panel Applet and make sure it works. maybe someone already
> changed the password or the server name changed.
>
> --
> David Gugick
> Imceda Software
> www.imceda.com
>|||Med103 wrote:
> Oops I was kind of wondering about that . It doesn't work anyway,
> but when I try to use the ODBC Control Panel I get the same error
> posted above. I also tried changing users, but it kept giving me an
> error message Invalid connection string; connection failed.. Can I
> just create a new database user in the enterprise manager and see if
> I can change it in the connection string?
Sure can. Give that a shot. Once you get it working in the ODBC control
panel applet, you should be good to go.
David Gugick
Imceda Software
www.imceda.com

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 Fatal Setup Error. This setup does not support installing on this operating system

I have XP Pro SP2 with MDAC 2.8.1022. It had a problem so I tried to reinstall MDAC and got a Fatal Setup Error. This setup does not support installing on this operating system. I downloaded MDAC 2.8 1177 and get the same error.

I thought of uninstalling/reinstalling SP2, but this is a 2 month old Dell Latitude 610 with factory installed XP. There is no Windows Service Pack 2 option listed in the Control Panel > Add/Remove Programs.

There's some other strange things, so I wonder if they are related.

1) I have Paul set up as an administrator account. Some folders like MSSQL show that account with no permissions. I grant all the permissions to Paul for that folder. I come back later and the permissions are gone.

2) I deleted 20 files in Explorer, but 7 of them did not go away. I deleted those 7 again and they instatnly reappeared. I deleted those 7 again and then they finally went away.

3) I get a slow reaction time for things like Windows Explorer and opening and closing programs. This is suprising since it has 2 gig of RAM and 2.3 Gig processor. Could it be a memory handling problem that's causing OS problems. Probably, the memory didn't handle the OS installation well and the whole system is compromised now.

I'm having the same problem on XP Sp2 trying to re-install MDAC.

Thought I'd try re-installing MDAC since my system errors out when I try to register DLL files.

|||

I've seen this error during MDAC installation on XP SP2 as well. I was able to get around it by changing the Compatibility Properties of the mdac installation file to Win NT. It then installs OK.

|||

Chnaces are the files did go away for an instant but they are on the system recovery list and XP replaced them.

|||

I have XP Pro SP2 . It had a problem so I tried to install ADO.Net (MDAC Version 2.8 SP1 ) many times and reload it from download.microsoft.com. I couldn't install on my computer. I get the Fatal Setup Error "This setup does not support installing on this operating system". How can I solve this problem ?

|||

I could not overcome the problem.. I finally did erased the drive and reinstalled windows.

Paul

|||Windows XP comes pre-installed with MDAC you should not install the standalone MDAC installer on Windows XP. If you have a problem with the MDAC install on XP then just run a repair install of XP this will reinstall the MDAC that XP ships with.|||

I had a similar experience. Two possible options can be used to allow XP to repair the entries or force the install without having to repair the XP installation.

1. To repair your MDAC installation. Found this solution on the web that works. Have your XP SP2 install disk handy. Go to and find c:\windows\inf\mdac.inf. Right click on the .inf file and pick Install. It will attempt to reinstall the files. Browse to source files on the XP CD. It should install smoothly. It may ask for the handler.reg (in c:\program files\common files\system\msadc\). Restart. Sign in (admin) and then after a few minutes windows update will want to apply the security patch again. You may want to follow up with the SJet update also.

2. To force the installation. Found this one also. XP SP2 will already have the SP1 update applied but has registry corruption (virus after affects). Right click on the MDAC 2.8 SP1 install exe file and select properties. Select the Compatability tab, check the compatability mode box and pick "windows NT" or possibly "Windows 2000". Click apply and run the file again. It should install all the proper files again.

This restored the complete connectivity to databases. In visual studio the data tables did not display properly with a flawed connection. If the access (mdb) tables display properly, then a connection to the SQL database (mdf) - missing tables -is a access/login rights problem. Grant login rights to the user for the database.

|||

John,

#2 works like a charms. Thanks a million.

sql

MDAC 2.8 Fatal Setup Error. This setup does not support installing on this operating system

There's some other strange things, so I wonder if they are related.

2) I deleted 20 files in Explorer, but 7 of them did not go away. I deleted those 7 again and they instatnly reappeared. I deleted those 7 again and then they finally went away.

I'm having the same problem on XP Sp2 trying to re-install MDAC.

Thought I'd try re-installing MDAC since my system errors out when I try to register DLL files.

|||

I've seen this error during MDAC installation on XP SP2 as well. I was able to get around it by changing the Compatibility Properties of the mdac installation file to Win NT. It then installs OK.

|||

Chnaces are the files did go away for an instant but they are on the system recovery list and XP replaced them.

|||

I could not overcome the problem.. I finally did erased the drive and reinstalled windows.

Paul

I had a similar experience. Two possible options can be used to allow XP to repair the entries or force the install without having to repair the XP installation.

|||

John,

#2 works like a charms. Thanks a million.

MDAC 2.8 Fatal Setup Error. This setup does not support installing on this operating system

There's some other strange things, so I wonder if they are related.

2) I deleted 20 files in Explorer, but 7 of them did not go away. I deleted those 7 again and they instatnly reappeared. I deleted those 7 again and then they finally went away.

I'm having the same problem on XP Sp2 trying to re-install MDAC.

Thought I'd try re-installing MDAC since my system errors out when I try to register DLL files.

|||

I've seen this error during MDAC installation on XP SP2 as well. I was able to get around it by changing the Compatibility Properties of the mdac installation file to Win NT. It then installs OK.

|||

Chnaces are the files did go away for an instant but they are on the system recovery list and XP replaced them.

|||

I could not overcome the problem.. I finally did erased the drive and reinstalled windows.

Paul

I had a similar experience. Two possible options can be used to allow XP to repair the entries or force the install without having to repair the XP installation.

|||

John,

#2 works like a charms. Thanks a million.

MDAC 2.8 Fatal Setup Error. This setup does not support installing on this operating system

There's some other strange things, so I wonder if they are related.

2) I deleted 20 files in Explorer, but 7 of them did not go away. I deleted those 7 again and they instatnly reappeared. I deleted those 7 again and then they finally went away.

I'm having the same problem on XP Sp2 trying to re-install MDAC.

Thought I'd try re-installing MDAC since my system errors out when I try to register DLL files.

|||

I've seen this error during MDAC installation on XP SP2 as well. I was able to get around it by changing the Compatibility Properties of the mdac installation file to Win NT. It then installs OK.

|||

Chnaces are the files did go away for an instant but they are on the system recovery list and XP replaced them.

|||

I could not overcome the problem.. I finally did erased the drive and reinstalled windows.

Paul

I had a similar experience. Two possible options can be used to allow XP to repair the entries or force the install without having to repair the XP installation.

|||

John,

#2 works like a charms. Thanks a million.

MDAC 2.8 Fatal Setup Error. This setup does not support installing on this operating system

There's some other strange things, so I wonder if they are related.

2) I deleted 20 files in Explorer, but 7 of them did not go away. I deleted those 7 again and they instatnly reappeared. I deleted those 7 again and then they finally went away.

I'm having the same problem on XP Sp2 trying to re-install MDAC.

Thought I'd try re-installing MDAC since my system errors out when I try to register DLL files.

|||

I've seen this error during MDAC installation on XP SP2 as well. I was able to get around it by changing the Compatibility Properties of the mdac installation file to Win NT. It then installs OK.

|||

Chnaces are the files did go away for an instant but they are on the system recovery list and XP replaced them.

|||

I could not overcome the problem.. I finally did erased the drive and reinstalled windows.

Paul

I had a similar experience. Two possible options can be used to allow XP to repair the entries or force the install without having to repair the XP installation.

|||

John,

#2 works like a charms. Thanks a million.

MDAC 2.8 and cursor FETCH NEXT

it seems that starting with MDAC 2.8 the FETCH NEXT statement for cursors requires an INTO clause. otherwise an unspecified error is returned.
so it's not possible to scroll through the records anymore without storing the values of the fields into local variables?Can you post the error code/description ?|||the following code executes from a connection object without issues using ado 2.6 and 2.7:

DECLARE c8281 CURSOR FOR
SELECT * From Users WHERE ( Users.User_ID = 17 )
OPEN c8281
FETCH NEXT FROM c8281
UPDATE [Users] SET
User_Name = 'Unknown'
WHERE CURRENT OF c8281
CLOSE c8281
DEALLOCATE c8281

however, if I use ADO 2.8 it returns error code 80004005 (unspecified error) and native error = 0. furthermore, it actually executes at the database server.

I made it work without errors by modifying the code in the following way:

DECLARE @.username VARCHAR
DECLARE c8281 CURSOR FOR
SELECT User_Name From Users WHERE ( Users.User_ID = 17 )
OPEN c8281
FETCH NEXT FROM c8281 INTO @.username
UPDATE [Users] SET
User_Name = 'Unknown'
WHERE CURRENT OF c8281
CLOSE c8281
DEALLOCATE c8281

which is closer to ansi92 I guess. but I just really need to scroll through the cursor. no need for local variables.

Wednesday, March 21, 2012

Maybe this explains the issue I am finding with SQLMail

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

Maybe this explains the issue I am finding with SQLMail

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

quote:

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

can do

quote:

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

part.

quote:

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

Microsoft

quote:

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

Server

quote:

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

Microsoft

quote:

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

quote:

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

sent.

quote:

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

pst.

quote:

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

Microsoft

quote:

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

quote:

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

Microsoft

quote:

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

quote:

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

profile I

quote:

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

Server

quote:

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

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

quote:

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

Outlook

quote:

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

for.

quote:

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

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 version error

Wednesday, March 28, 2012

MDAC error on VFP linked server

MDAC error on VFP linked server

MDAC error

mdac error

MDAC 2.8 Update Causes Problems

MDAC 2.8 Update Causes Problems

MDAC 2.8 Update Causes Problems

MDAC 2.8 on SQL 2000 Sp3a

MDAC 2.8 on SQL 2000 Sp3a

MDAC 2.8 on SQL 2000 Sp3a

MDAC 2.8 Fatal Setup Error. This setup does not support installing on this operating system

MDAC 2.8 Fatal Setup Error. This setup does not support installing on this operating system

MDAC 2.8 Fatal Setup Error. This setup does not support installing on this operating system

MDAC 2.8 Fatal Setup Error. This setup does not support installing on this operating system

MDAC 2.8 Fatal Setup Error. This setup does not support installing on this operating system

MDAC 2.8 and cursor FETCH NEXT

Wednesday, March 21, 2012

Maybe this explains the issue I am finding with SQLMail

Maybe this explains the issue I am finding with SQLMail

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