Saturday, February 25, 2012

ADODB Connection Error.

Error Type:
ADODB.Connection (0x800A0E7A)
Provider cannot be found. It may not be properly installed.
/visastatus/NewEmpVisaDetails.asp, line 35
Even registering the dll "sqloledb.dll" didn't fix the problem. Added to
it...
The Enterprise Manager is giving an error " Provider cannot be found. It may
not be properly installed."
Do let me know the fix, i have reinstalled the SQL 2000, the fix given by
the system support people is to reformat my system.
Arun
"Knowledge grows when Shared"
- Anonymous
What does your connection string look like? It will probably have the word
provider in it.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Arunkumar" <Arunkumar@.discussions.microsoft.com> wrote in message
news:41DF7DCA-0843-4635-B61C-3E133B760223@.microsoft.com...
> Error Type:
> ADODB.Connection (0x800A0E7A)
> Provider cannot be found. It may not be properly installed.
> /visastatus/NewEmpVisaDetails.asp, line 35
> Even registering the dll "sqloledb.dll" didn't fix the problem. Added to
> it...
> The Enterprise Manager is giving an error " Provider cannot be found. It
> may
> not be properly installed."
> Do let me know the fix, i have reinstalled the SQL 2000, the fix given by
> the system support people is to reformat my system.
> Arun
> --
> "Knowledge grows when Shared"
> - Anonymous
|||Hi
You may want to check MDAC is installed correctly see the component checker
http://www.microsoft.com/downloads/d...DisplayLang=en
John
"Arunkumar" <Arunkumar@.discussions.microsoft.com> wrote in message
news:41DF7DCA-0843-4635-B61C-3E133B760223@.microsoft.com...
> Error Type:
> ADODB.Connection (0x800A0E7A)
> Provider cannot be found. It may not be properly installed.
> /visastatus/NewEmpVisaDetails.asp, line 35
> Even registering the dll "sqloledb.dll" didn't fix the problem. Added to
> it...
> The Enterprise Manager is giving an error " Provider cannot be found. It
> may
> not be properly installed."
> Do let me know the fix, i have reinstalled the SQL 2000, the fix given by
> the system support people is to reformat my system.
> Arun
> --
> "Knowledge grows when Shared"
> - Anonymous
|||Cotter
Yep ur right it does house the word Provider in the connection, but i was
able to establish the connection previously.
Would that affect my enterprise manager too, even when i right click on a
table and when i choose return all rows it is giving me a "Provider...not
installed".
Rather it is a problem with the SQL(Enterprise manager) rather than the
connection string...(Guess so!), if not let me know how do i modify the
connection string.
Here is how my connection string looks
set objConn=Server.CreateObject("ADODB.CONNECTION")
objConn.Open "Provider=SQLOLEDB;data Source=<my server>;Initial Catalog=<my
database>;User Id= <id> ;Password= pwd"
"Knowledge grows when Shared"
- Anonymous
"Hilary Cotter" wrote:

> What does your connection string look like? It will probably have the word
> provider in it.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "Arunkumar" <Arunkumar@.discussions.microsoft.com> wrote in message
> news:41DF7DCA-0843-4635-B61C-3E133B760223@.microsoft.com...
>
>
|||John
I have already installed Component Checker, do let me know where do i find
the error, educate me how to use it for trouble shooting.
Arun
"Knowledge grows when Shared"
- Anonymous
"John Bell" wrote:

> Hi
> You may want to check MDAC is installed correctly see the component checker
> http://www.microsoft.com/downloads/d...DisplayLang=en
> John
> "Arunkumar" <Arunkumar@.discussions.microsoft.com> wrote in message
> news:41DF7DCA-0843-4635-B61C-3E133B760223@.microsoft.com...
>
>
|||Hi
If you run the component checker it will show you the dlls installed and
what version they are at. If you are at a version less than 2.8 SP1 then you
may want to consider trying an upgrade.
John
"Arunkumar" <Arunkumar@.discussions.microsoft.com> wrote in message
news:689B1660-DB62-4B85-B63B-7B8CD27F8C94@.microsoft.com...[vbcol=seagreen]
> John
> I have already installed Component Checker, do let me know where do i find
> the error, educate me how to use it for trouble shooting.
> Arun
> --
> "Knowledge grows when Shared"
> - Anonymous
>
> "John Bell" wrote:
|||I'm having MDAC 2.8 SP1...It is giving me the Product Release matches.
What else could be the problem...!!!
Arun
"Knowledge grows when Shared"
- Anonymous
"John Bell" wrote:

> Hi
> If you run the component checker it will show you the dlls installed and
> what version they are at. If you are at a version less than 2.8 SP1 then you
> may want to consider trying an upgrade.
> John
> "Arunkumar" <Arunkumar@.discussions.microsoft.com> wrote in message
> news:689B1660-DB62-4B85-B63B-7B8CD27F8C94@.microsoft.com...
>
>
|||The component checker will usually detect problems with installed
components. You might try reinstalling the MDAC 2.8 SP1.
Hope this helps.
Dan Guzman
SQL Server MVP
"Arunkumar" <Arunkumar@.discussions.microsoft.com> wrote in message
news:A7F3B556-4CDC-49F9-AAB9-3842A02E1AAF@.microsoft.com...[vbcol=seagreen]
> I'm having MDAC 2.8 SP1...It is giving me the Product Release matches.
> What else could be the problem...!!!
> Arun
> --
> "Knowledge grows when Shared"
> - Anonymous
>
> "John Bell" wrote:
|||Forgive me i have done that 2...reinstalled the SQL, MDAC 2.8, but nothing is
happening.
I wouldn't want to c my system getting formatted for this system...some1
HELP!!!!
Arun
"Knowledge grows when Shared"
- Anonymous
"Dan Guzman" wrote:

> The component checker will usually detect problems with installed
> components. You might try reinstalling the MDAC 2.8 SP1.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Arunkumar" <Arunkumar@.discussions.microsoft.com> wrote in message
> news:A7F3B556-4CDC-49F9-AAB9-3842A02E1AAF@.microsoft.com...
>
>
|||It's strange that the component checker didn't detect an error so server
that both ODBC and SQLOLEDB providers are not found. Do all components
match? Did you reboot after the MDAC reinstall?
Just to be clear, if SQL Server and your application are running on a
different machines, you should be focusing on the client box rather than the
database server.
Hope this helps.
Dan Guzman
SQL Server MVP
"Arunkumar" <Arunkumar@.discussions.microsoft.com> wrote in message
news:C4D95659-D871-4939-9BE3-45631F8AA1B7@.microsoft.com...[vbcol=seagreen]
> Forgive me i have done that 2...reinstalled the SQL, MDAC 2.8, but nothing
> is
> happening.
> I wouldn't want to c my system getting formatted for this system...some1
> HELP!!!!
> Arun
> --
> "Knowledge grows when Shared"
> - Anonymous
>
> "Dan Guzman" wrote:

No comments:

Post a Comment