Exception running SQL package

ngheadnghead Posts: 3
We have an interesting error coming from a SQL Packager executable. The error is:
dbdeployexe - Application Error : The exception unknown software exception (0xe0434f4d) occurred in the application at location 0x7c81eb33.

The dbdeploy.exe is being executed automatically by a Windows Service running as LocalSystem, and the error message displays as a message box. No other diagnostic or debugging information is available.

The executable is being executed with the following parameters:
/server:(local)\msde /quiet /database:OA-GW /username:sa /password:%password%

The interesting thing is when we execute the dbdeploy directly as a logged in user, it works perfectly. It only fails when executed by the service as LocalSystem.

The other bizarre thing is that this did use to work perfectly. Now it fails consistently on multiple deployment machines (but not in our dev environment). We have no idea what has changed in the meantime that could have caused the system to start failing.

We found this post that seemed to have a similar error, and alluded to osql.exe not being in the path, however we checked our deployment machines and SQL Server binn directory is definitely on the path:

So it doesn't appear to be a problem with the dbdeploy SQL logic, it seems to be either an environmental issue, or an issue with the SQL packager EXE itself. Hopefully someone has an idea what our problem could be.

Thanks in advance


  • Brian DonahueBrian Donahue Posts: 6,590 New member
    Hi Nick,

    You have a point there -- it could be the runtime environment. SQL Packager uses the %TMP% environment variable to specify a location to write temporary storage files.

    If the program is running as LocalSystem, then %TMP% is part of the System's environment area, so TMP could be set for users but not for LocalSystem. I'd right-click your 'My Computer' and have a look at the advanced tab to set your system TMP environment variable.
  • Yeah we've had a look at the deployment environment and %TMP% environment vairable is definitely set, and is set as a system wide variable. Therefore should not be dependant on the logged in user at all. %TMP% is being set to C:\Windows\Temp

    Our installer is actually writing the dbdeploy.exe to the %TMP% directory as well, so it appears not to be a permissions problem.

    Can you think of any other possible reason for this error?

  • Brian DonahueBrian Donahue Posts: 6,590 New member
    Hello Nick,

    Can you try running a SQL Profiler session on the server and try to figure out if any SQL is being run by the package at all? In other words, try to figure out if the application error is happening on start or when it's actually trying to execute some SQL.
Sign In or Register to comment.