Deserialization failed: File or assembly name Microsoft.ReportingServices.Interfaces not f

Hello,
I just installed Vault Source Control on my machine. I then opened a
Reporting Services project with rdl's in it. Every RDL that is currently in
source control opens with this error
"Deserialization failed: File or assembly name
Microsoft.ReportingServices.Interfaces, or one of its dependencies, was not
found."
If I open another instance of the MSIDE without Vault (locally) and open a
different RDL it works fine. Is this an issue with the source control or
with the way it opens the file?
Any help will be appreciated. Need to get this solved.
PonnuI think it has to do with the way the add-in is written. Some add-ins turn
on shadow-copy, which plays havoc with the report designer as our assemblies
aren't located in the VS shared location. You might be able to copy the
report designer assemlies into the IDE directory. Not sure if you can
configure the add-in not to shadow copy.
--
Brian Welcker
Group Program Manager
SQL Server Reporting Services
"Ponnurangam" <ponnurangam@.trellisys.net> wrote in message
news:uZiORNloEHA.1160@.tk2msftngp13.phx.gbl...
> Hello,
> I just installed Vault Source Control on my machine. I then opened a
> Reporting Services project with rdl's in it. Every RDL that is currently
> in
> source control opens with this error
> "Deserialization failed: File or assembly name
> Microsoft.ReportingServices.Interfaces, or one of its dependencies, was
> not
> found."
> If I open another instance of the MSIDE without Vault (locally) and open a
> different RDL it works fine. Is this an issue with the source control or
> with the way it opens the file?
> Any help will be appreciated. Need to get this solved.
> Ponnu
>

Deployment Copy/Paste Problems

Hi all,
We maintain our CAB (meta-data only) in a source control system. The
process for deployment is simply to restore the CAB on the production
server and then copy/paste it to the production database name where it
will have it's final resting place.
By doing this we allow for scalability and robust management since the
same CAB can be deployed to many places. (In some places we process
different sets of cubes than in other places but the same meta-data
can be re-used.)
The problem we are finding is that one of our production servers is a
64 bit box that is (necessarily) remotely managed from a 32 bit
instance of Analysis Manager. When copy/pasting the database remotely
it takes a very, very long time to complete. Keep in mind that only
meta-data is being copied. When copy/paste is happening, it looks
like DSO code is executing to rebuild an entire database from scratch.
Does anybody have a faster method of copy/pasting an Analysis Services
database into place for deployment purposes?
Thanks,
DavidDavid Beavon wrote:

> Hi all,
>
> We maintain our CAB (meta-data only) in a source control system. The
> process for deployment is simply to restore the CAB on the production
> server and then copy/paste it to the production database name where it
> will have it's final resting place.
> By doing this we allow for scalability and robust management since the
> same CAB can be deployed to many places. (In some places we process
> different sets of cubes than in other places but the same meta-data
> can be re-used.)
>
> The problem we are finding is that one of our production servers is a
> 64 bit box that is (necessarily) remotely managed from a 32 bit
> instance of Analysis Manager. When copy/pasting the database remotely
> it takes a very, very long time to complete. Keep in mind that only
> meta-data is being copied. When copy/paste is happening, it looks
> like DSO code is executing to rebuild an entire database from scratch.
>
> Does anybody have a faster method of copy/pasting an Analysis Services
> database into place for deployment purposes?
> Thanks,
> David
http://www.solgenia.com/usa/Solutio.../SheetRubik.htm

Deny remote access to MSDE for some users

HI!
I'm a complete MSDE newbie but I have to clarify an open question about
access control with MSDE 2000 running on WinNT 4.0:
Is it possible to grant some admin users remote access to the MSDE but
restrict other local users to local access?
Ciao, Michael.
hi Michael,
Michael Strder wrote:
> HI!
> I'm a complete MSDE newbie but I have to clarify an open question
> about access control with MSDE 2000 running on WinNT 4.0:
> Is it possible to grant some admin users remote access to the MSDE but
> restrict other local users to local access?
yes, of course..
you have to grant the remote logins access to the MSDE instance via the
sp_grantlogin system stored procedure
(http://msdn.microsoft.com/library/de...-us/tsqlref/ts
_sp_ga-gz_8dri.asp), while you have to deny local logins via sp_denylogin...
please have a look at
http://support.microsoft.com/default...;EN-US;q325003 for futher
info about how to perform these tasks via oSql.exe, the command line tool
provided with MSDE
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.11.1 - DbaMgr ver 0.57.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Andrea,
first many thanks for the pointers.
Andrea Montanari wrote:
> hi Michael,
> Michael Strder wrote:
> you have to grant the remote logins access to the MSDE instance via the
> sp_grantlogin system stored procedure
> (http://msdn.microsoft.com/library/de...-us/tsqlref/ts
> _sp_ga-gz_8dri.asp), while you have to deny local logins via sp_denylogin...
Let's assume I use Windows authentication for MSDE. Is the whole access
control also done via Windows rights based on groups? How to disallow a
remote login for local users then?
Ciao, Michael.
|||ciao Michael,
> ..
> Let's assume I use Windows authentication for MSDE. Is the whole
> access control also done via Windows rights based on groups? How to
> disallow a remote login for local users then?
let's say you have YourDomain\theUser member of TheGroup\
you want TheGroup\ to be able to connect to MSDE, so you grant
(sp_grantlogin) it connection...
but you want YourDomain\theUser not to be able to connect to MSDE .. you
deny YourDomain\theUser connection to MSDE via sp_denylogin...
this way you have YourDomain\TheGroup able to connect and YourDomain\theUser
unable...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.11.1 - DbaMgr ver 0.57.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply