Embadded code in VB.Net

Hello everyone!
We have a small problem with one report ,that include VB code.
The code - Vb function ,that connect to Active Directory and return some
value
from DB
When I run my report in local machine I got correctly results,
when I deploy the report - I have #Error.
In the custom code I did all necessary references .
Please help me and sorry for my EnglishOn the server, by default, all code has execute-only privileges. You need to
create a custom assembly to hold this code and then grant addition
permissions to it. See
http://msdn.microsoft.com/SQL/sqlwarehouse/ReportingServices/default.aspx?pull=/library/en-us/dnsql2k/html/dngrfcodeaccesssecurityinsqlserver2000reportingservices.asp.
--
Brian Welcker
Group Program Manager
Microsoft SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
"Vikont" <Vikont@.discussions.microsoft.com> wrote in message
news:2328E5C7-7A39-45D4-953E-A79B9B2FF1FD@.microsoft.com...
> Hello everyone!
> We have a small problem with one report ,that include VB code.
> The code - Vb function ,that connect to Active Directory and return some
> value
> from DB
> When I run my report in local machine I got correctly results,
> when I deploy the report - I have #Error.
> In the custom code I did all necessary references .
> Please help me and sorry for my English|||Did you follow the guidance in
http://msdn.microsoft.com/SQL/sqlwarehouse/ReportingServices/default.aspx?pull=/library/en-us/dnsql2k/html/dngrfcodeaccesssecurityinsqlserver2000reportingservices.asp?
--
Brian Welcker
Group Program Manager
Microsoft SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
"Vikont" <Vikont@.discussions.microsoft.com> wrote in message
news:2328E5C7-7A39-45D4-953E-A79B9B2FF1FD@.microsoft.com...
> Hello everyone!
> We have a small problem with one report ,that include VB code.
> The code - Vb function ,that connect to Active Directory and return some
> value
> from DB
> When I run my report in local machine I got correctly results,
> when I deploy the report - I have #Error.
> In the custom code I did all necessary references .
> Please help me and sorry for my English

EMail Task Problem

I have a pretty simple process that copies some files from an AS400 to a directory on the same server where my sql 2005 instance lives. I then use an email task to send these files to a client.

However, the email task does not work. I get the following message:

[Send Mail Task] Error: Either the file "BYNSOSR1;BYNSOSR2;BYNSOSR3;BYNSOSR4;BYNSOSR5;BYNSOSR6;BYNSOSR7" does not exist or you do not have permissions to access the file.

Well, the files definitely exist where they are supposed to be so I guess it's a permissions error. However, I have no clue which user would need permissions on that directory. As a test, I gave everyone read permissions and still got this error.

Any suggestions about which user I need to allow read access to the directory where these files exist?

Thanks in advance for any info.

I should say the path info in the previous post was changed so as not to reveal path info. But, the files do indeed exist where the email task expects them to be. I wrote a vb.net app that can email the files from that location just fine using the SMTP client of the .net.mail object hierarchy.|||Well, I never could figure out why the send email task wasn't working. It must have been some sort of permissions issue. I solved the problem by writing a console app in vb.net that sends the email via the net.mail smtpclient. I then run the console app as a execute process task. That sent the email with no problems and was a perfectly adequate way to solve the problem.

EM Issue - Missing servers in available servers list?

My PC was renamed and added to Active Directory in a new domain yesterday. Today when I tried to register a server in EM I only see SQL Servers in this new domain and not in the other, trusted, domains. I visited the machines of 5 developers and found that some people are experiencing the same issue while others can see SQL Servers in other domains, however they can only see SQL 2000 and not SQL 7 servers.

Any idea how the "Available Server" list is populate in EM and what might be causing this issue? It is important to note that even though I do not see server in the list, I can still register the servers without a problem.

Thanks, DaveThe entries are stored in the client registry, as you might have assumed:

HKEY_CURRENT_USER\Software\Microsoft\Microsoft SQL Server\80\Tools\Client\PrefServers|||...well, that's one of the places :)

I found another one:

HKEY_CURRENT_USER\Software\Microsoft\Microsoft SQL Server\80\Tools\SQLEW\Registered Servers|||Dave
I assume you are talking about the list of available servers in the register server wizard in Enterprise Manager? If so, then there is actually a security alert about this (lastest SQL Server cummulative patch).

Your client broadcasts out a message to all of your (sub)network, and says I"I am looking for SQL Servers". Anything listening on port 1433 or so will respond with "Hey, I am a SQL Server". The vulnerability is in the way the client accepts the response. If someone "fakes" a response from SQL Server, they can do something to you (I forget the details, but you can look it up on the SQL site under downloads). But that is the short of how the register server wizard works. That is also why I never use it. If I don't know about the server, I probably shouldn't be messing with it. Hope this helps.

rdjabarov has pointed out where you get the lists of servers already registered in SQL Server Enterprise Manager and where Query Analizer and Profiler get that drop-down list of servers to connect to. Basically just the last 20 servers you visited.|||well, my first posting shows the currently used location, and my second posting shows the location on my other workstation. Both locations are sources for EM, not Profiler or QA. The latter 2 truely are using the last 20 servers you connected to.|||Thanks for the info about the security issue. I'll read about it.

The only reason why I like to see the list of servers is to ensure nobody is trying to add an unauthorized SQL Server to our network. There are probably other ways to verify this, but I'm just use to using EM.

Dave