Hi I have an application that extracts data from a .mpp file using C# and the OLEDB provider shipped with MSP 2003. On my pre-production server it works fine, but on the production server I get a COMException : Provider cannot be found. It may not be properly installed. Both servers have installed: - .NET Framework 2.0 SP1 - Microsoft Project Office 2003 SP3 (default installation) - MDAC 2.8 SP2 The only noticeable difference between the two servers is that the production server runs 64-bit Windows Server 2003 and the pre-prod runs 32-bit. The connectionstring I'm using is "Provider=Microsoft.Project.OLEDB;Project Name=somefile.mpp". I would really appreciate it if someone can help me with a possible solution. Regards Jan
HI, The pjoledb.htm file that comes with project suggests a connection string of: "Provider=Microsoft.Project.OLEDB.11.0;PROJECT NAME=" & FILE_NAME Try adding the .11.0 Do be aware as well for the future that oledb is not supported by Project 2007 -- Rod Gill Microsoft MVP for Project Author of the only book on Project VBA, see: http://www.projectvbabook.com "Jan" wrote in message news:uW9P$LmDJHA.4724@TK2MSFTNGP05.phx.gbl... > Hi > > I have an application that extracts data from a .mpp file using C# and the > OLEDB provider shipped with MSP 2003. On my pre-production server it works > fine, but on the production server I get a COMException : Provider cannot > be found. It may not be properly installed. > > Both servers have installed: > - .NET Framework 2.0 SP1 > - Microsoft Project Office 2003 SP3 (default installation) > - MDAC 2.8 SP2 > > The only noticeable difference between the two servers is that the > production server runs 64-bit Windows Server 2003 and the pre-prod runs > 32-bit. > > The connectionstring I'm using is > "Provider=Microsoft.Project.OLEDB;Project Name=somefile.mpp". > > I would really appreciate it if someone can help me with a possible > solution. > > Regards > Jan
Hi Rod Thanks for the reply. I will try what you suggested. The reason for me using this connection sting is that it works for MSP 2000, 2002 and 2003. Also, for the moment we are happy to use MSP 2003 SP3 as it can access 2007 files as well. I guess we'll have to find some solution in future. Thanks Jan "Rod Gill" <rodATproject-systemsDOTcoDOTnz> wrote in message news:%23TIJS$mDJHA.4104@TK2MSFTNGP05.phx.gbl... > HI, > > The pjoledb.htm file that comes with project suggests a connection string > of: > > "Provider=Microsoft.Project.OLEDB.11.0;PROJECT NAME=" & FILE_NAME > > Try adding the .11.0 > > Do be aware as well for the future that oledb is not supported by Project > 2007 > > -- > > Rod Gill > Microsoft MVP for Project > > Author of the only book on Project VBA, see: > http://www.projectvbabook.com > > > > "Jan" wrote in message > news:uW9P$LmDJHA.4724@TK2MSFTNGP05.phx.gbl... >> Hi >> >> I have an application that extracts data from a .mpp file using C# and >> the OLEDB provider shipped with MSP 2003. On my pre-production server it >> works fine, but on the production server I get a COMException : Provider >> cannot be found. It may not be properly installed. >> >> Both servers have installed: >> - .NET Framework 2.0 SP1 >> - Microsoft Project Office 2003 SP3 (default installation) >> - MDAC 2.8 SP2 >> >> The only noticeable difference between the two servers is that the >> production server runs 64-bit Windows Server 2003 and the pre-prod runs >> 32-bit. >> >> The connectionstring I'm using is >> "Provider=Microsoft.Project.OLEDB;Project Name=somefile.mpp". >> >> I would really appreciate it if someone can help me with a possible >> solution. >> >> Regards >> Jan >
Hi Rod I tried the change to the connection string but no luck. Still get the same "Provider cannot be found" exception. I browsed the web for hours, and found more people battling with other OLEDB providers on 64-bit platforms. Could this be it? Do you have any experience on this? Thanks Jan "Rod Gill" <rodATproject-systemsDOTcoDOTnz> wrote in message news:%23TIJS$mDJHA.4104@TK2MSFTNGP05.phx.gbl... > HI, > > The pjoledb.htm file that comes with project suggests a connection string > of: > > "Provider=Microsoft.Project.OLEDB.11.0;PROJECT NAME=" & FILE_NAME > > Try adding the .11.0 > > Do be aware as well for the future that oledb is not supported by Project > 2007 > > -- > > Rod Gill > Microsoft MVP for Project > > Author of the only book on Project VBA, see: > http://www.projectvbabook.com > > > > "Jan" wrote in message > news:uW9P$LmDJHA.4724@TK2MSFTNGP05.phx.gbl... >> Hi >> >> I have an application that extracts data from a .mpp file using C# and >> the OLEDB provider shipped with MSP 2003. On my pre-production server it >> works fine, but on the production server I get a COMException : Provider >> cannot be found. It may not be properly installed. >> >> Both servers have installed: >> - .NET Framework 2.0 SP1 >> - Microsoft Project Office 2003 SP3 (default installation) >> - MDAC 2.8 SP2 >> >> The only noticeable difference between the two servers is that the >> production server runs 64-bit Windows Server 2003 and the pre-prod runs >> 32-bit. >> >> The connectionstring I'm using is >> "Provider=Microsoft.Project.OLEDB;Project Name=somefile.mpp". >> >> I would really appreciate it if someone can help me with a possible >> solution. >> >> Regards >> Jan >
Hi, I've just checked and OLEDB is working for me in Excel VBA reading data from a .mpp using Vista Business which is 64 bit. Can you run the macro from a Workstation instead? Other than that information I can't help you I'm afraid. -- Rod Gill Microsoft MVP for Project Author of the only book on Project VBA, see: http://www.projectvbabook.com "Jan" wrote in message news:138C44E4-C55D-46F1-AD96-64A8F883AE6F@microsoft.com... > Hi Rod > > I tried the change to the connection string but no luck. Still get the > same "Provider cannot be found" exception. > > I browsed the web for hours, and found more people battling with other > OLEDB providers on 64-bit platforms. Could this be it? Do you have any > experience on this? > > Thanks > Jan > > "Rod Gill" <rodATproject-systemsDOTcoDOTnz> wrote in message > news:%23TIJS$mDJHA.4104@TK2MSFTNGP05.phx.gbl... >> HI, >> >> The pjoledb.htm file that comes with project suggests a connection string >> of: >> >> "Provider=Microsoft.Project.OLEDB.11.0;PROJECT NAME=" & FILE_NAME >> >> Try adding the .11.0 >> >> Do be aware as well for the future that oledb is not supported by Project >> 2007 >> >> -- >> >> Rod Gill >> Microsoft MVP for Project >> >> Author of the only book on Project VBA, see: >> http://www.projectvbabook.com >> >> >> >> "Jan" wrote in message >> news:uW9P$LmDJHA.4724@TK2MSFTNGP05.phx.gbl... >>> Hi >>> >>> I have an application that extracts data from a .mpp file using C# and >>> the OLEDB provider shipped with MSP 2003. On my pre-production server it >>> works fine, but on the production server I get a COMException : Provider >>> cannot be found. It may not be properly installed. >>> >>> Both servers have installed: >>> - .NET Framework 2.0 SP1 >>> - Microsoft Project Office 2003 SP3 (default installation) >>> - MDAC 2.8 SP2 >>> >>> The only noticeable difference between the two servers is that the >>> production server runs 64-bit Windows Server 2003 and the pre-prod runs >>> 32-bit. >>> >>> The connectionstring I'm using is >>> "Provider=Microsoft.Project.OLEDB;Project Name=somefile.mpp". >>> >>> I would really appreciate it if someone can help me with a possible >>> solution. >>> >>> Regards >>> Jan >> >
