SQL Alternative to cursor: oledb

Showing posts with label oledb. Show all posts

Thursday, March 8, 2012

An error about & quot;[dbnmpntw]ConnectionOpen(CreateFile())".

Hi:
When I tried to connect SQL Server Databse which was on another machine,
using Microsoft OLEDB Provider for SQL Server, error 0x80040005 was
returned, and the error message was
"& #91;dbnmpntw]ConnectionOpen(CreateFile()
)".Hi,
Use the SQL Client Configuration utility (from the machine u are connecting)
to create alias server name for the sql server using the TCP/IP protocol
specifying IP and port number.
And use this Alias name to connect to SQL server using TCP/IP
Thanks
Hari
MCDBA
"arxing" <cjx@.nbdx.cn> wrote in message
news:eAfe$8PWEHA.4092@.TK2MSFTNGP11.phx.gbl...
> Hi:
> When I tried to connect SQL Server Databse which was on another
machine,
> using Microsoft OLEDB Provider for SQL Server, error 0x80040005 was
> returned, and the error message was
> "& #91;dbnmpntw]ConnectionOpen(CreateFile()
)".
>|||But if I don't installed SQL Client on the machine I am connecting, what can
I do?
thanks.
"Hari" <hari_prasad_k@.hotmail.com> д?
news:elatIOQWEHA.1128@.TK2MSFTNGP10.phx.gbl...
> Hi,
> Use the SQL Client Configuration utility (from the machine u are
connecting)
> to create alias server name for the sql server using the TCP/IP protocol
> specifying IP and port number.
> And use this Alias name to connect to SQL server using TCP/IP
> --
> Thanks
> Hari
> MCDBA
> "arxing" <cjx@.nbdx.cn> wrote in message
> news:eAfe$8PWEHA.4092@.TK2MSFTNGP11.phx.gbl...
> machine,
>|||You can also do this using the wizard to set up an ODBC=20
data source. Use the Client Configuration button.

>--Original Message--
>But if I don't installed SQL Client on the machine I am=20
connecting, what can
>I do?
>thanks.
>
>"Hari" <hari_prasad_k@.hotmail.com> =D0=B4=C8=EB=D3=CA=BC=FE
>news:elatIOQWEHA.1128@.TK2MSFTNGP10.phx.gbl...
machine u are[vbcol=seagreen]
>connecting)
the TCP/IP protocol[vbcol=seagreen]
TCP/IP[vbcol=seagreen]
was on another[vbcol=seagreen]
0x80040005 was[vbcol=seagreen]
>
>.
>|||You can also do this when you set up the ODBC data source.=20
Use the Client Configuration button in the wizard.

>--Original Message--
>But if I don't installed SQL Client on the machine I am=20
connecting, what can
>I do?
>thanks.
>
>"Hari" <hari_prasad_k@.hotmail.com> =D0=B4=C8=EB=D3=CA=BC=FE
>news:elatIOQWEHA.1128@.TK2MSFTNGP10.phx.gbl...
machine u are[vbcol=seagreen]
>connecting)
the TCP/IP protocol[vbcol=seagreen]
TCP/IP[vbcol=seagreen]
was on another[vbcol=seagreen]
0x80040005 was[vbcol=seagreen]
>
>.
>|||This utility is available even if you didn't install the SQL Client tools -
start -> run -> Cliconfg.exe.
Richard Waymire, MCSE, MCDBA
This posting is provided "AS IS" with no warranties, and confers no rights.
"arxing" <cjx@.nbdx.cn> wrote in message
news:O3sk4WSWEHA.4048@.TK2MSFTNGP12.phx.gbl...
> But if I don't installed SQL Client on the machine I am connecting, what
> can
> I do?
> thanks.
>
> "Hari" <hari_prasad_k@.hotmail.com> д?
> news:elatIOQWEHA.1128@.TK2MSFTNGP10.phx.gbl...
> connecting)
>

Wednesday, March 7, 2012

An attempt has been made to use a data extension OLEDB that is not registered for this report se

I am using SQL Server 2005 Express along with the other Express reporting tools (VS Express). I am trying to report against an oracle database. I can design and preview the report however when I attempt to 'deploy' the report to a report server that is on the same machine I am developing on, I get the above error. Is this because I am running an Express version of SQL Server or is this an error?

Thanks,

Sam

Yes, the Express Edition only allows connections to local data sources with a limited set of data extensions. Not all types of data sources are supported in the Express Edition.

-- Robert

An attempt has been made to use a data extension OLEDB that is not registered for this repor

Thanks,

Sam

Yes, the Express Edition only allows connections to local data sources with a limited set of data extensions. Not all types of data sources are supported in the Express Edition.

-- Robert

An attempt has been made to use a data extension 'DLLName' that is not registered for this

Hello,

I've created my own data extension which uses ADODB.NET (OleDB Provider) and connects to the named SQL instance. During the development phase of the report I can connect to my data source, retrieve data from it and display it in the report preview with no problems. But as soon as I want to deploy this report and my data source I get the message: “An attempt has been made to use a data extension 'DLLName' that is not registered for this report server.". I went thru all *.config files and set up them up as per instructions how to. I can see my extension in the combo box during designing my report which tells me that this is done correctly. I can create the report in the preview as well. But whatever I do, when I want to deploy it I'm always getting this message.

I've come across one post where it says that Reporting Services are limited to the default, unnamed instance of SQL Server (local). I don't think it should matter to me in this case because I'm using my OleDB Provider to connect to the database. Report doesn't know anything about it. It gets data from my extension, not directly from the database. But I've tried switching from my named instance to (local) just to see if it is going to work, but no luck.

I'd appreciate somebody giving me some suggestions on this issue.

Thanks...

did you update rssrvpolicy.config to grant fulltrust to your extension? Usually this error message appears when report server gets an exception when loading the extension, and this usually happens when extension is not trusted or it fails in constructor. The fact that it works in report designer (which runs everything in fulltrust by default) most likely means that extension is not getting fulltrust when loaded on server.|||

Yes I did. Here is the code from the rssrvpolicy.config:

</CodeGroup>

But it still doens't work. I still am getting the same message when I try to deploy my report.

Any suggestions would be appreciated.