Re: Deployment Problem

From: Curt Hagenlocher (faustus_at_pureevil.org)
Date: 06/22/04


Date: Tue, 22 Jun 2004 08:35:16 -0400


"Jim" <jfinegan@oceanfree.net> wrote in message
news:%232LVKNEWEHA.1012@TK2MSFTNGP09.phx.gbl...

> I am trying to deploy a comsumer of a web service. The operating system is
> Windows 2000. Its the old developer problem, its working on my development
> PC but not working on the production PC.
> The error I am getting is System.Security.SecurityException.

You're going to have to provide a lot more information than that.

What's the stack trace?
Is this a Windows Forms app?
What OS is your development PC?
Is it an "original" web service, WSE 1.0, WSE 2.0?
Does it work on the target PC when logged in as administrator?

--
Curt Hagenlocher
curt@hagenlocher.org


Relevant Pages

  • Re: Deployment Problem
    ... you clearly have some kind of permissions problem. ... > Windows 2000. ... Its the old developer problem, ... > PC but not working on the production PC. ...
    (microsoft.public.dotnet.framework.webservices)
  • RE: Web Service Security
    ... You could encrypt or hash your ... As far as web service authentication/authorisation is concerned you would be ... WSE does a pretty good job of abstracting away most of the ... a windows domain account). ...
    (microsoft.public.dotnet.framework.webservices)
  • WSE 3.0 Kerberos Auth and issue with Windows XP ASPNET Account
    ... Having our WSE 3.0-WebService over Windows Server 2003, ... The problem is that ASP.NET default user in Windows XP (ASPNET user account) ... Web Services, so, by default, using ASPNET account, it does not work (we ...
    (microsoft.public.dotnet.xml)
  • WSE 3.0 Kerberos Auth and issue with Windows XP ASPNET Account
    ... Having our WSE 3.0-WebService over Windows Server 2003, ... The problem is that ASP.NET default user in Windows XP (ASPNET user account) ... Web Services, so, by default, using ASPNET account, it does not work (we ...
    (microsoft.public.dotnet.framework.webservices.enhancements)
  • RE: How to prevent QA and EM access to DB
    ... Create an application Windows account and only allow users access to the ... the execution of the procedure that envokes SQL Server Application Roles. ... there is little you can do once the system has gone into production. ... > using windows authentication. ...
    (microsoft.public.sqlserver.server)