1. David Peace (Powersoft)
  2. PowerBuilder
  3. Monday, 30 January 2023 09:16 AM UTC

Hi Guys

We are using PBNISMTP downloaded from TopWiz (latest version). We are getting an when attempting to send an email. The error is a messagebox from the PBNISMTP code:

Could not send message: Error: 8007007B

Description: The filename, directory name, or volume label syntax is incorrect.

For clarification we are only seeing this error on the Clients Machines both in the IDE and production. We have no such issues in our DEV or Test environments.

The error makes very little sense and doesn ot really seem to relate to SMTP stuff. Has anyone seen anything like this before or any ideas how we can debug the problem?

Many thanks

David

Accepted Answer
David Peace (Powersoft) Accepted Answer Pending Moderation
  1. Wednesday, 1 February 2023 10:54 AM UTC
  2. PowerBuilder
  3. # Permalink

Thank you all for your help and input. The client has resolved the problem which was: the From Email address was null/empty.

Cheers

David

Comment
  1. Miguel Leeuwe
  2. Wednesday, 1 February 2023 10:57 AM UTC
wow! That error message could have been a bit more specific!

Glad it's solved.
  1. Helpful
  1. David Peace (Powersoft)
  2. Wednesday, 1 February 2023 11:33 AM UTC
Yes, I've added code to validate the data now. This was just a migration project so I'm glad it was not something fundamental.
  1. Helpful
There are no comments made yet.
Roland Smith Accepted Answer Pending Moderation
  1. Monday, 30 January 2023 14:05 PM UTC
  2. PowerBuilder
  3. # 1

It could be an attempt to attach a file and there is an invalid character in the file name or the file doesn't exist.

Comment
  1. David Peace (Powersoft)
  2. Monday, 30 January 2023 16:59 PM UTC
Hi Roland



It's a simple message subject "test" body "test" not attachments. It makes no sense and the error is meaningless. If you google that error number it looks like your windows environment is not Activated or something. I did check it was Activated....
  1. Helpful 2
There are no comments made yet.
Miguel Leeuwe Accepted Answer Pending Moderation
  1. Monday, 30 January 2023 11:04 AM UTC
  2. PowerBuilder
  3. # 2

Hi David,

Just a wild guess: could it be you have to allow some smtp port for inbound/outbound?

regards.

Comment
  1. David Peace (Powersoft)
  2. Monday, 30 January 2023 17:03 PM UTC
No file attachment, just a simple test message. No SMTP Authenticatioin either just Server name and port 25.
  1. Helpful
  1. Miguel Leeuwe
  2. Monday, 30 January 2023 17:09 PM UTC
port 25 is blocked by many anti virus programs. Try without having the anti virus active, just as a test?
  1. Helpful 1
  1. David Peace (Powersoft)
  2. Tuesday, 31 January 2023 13:58 PM UTC
Thanks, I'll talk to the client and see if they can eliminate the AV software. It's got to be something like that.
  1. Helpful
There are no comments made yet.
Miguel Leeuwe Accepted Answer Pending Moderation
  1. Monday, 30 January 2023 17:05 PM UTC
  2. PowerBuilder
  3. # 3

More thoughts:

- can you find anything in the event viewer?

- hate to say it, but maybe the fastest way to figure out what's going on is to run process monitor by sysinternals?

regards

 

Comment
There are no comments made yet.
Miguel Leeuwe Accepted Answer Pending Moderation
  1. Monday, 30 January 2023 17:39 PM UTC
  2. PowerBuilder
  3. # 4

Recently I had to do some testing on our own smtp server, since we switched offices. I had to add my internal IP address of my PC to our SMTP server, if not it didn't work.

Comment
  1. Miguel Leeuwe
  2. Monday, 30 January 2023 17:43 PM UTC
(I mean the "default" setting for that value).
  1. Helpful
  1. David Peace (Powersoft)
  2. Tuesday, 31 January 2023 13:57 PM UTC
It's not using MAPI, it's SMTP relay against the server. As you say if it allows the OLD pbnismtp code to work the real question is what is blocking the new code which has not really changed much from what I understand.



I'm starting to wonder if their Virus Software is blocking it and they had an exception for the previous version of the software. Especially as we have no problem on any of our DEV or Test environments, regardless of Windows version etc.
  1. Helpful
  1. Miguel Leeuwe
  2. Tuesday, 31 January 2023 14:12 PM UTC
yes, as a test just to exclude possible causes. Also ask if the firewall can be de-activated temporarily.
  1. Helpful
There are no comments made yet.
David Peace (Powersoft) Accepted Answer Pending Moderation
  1. Tuesday, 31 January 2023 17:02 PM UTC
  2. PowerBuilder
  3. # 5

Hi Guys

An interesting devlopment. The Client recompiled the PB2022 Source code after adding the PBNISMTP126.pbd as the first library in the code and the email problem went away. So it's not a migration issue it's definately something to do with the change in underlying PBX. My gut is telling me that they had to put some exception in their AV for the pbnismtp126.pbx and now it is called pbnismtp.pbx it is being blocked.

We will revert back to the Old PBD for now and await the next release of PB2022 and the new inbuilt SMTP stuff :)

Thanks for your input and ideas.

Cheers

David

Comment
  1. Miguel Leeuwe
  2. Tuesday, 31 January 2023 18:49 PM UTC
Thanks for sharing David!
  1. Helpful
  1. Roland Smith
  2. Tuesday, 31 January 2023 20:17 PM UTC
Was the PBD generated with pbx2pbd220.exe?
  1. Helpful
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.