Solved

A generic error occurred in GDI+.

Every time I name a diagram starting with "con.", when I try to publish it using "Web", it opens a window with the message "A generic error occurred in GDI+.".Ex: Diagram name "CON.Cobranca" I have an error. Diagram name "-CON.Cobranca" I don´t have errors.

Best Answer
photo

Dear Edmir,

We have seen this reported issue and will keep you posted.

Best regards,

photo
0

Dear Edmir,

We have seen this reported issue and will keep you posted.

Best regards,

photo
0

Dear Users,

We gladly announce that this problem has been solved in the recent December 2012 release (version 2.4.0.8).

Best regards,

photo
0

I get the same error with version 2.4.0.8 "A generic error occurred in GDI+" without any "con" or dots in the names. Until the day before yesterday everything worked fine. The validate button does not report any error. All I did was move a sub process into a different process.What can I do to find the error?

photo
0

Dear Matthias,

We clarify that this error was solved when it was triggered by the mentioned scenario (some specific characters in the diagram names).

However, the main cause for this error is related to memory issues.

Therefore, we would kindly recommend you to review if your machine has cornered its resources (i.e available RAM, CPU, etc) at that specific moment.

For instance, you may review if after a reboot, this problem is no longer shown (specially if you recall your models were working properly and had no issues whatsoever on them).

Best regards,

photo
0

This problem returned in version 2.6.0.4, but whith a diferent error message.The message now is "FileStream will not open Win32 devices such as a disk partitions and tape drives. Avoid use of "\\\" in the path."Try to name a process as "CON.NEW" and then publish it.

photo
0

Dear Edmir,

Can you please provide us additional information about this problem, such as:

1. Which operating system you are using (+ bits supported and service packs applied).

2. On which path is the Modeler installed?

3. The full path where the .bpm file throwing this error message is stored.

Best regards,