Re: file rights issue...

Brad,

What happens if you remove the Everyone Group and add Domain Users Group?

--
John Oliver, Jr
MCSE, MCT, CCNA
Exchange MVP 2007
Microsoft Certified Partner
"Brad Pears" <bradp@xxxxxxxxxxxxxxxxxxxxx> wrote in message
news:%234QA11YRHHA.4448@xxxxxxxxxxxxxxxxxxxxxxx
Yes, they do have TS support. We have been running on TS no probs all
along - and it still works now - it's just that they are unable to access
the files through the BV app UNLESS the everyone group has been granted
full access to the directory. This just started after moving the BV
accounting files over to the WIn2K machine where domain rights are now
being applied. Before, when we had the data on the NT box, it was not part
of the domain so no domain rights were being used - just the local NT
servers user rights were being used. I have BV tech support working on
it... Just thought someone may have run across similiar problems
before...

PS... No, the users do not need local admin rights and to test that
theory, I could not even access the data using BV and I am a domain admin.
I gave domain admins full acccess the the direcoties and still no go! Only
the addition of the 'everyone' group seems to solve the issue...

Thanks,
Brad


"John Oliver, Jr. [MVP]" <jcoliverjr@xxxxxxxxxxx> wrote in message
news:enZnSqXRHHA.4060@xxxxxxxxxxxxxxxxxxxxxxx
You need to get with BV again and ask them what are the required
permissions to run there App on both the client workstations and Terminal
Server. On the client machines, do the users need to have Local Admin
rights? The Terminal Server is an entirely different issue. They first
need to have support for their product on TS session. Is this the case?

--
John Oliver, Jr
MCSE, MCT, CCNA
Exchange MVP 2007
Microsoft Certified Partner

"Brad Pears" <bradp@xxxxxxxxxxxxxxxxxxxxx> wrote in message
news:OQC8PkWRHHA.5032@xxxxxxxxxxxxxxxxxxxxxxx
I am not sure if this is an issue related to Windows 2000 file security
or not but thought I'd post my issue here to see if anyone has
experienced this type of thing before.

We use an accounting package called Business Visions (BV). The version
of BV we are running uses an SQL DB engine called Pervasive SQL to
access the data. The pervasive server engine is running as a service on
our Windows 2000 SQL server - which is also where the accounting data is
stored (not part of the SQL server database). There are no conflicts
with both of these SQL products running on the same machine.

Accounting users run the Business Visions application either locally (on
their domain Windows XP workstations) or through a Windows 2003 terminal
server session. When the BV application starts it automatically kicks
off a Pervasive SQL client - which then accesses the accounting data on
the Windows 2000 server through the pervasive SQL gateway service
running there. This all works very well - as long as the 'everyone'
group has been given full permissions to the accounting data.

Since we can not have our accounting data available to the 'everyone'
group :-), I need to figure out WHY this is so... As soon as I remove
the 'everyone' group, leaving me with the other requried groups there -
(and they have also been given full access), the users are unable to
access the data through BV! I even tried having them browse to the
actual data folders and create a new file, rename a file etc... and all
those rights appear to be ok - so I do not know what difference adding
the 'everyone ' group makes - but it is certainly changing something!

As a side note, we recently migrated this accounting data from an NT 4.0
SP6 machine and we had NO problems with file access at all when the data
was on that machine. However, the NT machine was not part of the
domain - it was it's own workgroup - so no domain rights applied there.
Now that we have moved the data to a Windwos 2000 machine in our domain,
windows domain security rights now apply and we are having the problems.

Has anyone ever seen this type of a problem before?? Business Visions
tech support can not figure it out. At least not the techs that I have
talked to. It fails when BV is run on an XP machine (locally) and
through a Win2K3 terminal servers session. The users do have rightsd to
the folders because they can browse there and make changes to files in
there. I am at a loss!!!

Help!

Thanks, Brad









.

Relevant Pages

  • Re: file rights issue...
    ... Domain Admin has rights to everything so not being able to access the ... The Terminal Server is an entirely different ... of BV we are running uses an SQL DB engine called Pervasive SQL to ... the accounting data on the Windows 2000 server through the pervasive ...
    (microsoft.public.backoffice.smallbiz2000)
  • Re: file rights issue...
    ... files over to the WIn2K machine where domain rights are now being applied. ... The Terminal Server is an entirely different issue. ... BV we are running uses an SQL DB engine called Pervasive SQL to access ... Windows 2000 SQL server - which is also where the accounting data is ...
    (microsoft.public.backoffice.smallbiz2000)
  • Re: file rights issue...
    ... part of the domain so no domain rights were being used - just the local ... The Terminal Server is an entirely different issue. ... of BV we are running uses an SQL DB engine called Pervasive SQL to ... our Windows 2000 SQL server - which is also where the accounting data ...
    (microsoft.public.backoffice.smallbiz2000)
  • REPOST:SQL Login with no Fixed Server Role and DB Role can stop SQL Agent Service?
    ... I had checked all the user rights, and everything seems to be proper...but ... running SQL 2000 Enterprise Edition on ... Windows 2000 Server. ... SQL Server on his Enterprise Manager using this SQL Login. ...
    (microsoft.public.sqlserver.security)
  • REPOST:SQL Login with no Fixed Server Role and DB Role can stop SQL Agent Service?
    ... I had checked all the user rights, and everything seems to be proper...but ... running SQL 2000 Enterprise Edition on ... Windows 2000 Server. ... SQL Server on his Enterprise Manager using this SQL Login. ...
    (microsoft.public.sqlserver.security)