Error 2715 after deleting and adding ODBC source
I've been laborating with an ODBC source importing and changing values but only in the ODBC section of Wise Package Studio 8
Suddenly when I'm gonna try out the package it returns Internal Error 2715 "Application Name"
I've searched in Setup Editor - Tables for errors, but all I get is some Radio Button error internal Wise mojo.... Think I've seen that before on other packages so I don't think that's the one.
Anyone got a clue about this?
Suddenly when I'm gonna try out the package it returns Internal Error 2715 "Application Name"
I've searched in Setup Editor - Tables for errors, but all I get is some Radio Button error internal Wise mojo.... Think I've seen that before on other packages so I don't think that's the one.
Anyone got a clue about this?
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
anonymous_9363
13 years ago
Since you have deleted and re-added an ODBC component, I'd bet that the old component is still present but empty, a common cuase of this error.
My advice? Rebuild your MSI but avoid using the ODBC tables. In my experience, WPS has never been happy with them. Since ODBC entries end up in the registry anyway, import them into the Registry table instead.
My advice? Rebuild your MSI but avoid using the ODBC tables. In my experience, WPS has never been happy with them. Since ODBC entries end up in the registry anyway, import them into the Registry table instead.
Posted by:
morfeo
13 years ago
Thanks for the reply.
I actually solved in a bit of a slacker way. I used Setup Editor - Components and deleted the other ODBCDataSource entrys that I've generated throughout the frequent changing of the source content of ODBC.
And when I run the .msi it works... or at least I don't get the error message.
Though I will have to agree with You in using Registry table the next time.
I actually solved in a bit of a slacker way. I used Setup Editor - Components and deleted the other ODBCDataSource entrys that I've generated throughout the frequent changing of the source content of ODBC.
And when I run the .msi it works... or at least I don't get the error message.
Though I will have to agree with You in using Registry table the next time.
Posted by:
anonymous_9363
13 years ago
That's not a slacker's method at all but absolutely spot-on, in that you've removed the erroneous components which were causing the error.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.