Showing posts with label attempting. Show all posts
Showing posts with label attempting. Show all posts

Thursday, March 22, 2012

Deployment problem

I am attempting to deploy a report that I created with "Business Intelligent
Projects". When I attempt the deploy I get a message that my user account
doesn't have the rights to do it. It is an administrative account and the
same one used to start the service.
I have another development machine and it works fine. Any ideas?
Any help is greatly appreciated.On Apr 24, 1:54 pm, "Greg Smith" <g...@.umn.edu> wrote:
> I am attempting to deploy a report that I created with "Business Intelligent
> Projects". When I attempt the deploy I get a message that my user account
> doesn't have the rights to do it. It is an administrative account and the
> same one used to start the service.
> I have another development machine and it works fine. Any ideas?
> Any help is greatly appreciated.
Does your Windows Authentication user have administrative rights to
the Report Manager on the server w/the deployment issue?
Enrique Martinez
Sr. Software Consultant

Monday, March 19, 2012

Deploying vb.net english query application

Hi,
I'm attempting to distribute a vb.net english query application to a
client, however, when the client runs the application, it crahses when
it tries to create an instance of the "Mseq.Session" object.
As far as I can tell, the interop and the original dll are being
included in the setup correctly - are there any special settings (such
as com registration, system etc), or other files that I should be
including? Or are there any other prerequisits for the client's pc
before I can expect the software to run?
Cheers,
Tinium.
you are still going to need to install the EQ engine on the target
platform.. There's an awful lot of work done by the engine before the query
is shipped off the Server. EQ is a client function..
Guy
"Tinium" <tin@.ium.com> wrote in message
news:eWfltpaQFHA.132@.TK2MSFTNGP10.phx.gbl...
> Hi,
> I'm attempting to distribute a vb.net english query application to a
> client, however, when the client runs the application, it crahses when it
> tries to create an instance of the "Mseq.Session" object.
> As far as I can tell, the interop and the original dll are being included
> in the setup correctly - are there any special settings (such as com
> registration, system etc), or other files that I should be including? Or
> are there any other prerequisits for the client's pc before I can expect
> the software to run?
> Cheers,
> Tinium.