That is what I suspected too. I checked run.bat where java.library.path is defined. I hardcoded the location of where the dll should be. It still gave the same error.
I am going to try to compare the dlls on the machine and works vs the new one and see if there is any difference.
But I am curious about the stack trace because most times when people cite a dll problem doesnt the trace say xxx.so or xxx.dll cannot be found?
Thanks. I will post back my results. This has got me scratching my head.