Skip to content
+1-888-319-3663

COMMUNITY FORUM

Blank Error When Running a Map

judym@progressive-solutions.com asked 9 years ago
In the last week while attempting to build new maps I have started to encounter a blank error when running those maps.  This has occurred in two separate installs of SmartConnect; one is version 20.12.0.16 and the other is 20.12.0.14. 

Upon re-installing one of the .16 version I started seeing an error message which stated:

[quote=]1 Error in calculation column 'SQLDEF_MARCB-W7-PC' : End of statement expected.[/quote]

The same error occurs no matter what map I am running and now also occurs on older maps which used to run fine.  It occurs even on the simplest maps that have no calculated fields or tasks or .net code that I've added.  It appears to be something to do with a default SQL connection setup in the background of each map or possibly the connection to the SmartConnect database (but all navigation and maintenance inside of SC works fine).

Another side effect of this issue seems to be that no vb.net or c# code can be validated.  Even the code that was already in working maps and used to validate just fine.

Thanks a lot for any guidance you can provide,
Marc
Chris Hanson replied 9 years ago

There was an issue a few builds ago where maps would not work if there were any saved connections that had dashes in them.

You should either be able to remove and rename the saved sql connections without the dashes like hte one you have posted above, or you could upgrade to the latest release which should have it fixed as well.

H

marcb@progressive-solutions.com replied 9 years ago

Thanks a lot Chris.  That resolved my issue and everything seems to be working well now.

HowardJoslin replied 9 years ago

Did you receive any resolution for this error? I'm getting it now as well.

Answers
Best Answer
marcb@progressive-solutions.com answered 9 years ago
Yes, avoid using dashes in the id when creating anything in SmartConnect (ie. data source, map, etc.).  They seemed to have several bugs around this and in the current versions have just restricted you from using dashes at all in the id of an object.

Avoid dashes and this error goes away.

If you would like to submit an answer or comment, please sign in to the eOne portal.