Odd Rights Issue

From: CR (chuck.rich__ardson_at_sfcc.edu)
Date: 08/29/05 

Date: Mon, 29 Aug 2005 11:53:51 -0400

SQL Server 2000 Server at SP3a

WinXP SQL Server 2000 Client at SP4
Win2K SQL Server 2000 Client at SP3a

Identical local user account setup on both clients using peer-to-peer
windows authentication to server.

The account on Win2K client at SP3a can successfully open pre-existing
transformation tasks in DTS.
The account on WinXP client at SP4 cannot open pre-existing transforamtion
tasks in DTS (but can create new ones okay).

What gives? Thanks for any help anyone can offer!

Chuck

Relevant Pages

  • SOLUTION: Problem connecting to sql server
    ... it is an account problem. ... Not associated with a trusted SQL Server ... go to Client Configuation properties on the client machine ... >> settings on the SQL server, ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: SMS Client issue
    ... The account with the error needs to be an administrator account on your ... communication and one to the SQL Server that account must exist in there. ... boundaries are correct to assign and install. ... Push installation to client machines does ...
    (microsoft.public.sms.misc)
  • Re: Problem connecting to sql server
    ... go to Client Configuation properties on the client machine ... I need to clarify that I didn't change anything on the SQL server. ... The account my web application is using is the 'sa' account and yes, ... And I'm sure the connection string is ...
    (microsoft.public.dotnet.framework.adonet)
  • HELP! Connect errors!
    ... the following error message. ... trusted SQL server connection. ... client is WinXPSP1. ... I'm stumped as the Windows Domain account has to be ...
    (microsoft.public.sqlserver.tools)
  • Re: Upgrading SQL-Server client to sp3a
    ... SP3a can be applied to all version of SQL Server (MSDE is different ... The client being enterprise manager & the other client tools, ...
    (microsoft.public.sqlserver.security)