Permission error when running hcidbdump -e -D (testing 5.7)

[Stephen Bull]

Hi,

We have a test 5.7 build that we plan on migrating to. From initial testing I have a number of messages that I now want to delete from the recovery and error databases. So as I would in version 5.3, at the command line I run hcidbdump -e -D

As expected I get the “Deleting messages without saving them is dangerous!

Are you sure? [n]” prompt to which I type “y”

With my new 5.7 build I am getting the following:

“Unable to open temp file for deletion control: Permission denied”

I took a look at the folder/file permissions in the directory structure (we are running Windows Server 2008) thinking I could just change something there. I don’t want to remove ‘Read Only’ for too many files/folders though (especially not knowing if this is really the issue).

Has anyone experienced this same issue before? Any insights as to where the problem lies and what I can do to fix this?

Cheers,

Stephen

Topic

[Nick Stainback]

can you access the contents of the error DB

hcidbdump -e ?

[Stephen Bull]

Nick Stainback wrote:

can you access the contents of the error DB

hcidbdump -e ?

Hi Nick,

Yes, hcidbdump -e shows me the contents without a problem, along with other information-based switches. It just appears to be the delete switch which isn’t working with the permissions error.

Cheers,

Stephen

[Nick Stainback]

Are you executing the command as hci?  Also does the user executing the command have “execute” rights on the exec and databases folder.

[Stephen Bull]

Nick Stainback wrote:

Are you executing the command as hci?

Are you referring to user or admin? Apologies if I’ve misinterpreted the question!

Nick Stainback wrote:

Also does the user executing the command have “execute” rights on the exec and databases folder.

This I’ll need to check. I’m waiting for our temp license to be renewed so once that is received I can play with the permissions in these two locations (hopefully early next week). It’s good to have a directory location to focus on now, so thank-you!

I’ll post back here next week regarding the folder permissions.

Cheers,

Stephen

[Jill Fredericks]

We ran into this problem also. I don

[Author]

Replies