| Author |
SQL Server is not releasing Extended SP DLL
|
|
| Mr.Clean 2006-11-03, 7:12 pm |
| During a Wise Installation upgrade of our software, we are renaming a
directory that contains our ExtendedSP DLL. We issue a
DBCC TSWSQLXP(Free) call before doing the rename, yet SQL Server,
still "holds on" to that DLL. We install a new version, and the ListDLLs
utility (from sysinternals) lists the new DLL in the correct directory.
However, when trying to remove the renamed directory, it won't let us
remove the old DLL because it says it is in use. We can delete the NEW
DLL in the NEW directory with no problem.
I have run the DBCC call numerous times and SQL Server STILL won't
release the DLL for deletion. The only way to delete the OLD DLL is to
stop the SQL Server, delete the DLL, and then restart SQL Server. We
do NOT want to do this because there may be other processes running in
SQL Server.
Any help here would be greatly appreciated.
| |
| Mike C# 2006-11-03, 7:12 pm |
|
"Mr.Clean" <mrclean@p&G.com> wrote in message
news:MPG. 1fb53e0e9fd0c4df9896
bc@msnews.microsoft.com...
Are you DROPping the XP before you execute DBCC xp_name (FREE)?
| |
| Mr.Clean 2006-11-03, 7:12 pm |
| In article <OdpzOQ3$GHA.2328@TK2MSFTNGP02.phx.gbl>, xyz@xyz.com says...
>
> "Mr.Clean" <mrclean@p&G.com> wrote in message
> news:MPG. 1fb53e0e9fd0c4df9896
bc@msnews.microsoft.com...
>
> Are you DROPping the XP before you execute DBCC xp_name (FREE)?
>
>
>
Tried that as well and it still won't release it.
| |
| Mr.Clean 2006-11-03, 7:12 pm |
| In article <MPG. 1fb557fa4f866eef9896
bd@msnews.microsoft.com>,
mrclean@p&G.com says...
> In article <OdpzOQ3$GHA.2328@TK2MSFTNGP02.phx.gbl>, xyz@xyz.com says...
> Tried that as well and it still won't release it.
>
Here's the process inside our installation routine:
1. Drop Extended Stored procs
2. Unload OLD TSWSQLXP DLL
3. Rename BIN directory to BINxxx (where xxx = our software version)
{We rename the BIN directory to restore files in case of errors during
install}
4. Install NEW TSWSQLXP DLL into new BIN directory
5. Install Extended Stored procs
6. Call one of the newly installed Extended Stored procs
7. Delete renamed directory (fails because OLD TSWSQLXP DLL still in
use-manual delete fails, also)
We ARE able to delete NEW TSWSQLXP DLL from the new BIN directory even
though the references in the Exptended Stored proc point to the NEW
TSWSQLXP DLL.
Even using MoveFileEX with the MOVEFILE_DELAY_UNTIL
_REBOOT flag won't
allow the directory to be deleted when the system reboots. I have double
checked the registry key (HKEY_LOCAL_MACHINE\
SYSTEM\CurrentContro
lSet\
Control\Session Manager\FileRenameOp
erations) and it is correct.
| |
| Mr.Clean 2006-11-07, 7:12 pm |
| Anyone else have anything to add here?
| |
| Mike C# 2006-11-08, 7:12 pm |
|
"Mr.Clean" <mrclean@p&G.com> wrote in message
news:MPG. 1fb5679d336f882d9896
be@msnews.microsoft.com...
> Here's the process inside our installation routine:
>
> 1. Drop Extended Stored procs
> 2. Unload OLD TSWSQLXP DLL
> 3. Rename BIN directory to BINxxx (where xxx = our software version)
> {We rename the BIN directory to restore files in case of errors during
> install}
> 4. Install NEW TSWSQLXP DLL into new BIN directory
> 5. Install Extended Stored procs
> 6. Call one of the newly installed Extended Stored procs
> 7. Delete renamed directory (fails because OLD TSWSQLXP DLL still in
> use-manual delete fails, also)
>
And if you stop and re-start the SQL Server service after dropping and
releasing the XP what happens?
| |
| Mr.Clean 2006-11-08, 7:12 pm |
| In article <OysAyl1AHHA.1224@TK2MSFTNGP04.phx.gbl>, xyz@xyz.com says...
>
> "Mr.Clean" <mrclean@p&G.com> wrote in message
> news:MPG. 1fb5679d336f882d9896
be@msnews.microsoft.com...
>
> And if you stop and re-start the SQL Server service after dropping and
> releasing the XP what happens?
>
It is still holding on to the OLD DLL if the service is stopped in our
installation program. If we do it manually, it is able to be deleted
about 10 secs after it is stopped.
We are now installing the NEW TSWSQLXP.DLL in the Sys32 directory
because of the KB Article Q300965:
http://support.microsoft.com/defaul...b;en-us;Q300965
We have been 'registering' the TSWSQLXP.DLL wrongly for ages. We have
experienced loads of trouble trying to get a new version installed and
remove the old version due to this.
| |
| Mike C# 2006-11-09, 7:14 pm |
|
"Mr.Clean" <mrclean@p&G.com> wrote in message
news:MPG. 1fbc02e42ff537629896
c0@msnews.microsoft.com...
> In article <OysAyl1AHHA.1224@TK2MSFTNGP04.phx.gbl>, xyz@xyz.com says...
>
> It is still holding on to the OLD DLL if the service is stopped in our
> installation program. If we do it manually, it is able to be deleted
> about 10 secs after it is stopped.
>
> We are now installing the NEW TSWSQLXP.DLL in the Sys32 directory
> because of the KB Article Q300965:
> http://support.microsoft.com/defaul...b;en-us;Q300965
>
> We have been 'registering' the TSWSQLXP.DLL wrongly for ages. We have
> experienced loads of trouble trying to get a new version installed and
> remove the old version due to this.
Now that's interesting. Thanks for the link, I never heard of this
particular problem before.
|
|
|
|