PBNISMTP-Migrate from PB12.6 to PB2017

1
0
-1

Greetings All.  We recently upgraded to PB2017 from PB12.6.  We are having issues with pbnismtp.  I created a new library and imported the pbnismtp126.pbx file and compiled a pbd.  I added the new pbd and the pbx file to the working directory of the application.  Works in IDE, not in EXE.  We also added the crucial PB17 dlls to the start folder along with the libeay32.dll and the ​ssleay32.dll

It worked great in PB12.6, we're probably missing a dll or two for PB17, any ideas?

 

Thanks

Dennis

 

 

Question Tags: 

Answers

Ashutosh Varshney answered PBNISMTP-Migrate from PB12.6 to PB2017

1
0
-1

Try PB Runtime Packager. It should grab all necessary dlls and then you can compare which ones you are missing.

dlittle_19467's picture

The runtime packager installed a bunch of different dlls.  Works pretty slick, but didn't fix my problem.  Any other thoughts?

Roland Smith answered PBNISMTP-Migrate from PB12.6 to PB2017

1
0
-1

What do you mean by "Does not work"?

Are you running the EXE on the same machine as the IDE?

 

dlittle_19467's picture

Sorry, I thought I included the error message.  We get a bad runtime reference error when it gets to this line: l_smtp.SetRecipientEmail(ls_ToMail)

I am running the EXE on a different machine-it mimics the PRODUCTION runtime environment.

I just added the libeay32 and ssleay32 dlls because I saw an earlier post.  We never included them for the previous PB12.6 implementation.

 

I will give the runtime packager a try-we've never used it before.

Thanks

Dennis

Chris Pollach answered PBNISMTP-Migrate from PB12.6 to PB2017

1
0
-1
Hi Dennis; Since pbnismtp is a 3rd party object, you should contact the author about this issue. https://pbnismtp.codeplex.com Regards ... Chris

dlittle_19467's picture

Thanks Chris,

The codeplex site is shutting down.  I thought I saw somewhere that Bruce recommended users to post to this site.

Dennis

Roland Smith answered PBNISMTP-Migrate from PB12.6 to PB2017

1
0
-1

Are you deploying your application 64bit?

I downloaded the C++ source code and compiled it to 32bit and 64bit. I got the same error when I accidentally tried running a 32bit app using the 64bit pbx file.

I can get you the 64bit pbx if you want.

 

dlittle_19467's picture

We are creating the exe using the 32-bit platform.  I'll try to generate it using the 64-bit platform and see what happens.

BTW-How do I know if the pbx is 32 or 64 bit?

Roland's picture

You can't really. I was guessing that you were trying to run your app as 64bit with the 32bit pbx.

I downloaded the latest PBNISMTP C++ source code from Bruce's github. I updated the open source SMTP code to the latest version and compiled it to 32bit and 64bit. It seems to work fine. I had a similar error to yours which turned out to be running a 32bit app with the 64bit pbx.

dlittle_19467's picture

I tried to compile using the 64-bit platform, I get a Not a valid Win32 application. error.  I'm using the old pbnismtp126.pbx, so I assume that it is 32-bit.

Dennis Little answered PBNISMTP-Migrate from PB12.6 to PB2017

1
0
-1

Guys, I thought I'd add an answer, sometimes the comments get lost in the shuffle.

We get a bad runtime reference error when it gets to this line: l_smtp.SetRecipientEmail(ls_ToMail)

I am running the EXE on a different machine-it mimics the PRODUCTION runtime environment.

I just added the libeay32 and ssleay32 dlls because I saw an earlier post.  We never included them for the previous PB12.6 implementation.

We are creating the exe using the 32-bit platform.  I'll try to generate it using the 64-bit platform and see what happens.

I tried to compile using the 64-bit platform, I get a Not a valid Win32 application. error.  I'm using the old pbnismtp126.pbx, so I assume that it is 32-bit.

Thanks Dennis