|
| Re: SMTP COM Stopped working in Vista |
 |
Wed, 27 Feb 2008 12:04:43 -080 |
"Roberto Meneghini" <rmeneghini@separationsystems.com> wrote in
message
news:47c5be24$1@newsgroups.borland.com...
> However, in VISTA, the following message appears when a
> client application tries to use my SMTP server: "SMTP COM
> stopped working."
That is not an error message from either COM or Indy, so I am assuming that
the client itself is generating that error, is that correct? Please show
your actual code, including any error values that are being reported by the
OS when calling into the COM object. Chances are, your COM object is not
installed properly, or your client app does not have security access to it.
Gambit
|
| Post Reply
|
| SMTP COM Stopped working in Vista |
 |
Wed, 27 Feb 2008 13:46:45 -060 |
I wrote a small application to sen e-mail using the TIdSMTP component. The
application has a COM interface that allows other program to send messages.
Everything works fine on XP and 2000. However, in VISTA, the following
message appears when a client application tries to use my SMTP server:
"SMTP
COM stopped working."
Any suggestions?
Thanks,
Roberto
|
| Post Reply
|
| Re: SMTP COM Stopped working in Vista |
 |
Wed, 27 Feb 2008 14:57:31 -080 |
"Roberto Meneghini" <rmeneghini@separationsystems.com> wrote in
message
news:47c5dff8$1@newsgroups.borland.com...
> Thank you Gambit. It seems to be a message generated by windows.
I seriously dougt that is an OS error, either.
> The title bar is "Microsoft Windows" and the actual message is
SMTP
> COM has stopped working. A problem caused the program to stop
> working correctly".
Can you show a screenshot?
> The client application was written with the old Borland C++ 5.02.
Doesn't matter. COM is standardized. Again, please show your actual code
that is using the COM object.
> See portion of the client's source code.
I can't do that since you haven't provided it yet.
> The server was written with BDS2006 C++.
Again, doesn't matter.
Gambit
|
| Post Reply
|
| Re: SMTP COM Stopped working in Vista |
 |
Wed, 27 Feb 2008 15:16:27 -050 |
"Remy Lebeau (TeamB)" <no.spam@no.spam.com> wrote in message
news:47c5c243$1@newsgroups.borland.com...
>
> "Roberto Meneghini" <rmeneghini@separationsystems.com>
wrote in message
> news:47c5be24$1@newsgroups.borland.com...
>
>> However, in VISTA, the following message appears when a
>> client application tries to use my SMTP server: "SMTP COM
>> stopped working."
>
> That is not an error message from either COM or Indy
At least it didn't say "Error: The operation completed successfully",
so
it's still more descriptive than 95% of the error messages I usually see.
|
| Post Reply
|
| Re: SMTP COM Stopped working in Vista |
 |
Wed, 27 Feb 2008 16:11:05 -060 |
Thank you Gambit. It seems to be a message generated by windows. The title
bar is "Microsoft Windows" and the actual message is SMTP COM has
stopped
working. A problem caused the program to stop working correctly".
The client application was written with the old Borland C++ 5.02. See
portion of the client's source code. The server was written with BDS2006
C++.
You mentioned that the client application may not have security access. I'm
logged in as an Administrator. Are there other security settings that need
to be configured? Sorry, but I'm still not too familiar with VISTA.
Thanks,
Roberto
try
{
RM_Mail = new IRM_Mail2();
}
catch (...)
{
delete Module;
throw xmsg("Error creating RM_Mail");
}
try
{
RM_Mail->Bind("RM_Mailer.RM_Mail2");
}
catch (...)
{
delete RM_Mail;
RM_Mail = NULL;
}
"Remy Lebeau (TeamB)" <no.spam@no.spam.com> wrote in message
news:47c5c243$1@newsgroups.borland.com...
>
> "Roberto Meneghini" <rmeneghini@separationsystems.com>
wrote in message
> news:47c5be24$1@newsgroups.borland.com...
>
>> However, in VISTA, the following message appears when a
>> client application tries to use my SMTP server: "SMTP COM
>> stopped working."
>
> That is not an error message from either COM or Indy, so I am assuming
> that the client itself is generating that error, is that correct? Please
> show your actual code, including any error values that are being reported
> by the OS when calling into the COM object. Chances are, your COM object
> is not installed properly, or your client app does not have security
> access to it.
>
>
> Gambit
>
|
| Post Reply
|
|
|
|
|
|
|
|
|
|