OGR 3.3 Provider runtime error
|
|
Jackie Ng-2
|
Hi List,
I have an application that interrogates a provider's connection properties, but when I want to get the connection properties of the OGR provider. I get the following error: Microsoft Visual C++ Runtime Library Runtime Error! Program: [path to executable] R6034 An Application has made an attempt to load the C runtime library incorrectly. Please contact the application's support team for more information. If I run this through the vs debugger, I get an unhandled OSGeo.FDO.Common.Exception with the following message. "Unable to load the FDO Provider: A dynamic link library (DLL) initialization routine failed." Running OGRProvider.dll through depends.exe, I found that it was has a missing dependency dwmapi.dll, which after some googling turns out to be a Windows Vista dll (???). So I downloaded the file anyway, and put it into the working directory, but I still get the same error messages. I am using FDO 3.3.0 RC1 (binaries, not built from source) on Windows XP. I am using the managed dlls. Any ideas? - Jackie |
||||||||||||||||
Traian Stanev
|
DWMAPI.dll is a common false positive that depends throws. That's not your actual problem. In depends, look in one of the right panes (the one in the middle, not the top right), where it lists all the dependent DLL functions that are needed by the provider. See if any of them are listed in red. Traian ________________________________________ From: [hidden email] [[hidden email]] On Behalf Of Jackie Ng [[hidden email]] Sent: Monday, January 21, 2008 11:49 PM To: [hidden email] Subject: [fdo-users] OGR 3.3 Provider runtime error Hi List, I have an application that interrogates a provider's connection properties, but when I want to get the connection properties of the OGR provider. I get the following error: Microsoft Visual C++ Runtime Library Runtime Error! Program: [path to executable] R6034 An Application has made an attempt to load the C runtime library incorrectly. Please contact the application's support team for more information. If I run this through the vs debugger, I get an unhandled OSGeo.FDO.Common.Exception with the following message. "Unable to load the FDO Provider: A dynamic link library (DLL) initialization routine failed." Running OGRProvider.dll through depends.exe, I found that it was has a missing dependency dwmapi.dll, which after some googling turns out to be a Windows Vista dll (???). So I downloaded the file anyway, and put it into the working directory, but I still get the same error messages. I am using FDO 3.3.0 RC1 (binaries, not built from source) on Windows XP. I am using the managed dlls. Any ideas? - Jackie -- View this message in context: http://www.nabble.com/OGR-3.3-Provider-runtime-error-tp15012644s18162p15012644.html Sent from the fdo-users mailing list archive at Nabble.com. _______________________________________________ fdo-users mailing list [hidden email] http://lists.osgeo.org/mailman/listinfo/fdo-users _______________________________________________ fdo-users mailing list [hidden email] http://lists.osgeo.org/mailman/listinfo/fdo-users |
||||||||||||||||
|
Jackie Ng-2
|
I've combed through the list of functions (OGRProvider.dll and directly related dlls) and couldn't find any red ones. However the log window did say there was at least one unresolved export function in one of the delay-load dependent modules, but it doesn't say which one??
- Jackie
|
Jack Lee-2
|
Hi,
FDO 3.3.0 RC1 was built with Visual Studio 2005 SP1. Do you have Visual Studio 2005 SP1 or Visual Studio 2005 SP1 runtime installed? -----Original Message----- From: [hidden email] [mailto:[hidden email]] On Behalf Of Jackie Ng Sent: Tuesday, January 22, 2008 3:03 AM To: [hidden email] Subject: RE: [fdo-users] OGR 3.3 Provider runtime error I've combed through the list of functions (OGRProvider.dll and directly related dlls) and couldn't find any red ones. However the log window did say there was at least one unresolved export function in one of the delay-load dependent modules, but it doesn't say which one?? - Jackie Traian Stanev wrote: > > > DWMAPI.dll is a common false positive that depends throws. That's not your > actual problem. > In depends, look in one of the right panes (the one in the middle, not the > top right), where it lists all the dependent DLL functions that are needed > by the provider. See if any of them are listed in red. > > Traian > > > > ________________________________________ > From: [hidden email] > [[hidden email]] On Behalf Of Jackie Ng > [[hidden email]] > Sent: Monday, January 21, 2008 11:49 PM > To: [hidden email] > Subject: [fdo-users] OGR 3.3 Provider runtime error > > Hi List, > > I have an application that interrogates a provider's connection > properties, > but when I want to get the connection properties of the OGR provider. I > get > the following error: > > Microsoft Visual C++ Runtime Library > > Runtime Error! > Program: [path to executable] > R6034 > An Application has made an attempt to load the C runtime library > incorrectly. > Please contact the application's support team for more information. > > If I run this through the vs debugger, I get an unhandled > OSGeo.FDO.Common.Exception with the following message. > > "Unable to load the FDO Provider: A dynamic link library (DLL) > initialization routine failed." > > Running OGRProvider.dll through depends.exe, I found that it was has a > missing dependency dwmapi.dll, which after some googling turns out to be a > Windows Vista dll (???). So I downloaded the file anyway, and put it into > the working directory, but I still get the same error messages. > > I am using FDO 3.3.0 RC1 (binaries, not built from source) on Windows XP. > I am using the managed dlls. > > Any ideas? > > - Jackie > -- > View this message in context: > http://www.nabble.com/OGR-3.3-Provider-runtime-error-tp15012644s18162p15012644.html > Sent from the fdo-users mailing list archive at Nabble.com. > > _______________________________________________ > fdo-users mailing list > [hidden email] > http://lists.osgeo.org/mailman/listinfo/fdo-users > _______________________________________________ > fdo-users mailing list > [hidden email] > http://lists.osgeo.org/mailman/listinfo/fdo-users > > -- View this message in context: http://www.nabble.com/OGR-3.3-Provider-runtime-error-tp15012644s18162p15014222.html Sent from the fdo-users mailing list archive at Nabble.com. _______________________________________________ fdo-users mailing list [hidden email] http://lists.osgeo.org/mailman/listinfo/fdo-users _______________________________________________ fdo-users mailing list [hidden email] http://lists.osgeo.org/mailman/listinfo/fdo-users |
||||||||||||||||
|
Traian Stanev
|
In reply to this post
by Jackie Ng-2
So, you open depends for OGRProvider.dll, pick FDO.dll from the tree-view on the top left, and then look on the right side. It will show functions from FDO.dll that the OGRProvider calls. Most of them will have a green "C++" next to them. Are you saying none of them have a red C++ if you do this? Traian > -----Original Message----- > From: [hidden email] [mailto:fdo-users- > [hidden email]] On Behalf Of Jackie Ng > Sent: Tuesday, January 22, 2008 3:03 AM > To: [hidden email] > Subject: RE: [fdo-users] OGR 3.3 Provider runtime error > > > I've combed through the list of functions (OGRProvider.dll and directly > related dlls) and couldn't find any red ones. However the log window > did say > there was at least one unresolved export function in one of the delay- > load > dependent modules, but it doesn't say which one?? > > - Jackie > > > Traian Stanev wrote: > > > > > > DWMAPI.dll is a common false positive that depends throws. That's not > your > > actual problem. > > In depends, look in one of the right panes (the one in the middle, > not the > > top right), where it lists all the dependent DLL functions that are > needed > > by the provider. See if any of them are listed in red. > > > > Traian > > > > > > > > ________________________________________ > > From: [hidden email] > > [[hidden email]] On Behalf Of Jackie Ng > > [[hidden email]] > > Sent: Monday, January 21, 2008 11:49 PM > > To: [hidden email] > > Subject: [fdo-users] OGR 3.3 Provider runtime error > > > > Hi List, > > > > I have an application that interrogates a provider's connection > > properties, > > but when I want to get the connection properties of the OGR provider. > I > > get > > the following error: > > > > Microsoft Visual C++ Runtime Library > > > > Runtime Error! > > Program: [path to executable] > > R6034 > > An Application has made an attempt to load the C runtime library > > incorrectly. > > Please contact the application's support team for more information. > > > > If I run this through the vs debugger, I get an unhandled > > OSGeo.FDO.Common.Exception with the following message. > > > > "Unable to load the FDO Provider: A dynamic link library (DLL) > > initialization routine failed." > > > > Running OGRProvider.dll through depends.exe, I found that it was has > a > > missing dependency dwmapi.dll, which after some googling turns out to > be a > > Windows Vista dll (???). So I downloaded the file anyway, and put it > into > > the working directory, but I still get the same error messages. > > > > I am using FDO 3.3.0 RC1 (binaries, not built from source) on Windows > XP. > > I am using the managed dlls. > > > > Any ideas? > > > > - Jackie > > -- > > View this message in context: > > http://www.nabble.com/OGR-3.3-Provider-runtime-error- > tp15012644s18162p15012644.html > > Sent from the fdo-users mailing list archive at Nabble.com. > > > > _______________________________________________ > > fdo-users mailing list > > [hidden email] > > http://lists.osgeo.org/mailman/listinfo/fdo-users > > _______________________________________________ > > fdo-users mailing list > > [hidden email] > > http://lists.osgeo.org/mailman/listinfo/fdo-users > > > > > > -- > View this message in context: http://www.nabble.com/OGR-3.3-Provider- > runtime-error-tp15012644s18162p15014222.html > Sent from the fdo-users mailing list archive at Nabble.com. > > _______________________________________________ > fdo-users mailing list > [hidden email] > http://lists.osgeo.org/mailman/listinfo/fdo-users fdo-users mailing list [hidden email] http://lists.osgeo.org/mailman/listinfo/fdo-users |
||||||||||||||||
|
Jackie Ng-2
|
In reply to this post
by Jack Lee-2
Yes, I have both VS2005 SP1 and runtime installed.
- Jackie
|
||||||||||||||||
|
Jackie Ng-2
|
In reply to this post
by Traian Stanev
That is correct, there are no red C++ functions listed.
- Jackie
|
||||||||||||||||
|
Traian Stanev
|
Depends can export the dependency graph to a file. If you could export yours and send it over I can take a quick look. Since the file can be large, email it to me only. Traian -----Original Message----- From: [hidden email] [mailto:[hidden email]] On Behalf Of Jackie Ng Sent: Thursday, January 24, 2008 11:04 PM To: [hidden email] Subject: RE: [fdo-users] OGR 3.3 Provider runtime error That is correct, there are no red C++ functions listed. - Jackie Traian Stanev wrote: > > > So, you open depends for OGRProvider.dll, pick FDO.dll from the tree-view > on the top left, and then look on the right side. It will show functions > from FDO.dll that the OGRProvider calls. Most of them will have a green > "C++" next to them. Are you saying none of them have a red C++ if you do > this? > > Traian > > >> -----Original Message----- >> From: [hidden email] [mailto:fdo-users- >> [hidden email]] On Behalf Of Jackie Ng >> Sent: Tuesday, January 22, 2008 3:03 AM >> To: [hidden email] >> Subject: RE: [fdo-users] OGR 3.3 Provider runtime error >> >> >> I've combed through the list of functions (OGRProvider.dll and directly >> related dlls) and couldn't find any red ones. However the log window >> did say >> there was at least one unresolved export function in one of the delay- >> load >> dependent modules, but it doesn't say which one?? >> >> - Jackie >> >> >> Traian Stanev wrote: >> > >> > >> > DWMAPI.dll is a common false positive that depends throws. That's not >> your >> > actual problem. >> > In depends, look in one of the right panes (the one in the middle, >> not the >> > top right), where it lists all the dependent DLL functions that are >> needed >> > by the provider. See if any of them are listed in red. >> > >> > Traian >> > >> > >> > >> > ________________________________________ >> > From: [hidden email] >> > [[hidden email]] On Behalf Of Jackie Ng >> > [[hidden email]] >> > Sent: Monday, January 21, 2008 11:49 PM >> > To: [hidden email] >> > Subject: [fdo-users] OGR 3.3 Provider runtime error >> > >> > Hi List, >> > >> > I have an application that interrogates a provider's connection >> > properties, >> > but when I want to get the connection properties of the OGR provider. >> I >> > get >> > the following error: >> > >> > Microsoft Visual C++ Runtime Library >> > >> > Runtime Error! >> > Program: [path to executable] >> > R6034 >> > An Application has made an attempt to load the C runtime library >> > incorrectly. >> > Please contact the application's support team for more information. >> > >> > If I run this through the vs debugger, I get an unhandled >> > OSGeo.FDO.Common.Exception with the following message. >> > >> > "Unable to load the FDO Provider: A dynamic link library (DLL) >> > initialization routine failed." >> > >> > Running OGRProvider.dll through depends.exe, I found that it was has >> a >> > missing dependency dwmapi.dll, which after some googling turns out to >> be a >> > Windows Vista dll (???). So I downloaded the file anyway, and put it >> into >> > the working directory, but I still get the same error messages. >> > >> > I am using FDO 3.3.0 RC1 (binaries, not built from source) on Windows >> XP. >> > I am using the managed dlls. >> > >> > Any ideas? >> > >> > - Jackie >> > -- >> > View this message in context: >> > http://www.nabble.com/OGR-3.3-Provider-runtime-error- >> tp15012644s18162p15012644.html >> > Sent from the fdo-users mailing list archive at Nabble.com. >> > >> > _______________________________________________ >> > fdo-users mailing list >> > [hidden email] >> > http://lists.osgeo.org/mailman/listinfo/fdo-users >> > _______________________________________________ >> > fdo-users mailing list >> > [hidden email] >> > http://lists.osgeo.org/mailman/listinfo/fdo-users >> > >> > >> >> -- >> View this message in context: http://www.nabble.com/OGR-3.3-Provider- >> runtime-error-tp15012644s18162p15014222.html >> Sent from the fdo-users mailing list archive at Nabble.com. >> >> _______________________________________________ >> fdo-users mailing list >> [hidden email] >> http://lists.osgeo.org/mailman/listinfo/fdo-users > _______________________________________________ > fdo-users mailing list > [hidden email] > http://lists.osgeo.org/mailman/listinfo/fdo-users > > -- View this message in context: http://www.nabble.com/OGR-3.3-Provider-runtime-error-tp15012644s18162p15080594.html Sent from the fdo-users mailing list archive at Nabble.com. _______________________________________________ fdo-users mailing list [hidden email] http://lists.osgeo.org/mailman/listinfo/fdo-users _______________________________________________ fdo-users mailing list [hidden email] http://lists.osgeo.org/mailman/listinfo/fdo-users |
||||||||||||||||
|
Traian Stanev
|
The depends dump looks good, however I just thought of what may be causing this. Some time ago Kenneth posted about a similar problem. I remember him mentioning that it was due to a manifest being embedded in the OGRProvider dll at build time. Removing the embedded manifest fixed the problem for him. We need to check the OGRProvider vcproj file for that problem and fix it if the manifest is turned on. Traian -----Original Message----- From: [hidden email] [mailto:[hidden email]] On Behalf Of Traian Stanev Sent: Thursday, January 24, 2008 11:07 PM To: [hidden email] Subject: RE: [fdo-users] OGR 3.3 Provider runtime error Depends can export the dependency graph to a file. If you could export yours and send it over I can take a quick look. Since the file can be large, email it to me only. Traian -----Original Message----- From: [hidden email] [mailto:[hidden email]] On Behalf Of Jackie Ng Sent: Thursday, January 24, 2008 11:04 PM To: [hidden email] Subject: RE: [fdo-users] OGR 3.3 Provider runtime error That is correct, there are no red C++ functions listed. - Jackie Traian Stanev wrote: > > > So, you open depends for OGRProvider.dll, pick FDO.dll from the tree-view > on the top left, and then look on the right side. It will show functions > from FDO.dll that the OGRProvider calls. Most of them will have a green > "C++" next to them. Are you saying none of them have a red C++ if you do > this? > > Traian > > >> -----Original Message----- >> From: [hidden email] [mailto:fdo-users- >> [hidden email]] On Behalf Of Jackie Ng >> Sent: Tuesday, January 22, 2008 3:03 AM >> To: [hidden email] >> Subject: RE: [fdo-users] OGR 3.3 Provider runtime error >> >> >> I've combed through the list of functions (OGRProvider.dll and directly >> related dlls) and couldn't find any red ones. However the log window >> did say >> there was at least one unresolved export function in one of the delay- >> load >> dependent modules, but it doesn't say which one?? >> >> - Jackie >> >> >> Traian Stanev wrote: >> > >> > >> > DWMAPI.dll is a common false positive that depends throws. That's not >> your >> > actual problem. >> > In depends, look in one of the right panes (the one in the middle, >> not the >> > top right), where it lists all the dependent DLL functions that are >> needed >> > by the provider. See if any of them are listed in red. >> > >> > Traian >> > >> > >> > >> > ________________________________________ >> > From: [hidden email] >> > [[hidden email]] On Behalf Of Jackie Ng >> > [[hidden email]] >> > Sent: Monday, January 21, 2008 11:49 PM >> > To: [hidden email] >> > Subject: [fdo-users] OGR 3.3 Provider runtime error >> > >> > Hi List, >> > >> > I have an application that interrogates a provider's connection >> > properties, >> > but when I want to get the connection properties of the OGR provider. >> I >> > get >> > the following error: >> > >> > Microsoft Visual C++ Runtime Library >> > >> > Runtime Error! >> > Program: [path to executable] >> > R6034 >> > An Application has made an attempt to load the C runtime library >> > incorrectly. >> > Please contact the application's support team for more information. >> > >> > If I run this through the vs debugger, I get an unhandled >> > OSGeo.FDO.Common.Exception with the following message. >> > >> > "Unable to load the FDO Provider: A dynamic link library (DLL) >> > initialization routine failed." >> > >> > Running OGRProvider.dll through depends.exe, I found that it was has >> a >> > missing dependency dwmapi.dll, which after some googling turns out to >> be a >> > Windows Vista dll (???). So I downloaded the file anyway, and put it >> into >> > the working directory, but I still get the same error messages. >> > >> > I am using FDO 3.3.0 RC1 (binaries, not built from source) on Windows >> XP. >> > I am using the managed dlls. >> > >> > Any ideas? >> > >> > - Jackie >> > -- >> > View this message in context: >> > http://www.nabble.com/OGR-3.3-Provider-runtime-error- >> tp15012644s18162p15012644.html >> > Sent from the fdo-users mailing list archive at Nabble.com. >> > >> > _______________________________________________ >> > fdo-users mailing list >> > [hidden email] >> > http://lists.osgeo.org/mailman/listinfo/fdo-users >> > _______________________________________________ >> > fdo-users mailing list >> > [hidden email] >> > http://lists.osgeo.org/mailman/listinfo/fdo-users >> > >> > >> >> -- >> View this message in context: http://www.nabble.com/OGR-3.3-Provider- >> runtime-error-tp15012644s18162p15014222.html >> Sent from the fdo-users mailing list archive at Nabble.com. >> >> _______________________________________________ >> fdo-users mailing list >> [hidden email] >> http://lists.osgeo.org/mailman/listinfo/fdo-users > _______________________________________________ > fdo-users mailing list > [hidden email] > http://lists.osgeo.org/mailman/listinfo/fdo-users > > -- View this message in context: http://www.nabble.com/OGR-3.3-Provider-runtime-error-tp15012644s18162p15080594.html Sent from the fdo-users mailing list archive at Nabble.com. _______________________________________________ fdo-users mailing list [hidden email] http://lists.osgeo.org/mailman/listinfo/fdo-users _______________________________________________ fdo-users mailing list [hidden email] http://lists.osgeo.org/mailman/listinfo/fdo-users _______________________________________________ fdo-users mailing list [hidden email] http://lists.osgeo.org/mailman/listinfo/fdo-users |
||||||||||||||||
|
Jackie Ng-2
|
I've built FDO and providers from source, and still get the error.
I've set manifest to off in the OGRProvider vcproj file, rebuilt everything from source, still no good. I rewrote the C# test code in native C++, still the same error. I'm out of ideas :( - Jackie
|
||||||||||||||||
|
Traian Stanev
|
Were you doing a Debug or Release build?
________________________________________ From: [hidden email] [[hidden email]] On Behalf Of Jackie Ng [[hidden email]] Sent: Wednesday, January 30, 2008 7:20 PM To: [hidden email] Subject: RE: [fdo-users] OGR 3.3 Provider runtime error I've built FDO and providers from source, and still get the error. I've set manifest to off in the OGRProvider vcproj file, rebuilt everything from source, still no good. I rewrote the C# test code in native C++, still the same error. I'm out of ideas :( - Jackie Traian Stanev wrote: > > > The depends dump looks good, however I just thought of what may be causing > this. Some time ago Kenneth posted about a similar problem. I remember him > mentioning that it was due to a manifest being embedded in the OGRProvider > dll at build time. Removing the embedded manifest fixed the problem for > him. We need to check the OGRProvider vcproj file for that problem and fix > it if the manifest is turned on. > > > Traian > > -----Original Message----- > From: [hidden email] > [mailto:[hidden email]] On Behalf Of Traian Stanev > Sent: Thursday, January 24, 2008 11:07 PM > To: [hidden email] > Subject: RE: [fdo-users] OGR 3.3 Provider runtime error > > > Depends can export the dependency graph to a file. If you could export > yours and send it over I can take a quick look. Since the file can be > large, email it to me only. > > Traian > > > -----Original Message----- > From: [hidden email] > [mailto:[hidden email]] On Behalf Of Jackie Ng > Sent: Thursday, January 24, 2008 11:04 PM > To: [hidden email] > Subject: RE: [fdo-users] OGR 3.3 Provider runtime error > > > That is correct, there are no red C++ functions listed. > > - Jackie > > > Traian Stanev wrote: >> >> >> So, you open depends for OGRProvider.dll, pick FDO.dll from the tree-view >> on the top left, and then look on the right side. It will show functions >> from FDO.dll that the OGRProvider calls. Most of them will have a green >> "C++" next to them. Are you saying none of them have a red C++ if you do >> this? >> >> Traian >> >> >>> -----Original Message----- >>> From: [hidden email] [mailto:fdo-users- >>> [hidden email]] On Behalf Of Jackie Ng >>> Sent: Tuesday, January 22, 2008 3:03 AM >>> To: [hidden email] >>> Subject: RE: [fdo-users] OGR 3.3 Provider runtime error >>> >>> >>> I've combed through the list of functions (OGRProvider.dll and directly >>> related dlls) and couldn't find any red ones. However the log window >>> did say >>> there was at least one unresolved export function in one of the delay- >>> load >>> dependent modules, but it doesn't say which one?? >>> >>> - Jackie >>> >>> >>> Traian Stanev wrote: >>> > >>> > >>> > DWMAPI.dll is a common false positive that depends throws. That's not >>> your >>> > actual problem. >>> > In depends, look in one of the right panes (the one in the middle, >>> not the >>> > top right), where it lists all the dependent DLL functions that are >>> needed >>> > by the provider. See if any of them are listed in red. >>> > >>> > Traian >>> > >>> > >>> > >>> > ________________________________________ >>> > From: [hidden email] >>> > [[hidden email]] On Behalf Of Jackie Ng >>> > [[hidden email]] >>> > Sent: Monday, January 21, 2008 11:49 PM >>> > To: [hidden email] >>> > Subject: [fdo-users] OGR 3.3 Provider runtime error >>> > >>> > Hi List, >>> > >>> > I have an application that interrogates a provider's connection >>> > properties, >>> > but when I want to get the connection properties of the OGR provider. >>> I >>> > get >>> > the following error: >>> > >>> > Microsoft Visual C++ Runtime Library >>> > >>> > Runtime Error! >>> > Program: [path to executable] >>> > R6034 >>> > An Application has made an attempt to load the C runtime library >>> > incorrectly. >>> > Please contact the application's support team for more information. >>> > >>> > If I run this through the vs debugger, I get an unhandled >>> > OSGeo.FDO.Common.Exception with the following message. >>> > >>> > "Unable to load the FDO Provider: A dynamic link library (DLL) >>> > initialization routine failed." >>> > >>> > Running OGRProvider.dll through depends.exe, I found that it was has >>> a >>> > missing dependency dwmapi.dll, which after some googling turns out to >>> be a >>> > Windows Vista dll (???). So I downloaded the file anyway, and put it >>> into >>> > the working directory, but I still get the same error messages. >>> > >>> > I am using FDO 3.3.0 RC1 (binaries, not built from source) on Windows >>> XP. >>> > I am using the managed dlls. >>> > >>> > Any ideas? >>> > >>> > - Jackie >>> > -- >>> > View this message in context: >>> > http://www.nabble.com/OGR-3.3-Provider-runtime-error- >>> tp15012644s18162p15012644.html >>> > Sent from the fdo-users mailing list archive at Nabble.com. >>> > >>> > _______________________________________________ >>> > fdo-users mailing list >>> > [hidden email] >>> > http://lists.osgeo.org/mailman/listinfo/fdo-users >>> > _______________________________________________ >>> > fdo-users mailing list >>> > [hidden email] >>> > http://lists.osgeo.org/mailman/listinfo/fdo-users >>> > >>> > >>> >>> -- >>> View this message in context: http://www.nabble.com/OGR-3.3-Provider- >>> runtime-error-tp15012644s18162p15014222.html >>> Sent from the fdo-users mailing list archive at Nabble.com. >>> >>> _______________________________________________ >>> fdo-users mailing list >>> [hidden email] >>> http://lists.osgeo.org/mailman/listinfo/fdo-users >> _______________________________________________ >> fdo-users mailing list >> [hidden email] >> http://lists.osgeo.org/mailman/listinfo/fdo-users >> >> > > -- > View this message in context: > http://www.nabble.com/OGR-3.3-Provider-runtime-error-tp15012644s18162p15080594.html > Sent from the fdo-users mailing list archive at Nabble.com. > > _______________________________________________ > fdo-users mailing list > [hidden email] > http://lists.osgeo.org/mailman/listinfo/fdo-users > _______________________________________________ > fdo-users mailing list > [hidden email] > http://lists.osgeo.org/mailman/listinfo/fdo-users > _______________________________________________ > fdo-users mailing list > [hidden email] > http://lists.osgeo.org/mailman/listinfo/fdo-users > > -- View this message in context: http://www.nabble.com/OGR-3.3-Provider-runtime-error-tp15012644s18162p15195091.html Sent from the fdo-users mailing list archive at Nabble.com. _______________________________________________ fdo-users mailing list [hidden email] http://lists.osgeo.org/mailman/listinfo/fdo-users _______________________________________________ fdo-users mailing list [hidden email] http://lists.osgeo.org/mailman/listinfo/fdo-users |
||||||||||||||||
|
Jackie Ng-2
|
It was a release build.
- Jackie
|
||||||||||||||||
|
Jackie Ng-2
|
I ran this code on a fresh windows xp virtual machine (installed the SP1 runtime beforehand) and it complains about not being able to find msvcp80.dll (!?)
So next thing I did was copy the runtime dlls directly into the executable directory. Now I get the same R6034 error. Ok, I've aggressively pursued all lines of inquiry regarding the R6034 error, and as a result, I've tried building the OGR provider from source with a statically linked runtime library (/MT), and now I can get the connection properties of the provider, but now I get a different error (R6025 - pure virtual function call) Nevertheless, I now inclined to believe that it is nothing to do with FDO but rather to do with the VC++ 2005 runtime library. Why could it not detect the runtime dlls? - Jackie
|
||||||||||||||||
|
Jackie Ng-2
|
In reply to this post
by Traian Stanev
I solved the problem, but it was the other way round.
The release configuration for the OGRProvider vcproj *did not* have manifest generation and embedding enabled. I turned these options on, rebuilt the project and now I no longer get the runtime errors. I don't work with VC++ that much, so I dunno if this qualifies as an actual "fix", but there you have it. - Jackie
|
||||||||||||||||
|
Traian Stanev
|
That is just bizarre. Shows you how much I understand that manifest thing though. Yes, that's probably the right fix. Traian > -----Original Message----- > From: [hidden email] [mailto:fdo-users- > [hidden email]] On Behalf Of Jackie Ng > Sent: Tuesday, February 05, 2008 2:00 PM > To: [hidden email] > Subject: RE: [fdo-users] OGR 3.3 Provider runtime error [SOLVED] > > > I solved the problem, but it was the other way round. > > The release configuration for the OGRProvider vcproj *did not* have > manifest > generation and embedding enabled. I turned these options on, rebuilt > the > project and now I no longer get the runtime errors. > > I don't work with VC++ that much, so I dunno if this qualifies as an > actual > "fix", but there you have it. > > - Jackie > > > Traian Stanev wrote: > > > > > > The depends dump looks good, however I just thought of what may be > causing > > this. Some time ago Kenneth posted about a similar problem. I > remember him > > mentioning that it was due to a manifest being embedded in the > OGRProvider > > dll at build time. Removing the embedded manifest fixed the problem > for > > him. We need to check the OGRProvider vcproj file for that problem > and fix > > it if the manifest is turned on. > > > > > > Traian > > > > -----Original Message----- > > From: [hidden email] > > [mailto:[hidden email]] On Behalf Of Traian Stanev > > Sent: Thursday, January 24, 2008 11:07 PM > > To: [hidden email] > > Subject: RE: [fdo-users] OGR 3.3 Provider runtime error > > > > > > Depends can export the dependency graph to a file. If you could > export > > yours and send it over I can take a quick look. Since the file can be > > large, email it to me only. > > > > Traian > > > > > > -----Original Message----- > > From: [hidden email] > > [mailto:[hidden email]] On Behalf Of Jackie Ng > > Sent: Thursday, January 24, 2008 11:04 PM > > To: [hidden email] > > Subject: RE: [fdo-users] OGR 3.3 Provider runtime error > > > > > > That is correct, there are no red C++ functions listed. > > > > - Jackie > > > > > > Traian Stanev wrote: > >> > >> > >> So, you open depends for OGRProvider.dll, pick FDO.dll from the > tree-view > >> on the top left, and then look on the right side. It will show > functions > >> from FDO.dll that the OGRProvider calls. Most of them will have a > green > >> "C++" next to them. Are you saying none of them have a red C++ if > you do > >> this? > >> > >> Traian > >> > >> > >>> -----Original Message----- > >>> From: [hidden email] [mailto:fdo-users- > >>> [hidden email]] On Behalf Of Jackie Ng > >>> Sent: Tuesday, January 22, 2008 3:03 AM > >>> To: [hidden email] > >>> Subject: RE: [fdo-users] OGR 3.3 Provider runtime error > >>> > >>> > >>> I've combed through the list of functions (OGRProvider.dll and > directly > >>> related dlls) and couldn't find any red ones. However the log > window > >>> did say > >>> there was at least one unresolved export function in one of the > delay- > >>> load > >>> dependent modules, but it doesn't say which one?? > >>> > >>> - Jackie > >>> > >>> > >>> Traian Stanev wrote: > >>> > > >>> > > >>> > DWMAPI.dll is a common false positive that depends throws. That's > not > >>> your > >>> > actual problem. > >>> > In depends, look in one of the right panes (the one in the > middle, > >>> not the > >>> > top right), where it lists all the dependent DLL functions that > are > >>> needed > >>> > by the provider. See if any of them are listed in red. > >>> > > >>> > Traian > >>> > > >>> > > >>> > > >>> > ________________________________________ > >>> > From: [hidden email] > >>> > [[hidden email]] On Behalf Of Jackie Ng > >>> > [[hidden email]] > >>> > Sent: Monday, January 21, 2008 11:49 PM > >>> > To: [hidden email] > >>> > Subject: [fdo-users] OGR 3.3 Provider runtime error > >>> > > >>> > Hi List, > >>> > > >>> > I have an application that interrogates a provider's connection > >>> > properties, > >>> > but when I want to get the connection properties of the OGR > provider. > >>> I > >>> > get > >>> > the following error: > >>> > > >>> > Microsoft Visual C++ Runtime Library > >>> > > >>> > Runtime Error! > >>> > Program: [path to executable] > >>> > R6034 > >>> > An Application has made an attempt to load the C runtime library > >>> > incorrectly. > >>> > Please contact the application's support team for more > information. > >>> > > >>> > If I run this through the vs debugger, I get an unhandled > >>> > OSGeo.FDO.Common.Exception with the following message. > >>> > > >>> > "Unable to load the FDO Provider: A dynamic link library (DLL) > >>> > initialization routine failed." > >>> > > >>> > Running OGRProvider.dll through depends.exe, I found that it was > has > >>> a > >>> > missing dependency dwmapi.dll, which after some googling turns > out to > >>> be a > >>> > Windows Vista dll (???). So I downloaded the file anyway, and put > it > >>> into > >>> > the working directory, but I still get the same error messages. > >>> > > >>> > I am using FDO 3.3.0 RC1 (binaries, not built from source) on > Windows > >>> XP. > >>> > I am using the managed dlls. > >>> > > >>> > Any ideas? > >>> > > >>> > - Jackie > >>> > -- > >>> > View this message in context: > >>> > http://www.nabble.com/OGR-3.3-Provider-runtime-error- > >>> tp15012644s18162p15012644.html > >>> > Sent from the fdo-users mailing list archive at Nabble.com. > >>> > > >>> > _______________________________________________ > >>> > fdo-users mailing list > >>> > [hidden email] > >>> > http://lists.osgeo.org/mailman/listinfo/fdo-users > >>> > _______________________________________________ > >>> > fdo-users mailing list > >>> > [hidden email] > >>> > http://lists.osgeo.org/mailman/listinfo/fdo-users > >>> > > >>> > > >>> > >>> -- > >>> View this message in context: http://www.nabble.com/OGR-3.3- > Provider- > >>> runtime-error-tp15012644s18162p15014222.html > >>> Sent from the fdo-users mailing list archive at Nabble.com. > >>> > >>> _______________________________________________ > >>> fdo-users mailing list > >>> [hidden email] > >>> http://lists.osgeo.org/mailman/listinfo/fdo-users > >> _______________________________________________ > >> fdo-users mailing list > >> [hidden email] > >> http://lists.osgeo.org/mailman/listinfo/fdo-users > >> > >> > > > > -- > > View this message in context: > > http://www.nabble.com/OGR-3.3-Provider-runtime-error- > tp15012644s18162p15080594.html > > Sent from the fdo-users mailing list archive at Nabble.com. > > > > _______________________________________________ > > fdo-users mailing list > > [hidden email] > > http://lists.osgeo.org/mailman/listinfo/fdo-users > > _______________________________________________ > > fdo-users mailing list > > [hidden email] > > http://lists.osgeo.org/mailman/listinfo/fdo-users > > _______________________________________________ > > fdo-users mailing list > > [hidden email] > > http://lists.osgeo.org/mailman/listinfo/fdo-users > > > > > > -- > View this message in context: http://www.nabble.com/OGR-3.3-Provider- > runtime-error-tp15012644s18162p15296982.html > Sent from the fdo-users mailing list archive at Nabble.com. > > _______________________________________________ > fdo-users mailing list > [hidden email] > http://lists.osgeo.org/mailman/listinfo/fdo-users fdo-users mailing list [hidden email] http://lists.osgeo.org/mailman/listinfo/fdo-users |
||||||||||||||||
surrounded
|
I'm reading through your post and seems similar to my problems.
Trying to use FDO on web server. It works fine on my PC (Windows XP) both from VS 2008 web service I wrote and from localhost when I call the web service. When I copy the web service over to production server, I get a: System.IO module not found error. DependencyWalker states I'm missing DWMAPI.dll, but from posts I see this is a red herring. Is there anyway to solve this without the manifest thing you talk about. I'm clueless on how to resolve that? Thanks......
|
||||||||||||||||
Jackie Ng
|
Have you installed the Visual C++ runtime on your production machine?
- Jackie
|
||||||||||||||||
| Free Embeddable Forum Powered by Nabble | Help |
