Error 1919 Odbc Error 11
Contents |
hi folks, i have captured an app that has datasources, nothing seems wrong with them but when i install them i get this error:- "error 1919. error error 1919 odbc data source configuring data source: cpblims, odbc error 11: driver's configDSN, COnfig driver, or config
Error 1919 Error Configuring Odbc
translator failed. verify that the file cpblims exists and that you can access it" i read a couple of error 1919 error configuring odbc data source visual foxpro database posts saying install mdac, this is allready on the build so i have began to worry. the registry entries for odbc.ini are present also. i have pasted the attributes and table entry
Error 1919 Office 2003 Windows 10
below, any help is much appreciated on this on:- odbcDataSource table entry:- "cpblims","ODBCDataSource","cpblims","Microsoft ODBC for Oracle","0" attributes:- Description=cpblims Attributes=W ServerName=rvlpcpb.world Translation Option=0 Application Attributes=T PrefetchCount=10 Lobs=T ResultSets=T Longs=F DisableMTS=F Failover=T QueryTimeout=T CloseCursor=F FailoverRetryCount=10 FailoverDelay=10 DSN=cpblims UID=cpblims SERVER=rvlpcpb.world BufferSize=65535 SynonymColumns=1 Remarks=0 StdDayOfWeek=1 GuessTheColDef=0 StripTrailingZero=0 UserID= Translation DLL= PWD= 0 Comments [ + ] Show Comments Comments Please log in to comment Rating comments in this error 1919 windows 7 legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable. Answers 0 Whenever I get a 1919 error I delete the odbc entries from the odbc tab in Wise. Then export the odbc info from HKLM\sotware\odbc on a clean install of the program. Now import that .reg into the registry section of Wise. This is fixed 1919's for me everytime from what I remember. Also, Oracle has been installed already right? Answered 12/16/2005 by: schieb Please log in to comment Please log in to comment 1 Setting up the ODBC connection via the reg table (instead of the odbcdatasource table) as schieb suggests is a good solution as it means that the MSI doesn't worry about 3rd party ODBC drivers (such as Oracle) acutally being installed first. You will obviously need Oracle drivers ultimately installed for the app to work but it doesn't matter about installation order - which is probably what's causing the error message. There are no drawbacks to this method that I know of... Regards, Rob. Answered 12/17/2005 by: MSIPackager Please log in to comment Please log in to comment 0 thanks guys,
by an error while installing the package release on a clean machine. The application is Dreamweaver Ultradev 4, the release was successfully
Error 1919 Windows 10
build with no warnings or error. At the end of the installation
Visual Foxpro Database Odbc Error 6 Windows 8
process, the following message occurs : Error 1919. Error configuring ODBC Data source "...", ODBC error 11 : Driver's error 1919 error configuring odbc data source windows 10 ConfigDSN, ConfigDriver or ConfigTranslator failed. Verify that the file "..." exists (It does) and that .... (the message ends here) I could not find any solution to this, if anyone have http://www.itninja.com/question/odbc-error-1919 an idea... TsungH08-22-2002, 11:43 AMThere isn't enough information on the problem you encountered. It will not be an easy task to troubleshoot without having the installation source, and seeing the error. One simple way is to set up ODBC using registry. You will be able to find the required registry entries under HKLM\Software\ODBC. erwann08-23-2002, 03:44 AMThanks for advice, i'll try this... By https://community.flexerasoftware.com/archive/index.php?t-101151.html the way, I have a warning message : ** Warning: -3114: Application path ;%CommonFilesFolder%\Macromedia does not contain destination of associated component RegistryData_Machine But I can't find a way to access this path Maybe this is linked as the RegistryData_Machine component contains registry information about ODBC ressources... If you have any Idea, please let me know DarshanSingh08-23-2002, 10:33 AMI personally have not seen this error. Searching on the Web only thing I can see is if the Asycfilt.dll is missing then you might get this error, and that this error is in some way related to Microsoft Office. See following Microsoft KB articles: http://support.microsoft.com/default.aspx?scid=KB;EN-US;Q299066 (http://support.microsoft.com/default.aspx?scid=KB;EN-US;Q299066&) http://support.microsoft.com/default.aspx?scid=KB;EN-US;Q295345 http://support.microsoft.com/default.aspx?scid=KB;EN-US;Q299611 In addition, is it possible to try a different ODBC driver? Which one are you using right now? Best Wishes, Darshan Singh TsungH08-23-2002, 03:37 PMIt looks like something related to App Path in Advanced Settings in component RegistryData_Machine. You might need to set %CommonFilesFolder%\Macromedia to the destination of the component. For additional information, please refer to AdminStudio Help, look under "Troubleshooting Build Errors and Warnings" page. Or you can do a search on 3114, it will lead y