Tuesday, March 6, 2012
ADOMD.NET DbProviderFactory
Moved it from BCL forum to Data Access and Storage forum where is more appropriate.
Thank you for your active participation!
ADOMD.Connection error
and there is no designated default provider' on a 64 bit machine with
both Sql 2K 32bit and Sql 2K5 64bit installed. It happens from Vbscript
that backs up our Olap databases. The script (below) works fine on a 32
bit server with Sql 2K installed.
Function QueryDatabaseList()
Dim oConnectionServer
Dim oRS
Dim arrDatabase
Set oConnectionServer =CreateObject("ADODB.Connection")
oConnectionServer.ConnectionString = "Data Source=" & ServerName &
"; Provider=MSOLAP.2"
oConnectionServer.Open
Set oRS = oConnectionServer.OpenSchema(adSchemaCatalogs)
arrDatabase = oRs.GetRows
oConnectionServer.Close
Set oConnectionServer = Nothing
QueryDatabaseList = arrDatabase
End Function
I am pretty sure the problem has to do with the fact that the right
driver can not be found. But which one?
Thanks in advance,
Koni.
MSOLAP.2 is for AS2000
so try MSOLAP.3 for SSAS2005
"Koni" <kkogan@.haiint.com> wrote in message
news:uAgqmPoPHHA.1152@.TK2MSFTNGP03.phx.gbl...
> We are getting this error: 'ADODB.Connection: Provider is not specified
> and there is no designated default provider' on a 64 bit machine with both
> Sql 2K 32bit and Sql 2K5 64bit installed. It happens from Vbscript that
> backs up our Olap databases. The script (below) works fine on a 32 bit
> server with Sql 2K installed.
> Function QueryDatabaseList()
> Dim oConnectionServer
> Dim oRS
> Dim arrDatabase
>
> Set oConnectionServer =CreateObject("ADODB.Connection")
> oConnectionServer.ConnectionString = "Data Source=" & ServerName & ";
> Provider=MSOLAP.2"
> oConnectionServer.Open
> Set oRS = oConnectionServer.OpenSchema(adSchemaCatalogs)
> arrDatabase = oRs.GetRows
> oConnectionServer.Close
> Set oConnectionServer = Nothing
> QueryDatabaseList = arrDatabase
> End Function
> I am pretty sure the problem has to do with the fact that the right driver
> can not be found. But which one?
>
> Thanks in advance,
> Koni.
ADOMD.Connection error
and there is no designated default provider' on a 64 bit machine with
both Sql 2K 32bit and Sql 2K5 64bit installed. It happens from Vbscript
that backs up our Olap databases. The script (below) works fine on a 32
bit server with Sql 2K installed.
Function QueryDatabaseList()
Dim oConnectionServer
Dim oRS
Dim arrDatabase
Set oConnectionServer =CreateObject("ADODB.Connection")
oConnectionServer.ConnectionString = "Data Source=" & ServerName &
"; Provider=MSOLAP.2"
oConnectionServer.Open
Set oRS = oConnectionServer.OpenSchema(adSchemaCatalogs)
arrDatabase = oRs.GetRows
oConnectionServer.Close
Set oConnectionServer = Nothing
QueryDatabaseList = arrDatabase
End Function
I am pretty sure the problem has to do with the fact that the right
driver can not be found. But which one?
Thanks in advance,
Koni.MSOLAP.2 is for AS2000
so try MSOLAP.3 for SSAS2005
"Koni" <kkogan@.haiint.com> wrote in message
news:uAgqmPoPHHA.1152@.TK2MSFTNGP03.phx.gbl...
> We are getting this error: 'ADODB.Connection: Provider is not specified
> and there is no designated default provider' on a 64 bit machine with both
> Sql 2K 32bit and Sql 2K5 64bit installed. It happens from Vbscript that
> backs up our Olap databases. The script (below) works fine on a 32 bit
> server with Sql 2K installed.
> Function QueryDatabaseList()
> Dim oConnectionServer
> Dim oRS
> Dim arrDatabase
>
> Set oConnectionServer =CreateObject("ADODB.Connection")
> oConnectionServer.ConnectionString = "Data Source=" & ServerName & ";
> Provider=MSOLAP.2"
> oConnectionServer.Open
> Set oRS = oConnectionServer.OpenSchema(adSchemaCatalogs)
> arrDatabase = oRs.GetRows
> oConnectionServer.Close
> Set oConnectionServer = Nothing
> QueryDatabaseList = arrDatabase
> End Function
> I am pretty sure the problem has to do with the fact that the right driver
> can not be found. But which one?
>
> Thanks in advance,
> Koni.
Saturday, February 25, 2012
ADODB Connection Error.
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:
ADODB Connection Error.
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"
- AnonymousWhat 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/details.aspx?FamilyID=8f0a8df6-4a21-4b43-bf53-14332ef092c9&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...
> > 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
>
>|||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/details.aspx?FamilyID=8f0a8df6-4a21-4b43-bf53-14332ef092c9&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
>
>|||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...
> 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/details.aspx?FamilyID=8f0a8df6-4a21-4b43-bf53-14332ef092c9&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
>>|||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...
> > 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/details.aspx?FamilyID=8f0a8df6-4a21-4b43-bf53-14332ef092c9&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
> >>
> >>
> >>
>
>|||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...
> 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...
>> > 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/details.aspx?FamilyID=8f0a8df6-4a21-4b43-bf53-14332ef092c9&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
>> >>
>> >>
>> >>
>>|||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...
> > 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...
> >> > 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/details.aspx?FamilyID=8f0a8df6-4a21-4b43-bf53-14332ef092c9&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
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>
>
>|||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...
> 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...
>> > 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...
>> >> > 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/details.aspx?FamilyID=8f0a8df6-4a21-4b43-bf53-14332ef092c9&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
>> >> >>
>> >> >>
>> >> >>
>> >>
>> >>
>> >>
>>|||Hi
Can you confirm that other workstations are working ok?
You may want to try re-installing the client tools.
John
"Arunkumar" <Arunkumar@.discussions.microsoft.com> wrote in message
news:C4D95659-D871-4939-9BE3-45631F8AA1B7@.microsoft.com...
> 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...
>> > 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...
>> >> > 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/details.aspx?FamilyID=8f0a8df6-4a21-4b43-bf53-14332ef092c9&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
>> >> >>
>> >> >>
>> >> >>
>> >>
>> >>
>> >>
>>|||Tried with my neighbours system, found to be working fine. But the error is
ONLY
with my system.
The application is in my system and the database is in different workstation
- DAN this is FYI
Arun
--
"Knowledge grows when Shared"
- Anonymous
"John Bell" wrote:
> Hi
> Can you confirm that other workstations are working ok?
> You may want to try re-installing the client tools.
> John
> "Arunkumar" <Arunkumar@.discussions.microsoft.com> wrote in message
> news:C4D95659-D871-4939-9BE3-45631F8AA1B7@.microsoft.com...
> > 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...
> >> > 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...
> >> >> > 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/details.aspx?FamilyID=8f0a8df6-4a21-4b43-bf53-14332ef092c9&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
> >> >> >>
> >> >> >>
> >> >> >>
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>
>
>|||> The application is in my system and the database is in different
> workstation
> - DAN this is FYI
I just wanted to make sure that you are doing this the client rather than
the server.
I've never run into a situation where an errant MDAC installation wasn't
identified by the component checker. I don't have any other suggestions
other than those already provided.
Unless someone else chimes in, you might take the advise of the system
support people and repave. As painful as that is, it might be the most
expedient solution.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Arunkumar" <Arunkumar@.discussions.microsoft.com> wrote in message
news:09442D27-7968-42F8-ABC2-D98E9F860374@.microsoft.com...
> Tried with my neighbours system, found to be working fine. But the error
> is
> ONLY
> with my system.
> The application is in my system and the database is in different
> workstation
> - DAN this is FYI
> Arun
> --
> "Knowledge grows when Shared"
> - Anonymous
>
> "John Bell" wrote:
>> Hi
>> Can you confirm that other workstations are working ok?
>> You may want to try re-installing the client tools.
>> John
>> "Arunkumar" <Arunkumar@.discussions.microsoft.com> wrote in message
>> news:C4D95659-D871-4939-9BE3-45631F8AA1B7@.microsoft.com...
>> > 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...
>> >> > 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...
>> >> >> > 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/details.aspx?FamilyID=8f0a8df6-4a21-4b43-bf53-14332ef092c9&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
>> >> >> >>
>> >> >> >>
>> >> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >>
>> >>
>> >>
>>
ADODB Connection Error.
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"
- AnonymousWhat 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/...&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 checke
r
> http://www.microsoft.com/downloads/...&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 y
ou
> 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 i
s
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:
>
ADODB - Cube connection error: Provider could not set DATASOURCE, USERID, or PASSWORD property
When attempting to connect to my cube from the same server, I receive this error:
"Provider could not set DATASOURCE, USERID, or PASSWORD property"
The connection works just fine from my machine, but when going from the server to the server, I profile it, and no connection attempts are made. The server is w2k3 SE sp1, and the successful client is win xp pro sp2.
The method I'm using is an adodb ConnectionClass in C# vs.net 2003. The adodb is using v2.8, and I used the component checker to make sure the server has 2.8 - it does.
I have the user name and password in the connection string,
"Provider=MSOLAP.3;Cache Authentication=True;Persist Security Info=False;Initial Catalog=thecatalog;Data Source=theServerName;"
calling the open like: cn.Open(ConnectionString, "theuser", "thepass", 0);
and if it successfully opens, then I make use of an adomd.cellset.
I'm currently checking component differences between the 2 machines, but does anyone have any specific things to try or specific components to check?
First I would make sure you can establish OLED connection from one machine to another.
You can find here some clues on how to troubleshoot connection problems: http://www.sqljunkies.com/WebLog/edwardm/archive/2006/05/26/21447.aspx
Second, as you already suggested, I would check configuration of components.
Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
ADODB - Cube connection error: Provider could not set DATASOURCE, USERID, or PASSWORD proper
When attempting to connect to my cube from the same server, I receive this error:
"Provider could not set DATASOURCE, USERID, or PASSWORD property"
The connection works just fine from my machine, but when going from the server to the server, I profile it, and no connection attempts are made. The server is w2k3 SE sp1, and the successful client is win xp pro sp2.
The method I'm using is an adodb ConnectionClass in C# vs.net 2003. The adodb is using v2.8, and I used the component checker to make sure the server has 2.8 - it does.
I have the user name and password in the connection string,
"Provider=MSOLAP.3;Cache Authentication=True;Persist Security Info=False;Initial Catalog=thecatalog;Data Source=theServerName;"
calling the open like: cn.Open(ConnectionString, "theuser", "thepass", 0);
and if it successfully opens, then I make use of an adomd.cellset.
I'm currently checking component differences between the 2 machines, but does anyone have any specific things to try or specific components to check?
First I would make sure you can establish OLED connection from one machine to another.
You can find here some clues on how to troubleshoot connection problems: http://www.sqljunkies.com/WebLog/edwardm/archive/2006/05/26/21447.aspx
Second, as you already suggested, I would check configuration of components.
Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Friday, February 24, 2012
ADO.NET OleDb SET ROWCOUNT or DBPROP_MAXROWS
I am writing a data access tool that needs to be non provider specific. I have used System.Data.OleDb to access a variety of data source types (MSSQLServer, MSAccess, MSExcel, CSV, Oracle, XML). This works beautifully. Thankyou Microsoft for giving us ADO.NET2.0.
However, I now need to restrict the number of rows returned from a SELECT statement. Is there any way I can I achieve this in a non provider specific fashion?
So far searches have yielded DBPROP_MAXROWS however I can find no way of setting the DBProperties using ADO.NET2.0. Is this possible?
Documentation for DBPROP_MAXROWS states that it uses "SET ROWCOUNT n" as part of the command text. I tried this and it works but not for the JET4 provider (this is a problem since I use JET4 to access .mdb, .xls and .csv files)!
Any tips here would be greatly appreciated. Even if somebody were to tell me that it's just not possible, at least that would put me out of my misery :)
Thanks.
Because of the way JET accesses data, bringing all of the data to the client before processing the criteria, I don't think that there is a way to make that work.|||Thanks for the reply Arnie,
since posting I have done some more research and discovered that using TOP works for Jet. This is good for me as it also works for SQL Server. The approach I have taken is as follows:
int maxRows = 100;
string someQry = "SELECT * FROM table1";
string topQry = "SELECT TOP " + maxRows.ToString() + " * FROM (" + someQry + ") as topSubQry";
However it doesn't work for XML files. To get data from XML files I use a connection string of "Provider=MSDAOSP.1;Data Source=MSXML2.DSOControl.2.6;" and then the full path to the XML file as the command text. I am guessing there will just be no way to limit the rows returned when using this provider.
ADO with SQLXMLOLEDB
A command is created on a connection with SQLXMLOLEDB provider(SQLXML4.0).
1. Where do you find information for the [cmd.dialect]
2. With you can provide an InputFile and get an outputFile. What are the formats of these files?
3. What are the appropraite argumetns for the cmd's execute method?
Can you provide a link for SQLXML4.0 download?
Appreciate even part answers.
Thanks.
Jayaram Krishnaswamy
my web site: http://www.angelfire.com/vt2/hodentek
I blog at: http://hodentek.blogspot.com
The inputFile is really a template file. The structure of thsi file seems to have changed from version 3.0 to version 4.0.
If the inputFile(template) sent a SQL statement, it shound be executed on the server and the outFile should have the result in XML.
So far the only thing that has happnned is that the inpuTemplate file is read, the outpuFile is produced, but alas! it is the exact reproduction of input file.
inputFile: "Select * from Employees for xml raw"
outputFile: "Select * from Employees for xml raw"
Conclusions at this point:
The query never reached the server. so there appears to be a feed forward from inputFile to outFile bypassing the server.
Action Itemsleft:
find documenttion!
Monday, February 13, 2012
ADO connection options
number of SET commands are issued. In particular
SET CONCAT_NULL_YIELDS_NULL ON
is issued, and I'd like to change that to OFF. I've set the database option
to turn this off by default, but all of the client connections still issue
the command. Is there a way in the connect string to specify SET options?
Thanks,
TomI don=B4t know of any settings to manipulate this. You only chance for
this is to put the command in your batch fired against the SQL Server.
HTH, jens Suessmeyer.|||Change you query to ISNULL(column,'')
Tom wrote:
> I noticed when connecting to SQL Server using the SQL OLEDB provider that
a
> number of SET commands are issued. In particular
> SET CONCAT_NULL_YIELDS_NULL ON
> is issued, and I'd like to change that to OFF. I've set the database opti
on
> to turn this off by default, but all of the client connections still issue
> the command. Is there a way in the connect string to specify SET options?
> Thanks,
> Tom
ADO connection options
number of SET commands are issued. In particular
SET CONCAT_NULL_YIELDS_NULL ON
is issued, and I'd like to change that to OFF. I've set the database option
to turn this off by default, but all of the client connections still issue
the command. Is there a way in the connect string to specify SET options?
Thanks,
Tom
I don=B4t know of any settings to manipulate this. You only chance for
this is to put the command in your batch fired against the SQL Server.
HTH, jens Suessmeyer.
|||Change you query to ISNULL(column,'')
Tom wrote:
> I noticed when connecting to SQL Server using the SQL OLEDB provider that a
> number of SET commands are issued. In particular
> SET CONCAT_NULL_YIELDS_NULL ON
> is issued, and I'd like to change that to OFF. I've set the database option
> to turn this off by default, but all of the client connections still issue
> the command. Is there a way in the connect string to specify SET options?
> Thanks,
> Tom
ADO Connection BeginTrans() CommitTrans() RollbackTrans()
i had to encapsulate anything related to DB connections into a class, and had an instance variable store where a transaction was active.|||Yeah, that's what we did too. I guess the design mistake we made was sharing 1 connection accross multiple instances of this class. I guess we could change the m_bTrans member to be static.
Thanks,