.comment-link {margin-left:.6em;}

Ben Cops

Friday, February 13, 2009

SSIS Package fails on execute "Integration Services evaluation period has expired"

This was a nasty gotcha, requiring a MS support call and some mucking about.
We had a number of SQL servers, half of which would not allow execution of SSIS packages via the .net API (so it seemed), although they would directly via DTExec - it looked like we'd had the eval copy of SSIS only (odd as SQL wasn't eval) installed on half the servers.
Turns out the user executing the package didn't have access to the registry key which tells SSIS which version the software is licensed as.

The registry node in question is under
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\90\DTS\Setup

The nodes Edition and EditionType should say "Enterprise Edition (64-bit)" for the licensed copy (not sure what it would say for the eval copy). But SSIS couldn't read this key and so assumed it was a trial version - permissions to the Users group had been removed as part of the server hardening. Adding read access back for the account in question solved the problem.

Thursday, February 05, 2009

BizTalk Administration group hub page hangs

Just had the group hub page repeatedly hanging while refreshing the following;
"loading configuration of adapter handlers"

From past experience, enumerating the adapter handlers requires access to the master secret service. Restarting this on our cluster sorted this out.