Server 2008 permission problem (I suspect?) Please help.

[Wowgasm]

Hi there,

My boss as approached me with a problem I just cannot seem to resolve.

Basically, he's got a program running on Server 2008, that is supposed to save information with .epi extensions to a local drive, other than C:\

The server is running Server 2008 R2 64-bit and has 3 partitions, C: D: and E:

The program can save the info to the C: drive, but not it the root directory. So if you create a folder called C:\test for instance and set the said program to save the info to that folder, it will work.

It will not save the data to the E: or D: partition, no matter what I try.

At first I thought it was a permission error, so I've set the security permission to give full access to the "Everyone" group on drive E: It still didn't work. I've tried multiple things like disabling the Anti Virus; I turned off the firewall; I did all windows updates; tried running the program as an administrator etc... No luck.

If anyone has an idea of what to do, I'd appreciate the help.

Thanks in advanced

 

[katangeleus]

Is this in a domain enviroment or workgroup? Is this with your user account that you logged onto the server with or is there a user account that this program will use?

 

[Wowgasm]

Is this in a domain enviroment or workgroup? Is this with your user account that you logged onto the server with or is there a user account that this program will use?

It's running in a standard workgroup that I created called "BN5" We're using the administrator user account, but I know this program runs off a sql database and the service runs under the system account if that helps?

 

[Electron1]

Had a similar problem with Windows 7 (basically same OS as server 2008 R2) -try turn off UAC (solution not ideal for a server from a security perspective).

 

[Wowgasm]

I made sure UAC was disabled, for test purposes. I stripped down the security as much as I possibly could, it's more open than the South African border. Nothing else is running on this server so security issues isn't really something I'm worried about at the moment. It sits behind a proxy and internal firewall as well. But thanks, I welcome and appreciate all suggestions.

 

[Electron1]

it's more open than the South African border.

Lol, Just to clarify:
App can write to to a subdirectory on C: drive, just not root (writing to root is not a good idea anyway)
App cannot write to D: or E: drive - is this also to root, or anywhere on the drives?
Are the D: and E: formatted with NTFS?
Were the drives formatted on that server or from another machine?

 

[Wowgasm]

App can write to to a subdirectory on C: drive, just not root (writing to root is not a good idea anyway)

Correct, I can save it to any sub-directory just not C: Some research revealed this is a built in security feature. *Questionable

App cannot write to D: or E: drive - is this also to root, or anywhere on the drives?

Cannot write to D: or E: neither to root, or any of it's sub directories.

Are the D: and E: formatted with NTFS?
Were the drives formatted on that server or from another machine?

It is indeed formatted with NTFS, I just formatted the E: drive from the server disk manager for test purposes, still no luck.

Thank you for your replies so far, Appreciate it.

 

[Demon7]

You said you welcome all suggestions..
Perhaps try turning the UAC back on and then running the app with elevated permissions... "as admin"
or run the app in compatibility mode... worth a try I think...

 

[Wowgasm]

Omw. After hours and hours of trying to figure it out, I asked my boss if I could look at the properties of the program. He was reluctant to this at first, because he was convinced it was a server related error. Anyway, he eventually let me have a squizz and there was an option to cache the data locally only. Once I unticked this, it worked perfectly -.-

Anyway, thanks a lot for the help anyway, I appreciate it.

 

[Wowgasm]

You said you welcome all suggestions..
Perhaps try turning the UAC back on and then running the app with elevated permissions... "as admin"
or run the app in compatibility mode... worth a try I think...

Thanks for your reply It ended up to be a silly application side error, which I would have sorted out in 2 minutes if *someone wasn't so suborn hehe. But thanks mate, appreciate the reply.

 

[Electron1]

Omw. After hours and hours of trying to figure it out, I asked my boss if I could look at the properties of the program. He was reluctant to this at first, because he was convinced it was a server related error. Anyway, he eventually let me have a squizz and there was an option to cache the data locally only. Once I unticked this, it worked perfectly -.-

Anyway, thanks a lot for the help anyway, I appreciate it.

Well done, interesting fix!