Unable to get APS instances on webspace id 19 (ErrorCode: 255, STDOUT:).

[UweP]

Hello. I can't remove a webapplication from one of my webspaces. The backups fail with this error:
Unable to get APS instances on webspace id 19 (ErrorCode: 255, STDOUT.

Here the psadump.log:


[28366]: 22:05:10 INFO Status file: /opt/psa/PMM/sessions/2012-06-12-000508.113/dump-status.xml
[28366]: 22:05:10 INFO ------------------------------------------------------------
[28366]: 22:12:29 ERROR 7c612b90-62d6-4a56-8a13-ff4d98c8681d Unable to get APS instances on webspace id 19 (ErrorCode: 255, STDOUT.

== STDERR ====================
1+0 records in
1+0 records out
31457280 bytes (31 MB) copied, 0.101945 s, 309 MB/s
/bin/tar: subdomains/et/conf: Cannot open: Permission denied
/bin/tar: subdomains/et/error_docs: Cannot open: Permission denied
/bin/tar: Exiting with failure status due to previous errors
/bin/tar: subdomains/shop/conf: Cannot open: Permission denied
/bin/tar: subdomains/shop/error_docs: Cannot open: Permission denied
/bin/tar: Exiting with failure status due to previous errors
/bin/tar: subdomains/studi/conf: Cannot open: Permission denied
/bin/tar: subdomains/studi/error_docs: Cannot open: Permission denied
/bin/tar: subdomains/wow/conf: Cannot open: Permission denied
17,1 Top
[28366]: 22:05:10 INFO ------------------------------------------------------------
[28366]: 22:05:10 INFO Migration status reporting initialized.
[28366]: 22:05:10 INFO Status file: /opt/psa/PMM/sessions/2012-06-12-000508.113/dump-status.xml
[28366]: 22:05:10 INFO ------------------------------------------------------------
[28366]: 22:12:29 ERROR 7c612b90-62d6-4a56-8a13-ff4d98c8681d Unable to get APS instances on webspace id 19 (ErrorCode: 255, STDOUT.

The error I get is Unable to get APS instances on webspace id 19 (ErrorCode: 255, STDOUT.. I probably also have to look into the permission denied errors. But first I need to fix this one.

I hope someone can help me.
What I did was, I deleted the directory content of the application then tried to remove the application which didn't work anymore. It is 1 week behind and I only keep backups for two days.

Hope someone can help me. Thank you!

 

[IgorG]

Database Inconsistency
Find the domains for which webspace_id is 0 or incorrectly set

select id,webspace_id from domains;

Set with the exact webspace_id that is required. Check it with

select id,cacheId,registryUid from smb_apsPackages;

registryUid shouldn't be NULL. You can try to remove such records so as to run the backup perfectly.
Contact Support Team if you can't fix this database inconsistency by yourself.

 

[iKovah]

Same error

Hello Parallels team,

i'm getting the same error while trying to create a backup via the backup manager.
It's exactly the same problem but its with the webspace id 2.

I already tried to fix the inconsistency but i couldn't succeed.
With the
select id,webspace_id from domains;
i get a table with all my domains listed, every domain has the webspace_id 2, only the webspace with the id has the webspace_id 0.

Then i tried the
select id,cacheId,registryUid from smb_apsPackages;
code, i rewrote registryUid with NULL but the backup still fails with the error mentioned above.

What can i do now?
I'm running PPP at version 11.0.9.
I have a problem with an application install named TeamWox. I installed it, tried it and deinstalled it. But it keeps showing up in the Installed Applications list. Maybe this could be the error source?

Greetings,
Kovah

 

[l.with]

Having the same problem, on my system the table smb_apsPackages is empty.
Thus I have no idea what to do.

Database Inconsistency
Find the domains for which webspace_id is 0 or incorrectly set

select id,webspace_id from domains;

Set with the exact webspace_id that is required. Check it with

select id,cacheId,registryUid from smb_apsPackages;

registryUid shouldn't be NULL. You can try to remove such records so as to run the backup perfectly.
Contact Support Team if you can't fix this database inconsistency by yourself.

 

[IgorG]

Thus I have no idea what to do.

As I wrote before:

Contact Support Team if you can't fix this database inconsistency by yourself.