One Web Service updates SQL, another can't?
From: Steve Ricketts (steve_at_velocedge.com)
Date: 10/26/04
- Next message: Tom Moreau: "Re: One Web Service updates SQL, another can't?"
- Previous message: Adam Machanic: "Re: kb831997"
- Next in thread: Tom Moreau: "Re: One Web Service updates SQL, another can't?"
- Reply: Tom Moreau: "Re: One Web Service updates SQL, another can't?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Tue, 26 Oct 2004 12:06:48 -0400
I have a production and development system both running on one PC under W2K
with SQL7sp4. One Web Service can access and update the SQL Server 7
database fine. Another instance of the same Web Service code, accessing a
different, but identical database, can read but not update records. It
seems like whichever Web Service I start first is allowed to read and write,
but the other has only read permissions.
Is there a exclusive, read-only, permissions setting that I've missed
somewhere? The problem is simply the second Web Service can't write to SQL,
but why is the big question. Any help would be greatly appreciated, I'm
into days on this one!
Thanks,
Steve Ricketts
- Next message: Tom Moreau: "Re: One Web Service updates SQL, another can't?"
- Previous message: Adam Machanic: "Re: kb831997"
- Next in thread: Tom Moreau: "Re: One Web Service updates SQL, another can't?"
- Reply: Tom Moreau: "Re: One Web Service updates SQL, another can't?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
|