As you can see from this logs it just detects that dataset is non-conformant and exits.
The only reason for it to be non-conformant is because the destination snapvault aggregate has reached it full threshold. (90%)
This should not be a reason for not registering the primary snapshot in my opinion.
Regards Magnus
########## Taking Snapshot on Primary xxx:xxx ##########
[Wed Mar 27 09:07:41 2013] INFO: Creating Snapshot for xxx on xxx
[Wed Mar 27 09:07:57 2013] INFO: Snapshot Create of xxx_db2-hourly_20130327090724 on xxx:xxx Completed Successfully
########## PRE APPLICATION UNQUIESCE COMMANDS ##########
[Wed Mar 27 09:07:57 2013] INFO: No commands defined
########## PRE APPLICATION UNQUIESCE COMMANDS FINISHED SUCCESSFULLY ##########
########## Application unquiesce ##########
[Wed Mar 27 09:07:57 2013] INFO: Unquiescing databases
[Wed Mar 27 09:07:57 2013] INFO: Unquiescing database XXX
[Wed Mar 27 09:07:58 2013] INFO: Unquiescing database XXX finished successfully
[Wed Mar 27 09:07:58 2013] INFO: Unquiescing databases finished successfully
########## POST APPLICATION UNQUIESCE COMMANDS ##########
[Wed Mar 27 09:07:58 2013] INFO: No commands defined
########## POST APPLICATION UNQUIESCE COMMANDS FINISHED SUCCESSFULLY ##########
########## Generating Info ASUP on XXX ##########
[Wed Mar 27 09:07:58 2013] INFO: ASUP create on XXX finished successfully
########## Checking Protection Manager dataset snapcreator_XXX ##########
[Wed Mar 27 09:07:59 2013] INFO: Checking if Protection Manager dataset snapcreator_XXX is conformant
[Wed Mar 27 09:08:12 2013] ERROR: [scf-00018] Protection Manager dataset snapcreator_XXX is nonconformant, Exiting!