Error access Custom Assembly in Deploying

Please,

i did a class in C# that return a array of bytes... in preview mode (design) i can see this return, but when i use Deploy (Server) i can′t see.

I already put the lines on of security in file srrsvpolicy.config and copy the file dll to folder, however i cant see the result.

Anybody help me?

I′m using:

- SQL 2005
- dll no strong name

Thanks

Jota

Assuming you have put the right security settings and deployed the assembly to the Report Server bin folder, your method may need additional CAS security rights depending on what your code is trying to do, as explained in more details here. What I suggest you do is put a breakpoint in your assembly code, attach to the ASP.NET process, and run the report so you can debug your code and see where the exception is thrown.

Error 9104

Why does the server return Error 9104 "auto statistics internal"? I can't find an error description in BOL, MSDN or through a groups/forum search either.

We running Sql Server 2005 (no sp yet) on Windows 2003 server.

Thanks

Do you have the associated state number for this error? It is number like in the range of 1-255 in general. It would be helpful in identifying the cause.|||

Hi Mark,

I only have the severity level, 16. I don't capture the state in my error trace.

We migrated to 2005 in mid-March and this error has been returned twice.

|||

Error 9104 is used internally for control flow. It is never surfaced through T-SQL. I assume you ran a trace to capture errors.

9104 essentially means that auto statistics failed for some reason (deadlock, resource crunch, ...). Since the engine can go on without auto-created or auto-refreshed statistics, the engine doesn't surface this error.

Peter Zabback

SQL Server Optimizer Development

Error 8623

Hi,
When I execute an Insert form a select, SQL Server return the following
message
Server: Msg 8623, Level 16, State 1, Line 109
Internal Query Processor Error: The query processor could not produce a
query plan. Contact your primary support provider for more information.
I have search on technet and find the following article
(http://support.microsoft.com/defaul...kb;en-us;832412). It said to
put the FLAG 9136 on SQL Server.
I have search on Internet and don't find any information about this flag.
Procurei na internet e no encontrei informaes sobre este FLAG.
Does someone know any information about this error or about this flag?I found several KB's associated with that error such as this one:
http://support.microsoft.com/defaul...4&Product=sql2k
But it depends on what your doing. In any case I feel it's a bug and you
should contact MS PSS.
http://support.microsoft.com/defaul...id=fh;EN-US;sql SQL Support
http://www.mssqlserver.com/faq/general-pss.asp MS PSS
Andrew J. Kelly
SQL Server MVP
"Thiago Campos Pereira" <tpereira@.attps.com.br> wrote in message
news:%23sH0wnkQEHA.2716@.tk2msftngp13.phx.gbl...
> Hi,
> When I execute an Insert form a select, SQL Server return the following
> message
> Server: Msg 8623, Level 16, State 1, Line 109
> Internal Query Processor Error: The query processor could not produce a
> query plan. Contact your primary support provider for more information.
>
> I have search on technet and find the following article
> (http://support.microsoft.com/defaul...kb;en-us;832412). It said
to
> put the FLAG 9136 on SQL Server.
> I have search on Internet and don't find any information about this flag.
> Procurei na internet e no encontrei informaes sobre este FLAG.
>
> Does someone know any information about this error or about this flag?
>

Error 8623

Hi,
When I execute an Insert form a select, SQL Server return the following
message
Server: Msg 8623, Level 16, State 1, Line 109
Internal Query Processor Error: The query processor could not produce a
query plan. Contact your primary support provider for more information.
I have search on TechNet and find the following article
(http://support.microsoft.com/default...b;en-us;832412). It said to
put the FLAG 9136 on SQL Server.
I have search on Internet and don't find any information about this flag.
Procurei na internet e no encontrei informaes sobre este FLAG.
Does someone know any information about this error or about this flag?
I found several KB's associated with that error such as this one:
http://support.microsoft.com/default...&Product=sql2k
But it depends on what your doing. In any case I feel it's a bug and you
should contact MS PSS.
http://support.microsoft.com/default...d=fh;EN-US;sql SQL Support
http://www.mssqlserver.com/faq/general-pss.asp MS PSS
Andrew J. Kelly
SQL Server MVP
"Thiago Campos Pereira" <tpereira@.attps.com.br> wrote in message
news:%23sH0wnkQEHA.2716@.tk2msftngp13.phx.gbl...
> Hi,
> When I execute an Insert form a select, SQL Server return the following
> message
> Server: Msg 8623, Level 16, State 1, Line 109
> Internal Query Processor Error: The query processor could not produce a
> query plan. Contact your primary support provider for more information.
>
> I have search on TechNet and find the following article
> (http://support.microsoft.com/default...b;en-us;832412). It said
to
> put the FLAG 9136 on SQL Server.
> I have search on Internet and don't find any information about this flag.
> Procurei na internet e no encontrei informaes sobre este FLAG.
>
> Does someone know any information about this error or about this flag?
>

Error 8623

Hi,
When I execute an Insert form a select, SQL Server return the following
message
Server: Msg 8623, Level 16, State 1, Line 109
Internal Query Processor Error: The query processor could not produce a
query plan. Contact your primary support provider for more information.
I have search on TechNet and find the following article
(http://support.microsoft.com/default.aspx?scid=kb;en-us;832412). It said to
put the FLAG 9136 on SQL Server.
I have search on Internet and don't find any information about this flag.
Procurei na internet e não encontrei informações sobre este FLAG.
Does someone know any information about this error or about this flag?I found several KB's associated with that error such as this one:
http://support.microsoft.com/default.aspx?scid=kb;en-us;841404&Product=sql2k
But it depends on what your doing. In any case I feel it's a bug and you
should contact MS PSS.
http://support.microsoft.com/default.aspx?scid=fh;EN-US;sql SQL Support
http://www.mssqlserver.com/faq/general-pss.asp MS PSS
--
Andrew J. Kelly
SQL Server MVP
"Thiago Campos Pereira" <tpereira@.attps.com.br> wrote in message
news:%23sH0wnkQEHA.2716@.tk2msftngp13.phx.gbl...
> Hi,
> When I execute an Insert form a select, SQL Server return the following
> message
> Server: Msg 8623, Level 16, State 1, Line 109
> Internal Query Processor Error: The query processor could not produce a
> query plan. Contact your primary support provider for more information.
>
> I have search on TechNet and find the following article
> (http://support.microsoft.com/default.aspx?scid=kb;en-us;832412). It said
to
> put the FLAG 9136 on SQL Server.
> I have search on Internet and don't find any information about this flag.
> Procurei na internet e não encontrei informações sobre este FLAG.
>
> Does someone know any information about this error or about this flag?
>

error 7391 in distributed transaction

I have a procedure running locally on my server A. This procedure does an
insert into a table after getting a return value from a select done on
another server say B . Server B is set up as linked server on server A. th
error i get shows as
The operation could not be performed because the OLE DB provider 'SQLOLEDB'
was unable to begin a distributed transaction.
[OLE/DB provider returned message: New transaction cannot enlist in the
specified transaction coordinator. ]
OLE DB error trace [OLE/DB Provider 'SQLOLEDB'
ITransactionJoin::JoinTransaction returned 0x8004d00a].
Has anyone seen this before? Is there any solution to this or any setting
that needs to be changed to get this working? any help will be greatly
appreciated.
TIA
Message posted via http://www.webservertalk.comFor distributed transaction you need to have a Primary key on updated table.
So pLease add primary key to resolve your issue. Please let me know if
doesn't work.
Regards,
Jagan Mohan
MCDBA
"ishaan99 via webservertalk.com" wrote:

> I have a procedure running locally on my server A. This procedure does an
> insert into a table after getting a return value from a select done on
> another server say B . Server B is set up as linked server on server A. th
> error i get shows as
> The operation could not be performed because the OLE DB provider 'SQLOLEDB
'
> was unable to begin a distributed transaction.
> [OLE/DB provider returned message: New transaction cannot enlist in the
> specified transaction coordinator. ]
> OLE DB error trace [OLE/DB Provider 'SQLOLEDB'
> ITransactionJoin::JoinTransaction returned 0x8004d00a].
> Has anyone seen this before? Is there any solution to this or any setting
> that needs to be changed to get this working? any help will be greatly
> appreciated.
> TIA
> --
> Message posted via http://www.webservertalk.com
>|||I've had this same error, mine only happened during times when transactions
were high on the system, I think there is a setting to increase the number o
f
concurrent distributed transactions, don't know what else you could do, I
know it has to do with MSDTC.
"ishaan99 via webservertalk.com" wrote:

> I have a procedure running locally on my server A. This procedure does an
> insert into a table after getting a return value from a select done on
> another server say B . Server B is set up as linked server on server A. th
> error i get shows as
> The operation could not be performed because the OLE DB provider 'SQLOLEDB
'
> was unable to begin a distributed transaction.
> [OLE/DB provider returned message: New transaction cannot enlist in the
> specified transaction coordinator. ]
> OLE DB error trace [OLE/DB Provider 'SQLOLEDB'
> ITransactionJoin::JoinTransaction returned 0x8004d00a].
> Has anyone seen this before? Is there any solution to this or any setting
> that needs to be changed to get this working? any help will be greatly
> appreciated.
> TIA
> --
> Message posted via http://www.webservertalk.com
>sql