Data Source Provider Error: The event log file is full

I'm trying to process one of my cubes and am getting this error, see subject
line. Mt configuration is this: Development Web server Dul09 holds the cube
s. The data lives on a SQL server DryHou10. I have had my sysadmin check the
event logs on both serv
ers, neither of which is full. This setup has been working just fine for the
last few years. Other cubes on Dul09, using different SQL servers for data,
process just fine.
All servers are running SQL 2000TJSully wrote:
> *I'm trying to process one of my cubes and am getting this error, see
> subject line. Mt configuration is this: Development Web server Dul09
> holds the cubes. The data lives on a SQL server DryHou10. I have had
> my sysadmin check the event logs on both serv
> ers, neither of which is full. This setup has been working just fine
> for the last few years. Other cubes on Dul09, using different SQL
> servers for data, process just fine.
> All servers are running SQL 2000 *
annieckl
---
Posted via http://www.mcse.ms
---
View this thread: http://www.mcse.ms/message441896.html|||Are you sure that they are not full...I got the same error once and emptied
all my logs (you can put them into files if
you want to keep them) - it worked again after that.
--Michael
"annieckl" <annieckl.1dtcei@.mail.mcse.ms> skrev i en meddelelse
news:annieckl.1dtcei@.mail.mcse.ms...
> TJSully wrote:
>
> --
> annieckl
> ---
> Posted via http://www.mcse.ms
> ---
> View this thread: http://www.mcse.ms/message441896.html
>

data provider or other service returned an E_Fail status in sql server 2005

after converting database from sql server 2000 to sql server 2005. my program on vb6 is facing runtime error. i.e.data provider or other service returned an E_Fail status .

how can i get rid this problem

Could you please post your connection string and the exact error message that you are getting.

Jag

|||

Main_Module.STRCNNN1 = "driver={SQL Server};server=" & Main_Module.Server_Name & ";" & _
"uid=SA;pwd=;database=" & Main_Module.Common_Database
error msg is

runtime error

data provider or other service returned an E_Fail status in sql server 2005

when i am fetching record from view using order by clause in select statement then error is coming

as

select * from vew_emp where grade='C' order empno

at the first time it fetching record with order by

but when i am using recordset.Requiry

it cud not fetch the record

i think when the recordset is open with the record of view

i am deleting ,inserting record in the view base table then the main recordset is not working

without using order by it is running and working well
plz reply me quickly

data provider or other service returned an E_Fail status in sql server 2005

Main_Module.STRCNNN1 = "driver={SQL Server};server=" & Main_Module.Server_Name & ";" & _
"uid=SA;pwd=;database=" & Main_Module.Common_Database
error msg is

runtime error

data provider or other service returned an E_Fail status in sql server 2005

when i am fetching record from view using order by clause in select statement then error is coming

as

select * from vew_emp where grade='C' order empno

at the first time it fetching record with order by

but when i am using recordset.Requiry

it cud not fetch the record

i think when the recordset is open with the record of view

i am deleting ,inserting record in the view base table then the main recordset is not working

without using order by it is running and working well
plz reply me quickly

Move the thread from Visual Basic Language in order to get better and satisfied answers.

|||

Take a look at this - http://www.sql-server-performance.com/forum/topic.asp?TOPIC_ID=3778

Hope this helps

Data Provider List Missing...very odd SQL 2000

Hey All!

I have an interseting situation with one of my dev machines. (W2k3EE, SQL2k SP4)

All my linked servers stopped working posting this error:

Server: Msg 7302, Level 16, State 1, Line 1
Could not create an instance of OLE DB provider [enter provider name here, e.g. 'SQLOLEDB'.

So...when attempting to drop and recreate the linked server, the Provider pull down in the GUI is completely empty.

YIKES!

I'm thinking of reinstalling MDAC, but I've never seen this in 10 years of DBA'ing.

Have any of you? Any thoughts out there? Registry issues?

Cheers,
OddNever seen anything like it either. I'm running the same combination in my environment, so if you have any solutions, please post.

Some thoughts and/or suggestions:

1. Was the server recently patched?

2. Was any new software (eg. driver package) recently installed?

3. Any entries in the Application or System error log(s)?

4. Do you back up the registry on this machine? Can it be restored?

Regards,

hmscott|||Thanks for the reply...will definitely post what I find...

1 - yeah, SP4
2 - prolly so...the network guys love to drop agents on my dev servers without mentioning it...Alteris monitor, i think this time
3 - nada
4 - heck no, that would be too easy

:)

data provider cannot be found

Hi there,

I am trying to use the new ListView control in VS2008 in an ASP.Net app. My problem starts already with the datasource. I drag and drop a SqlDataSource and select

Microsoft SQL Server Compact 3.5 (.NET Framework Data Provider for Microsoft SQL Server Compact 3.5)

I can connect to the database and test the query in the wizard (I do not need to use a password??)

This is the webconfig entry

<add name="ConnectionString" connectionString="Data Source=C:\Program Files\Microsoft SQL Server Compact Edition\v3.5\Samples\Northwind.sdf" providerName="Microsoft.SqlServerCe.Client.3.5"/>

I add the following line in the page load event

AppDomain.CurrentDomain.SetData("SQLServerCompactEditionUnderWebHosting", true);

However I get the error message that the data provider cannot be found and it might not be installed. I added the reference and also gave the folder above ASP.NET full access rights.

Anyone else encountered this problem. It is quiet strange? Thanks a lot for your help.

Cheers,

Chris

Hi,

From your description, it seems that you are wondering why the database creating wizard doesn't ask for your userid and password, and another question is why does you application can't find the data provider, right?

For you first question, I think what the database you created is in Windows Authentication mode, so when you create a database connection wizard, the wizard connects to your database by your windows account. If you want to change the windows authentication mode, you may open your sqlserver enterprise manager, and change the authentication mode to SQL mixed authentication mode in the security part.

Second, from the provider in your connection string, you are using .NET Framework Data Provider for Microsoft SQL Server Compact 3.5. But the application you created is a ASP.NET application, so are you sure you want to connect a SQLServer compact edition. Generally, you should create a SQLServer database and use "System.Data.SqlClient" as the providername in your connection string.

Thanks.

|||

Hi Michael,

of course you are right. I realised yesterday that I just use the wrong data provider. Stupid me. All works fine now.

Thanks again,

Cheers,

Chris

sql

Data Processing Extension for ADO.NET?

Is there a data processing extension for use with an ADO.NET provider? MSDN
lists ones for SQL Server, OLEDB, Oracle, and ODBC.. ADO.NET is a glaring
omission.
The extension interfaces (IDbConnection, etc) are all similar to ADO.NET's.
I could write a pretty thin custom extension wrapper around an ADO.NET
provider, but why should I have to?Ah, it says you can use a .NET data provider directly from Reporting
Services, without a data processing extension. However, how do you let
Reporting Services know about your provider?
"Daniel Michaeloff" wrote:
> Is there a data processing extension for use with an ADO.NET provider? MSDN
> lists ones for SQL Server, OLEDB, Oracle, and ODBC.. ADO.NET is a glaring
> omission.
> The extension interfaces (IDbConnection, etc) are all similar to ADO.NET's.
> I could write a pretty thin custom extension wrapper around an ADO.NET
> provider, but why should I have to?|||When using a managed provider, you can either use it directly or write a
custom data extension which internally uses the provider. In general you can
use most .NET data providers (which implement System.Data.IDBConnection,
etc.). A .NET data provider would need to be registered in both,
rsReportDesigner.config and rsReportServer.config.
Lets assume your .NET provider has the assembly name "MyAssembly" and the
actual class that implements IDBConnection is called
"MyAssembly.MyConnection". Here is how you would register it:
* RSReportServer.config:
<Extension Name="MyProvider"
Type="MyAssembly.MyConnection,MyAssembly"/>
* RSReportDesigner.config
The registration for report designer would need to happen in two places - in
the <Data> section and in the <Designer> section.
<Data>
...
<Extension Name="MyProvider"
Type="MyAssembly.MyConnection,MyAssembly"/>
</Data>
<Designer>
...
<Extension Name="MyProvider"
Type="MyAssembly.MyConnection,MyAssembly"/>
</Designer>
After registering, you will get a new entry "MyProvider" in the data source
type drop-down list.
See also:
http://msdn.microsoft.com/library/en-us/RSPROG/htm/rsp_prog_extend_dataproc_8iqq.asp
Robert M. Bruckner
Microsoft SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Daniel Michaeloff" <DanielMichaeloff@.discussions.microsoft.com> wrote in
message news:BD89B815-BC0E-4ABD-9A36-07F7B31A303B@.microsoft.com...
> Is there a data processing extension for use with an ADO.NET provider?
> MSDN
> lists ones for SQL Server, OLEDB, Oracle, and ODBC.. ADO.NET is a glaring
> omission.
> The extension interfaces (IDbConnection, etc) are all similar to
> ADO.NET's.
> I could write a pretty thin custom extension wrapper around an ADO.NET
> provider, but why should I have to?|||Correction to my posting below - the <Designer> element in
RSReportDesigner.config should have the following contents:
<Designer>
...
<Extension Name="MyProvider"
Type="Microsoft.ReportDesigner.Design.GQDQueryDesigner,Microsoft.ReportingServices.Designer"/>
</Designer>
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Robert Bruckner [MSFT]" <robruc@.online.microsoft.com> wrote in message
news:%23qgs5sXXFHA.3280@.TK2MSFTNGP09.phx.gbl...
> When using a managed provider, you can either use it directly or write a
> custom data extension which internally uses the provider. In general you
> can use most .NET data providers (which implement
> System.Data.IDBConnection, etc.). A .NET data provider would need to be
> registered in both, rsReportDesigner.config and rsReportServer.config.
> Lets assume your .NET provider has the assembly name "MyAssembly" and the
> actual class that implements IDBConnection is called
> "MyAssembly.MyConnection". Here is how you would register it:
> * RSReportServer.config:
> <Extension Name="MyProvider"
> Type="MyAssembly.MyConnection,MyAssembly"/>
> * RSReportDesigner.config
> The registration for report designer would need to happen in two places -
> in the <Data> section and in the <Designer> section.
> <Data>
> ...
> <Extension Name="MyProvider"
> Type="MyAssembly.MyConnection,MyAssembly"/>
> </Data>
> <Designer>
> ...
> <Extension Name="MyProvider"
> Type="MyAssembly.MyConnection,MyAssembly"/>
> </Designer>
> After registering, you will get a new entry "MyProvider" in the data
> source type drop-down list.
> See also:
> http://msdn.microsoft.com/library/en-us/RSPROG/htm/rsp_prog_extend_dataproc_8iqq.asp
>
> --
> Robert M. Bruckner
> Microsoft SQL Server Reporting Services
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
> "Daniel Michaeloff" <DanielMichaeloff@.discussions.microsoft.com> wrote in
> message news:BD89B815-BC0E-4ABD-9A36-07F7B31A303B@.microsoft.com...
>> Is there a data processing extension for use with an ADO.NET provider?
>> MSDN
>> lists ones for SQL Server, OLEDB, Oracle, and ODBC.. ADO.NET is a glaring
>> omission.
>> The extension interfaces (IDbConnection, etc) are all similar to
>> ADO.NET's.
>> I could write a pretty thin custom extension wrapper around an ADO.NET
>> provider, but why should I have to?
>|||Thanks Robert, this is what I needed.
However, is there a way to avoid putting our provider assemblies in the
global assembly cache?
"Robert Bruckner [MSFT]" wrote:
> Correction to my posting below - the <Designer> element in
> RSReportDesigner.config should have the following contents:
> <Designer>
> ...
> <Extension Name="MyProvider"
> Type="Microsoft.ReportDesigner.Design.GQDQueryDesigner,Microsoft.ReportingServices.Designer"/>
> </Designer>
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Robert Bruckner [MSFT]" <robruc@.online.microsoft.com> wrote in message
> news:%23qgs5sXXFHA.3280@.TK2MSFTNGP09.phx.gbl...
> > When using a managed provider, you can either use it directly or write a
> > custom data extension which internally uses the provider. In general you
> > can use most .NET data providers (which implement
> > System.Data.IDBConnection, etc.). A .NET data provider would need to be
> > registered in both, rsReportDesigner.config and rsReportServer.config.
> >
> > Lets assume your .NET provider has the assembly name "MyAssembly" and the
> > actual class that implements IDBConnection is called
> > "MyAssembly.MyConnection". Here is how you would register it:
> > * RSReportServer.config:
> > <Extension Name="MyProvider"
> > Type="MyAssembly.MyConnection,MyAssembly"/>
> >
> > * RSReportDesigner.config
> > The registration for report designer would need to happen in two places -
> > in the <Data> section and in the <Designer> section.
> >
> > <Data>
> > ...
> > <Extension Name="MyProvider"
> > Type="MyAssembly.MyConnection,MyAssembly"/>
> > </Data>
> > <Designer>
> > ...
> > <Extension Name="MyProvider"
> > Type="MyAssembly.MyConnection,MyAssembly"/>
> > </Designer>
> >
> > After registering, you will get a new entry "MyProvider" in the data
> > source type drop-down list.
> >
> > See also:
> > http://msdn.microsoft.com/library/en-us/RSPROG/htm/rsp_prog_extend_dataproc_8iqq.asp
> >
> >
> > --
> > Robert M. Bruckner
> > Microsoft SQL Server Reporting Services
> > This posting is provided "AS IS" with no warranties, and confers no
> > rights.
> >
> >
> >
> > "Daniel Michaeloff" <DanielMichaeloff@.discussions.microsoft.com> wrote in
> > message news:BD89B815-BC0E-4ABD-9A36-07F7B31A303B@.microsoft.com...
> >> Is there a data processing extension for use with an ADO.NET provider?
> >> MSDN
> >> lists ones for SQL Server, OLEDB, Oracle, and ODBC.. ADO.NET is a glaring
> >> omission.
> >>
> >> The extension interfaces (IDbConnection, etc) are all similar to
> >> ADO.NET's.
> >> I could write a pretty thin custom extension wrapper around an ADO.NET
> >> provider, but why should I have to?
> >
> >
>
>|||Actually, I'm not getting Report Designer to pick up my assembly from the
GAC, and I don't see anything like "Microsoft.ReportingServices" in the GAC
either. I've also tried dropping my dll in Report Designer's main directory.
Where does Report Designer / Reporting Services look for extensions?
"Daniel Michaeloff" wrote:
> Thanks Robert, this is what I needed.
> However, is there a way to avoid putting our provider assemblies in the
> global assembly cache?
> "Robert Bruckner [MSFT]" wrote:
> > Correction to my posting below - the <Designer> element in
> > RSReportDesigner.config should have the following contents:
> >
> > <Designer>
> > ...
> > <Extension Name="MyProvider"
> > Type="Microsoft.ReportDesigner.Design.GQDQueryDesigner,Microsoft.ReportingServices.Designer"/>
> > </Designer>
> >
> > --
> > This posting is provided "AS IS" with no warranties, and confers no rights.
> >
> >
> > "Robert Bruckner [MSFT]" <robruc@.online.microsoft.com> wrote in message
> > news:%23qgs5sXXFHA.3280@.TK2MSFTNGP09.phx.gbl...
> > > When using a managed provider, you can either use it directly or write a
> > > custom data extension which internally uses the provider. In general you
> > > can use most .NET data providers (which implement
> > > System.Data.IDBConnection, etc.). A .NET data provider would need to be
> > > registered in both, rsReportDesigner.config and rsReportServer.config.
> > >
> > > Lets assume your .NET provider has the assembly name "MyAssembly" and the
> > > actual class that implements IDBConnection is called
> > > "MyAssembly.MyConnection". Here is how you would register it:
> > > * RSReportServer.config:
> > > <Extension Name="MyProvider"
> > > Type="MyAssembly.MyConnection,MyAssembly"/>
> > >
> > > * RSReportDesigner.config
> > > The registration for report designer would need to happen in two places -
> > > in the <Data> section and in the <Designer> section.
> > >
> > > <Data>
> > > ...
> > > <Extension Name="MyProvider"
> > > Type="MyAssembly.MyConnection,MyAssembly"/>
> > > </Data>
> > > <Designer>
> > > ...
> > > <Extension Name="MyProvider"
> > > Type="MyAssembly.MyConnection,MyAssembly"/>
> > > </Designer>
> > >
> > > After registering, you will get a new entry "MyProvider" in the data
> > > source type drop-down list.
> > >
> > > See also:
> > > http://msdn.microsoft.com/library/en-us/RSPROG/htm/rsp_prog_extend_dataproc_8iqq.asp
> > >
> > >
> > > --
> > > Robert M. Bruckner
> > > Microsoft SQL Server Reporting Services
> > > This posting is provided "AS IS" with no warranties, and confers no
> > > rights.
> > >
> > >
> > >
> > > "Daniel Michaeloff" <DanielMichaeloff@.discussions.microsoft.com> wrote in
> > > message news:BD89B815-BC0E-4ABD-9A36-07F7B31A303B@.microsoft.com...
> > >> Is there a data processing extension for use with an ADO.NET provider?
> > >> MSDN
> > >> lists ones for SQL Server, OLEDB, Oracle, and ODBC.. ADO.NET is a glaring
> > >> omission.
> > >>
> > >> The extension interfaces (IDbConnection, etc) are all similar to
> > >> ADO.NET's.
> > >> I could write a pretty thin custom extension wrapper around an ADO.NET
> > >> provider, but why should I have to?
> > >
> > >
> >
> >
> >|||Okay, I tried actually following that link you gave. Sorry.
"Daniel Michaeloff" wrote:
> Actually, I'm not getting Report Designer to pick up my assembly from the
> GAC, and I don't see anything like "Microsoft.ReportingServices" in the GAC
> either. I've also tried dropping my dll in Report Designer's main directory.
> Where does Report Designer / Reporting Services look for extensions?
> "Daniel Michaeloff" wrote:
> > Thanks Robert, this is what I needed.
> >
> > However, is there a way to avoid putting our provider assemblies in the
> > global assembly cache?
> >
> > "Robert Bruckner [MSFT]" wrote:
> >
> > > Correction to my posting below - the <Designer> element in
> > > RSReportDesigner.config should have the following contents:
> > >
> > > <Designer>
> > > ...
> > > <Extension Name="MyProvider"
> > > Type="Microsoft.ReportDesigner.Design.GQDQueryDesigner,Microsoft.ReportingServices.Designer"/>
> > > </Designer>
> > >
> > > --
> > > This posting is provided "AS IS" with no warranties, and confers no rights.
> > >
> > >
> > > "Robert Bruckner [MSFT]" <robruc@.online.microsoft.com> wrote in message
> > > news:%23qgs5sXXFHA.3280@.TK2MSFTNGP09.phx.gbl...
> > > > When using a managed provider, you can either use it directly or write a
> > > > custom data extension which internally uses the provider. In general you
> > > > can use most .NET data providers (which implement
> > > > System.Data.IDBConnection, etc.). A .NET data provider would need to be
> > > > registered in both, rsReportDesigner.config and rsReportServer.config.
> > > >
> > > > Lets assume your .NET provider has the assembly name "MyAssembly" and the
> > > > actual class that implements IDBConnection is called
> > > > "MyAssembly.MyConnection". Here is how you would register it:
> > > > * RSReportServer.config:
> > > > <Extension Name="MyProvider"
> > > > Type="MyAssembly.MyConnection,MyAssembly"/>
> > > >
> > > > * RSReportDesigner.config
> > > > The registration for report designer would need to happen in two places -
> > > > in the <Data> section and in the <Designer> section.
> > > >
> > > > <Data>
> > > > ...
> > > > <Extension Name="MyProvider"
> > > > Type="MyAssembly.MyConnection,MyAssembly"/>
> > > > </Data>
> > > > <Designer>
> > > > ...
> > > > <Extension Name="MyProvider"
> > > > Type="MyAssembly.MyConnection,MyAssembly"/>
> > > > </Designer>
> > > >
> > > > After registering, you will get a new entry "MyProvider" in the data
> > > > source type drop-down list.
> > > >
> > > > See also:
> > > > http://msdn.microsoft.com/library/en-us/RSPROG/htm/rsp_prog_extend_dataproc_8iqq.asp
> > > >
> > > >
> > > > --
> > > > Robert M. Bruckner
> > > > Microsoft SQL Server Reporting Services
> > > > This posting is provided "AS IS" with no warranties, and confers no
> > > > rights.
> > > >
> > > >
> > > >
> > > > "Daniel Michaeloff" <DanielMichaeloff@.discussions.microsoft.com> wrote in
> > > > message news:BD89B815-BC0E-4ABD-9A36-07F7B31A303B@.microsoft.com...
> > > >> Is there a data processing extension for use with an ADO.NET provider?
> > > >> MSDN
> > > >> lists ones for SQL Server, OLEDB, Oracle, and ODBC.. ADO.NET is a glaring
> > > >> omission.
> > > >>
> > > >> The extension interfaces (IDbConnection, etc) are all similar to
> > > >> ADO.NET's.
> > > >> I could write a pretty thin custom extension wrapper around an ADO.NET
> > > >> provider, but why should I have to?
> > > >
> > > >
> > >
> > >
> > >