I have a database that has been scripted using SQL Packager 6. When I execute the script against an empty database I get what appear to be erroneous errors reported. In particular, it reports Invalid Object Name citing an object which has been created earlier in the script. I have searched for the object name in the script and can see the CREATE prior to where it is reported as invalid.

So, it appears to have worked out the correct creation order, but for some reason it doesn't recognise that the object has been created.

I have seen this error before. It's pretty rare, but sometimes SQL Server seems to "forget" about uncommited transactions and I don't know why. In all cases, it works to disable transactions using the "Do not use transactions in synchronization scripts" option. This is not ideal if you want to roll back, but in the case of a new database package it's probably not that important anyway.