Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
8 years ago
Solved

Service/Gateway Error: .Net Framework Dataprovider

Hello,   I am having troubles using an Oracle DB as source for PBI Reports within the service.   I did install the gateway (enterprise – not personal) successfully. In PBI-Service I could establi...
Need Help
  • Anonymous's avatar
    Anonymous
    8 years ago

    I wasn't able to solve this error. However running the gateway on a different PC did the trick. I assume it must have had something to do with the .net installation on the first PC.....

Anonymous's avatar
Anonymous
Not applicable
8 years ago

Hello again!

Unfortunatly reinstalling .Net did not do the trick. Also I did not have multiple DbProviderFactories entries in the machine.config file. So any help is still very welcome!

Thanks,

Chris

Anonymous's avatar
Anonymous
Not applicable
8 years ago

I noticed that the error message is now a different one:

 

 

As mentioned above the gataway connection seems to be working (green checkmark) so I can't figure out the problem might be here! 

Thanks!

Chris

  • Anonymous's avatar
    Anonymous
    Not applicable
    8 years ago

    I took a look at the logfiles and found this to be the last errror message within the logfile:

     

    GatewayPipelineErrorCode=DM_GWPipeline_UnknownError
InnerType=ArgumentException
InnerMessage=<pi>Unable to find the requested .Net Framework Data Provider.  It may not be installed.</pi>
InnerToString=<pi>System.ArgumentException: Unable to find the requested .Net Framework Data Provider.  It may not be installed.
   at System.Data.Common.DbProviderFactories.GetFactory(String providerInvariantName)
   at Microsoft.PowerBI.DataMovement.Pipeline.GatewayDataAccess.OracleConnectionProvider.<OpenConnectionAsync>d__5.MoveNext()

    If helpfull I can post the entire logfile - please let me know!

    Thanks!

    Chris

    • Anonymous's avatar
      Anonymous
      Not applicable
      8 years ago

      I wasn't able to solve this error. However running the gateway on a different PC did the trick. I assume it must have had something to do with the .net installation on the first PC.....