I have a WAA server with six package DLLs running.  This evening I made some 
changes to one of the applications on my laptop.  I have WAA and IIS running 
there for testing, and it worked fine.  I shut down waa1srv.exe on my 
server, loaded the new DLL, and launched startwaa.bat, as I've done a 
million times before.  But this time, the dll I'd just copied to the server 
wouldn't load!  All the others loaded just fine.  Hmmm....  Runs on my 
laptop...  So I take WAA down, delete the new DLL, and copy the old DLL back 
out to the server and launch StartWAA.bat again.  You guessed it--the OLD 
DLL won't load now, either!!!

I've tried rebooting the server, checking log files, copying out new 
versions of the DLL after making minor changes, etc.  Nothing seems to work! 
It works great on my laptop, but I get and ERR Could not load package DLL... 
in the WAA10810.LOG file in the \waa folder on the server.

I need this package to RUN!  I'll have users swarming me in the morning. 
Any ideas?

Steve,

 it is very often the case that a DLL could not be loaded because this DLL
 requires other DLLs which are not available or are not deployed at the
 WAA Server site. You can check if all DLLs are loadable using the
 attached utility. Simple go to the location where your waa1srv.exe
 is deployed and run chk4dll yourpackage.dll

 We also had sometimes the case that customers have added init exit
 procedures to packages - leading to a immediate shutdown at package load.

 Anyway, in the event even your old package do not load anymore i
 would suspect that something has changed in means of environment
 or user-rights.

 Lets assime that somebody changed the configuration of the OS while the WAA
 was running. A typical scenario is that some one changes the path env. var.
 in control-panel -> system while the WAA runs. After a couple of days the
 WAA is shutted down, now you try to start the WAA again but it fails with
 could not find/load package dll. -> Reason: Path changes only affect new
 processes not existing ones!

 I have no idea if this helps, but thats all which comes to mind right know.
 with best regards
 Steffen F. Pirsig
 Alaska Software

"Steve Woolstenhulme" <Steve At Bestaero.com> wrote in message 
news:50cfa936$2640a6d8$118ab@news.alaska-software.com...
>I have a WAA server with six package DLLs running.  This evening I made 
>some changes to one of the applications on my laptop.  I have WAA and IIS 
>running there for testing, and it worked fine.  I shut down waa1srv.exe on 
>my server, loaded the new DLL, and launched startwaa.bat, as I've done a 
>million times before.  But this time, the dll I'd just copied to the server 
>wouldn't load!  All the others loaded just fine.  Hmmm....  Runs on my 
>laptop...  So I take WAA down, delete the new DLL, and copy the old DLL 
>back out to the server and launch StartWAA.bat again.  You guessed it--the 
>OLD DLL won't load now, either!!!
>
> I've tried rebooting the server, checking log files, copying out new 
> versions of the DLL after making minor changes, etc.  Nothing seems to 
> work! It works great on my laptop, but I get and ERR Could not load 
> package DLL... in the WAA10810.LOG file in the \waa folder on the server.
>
> I need this package to RUN!  I'll have users swarming me in the morning. 
> Any ideas?
>

Oops, here we go with the attachment,

regards
Steffen

Thanks Steffen.  Your answer was right on.  I did indeed delete one more DLL 
than I should have!


<Steffen F. Pirsig> wrote in message 
news:4e905e08$54cc9fc3$aad@news.alaska-software.com...
> Steve,
>
> it is very often the case that a DLL could not be loaded because this DLL
> requires other DLLs which are not available or are not deployed at the
> WAA Server site. You can check if all DLLs are loadable using the
> attached utility. Simple go to the location where your waa1srv.exe
> is deployed and run chk4dll yourpackage.dll
>
> We also had sometimes the case that customers have added init exit
> procedures to packages - leading to a immediate shutdown at package load.
>
> Anyway, in the event even your old package do not load anymore i
> would suspect that something has changed in means of environment
> or user-rights.
>
> Lets assime that somebody changed the configuration of the OS while the 
> WAA
> was running. A typical scenario is that some one changes the path env. 
> var.
> in control-panel -> system while the WAA runs. After a couple of days the
> WAA is shutted down, now you try to start the WAA again but it fails with
> could not find/load package dll. -> Reason: Path changes only affect new
> processes not existing ones!
>
> I have no idea if this helps, but thats all which comes to mind right 
> know.
> with best regards
> Steffen F. Pirsig
> Alaska Software
>
> "Steve Woolstenhulme" <Steve At Bestaero.com> wrote in message 
> news:50cfa936$2640a6d8$118ab@news.alaska-software.com...
>>I have a WAA server with six package DLLs running.  This evening I made 
>>some changes to one of the applications on my laptop.  I have WAA and IIS 
>>running there for testing, and it worked fine.  I shut down waa1srv.exe on 
>>my server, loaded the new DLL, and launched startwaa.bat, as I've done a 
>>million times before.  But this time, the dll I'd just copied to the 
>>server wouldn't load!  All the others loaded just fine.  Hmmm....  Runs on 
>>my laptop...  So I take WAA down, delete the new DLL, and copy the old DLL 
>>back out to the server and launch StartWAA.bat again.  You guessed it--the 
>>OLD DLL won't load now, either!!!
>>
>> I've tried rebooting the server, checking log files, copying out new 
>> versions of the DLL after making minor changes, etc.  Nothing seems to 
>> work! It works great on my laptop, but I get and ERR Could not load 
>> package DLL... in the WAA10810.LOG file in the \waa folder on the server.
>>
>> I need this package to RUN!  I'll have users swarming me in the morning. 
>> Any ideas?
>>
>