Be careful when using the wizard. It uses an encrypted ID that can change if the package is amended (IE - becomes a new package).
Best way is to use the msdb job and specify the name fo the package.
EXEC msdb.dbo.sp_start_job
@job_name = 'jobname' , @server_name = 'servername'
------------------------------
The Users are always right - when I'm not wrong!