April 6, 2006 at 8:49 pm
Hi all, hate SSIS already... I have created some maint plans and all work. I migrate them into filesystem ok, then reimport them to another server but, when I change connection properties etc I cannot save them without getting an error "GUID should contain 32 digits with 4 dashes". I have almost given up on this, the package actually executes and runs with success but appears to do nothing that it should. Are packages portable?? How do I get these things to save and run properly
Thanks in advance.
April 10, 2006 at 8:00 am
This was removed by the editor as SPAM
April 11, 2006 at 4:31 am
How are you changing connection properties? Which properties are you changing?
Yes, packages are portable. The correct method of moving packages between different environments is to employ the use of configurations!
-Jamie
Jamie Thomson
http://sqlblog.com/blogs/jamie_thomson
April 11, 2006 at 7:12 pm
ok try this. create a maint plan via the gui in em. Simple check integrity then backup all system databases. Modify logging to appropriate directory.
Right now export that package using ssis gui interface (or dtutil) makes no difference. Export to filesystem.
ok all straight forward so far.. But I am not able to import that package to another server or even back to the same server using the reverse of above, i.e an import via the ssis gui after deletion of existing maint package. Sure it imports and looks fine but try executing it. I tsays successfull but generates no log output nor does it actually perform integrity check or backup.
Now try to edit the package and change anything (try altering log destination) then save it and you will get the guid error I described above. Sorry but this has to be a bug as in all steps I am using supplied tools or Gui interfaces. Why provide an export and import function when it fails to even work correctly from and to the same server the package was created on.
Not sure what you mean by configurations but I will read up on this anyway.
oh btw I have tried editing the package via visual studio to correct the connections also but this fails to get the package to work. I suspect something 'breaks' in regard to the guid value described in the error during an export or import.
April 19, 2006 at 4:43 am
I've had the same error message (guid should contain 32 digits). But not when moving packages, just trying to create a very simple Maintenance job.
It turned out to be cause by the fact that SSIS was not installed. My fault. Easy to fix as well. HIH.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply