command line ivm.exe -option causes abnormal exception (returns error -2) in WIN2008

Claudio

Has anyone tested the IVM command line option (e.g. ivm.exe -outbound 63636363) within an WIN2008 Server environment? We have been using IVM for quite a long time with WIN2000 (IVM 2.43 and IVM 3.0 Pro and Enterprise since 2005). Because of Win2000 End-Of-LifeCycle we have to switch to WIN2008 now and bought the IVM 5.03 Enterprise Edition. Everything is set up, and ready to go to production environment.

But when using the command line option, for example ivm.exe -outbound 63636363 (or any other option), the ivm.exe returns error: -2. When launched within a program by shell it returns an "abnormal execution problem". We made a bug report that has been opened by IVM.exe itself and are now waiting for reply.

Did somebody had experience with the command line options in WIN2008? Can somebody test command line on WIN2008 if available to see if it is an WIN2008 issue?

Thanks

Claudio

Isn't there anybody out there who has the Windows Server 2008 installed with IVM, just to try out an simple command line "ivm.exe -outbound xxxxxxxxx" ??? This takes a minute to test. This is a serious bug of an full payed premium enterprise version. Only because of this, we were not able to switch to WIN 2008 to production, and have to run on WIN 2000 that reached end of life cycle this week in a production environment. Now we are about to switch to another software. Notified support and bug report more than a week ago, got a contact from NCH Support then, but still no help or comments for any workarounds or planned fixes.

Claudio

We are waiting almost 2 months for this very important bug fix. When is the fixed version expected to be released?

Claudio

n_c_h_dj wrote:

Hi,

IVM has been in testing for 2 weeks. It is a process. As soon as the cycle is complete it will be released. Could be 5 days, could be another 2 weeks. As of this moment I don't think it will be any more than 2 weeks from today, hopefully sooner.

DJ

thanks for reply DJ.

Claudio

We are already in the 6th week since last message, and over 3 months since our first notification of this bug, and still no update, neither a workaround. We are bleeding here and anxiously waiting for bugfix of a full payed enterprise WIN 2008 version. Our patience has almost ended. What can be the reason of this taking so long? Some other software of NCH has been updated twice already. By the way... the bugged software is still available for download and purchase without any warnings about this important issue.