Kaspersky Lab Forum > Impossible to create a new task : access forbidden

Full Version: Impossible to create a new task : access forbidden

Kaspersky Lab Forum > English User Forum > Protection for Small and Medium Businesses

socemj

26.07.2007 11:56

We use MySQL 5.0.32 and the administration kit 6.0.35

Very often we have "Impossible to create a new task : access forbidden" (translated from french) when we want to create a new task. Similar message when we want to create a new policy.

Restarting the administration kit service and/or MySQL does not solve the problem.

We have to wait for 1 or 2 days and, magically, things works for several hours before stopping again.

We can not use anymore Kaspersky products. Way too much blocking bugs and missing standard features. We bought 250 licences and we only use 20 of them.

Helmut

26.07.2007 12:48

Hello,

please try version 6.0.1405.

Is 6.0.35 a beta version?

socemj

26.07.2007 15:04

QUOTE(Helmut)

please try version 6.0.1405

I'm sorry but the 6.0.1405 is more buggy than the 6.0.35

I don't know who you are to say "please try version xxx" instead of a version recommanded by the folks at Kaspersky.

The 6.0.35 version was released to correct some bugs people were facing.

With the "official" version we can not even start the administration kit service.
With the 6.0.35 it at least starts. But we can not create any usefull things.

socemj

31.07.2007 18:27

QUOTE(socemj)

Very often we have "Impossible to create a new task : access forbidden" (translated from french) when we want to create a new task. Similar message when we want to create a new policy.

Maybe there is a way to create a trace file for SQL commands or so ?

socemj

1.08.2007 15:34

QUOTE(socemj)

Maybe there is a way to create a trace file for SQL commands or so ?

Yes, ok, there's a way

Looking at the log, seems this is not a problem related to the database but to files.
Aren't the files created twice ?

Here is the log file around the problem :

CODE

mer. août 01 2007 14:24:49.781 00000A48 KLSTD: KLSTD_CreateFile path - 'C:\Program Files\Kaspersky Lab\Kaspersky Administration Kit\Dat\srv_tsk_storage\d92b447f-1758-4102-958d-414f38a533f0.lck' timeout - -1 creation flags - 0x3
mer. août 01 2007 14:24:49.781 00000A48 KLSTD: Starting KLSTD_CreateFile...
mer. août 01 2007 14:24:49.781 00000A48 KLSTD: ...KLSTD_CreateFile took 0 ms (User: 0 ms, Kernel: 0 ms, FullLoad: 0 %)
mer. août 01 2007 14:24:49.781 00000A48 KLSTD: KLSTD_CreateFile path - 'C:\Program Files\Kaspersky Lab\Kaspersky Administration Kit\Dat\srv_tsk_storage\d92b447f-1758-4102-958d-414f38a533f0.klt' timeout - -1 creation flags - 0x3
mer. août 01 2007 14:24:49.781 00000A48 KLSTD: Starting KLSTD_CreateFile...
mer. août 01 2007 14:24:49.781 00000A48 KLSTD: ...KLSTD_CreateFile took 0 ms (User: 0 ms, Kernel: 0 ms, FullLoad: 0 %)
mer. août 01 2007 14:24:49.781 00000A48 KLPRSS: ...CStorage::trans_begin took 0 ms (User: 0 ms, Kernel: 0 ms, FullLoad: 0 %)
mer. août 01 2007 14:24:49.781 00000A48 KLPRSS: Starting CStorage::trans_end...
mer. août 01 2007 14:24:49.781 00000A48 KLSTD: KLSTD_Rename2('C:\Program Files\Kaspersky Lab\Kaspersky Administration Kit\Dat\srv_tsk_storage\d92b447f-1758-4102-958d-414f38a533f0.klt', 'C:\Program Files\Kaspersky Lab\Kaspersky Administration Kit\Dat\srv_tsk_storage\~d92b447f-1758-4102-958d-414f38a533f0.klt~')
mer. août 01 2007 14:24:49.781 00000A48 KLSTD: KLSTD_CreateFile path - 'C:\Program Files\Kaspersky Lab\Kaspersky Administration Kit\Dat\srv_tsk_storage\d92b447f-1758-4102-958d-414f38a533f0.klt' timeout - 0 creation flags - 0x7
mer. août 01 2007 14:24:49.781 00000A48 KLSTD: Starting KLSTD_CreateFile...
mer. août 01 2007 14:24:49.781 00000A48 KLSTD: ...KLSTD_CreateFile took 0 ms (User: 0 ms, Kernel: 0 ms, FullLoad: 0 %)
mer. août 01 2007 14:24:49.781 00000A48 KLSTD: KLSTD_Unlink2('C:\Program Files\Kaspersky Lab\Kaspersky Administration Kit\Dat\srv_tsk_storage\~d92b447f-1758-4102-958d-414f38a533f0.klt~')
mer. août 01 2007 14:24:49.781 00000A48 KLPRSS: ...CStorage::trans_end took 0 ms (User: 0 ms, Kernel: 0 ms, FullLoad: 0 %)
mer. août 01 2007 14:24:49.781 00000A48 KLPRSS: Starting CStorage::trans_begin...
mer. août 01 2007 14:24:49.781 00000A48 KLPRSS: Starting CStorage::trans_end...
mer. août 01 2007 14:24:49.781 00000A48 KLPRSS: ...CStorage::trans_end took 0 ms (User: 0 ms, Kernel: 0 ms, FullLoad: 0 %)
mer. août 01 2007 14:24:49.781 00000A48 KLSTD: KLSTD_CreateFile path - 'C:\Program Files\Kaspersky Lab\Kaspersky Administration Kit\Dat\srv_tsk_storage\d92b447f-1758-4102-958d-414f38a533f0.lck' timeout - -1 creation flags - 0x3
mer. août 01 2007 14:24:49.781 00000A48 KLSTD: Starting KLSTD_CreateFile...
mer. août 01 2007 14:24:49.781 00000A48 KLSTD: ...KLSTD_CreateFile took 0 ms (User: 0 ms, Kernel: 0 ms, FullLoad: 0 %)
mer. août 01 2007 14:24:49.781 00000A48 KLSTD: KLSTD_CreateFile path - 'C:\Program Files\Kaspersky Lab\Kaspersky Administration Kit\Dat\srv_tsk_storage\d92b447f-1758-4102-958d-414f38a533f0.klt' timeout - -1 creation flags - 0x3
mer. août 01 2007 14:24:49.781 00000A48 KLSTD: Starting KLSTD_CreateFile...
mer. août 01 2007 14:24:49.781 00000A48 KLSTD: ...KLSTD_CreateFile took 0 ms (User: 0 ms, Kernel: 0 ms, FullLoad: 0 %)
mer. août 01 2007 14:24:49.781 00000A48 KLPRSS: ...CStorage::trans_begin took 0 ms (User: 0 ms, Kernel: 0 ms, FullLoad: 0 %)
mer. août 01 2007 14:24:49.781 00000A48 KLPRSS: Starting CStorage::trans_end...
mer. août 01 2007 14:24:49.781 00000A48 KLSTD: KLSTD_Rename2('C:\Program Files\Kaspersky Lab\Kaspersky Administration Kit\Dat\srv_tsk_storage\d92b447f-1758-4102-958d-414f38a533f0.klt', 'C:\Program Files\Kaspersky Lab\Kaspersky Administration Kit\Dat\srv_tsk_storage\~d92b447f-1758-4102-958d-414f38a533f0.klt~')
mer. août 01 2007 14:24:49.781 00000A48 KLSTD: KLSTD_CreateFile path - 'C:\Program Files\Kaspersky Lab\Kaspersky Administration Kit\Dat\srv_tsk_storage\d92b447f-1758-4102-958d-414f38a533f0.klt' timeout - 0 creation flags - 0x7
mer. août 01 2007 14:24:49.781 00000A48 KLSTD: Starting KLSTD_CreateFile...
mer. août 01 2007 14:24:49.781 00000A48 KLSTD: ...KLSTD_CreateFile took 0 ms (User: 0 ms, Kernel: 0 ms, FullLoad: 0 %)
mer. août 01 2007 14:24:49.781 00000A48 KLSTD: KLSTD_Unlink2('C:\Program Files\Kaspersky Lab\Kaspersky Administration Kit\Dat\srv_tsk_storage\~d92b447f-1758-4102-958d-414f38a533f0.klt~')
mer. août 01 2007 14:24:49.781 00000A48 KLPRSS: ...CStorage::trans_end took 0 ms (User: 0 ms, Kernel: 0 ms, FullLoad: 0 %)
mer. août 01 2007 14:24:49.781 00000A48 KLPRSS: Starting CStorage::trans_begin...
mer. août 01 2007 14:24:49.781 00000A48 KLPRSS: Starting CStorage::trans_end...
mer. août 01 2007 14:24:49.781 00000A48 KLPRSS: ...CStorage::trans_end took 0 ms (User: 0 ms, Kernel: 0 ms, FullLoad: 0 %)
mer. août 01 2007 14:24:49.781 00000A48 KLSTD: KLSTD_CreateFile path - 'C:\Program Files\Kaspersky Lab\Kaspersky Administration Kit\Dat\srv_tsk_storage\d92b447f-1758-4102-958d-414f38a533f0.lck' timeout - -1 creation flags - 0x3
mer. août 01 2007 14:24:49.781 00000A48 KLSTD: Starting KLSTD_CreateFile...
mer. août 01 2007 14:24:49.781 00000A48 KLSTD: ...KLSTD_CreateFile took 0 ms (User: 0 ms, Kernel: 0 ms, FullLoad: 0 %)
mer. août 01 2007 14:24:49.781 00000A48 KLSTD: KLSTD_CreateFile path - 'C:\Program Files\Kaspersky Lab\Kaspersky Administration Kit\Dat\srv_tsk_storage\d92b447f-1758-4102-958d-414f38a533f0.klt' timeout - -1 creation flags - 0x3
mer. août 01 2007 14:24:49.781 00000A48 KLSTD: Starting KLSTD_CreateFile...
mer. août 01 2007 14:24:49.781 00000A48 KLSTD: ...KLSTD_CreateFile took 0 ms (User: 0 ms, Kernel: 0 ms, FullLoad: 0 %)
mer. août 01 2007 14:24:49.781 00000A48 KLPRSS: ...CStorage::trans_begin took 0 ms (User: 0 ms, Kernel: 0 ms, FullLoad: 0 %)
mer. août 01 2007 14:24:49.781 00000A48 KLPRSS: Starting CStorage::trans_end...
mer. août 01 2007 14:24:49.781 00000A48 KLSTD: KLSTD_Rename2('C:\Program Files\Kaspersky Lab\Kaspersky Administration Kit\Dat\srv_tsk_storage\d92b447f-1758-4102-958d-414f38a533f0.klt', 'C:\Program Files\Kaspersky Lab\Kaspersky Administration Kit\Dat\srv_tsk_storage\~d92b447f-1758-4102-958d-414f38a533f0.klt~')
mer. août 01 2007 14:24:49.781 00000A48 KLSTD: KLSTD_CreateFile path - 'C:\Program Files\Kaspersky Lab\Kaspersky Administration Kit\Dat\srv_tsk_storage\d92b447f-1758-4102-958d-414f38a533f0.klt' timeout - 0 creation flags - 0x7
mer. août 01 2007 14:24:49.781 00000A48 KLSTD: Starting KLSTD_CreateFile...
mer. août 01 2007 14:24:49.781 00000A48 KLSTD: ...KLSTD_CreateFile took 0 ms (User: 0 ms, Kernel: 0 ms, FullLoad: 0 %)
mer. août 01 2007 14:24:49.781 00000A48 KLSTD: KLSTD_Unlink2('C:\Program Files\Kaspersky Lab\Kaspersky Administration Kit\Dat\srv_tsk_storage\~d92b447f-1758-4102-958d-414f38a533f0.klt~')
mer. août 01 2007 14:24:49.781 00000A48 KLPRSS: ...CStorage::trans_end took 0 ms (User: 0 ms, Kernel: 0 ms, FullLoad: 0 %)
mer. août 01 2007 14:24:49.796 00000A48 KLPRSS: Starting CStorage::trans_begin...
mer. août 01 2007 14:24:49.796 00000A48 KLPRSS: Starting CStorage::trans_end...
mer. août 01 2007 14:24:49.796 00000A48 KLPRSS: ...CStorage::trans_end took 0 ms (User: 0 ms, Kernel: 0 ms, FullLoad: 0 %)
mer. août 01 2007 14:24:49.796 00000A48 KLSTD: KLSTD_CreateFile path - 'C:\Program Files\Kaspersky Lab\Kaspersky Administration Kit\Dat\srv_tsk_storage\d92b447f-1758-4102-958d-414f38a533f0.lck' timeout - -1 creation flags - 0x3
mer. août 01 2007 14:24:49.796 00000A48 KLSTD: Starting KLSTD_CreateFile...
mer. août 01 2007 14:24:49.796 00000A48 KLSTD: ...KLSTD_CreateFile took 0 ms (User: 0 ms, Kernel: 0 ms, FullLoad: 0 %)
mer. août 01 2007 14:24:49.796 00000A48 KLPRSS: Starting CStorage::trans_end...
mer. août 01 2007 14:24:49.796 00000A48 KLPRSS: ...CStorage::trans_end took 0 ms (User: 0 ms, Kernel: 0 ms, FullLoad: 0 %)
mer. août 01 2007 14:24:49.796 00000A48 KLPRSS: ...CStorage::trans_begin took 0 ms (User: 0 ms, Kernel: 0 ms, FullLoad: 0 %)
mer. août 01 2007 14:24:49.796 00000A48 KLERR: #1, Error was caught in module "KLPRSS" in file "O:\CS AdminKit\development2\kca\prss\settingsstorage.cpp" on line 676. Error: ''., Error params: (1184/0x0 ("Access denied"), "KLSTD", "O:\CS AdminKit\development2\std\io\klio.cpp", 948)
mer. août 01 2007 14:24:49.796 00000A48 KLPRSS: Starting CStorage::trans_end...
mer. août 01 2007 14:24:49.796 00000A48 KLPRSS: ...CStorage::trans_end took 0 ms (User: 0 ms, Kernel: 0 ms, FullLoad: 0 %)
mer. août 01 2007 14:24:49.796 00000A48 KLSSS: Removed store 'Ou+TcA0o3fqW2kZrKPjh22' in ss-server 'KLSSS_DEFAULT_SERVER' (now 3 stores)
mer. août 01 2007 14:24:49.796 00000A48 KLPRSS: Starting CStorage::trans_end...
mer. août 01 2007 14:24:49.796 00000A48 KLPRSS: ...CStorage::trans_end took 0 ms (User: 0 ms, Kernel: 0 ms, FullLoad: 0 %)
mer. août 01 2007 14:24:49.796 00000A48 KLTSK: KLDB_TRANSACTION_RERUN_END - CATCH, file:O:\CS AdminKit\development2\server\tsk\grouptaskcontrolimpl.cpp, line:2640
mer. août 01 2007 14:24:49.796 00000A48 KLERR: #1, Error was caught in module "KLTSK" in file "O:\CS AdminKit\development2\server\tsk\grouptaskcontrolimpl.cpp" on line 2643. Error: ''., Error params: (1184/0x0 ("Access denied"), "KLSTD", "O:\CS AdminKit\development2\std\io\klio.cpp", 948)
mer. août 01 2007 14:24:49.796 00000A48 KLTSK: Cannot add task.
mer. août 01 2007 14:24:49.796 00000A48 KLERR: #1, Error was caught in module "KLTSK" in file "O:\CS AdminKit\development2\server\tsk\grouptaskcontrolimpl.cpp" on line 2685. Error: ''., Error params: (1184/0x0 ("Access denied"), "KLSTD", "O:\CS AdminKit\development2\std\io\klio.cpp", 948)
mer. août 01 2007 14:24:49.796 00000A48 KLPAR: ExceptionForSoap. See errorinfo below
mer. août 01 2007 14:24:49.796 00000A48 KLERR: #1, Error was caught in module "KLPAR" in file "O:\CS AdminKit\development2\std\par\s_params.cpp" on line 363. Error: ''., Error params: (1184/0x0 ("Access denied"), "KLSTD", "O:\CS AdminKit\development2\std\io\klio.cpp", 948)

Anyone knows better than me ?

Whizard

2.08.2007 06:28

That error can be seen if you creating a task and the machine refuses to honour your default SERVER credentials.

socemj

3.08.2007 14:56

QUOTE(Whizard)

That error can be seen if you creating a task and the machine refuses to honour your default SERVER credentials.

What are those default SERVER credentials ?

The files are created. They exist in the directory. Once the error occured they remain in the directory. This may be a proof the application can create them, rename them, and write to them (some have datas inside).

I tested with granting every rights to everyonce into this directory. But nothing better.

"Administrators" and "System" have full rights into this directory. Nothing else.

Any idea ?

Tybilly

3.08.2007 15:30

Hello,

Please check that the Administrator server account has necessary rights to manage the logical network : http://support.kaspersky.com/faq/?qid=208279253

And also please check account under which Administration Server and MySQL services are started : http://support.kaspersky.com/faq/?qid=203993547

Best Regards,
DB

andkaz

3.08.2007 20:13

QUOTE(socemj @ 3.08.2007 14:56)

QUOTE(Whizard)

That error can be seen if you creating a task and the machine refuses to honour your default SERVER credentials.

What are those default SERVER credentials ?
The files are created. They exist in the directory. Once the error occured they remain in the directory. This may be a proof the application can create them, rename them, and write to them (some have datas inside).

I tested with granting every rights to everyonce into this directory. But nothing better.

"Administrators" and "System" have full rights into this directory. Nothing else.
Any idea ?

[right][snapback]410461[/snapback][/right]

We are making fix for this problem next week. It's being tested now.

Whizard

4.08.2007 06:19

Hello andkaz,

Can you give us some ETA on the fix and what is the exact cause of this error nature is. As I am kind of facing the similar issues.

andkaz

6.08.2007 12:45

QUOTE(Whizard @ 4.08.2007 06:19)

Hello andkaz,

Can you give us some ETA on the fix and what is the exact cause of this error nature is. As I am kind of facing the similar issues.
[right][snapback]410968[/snapback][/right]

On some configurations OS may return error ERROR_ACCESS_DENIED while accessing directory entries (reading file attributes) just after deleting a file in that directory. We don't know exactly cause of the error yet as we failed to reproduce it, though some customers faced it. We have a build with workaround for this issue, it is being tested now.

Whizard

6.08.2007 19:30

Thanks for a quick FYI.

socemj

7.08.2007 14:22

QUOTE(andkaz)

We don't know exactly cause of the error yet as we failed to reproduce it, though some customers faced it.

We can provide you a copy of our machine hosting the admin kit. You could then have access to this computer with vnc. As I'm bored with those problems, this offer won't last long.

I'm very annoyed to face this kind of bug. I have the feeling this is a pre-beta test version

This is the second time our server is totally unusable because the admin kit is buggy. We use this product since 4 monthes, I then suppose we will have a major problem every 2 monthes... We can't afford to have 200 computers with popups every 10 minutes saying Kaspersky have a problem, Kaspersky can't connect to server, Kaspersky this, Kaspersky that.

This was a try with Kaspersky. I now know what product not to buy.

Seriously, you have a good antivirus engine. But your "enterprise grade products" really sucks.

andkaz

7.08.2007 14:31

Build 6.0.1500 with workaround for the problem is available here.

Whizard

7.08.2007 16:03

So just install on top of the current AK?

andkaz

7.08.2007 16:23

QUOTE(Whizard @ 7.08.2007 16:03)

So just install on top of the current AK?
[right][snapback]413068[/snapback][/right]

Yes.
Don't forget to run klbackup before upgrading.

socemj

7.08.2007 20:32

QUOTE(andkaz)

Build 6.0.1500 with workaround for the problem is available

This seems to work.

Whizard

8.08.2007 00:59

Hello,

The upgrade went quite smooth.

jmoncrieffe

3.11.2009 01:05

I am running AK 8 and I get the same error.

The Admin server does not share our files KLSHARE$ exists on File Server,,,,, IT SERVER runs all IT MONITORING AND AUTOMATION.... AK is installed there.

Rights on FILE SERVER for share and directory and files = FULL CONTROL....

Now what?

JM

This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.