Diese Seite mit anderen teilen ...

Informationen zum Thema:
Forum:
WinDev Forum
Beiträge im Thema:
11
Erster Beitrag:
vor 5 Jahren, 2 Monaten
Letzter Beitrag:
vor 4 Jahren, 8 Monaten
Beteiligte Autoren:
TODD ( Beaulieu of A).pcs.crosspost, Fabrice Harari.pcs.crosspost, Cesar Flores, Piet van Zanten, Stefan Bentvelsen

.net assembly not found only when in production

Startbeitrag von TODD ( Beaulieu of A).pcs.crosspost am 11.02.2013 17:07

Hello All,
Why is it that the syntax used will work fine in a developement environment with the same .net framework as production. But once placed on the production server the program suddenly cannot find a module. This is frustrating. I've instantiated properly run in test, compiled, used the workshop to move it to the production box
the production box DOES have the .net 4 framework although my dlls are in 2.0. and what I get is the following message....Anyone have any Ideas or run across the answer to this I've been looking all morning to no avail. Thank you all.

WL call:
Process of 'Global Procedure Get_SecHasObject (server)' (ServerProcedures.Get_SecHasObject), line 23, thread 0

What happened?
Check whether the .NET framework is available on the computer.
Unable to load D:\WebDev17\wd170net4.dll DLL

Error code: 1065
Level: fatal error (EL_FATAL)

System error code: 126
System error message:
The specified module could not be found.

Dump of the error of 'wd170vm.dll' module (17.0.287.3).
Identifier of detailed information (.err): 1065
Debugging information:
DLL qui provoque le chargement : WDVM
DLL à charger : wd170net4.dll
DLL chargée : D:\WebDev17\wd170net4.dll
Chemin des DLL : D:\WebDev17
Chemin de l'EXE :
Additional Information:
EIT_PILEWL :
Global Procedure Get_SecHasObject (server) (ServerProcedures.Get_SecHasObject), line 23
Global Procedure GetUrlRequest (server) (ServerProcedures.GetUrlRequest), line 109
EIT_DATEHEURE : 11/02/2013 11:32:55

Message forwarded from pcsoft.us.windev

Antworten:

Hi TODD,

the program is looking for the D:\WebDev17\wd170net4.dll DLL.
Is it present on the production server ?

von Stefan Bentvelsen - am 12.02.2013 13:21
Hello Todd

First, the fact that you say you have included them "IN THE PROJECT" may
be the cause of the problem...

You should not include them in the project, but in the INSTALLER, which
is not the same thing at all...

Second point, did you check on the target machine that the DLL in
question has indeed been installed in the exe directory?

Best regards

--
Fabrice Harari
International WinDev, WebDev and WinDev mobile Consulting

More information on http://www.fabriceharari.com


On 2/12/2013 1:43 AM, TODD ( Beaulieu of A) wrote:
> I have now included both the wd170net4.dll and the wd170net2.dll in the project and it gave me the same message. thanks for the quick reply though.
>
Message forwarded from pcsoft.us.windev

von Fabrice Harari.pcs.crosspost - am 12.02.2013 13:33
Fabrice, Thanks for the reply.
I have tried having the wd170XX included in the deploy to server by adding files to include. I have also tried it without them included. same results both ways. To which files to you refer when you say make sure "they" are located in the same directory as the EXE, the wd70XX files or my .net assembly. I have placed the .net assemblies all over this project and any directory that may even remotely relate to the project....same result. I did get a response from someone that I had contacted who said that this might have to do with the security level the server exerts over the .net framework so that it might not be allowing it to function properly. He said that he read it in the french forums...unfortunately I don't speak French...not now at least. Do you have any other thoughts as to what it might be. Thank you so much for the help. Todd

Message forwarded from pcsoft.us.windev

von TODD ( Beaulieu of A).pcs.crosspost - am 12.02.2013 14:29
Hi Todd

this may be just a semantic problem, but it also may be the problem, so
I will insist on it...

Your error message is saying that one of the windev DLL is missing
(wd170net4.dll)... This dll is part of the windev framework and,
according to its name, is in charge of dealing with .net assemblies...

Clearly, if it's not at the right place on the production server, your
program cannot work...

So in the installer setup, you have the possibility to include files
(but in that case, you have to tell WHERE they will be installed) but
you also have a step in which you check all the framework dll that have
to be included/installed... it's in THAT step that you have to verify
that the dll in question (wd170net4) is checked...

The second thing that you need to check is that after installing on the
production server, the same dll (wd170net4.dll) is INDEED present in
your EXE directory...

Till I have confirmation of those 2 precise points, there is nothing
else to look at...

Best regards


--
Fabrice Harari
International WinDev, WebDev and WinDev mobile Consulting

More information on http://www.fabriceharari.com

On 2/12/2013 10:29 AM, TODD ( Beaulieu of A) wrote:
> Fabrice, Thanks for the reply.
> I have tried having the wd170XX included in the deploy to server by adding files to include. I have also tried it without them included. same results both ways. To which files to you refer when you say make sure "they" are located in the same directory as the EXE, the wd70XX files or my .net assembly. I have placed the .net assemblies all over this project and any directory that may even remotely relate to the project....same result. I did get a response from someone that I had contacted who said that this might have to do with the security level the server exerts over the .net framework so that it might not be allowing it to function properly. He said that he read it in the french forums...unfortunately I don't speak French...not now at least. Do you have any other thoughts as to what it might be. Thank you so much for the help. Todd
>
Message forwarded from pcsoft.us.windev

von Fabrice Harari.pcs.crosspost - am 12.02.2013 14:53
Hi,

Stefan presented the solution.
Fabrice's answer is correct for Windev, not for Webdev.
A Webdev site never uses DLL's from the site directory, it is useless to include it in your deployment package.
A site only holds the pages and resources interpreted by the Webdev Application Server.
The WAS is running as a service and apparently needs the wd170net4.dll
In my server installation in c:\WebDev17 it is not present, only wd170net1.dll, wd170net2.dll and wd170net2_64.dll.
So it's probably an option in the Webdev Engine installation (re-install) or you have to copy it manually to your server.

Regards,
Piet

von Piet van Zanten - am 12.02.2013 15:38
Fabrice,
I have included the wd170xxxx.dll for 1,2,4 in the exe folder before deploying to the server. I made sure that they were included in the project during deployment. Once deploy I tried it...no luck on the website. So, I put the wd170xxxx.dll along with the modules(assemblies) that it should be trying to run..in EVERY folder that might even possibly have to do with the project as well as a few others. both the .net dlls and the wd170xxxx.dlls are now in nearly every folder in the inetpub.wwwroot of the server. I have only been doing this a very short time so please have some patience as I am attempting to understand the linkages to the parts of the software required to make the coding run in the production environment...I'm not a server guy. I am a programmer and am having a great time with the programs I am developing and the dev environment. Thank you for hanging in there with me as I try to get this figured out. Todd

Message forwarded from pcsoft.us.windev

von TODD ( Beaulieu of A).pcs.crosspost - am 12.02.2013 15:52
Hi Todd

from your last message, it seems that you are talking about a WEBDEV
development (website, inetpub, etc...), which would explain partly why
we are not talking about the same thing

Is that correct?

If yes, it means that you have a web site whose server code is trying to
use a .net assembly... And yes, that may means a lot of permissions/problems

Best regards

--
Fabrice Harari
International WinDev, WebDev and WinDev mobile Consulting

More information on http://www.fabriceharari.com


On 2/12/2013 11:51 AM, TODD ( Beaulieu of A) wrote:
> Fabrice,
> I have included the wd170xxxx.dll for 1,2,4 in the exe folder before deploying to the server. I made sure that they were included in the project during deployment. Once deploy I tried it...no luck on the website. So, I put the wd170xxxx.dll along with the modules(assemblies) that it should be trying to run..in EVERY folder that might even possibly have to do with the project as well as a few others. both the .net dlls and the wd170xxxx.dlls are now in nearly every folder in the inetpub.wwwroot of the server. I have only been doing this a very short time so please have some patience as I am attempting to understand the linkages to the parts of the software required to make the coding run in the production environment...I'm not a server guy. I am a programmer and am having a great time with the programs I am developing and the dev environment. Thank you for hanging in there with me as I try to get this figured out. Todd
>
Message forwarded from pcsoft.us.windev

von Fabrice Harari.pcs.crosspost - am 12.02.2013 16:09
Fabrice,
Yes it is a website. I call a global procedure in webdev that call to one .Net assembly that then calls another .net assembly and passes data back upstream to the webdev procedure. I am going to compare (again my pc to the server wesite to sebsite) parameters, .Net versions, and locations of the dlls to see if there is a difference. I have complete rights to both the production server and my pc. Thank you again for all your help on this. I'll keep plugging away at it. If you think of something else, Please let me know and I'll try it. Thanks again. Todd

Message forwarded from pcsoft.us.windev

von TODD ( Beaulieu of A).pcs.crosspost - am 12.02.2013 17:16
Fabrice,
thanks for the information. we have uninstalled and reinstalled the server to the root directory c:...the site is now on the d: with pointer and web site showing no errors in the WEBDEV17 admin program. still the error persists that the wd170net4.dll cannot find the .net assembly. As you suggest I will try copying the .net assemblies to the webdev17 directory on the root drive where the wd170net4.dll resides and see if that works. I am copying a response I recieved from PCSoft reguarding the problem for you to examine.

The LIBC DLLs might not be installed on your machine.
The .NET 4 DLL requires the LibC 10. Therefore, it is not loaded on the computers:

that only own the .NET 4 framework
on which no other application has installed the LibC 10 yet (Visual 2010 for example).

The distributable version of the LibC 10 can be freely downloaded from the Microsoft site (address valid when this documentation was published: http://www.microsoft.com/downloads/details.aspx?FamilyID=a7b7a05e-6de6-4d3a-a423-37bf0912db84&displayLang=fr ).
You may also use an utility such as Procmon.exe. It will show use all the files that your application is using or attempting to use. It often helps a lot.
See here:
http://www.mztools.com/articles/2008/MZ2008024.aspx


Message forwarded from pcsoft.us.windev

von TODD ( Beaulieu of A).pcs.crosspost - am 15.02.2013 15:15
Hi Todd

did you found a solution to this problem? im having the same error.
hope you could share your results.

Regards

von Cesar Flores - am 08.08.2013 16:39
Zur Information:
MySnip.de hat keinen Einfluss auf die Inhalte der Beiträge. Bitte kontaktieren Sie den Administrator des Forums bei Problemen oder Löschforderungen über die Kontaktseite.
Falls die Kontaktaufnahme mit dem Administrator des Forums fehlschlägt, kontaktieren Sie uns bitte über die in unserem Impressum angegebenen Daten.