Add connection wizard fails with Access database
-
Monday, November 14, 2005 7:40 AMI have the RTM version installed. I am quite puzzled at this wizard. It works fine with SqlClient. But for Access databases, this wizard completely fails.
In this wizard, I only have one option to do - setting the ConnectionString. I set it to Provider=Microsoft.Jet.OLEDB.4.0;Data Source=D:\path\abc.mdb, which works fine in my code. But when I click OK, it complains:
---------------------------
Microsoft Visual Studio
---------------------------
Format of the initialization string does not conform to specification starting at index 0.
---------------------------
OK
---------------------------
And more, the Advanced button is disabled and the dialog does have the same funtionalities as described in MSDN ms-help://MS.VSCC.v80/MS.MSDN.v80/MS.VisualStudio.v80.en/dv_vdt01/html/a7df4f53-2a58-4e03-8326-cb578e61f1a7.htm.
Bug?
Answers
-
Wednesday, May 03, 2006 5:39 PM
Hi Pete,
I tried using WinTools.net to clean the registry and I can reproduce the problem, but it is because the same registry key I already pointed out was being removed. Just to be sure you tried out the right thing, let me be more explicit about the steps in examining and modifying the registry.
To examine the registry:
1) Run regedit.exe;
2) Browse to the location "HKEY_CLASSES_ROOT\CLSID\{F9AE8980-7E52-11d0-8964-00C04FD611D7}" in the tree;
3) If there is a child node in the tree called "ProgID", then you are indeed experiencing a different problem - let me know if this is the case.Otherwise, follow these steps to modify the registry:
1) Right click the node and select "New > Key";
2) Enter "ProgID" as the name;
3) Go to the main window and double click "(Default)";
4) Enter the value "MSIDXS.1";Now if you run Visual Studio, it should be working.
Thanks,
Stephen
All Replies
-
Thursday, December 01, 2005 5:38 PMI got the same problem when trying to use access database connection. I am currently using VWD 2005 express edition for my website. The connection string in web.config is as follow:
<
connectionStrings><
add name="AccessFileName" connectionString="~/App_Data/ASPNetDB.mdb" providerName="System.Data.OleDb"/><
add name="facility" connectionString="~/App_Data/facility.mdb;" providerName="System.Data.OleDb" /></
connectionStrings>
when running the application, give me the message
"Format of the initialization string does not conform to specification starting at index 0."
I looked online. This is supposed to be a bug in .NET 1.1 for Microsoft SQL Server .NET Data Provider (SqlClient), was fixed. http://support.microsoft.com/?kbid=823679
Weird thing is the first connection which takes care of the membership and roles works ok, only the second connection to "facility" returns the error. -
Tuesday, January 03, 2006 7:22 AM
I'm experiencing the same problem.
lynch12,
You said the first database worked in VB? I'm not sure if it makes a difference, but you have a semicolon at the end of your connectionString inside the quotes.
- Proposed As Answer by CNiehus Saturday, October 18, 2008 12:41 PM
-
Thursday, January 26, 2006 5:29 PMDid you ever figure this out? I've been having the same problem with this and other dispositions. I'm also using VWD Express. It works on one of my machines but not on the other. When I try to add an Access DB in the DB Explorer, I do not get the correct screen for the Access DB. Instead, I see a generic Add Connection box that displays a blank ConnectionString property. If I add anything (even gargage) to the CS property and click Test Connection, it returns with a Test Connection Succeeded which I know is bogus. I've tried completely uninstalling and reinstalling Office 2003 and VWD and checking MDAC and Jet installations. Nothing has worked. It's got to be something simple. I seem to be the only person in the world having this problem.
Thanks. -
Friday, January 27, 2006 5:57 PMModerator
Hi Neo,
It sounds like there is a problem with VS setup -- specifically registration of the data provider.
Can you try reinstalling VS?
Thanks.
Milind Lele
PM, VS Data -
Saturday, January 28, 2006 5:15 PMThanks Milind,
I've tried uninstalling and reinstalling. I'm suspect though that I didn't ever get a clean uninstall of beta versions even though I ended up using manual uninstalls and the beta uninstall tool (vs_uninst_betas.exe). I think I need more info on where to look for incorrect files and registry values etc.
Gerry -
Tuesday, January 31, 2006 3:00 AMModerator
Hi Gerry,
You suspision seems valid. The only thing I can think of is to get your reg hive for the data provider.
Can you send me the subtrees under:
HKLM\Software\Microsoft\VisualStudio\8.0\DataProviders and
HKLM\Software\Microsoft\VisualStudio\8.0\DataSourcesI hope that can give us some clue.
Thanks.
Milind
-
Tuesday, January 31, 2006 4:11 PMHi Milind,
There were no DataSource or DataProvider entries under VisualStudio, only under VWDExpress. These entries are below but they look the same as those on a working machine.
Thanks.
Gerry
DataSources:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VWDExpress\8.0\DataSources]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VWDExpress\8.0\DataSources\{067EA0D9-BA62-43f7-9106-34930C60C528}]
@="Microsoft SQL Server"
"DefaultProvider"="{91510608-8809-4020-8897-FBA057E22D54}"
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VWDExpress\8.0\DataSources\{067EA0D9-BA62-43f7-9106-34930C60C528}\SupportingProviders]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VWDExpress\8.0\DataSources\{067EA0D9-BA62-43f7-9106-34930C60C528}\SupportingProviders\{7F041D59-D76A-44ed-9AA2-FBF6B0548B80}]
"Description"="DataProvider_OleDB_SqlDataSource_Description, SR, Microsoft.Data.ConnectionUI.Dialog, Version=8.0.0.0, Culture=Neutral, PublicKeyToken=b03f5f7f11d50a3a"
"SpecializedProvider"="SQLOLEDB.1"
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VWDExpress\8.0\DataSources\{067EA0D9-BA62-43f7-9106-34930C60C528}\SupportingProviders\{91510608-8809-4020-8897-FBA057E22D54}]
"DisplayName"="DataSource_MicrosoftSqlServer, SR, Microsoft.Data.ConnectionUI.Dialog, Version=8.0.0.0, Culture=Neutral, PublicKeyToken=b03f5f7f11d50a3a"
"Description"="DataProvider_Sql_DataSource_Description, SR, Microsoft.Data.ConnectionUI.Dialog, Version=8.0.0.0, Culture=Neutral, PublicKeyToken=b03f5f7f11d50a3a"
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VWDExpress\8.0\DataSources\{42568F9E-354A-4c76-9916-3225D8C8E750}]
@="ODBC Data Source"
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VWDExpress\8.0\DataSources\{42568F9E-354A-4c76-9916-3225D8C8E750}\SupportingProviders]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VWDExpress\8.0\DataSources\{42568F9E-354A-4c76-9916-3225D8C8E750}\SupportingProviders\{C3D4F4CE-2C48-4381-B4D6-34FA50C51C86}]
"DisplayName"="DataSource_MicrosoftOdbcDsn, SR, Microsoft.Data.ConnectionUI.Dialog, Version=8.0.0.0, Culture=Neutral, PublicKeyToken=b03f5f7f11d50a3a"
"Description"="DataProvider_Odbc_DataSource_Description, SR, Microsoft.Data.ConnectionUI.Dialog, Version=8.0.0.0, Culture=Neutral, PublicKeyToken=b03f5f7f11d50a3a"
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VWDExpress\8.0\DataSources\{466CE797-67A4-4495-B75C-A3FD282E7FC3}]
@="Microsoft Access Database File"
"DefaultProvider"="{7F041D59-D76A-44ed-9AA2-FBF6B0548B80}"
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VWDExpress\8.0\DataSources\{466CE797-67A4-4495-B75C-A3FD282E7FC3}\SupportingProviders]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VWDExpress\8.0\DataSources\{466CE797-67A4-4495-B75C-A3FD282E7FC3}\SupportingProviders\{7F041D59-D76A-44ed-9AA2-FBF6B0548B80}]
"DisplayName"="DataSource_MicrosoftAccess, SR, Microsoft.Data.ConnectionUI.Dialog, Version=8.0.0.0, Culture=Neutral, PublicKeyToken=b03f5f7f11d50a3a"
"Description"="DataProvider_OleDB_AccessDataSource_Description, SR, Microsoft.Data.ConnectionUI.Dialog, Version=8.0.0.0, Culture=Neutral, PublicKeyToken=b03f5f7f11d50a3a"
"SpecializedProvider"="Microsoft.Jet.OLEDB.4.0"
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VWDExpress\8.0\DataSources\{485C80D5-BC85-46db-9E6D-4238A0AD7B6B}]
@="Microsoft SQL Server Database File"
"DefaultProvider"="{91510608-8809-4020-8897-FBA057E22D54}"
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VWDExpress\8.0\DataSources\{485C80D5-BC85-46db-9E6D-4238A0AD7B6B}\SupportingProviders]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VWDExpress\8.0\DataSources\{485C80D5-BC85-46db-9E6D-4238A0AD7B6B}\SupportingProviders\{91510608-8809-4020-8897-FBA057E22D54}]
"DisplayName"="DataSource_MicrosoftSqlServerFile, SR, Microsoft.Data.ConnectionUI.Dialog, Version=8.0.0.0, Culture=Neutral, PublicKeyToken=b03f5f7f11d50a3a"
"Description"="DataProvider_Sql_FileDataSource_Description, SR, Microsoft.Data.ConnectionUI.Dialog, Version=8.0.0.0, Culture=Neutral, PublicKeyToken=b03f5f7f11d50a3a"
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VWDExpress\8.0\DataSources\{E5E86CD6-6454-4fdd-910F-DC5DFC73EB45}]
@="Oracle Database"
"DefaultProvider"="{8F5C5018-AE09-42cf-B2CC-2CCCC7CFC2BB}"
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VWDExpress\8.0\DataSources\{E5E86CD6-6454-4fdd-910F-DC5DFC73EB45}\SupportingProviders]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VWDExpress\8.0\DataSources\{E5E86CD6-6454-4fdd-910F-DC5DFC73EB45}\SupportingProviders\{7F041D59-D76A-44ed-9AA2-FBF6B0548B80}]
"Description"="DataProvider_OleDB_OracleDataSource_Description, SR, Microsoft.Data.ConnectionUI.Dialog, Version=8.0.0.0, Culture=Neutral, PublicKeyToken=b03f5f7f11d50a3a"
"SpecializedProvider"="MSDAORA.1"
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VWDExpress\8.0\DataSources\{E5E86CD6-6454-4fdd-910F-DC5DFC73EB45}\SupportingProviders\{8F5C5018-AE09-42cf-B2CC-2CCCC7CFC2BB}]
"DisplayName"="DataSource_Oracle, SR, Microsoft.Data.ConnectionUI.Dialog, Version=8.0.0.0, Culture=Neutral, PublicKeyToken=b03f5f7f11d50a3a"
"Description"="DataProvider_Oracle_DataSource_Description, SR, Microsoft.Data.ConnectionUI.Dialog, Version=8.0.0.0, Culture=Neutral, PublicKeyToken=b03f5f7f11d50a3a"
DataProviders:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VWDExpress\8.0\DataProviders]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VWDExpress\8.0\DataProviders\{7F041D59-D76A-44ed-9AA2-FBF6B0548B80}]
@=".NET Framework Data Provider for OLE DB"
"DisplayName"="DataProvider_OleDB, SR, Microsoft.Data.ConnectionUI.Dialog, Version=8.0.0.0, Culture=Neutral, PublicKeyToken=b03f5f7f11d50a3a"
"ShortDisplayName"="DataProvider_OleDB_Short, SR, Microsoft.Data.ConnectionUI.Dialog, Version=8.0.0.0, Culture=Neutral, PublicKeyToken=b03f5f7f11d50a3a"
"Description"="DataProvider_OleDB_Description, SR, Microsoft.Data.ConnectionUI.Dialog, Version=8.0.0.0, Culture=Neutral, PublicKeyToken=b03f5f7f11d50a3a"
"Technology"="{77AB9A9D-78B9-4ba7-91AC-873F5338F1D2}"
"FactoryService"="{8CB5F787-2D74-459e-88D6-39E20A4D9454}"
"InvariantName"="System.Data.OleDb"
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VWDExpress\8.0\DataProviders\{7F041D59-D76A-44ed-9AA2-FBF6B0548B80}\Specialization]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VWDExpress\8.0\DataProviders\{7F041D59-D76A-44ed-9AA2-FBF6B0548B80}\Specialization\Microsoft.Jet.OLEDB.4.0]
"DataSource"="{466CE797-67A4-4495-B75C-A3FD282E7FC3}"
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VWDExpress\8.0\DataProviders\{7F041D59-D76A-44ed-9AA2-FBF6B0548B80}\Specialization\Microsoft.Jet.OLEDB.4.0\DataConnectionPromptDialog]
@="Microsoft.VisualStudio.DataTools.Providers.OleDB.OleDBJetConnectionPromptDialog, Microsoft.VisualStudio.DataTools, Version=8.0.0.0, Culture=Neutral, PublicKeyToken=b03f5f7f11d50a3a"
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VWDExpress\8.0\DataProviders\{7F041D59-D76A-44ed-9AA2-FBF6B0548B80}\Specialization\Microsoft.Jet.OLEDB.4.0\DataConnectionProperties]
@="Microsoft.Data.ConnectionUI.OleDBAccessConnectionProperties, Microsoft.Data.ConnectionUI.Dialog, Version=8.0.0.0, Culture=Neutral, PublicKeyToken=b03f5f7f11d50a3a"
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VWDExpress\8.0\DataProviders\{7F041D59-D76A-44ed-9AA2-FBF6B0548B80}\Specialization\Microsoft.Jet.OLEDB.4.0\DataConnectionUIControl]
@="Microsoft.Data.ConnectionUI.AccessConnectionUIControl, Microsoft.Data.ConnectionUI.Dialog, Version=8.0.0.0, Culture=Neutral, PublicKeyToken=b03f5f7f11d50a3a"
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VWDExpress\8.0\DataProviders\{7F041D59-D76A-44ed-9AA2-FBF6B0548B80}\Specialization\Microsoft.Jet.OLEDB.4.0\DataSourceInformation]
@="Microsoft.VisualStudio.DataTools.Providers.OleDB.OleDBJetDataSourceInformation, Microsoft.VisualStudio.DataTools, Version=8.0.0.0, Culture=Neutral, PublicKeyToken=b03f5f7f11d50a3a"
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VWDExpress\8.0\DataProviders\{7F041D59-D76A-44ed-9AA2-FBF6B0548B80}\Specialization\Microsoft.Jet.OLEDB.4.0\DataViewSupport]
@="OleDBJetDataViewSupport"
"Assembly"="Microsoft.VisualStudio.DataTools, Version=8.0.0.0, Culture=Neutral, PublicKeyToken=b03f5f7f11d50a3a"
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VWDExpress\8.0\DataProviders\{7F041D59-D76A-44ed-9AA2-FBF6B0548B80}\Specialization\MSDAORA.1]
"DataSource"="{E5E86CD6-6454-4fdd-910F-DC5DFC73EB45}"
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VWDExpress\8.0\DataProviders\{7F041D59-D76A-44ed-9AA2-FBF6B0548B80}\Specialization\MSDAORA.1\DataConnectionProperties]
@="Microsoft.Data.ConnectionUI.OleDBOracleConnectionProperties, Microsoft.Data.ConnectionUI.Dialog, Version=8.0.0.0, Culture=Neutral, PublicKeyToken=b03f5f7f11d50a3a"
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VWDExpress\8.0\DataProviders\{7F041D59-D76A-44ed-9AA2-FBF6B0548B80}\Specialization\MSDAORA.1\DataConnectionUIControl]
@="Microsoft.Data.ConnectionUI.OracleConnectionUIControl, Microsoft.Data.ConnectionUI.Dialog, Version=8.0.0.0, Culture=Neutral, PublicKeyToken=b03f5f7f11d50a3a"
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VWDExpress\8.0\DataProviders\{7F041D59-D76A-44ed-9AA2-FBF6B0548B80}\Specialization\MSDAORA.1\DataSourceInformation]
@="Microsoft.VisualStudio.DataTools.Providers.OleDB.OleDBOracleDataSourceInformation, Microsoft.VisualStudio.DataTools, Version=8.0.0.0, Culture=Neutral, PublicKeyToken=b03f5f7f11d50a3a"
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VWDExpress\8.0\DataProviders\{7F041D59-D76A-44ed-9AA2-FBF6B0548B80}\Specialization\MSDAORA.1\DataViewSupport]
@="OleDBOracleDataViewSupport"
"Assembly"="Microsoft.VisualStudio.DataTools, Version=8.0.0.0, Culture=Neutral, PublicKeyToken=b03f5f7f11d50a3a"
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VWDExpress\8.0\DataProviders\{7F041D59-D76A-44ed-9AA2-FBF6B0548B80}\Specialization\SQLNCLI.1]
"DataSource"="{067EA0D9-BA62-43f7-9106-34930C60C528}"
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VWDExpress\8.0\DataProviders\{7F041D59-D76A-44ed-9AA2-FBF6B0548B80}\Specialization\SQLNCLI.1\DataConnectionProperties]
@="Microsoft.Data.ConnectionUI.OleDBSqlConnectionProperties, Microsoft.Data.ConnectionUI.Dialog, Version=8.0.0.0, Culture=Neutral, PublicKeyToken=b03f5f7f11d50a3a"
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VWDExpress\8.0\DataProviders\{7F041D59-D76A-44ed-9AA2-FBF6B0548B80}\Specialization\SQLNCLI.1\DataConnectionUIControl]
@="Microsoft.Data.ConnectionUI.SqlConnectionUIControl, Microsoft.Data.ConnectionUI.Dialog, Version=8.0.0.0, Culture=Neutral, PublicKeyToken=b03f5f7f11d50a3a"
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VWDExpress\8.0\DataProviders\{7F041D59-D76A-44ed-9AA2-FBF6B0548B80}\Specialization\SQLNCLI.1\DataSourceInformation]
@="Microsoft.VisualStudio.DataTools.Providers.OleDB.OleDBSqlDataSourceInformation, Microsoft.VisualStudio.DataTools, Version=8.0.0.0, Culture=Neutral, PublicKeyToken=b03f5f7f11d50a3a"
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VWDExpress\8.0\DataProviders\{7F041D59-D76A-44ed-9AA2-FBF6B0548B80}\Specialization\SQLNCLI.1\DataViewSupport]
@="OleDBSqlDataViewSupport"
"Assembly"="Microsoft.VisualStudio.DataTools, Version=8.0.0.0, Culture=Neutral, PublicKeyToken=b03f5f7f11d50a3a"
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VWDExpress\8.0\DataProviders\{7F041D59-D76A-44ed-9AA2-FBF6B0548B80}\Specialization\SQLOLEDB.1]
"DataSource"="{067EA0D9-BA62-43f7-9106-34930C60C528}"
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VWDExpress\8.0\DataProviders\{7F041D59-D76A-44ed-9AA2-FBF6B0548B80}\Specialization\SQLOLEDB.1\DataConnectionProperties]
@="Microsoft.Data.ConnectionUI.OleDBSqlConnectionProperties, Microsoft.Data.ConnectionUI.Dialog, Version=8.0.0.0, Culture=Neutral, PublicKeyToken=b03f5f7f11d50a3a"
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VWDExpress\8.0\DataProviders\{7F041D59-D76A-44ed-9AA2-FBF6B0548B80}\Specialization\SQLOLEDB.1\DataConnectionUIControl]
@="Microsoft.Data.ConnectionUI.SqlConnectionUIControl, Microsoft.Data.ConnectionUI.Dialog, Version=8.0.0.0, Culture=Neutral, PublicKeyToken=b03f5f7f11d50a3a"
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VWDExpress\8.0\DataProviders\{7F041D59-D76A-44ed-9AA2-FBF6B0548B80}\Specialization\SQLOLEDB.1\DataSourceInformation]
@="Microsoft.VisualStudio.DataTools.Providers.OleDB.OleDBSqlDataSourceInformation, Microsoft.VisualStudio.DataTools, Version=8.0.0.0, Culture=Neutral, PublicKeyToken=b03f5f7f11d50a3a"
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VWDExpress\8.0\DataProviders\{7F041D59-D76A-44ed-9AA2-FBF6B0548B80}\Specialization\SQLOLEDB.1\DataViewSupport]
@="OleDBSqlDataViewSupport"
"Assembly"="Microsoft.VisualStudio.DataTools, Version=8.0.0.0, Culture=Neutral, PublicKeyToken=b03f5f7f11d50a3a"
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VWDExpress\8.0\DataProviders\{7F041D59-D76A-44ed-9AA2-FBF6B0548B80}\Specialization\VFPOLEDB.1]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VWDExpress\8.0\DataProviders\{7F041D59-D76A-44ed-9AA2-FBF6B0548B80}\Specialization\VFPOLEDB.1\DataSourceInformation]
@="Microsoft.VisualStudio.DataTools.Providers.OleDB.OleDBFoxDataSourceInformation, Microsoft.VisualStudio.DataTools, Version=8.0.0.0, Culture=Neutral, PublicKeyToken=b03f5f7f11d50a3a"
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VWDExpress\8.0\DataProviders\{7F041D59-D76A-44ed-9AA2-FBF6B0548B80}\SupportedObjects]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VWDExpress\8.0\DataProviders\{7F041D59-D76A-44ed-9AA2-FBF6B0548B80}\SupportedObjects\DataConnectionPromptDialog]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VWDExpress\8.0\DataProviders\{7F041D59-D76A-44ed-9AA2-FBF6B0548B80}\SupportedObjects\DataConnectionPromptDialog\{466CE797-67A4-4495-B75C-A3FD282E7FC3}]
@=""
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VWDExpress\8.0\DataProviders\{7F041D59-D76A-44ed-9AA2-FBF6B0548B80}\SupportedObjects\DataConnectionProperties]
@=""
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VWDExpress\8.0\DataProviders\{7F041D59-D76A-44ed-9AA2-FBF6B0548B80}\SupportedObjects\DataConnectionSupport]
@=""
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VWDExpress\8.0\DataProviders\{7F041D59-D76A-44ed-9AA2-FBF6B0548B80}\SupportedObjects\DataConnectionUIControl]
@=""
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VWDExpress\8.0\DataProviders\{7F041D59-D76A-44ed-9AA2-FBF6B0548B80}\SupportedObjects\DataObjectSupport]
@=""
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VWDExpress\8.0\DataProviders\{7F041D59-D76A-44ed-9AA2-FBF6B0548B80}\SupportedObjects\DataSourceSpecializer]
@=""
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VWDExpress\8.0\DataProviders\{7F041D59-D76A-44ed-9AA2-FBF6B0548B80}\SupportedObjects\DataViewSupport]
@=""
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VWDExpress\8.0\DataProviders\{8F5C5018-AE09-42cf-B2CC-2CCCC7CFC2BB}]
@=".NET Framework Data Provider for Oracle"
"DisplayName"="DataProvider_Oracle, SR, Microsoft.Data.ConnectionUI.Dialog, Version=8.0.0.0, Culture=Neutral, PublicKeyToken=b03f5f7f11d50a3a"
"ShortDisplayName"="DataProvider_Oracle_Short, SR, Microsoft.Data.ConnectionUI.Dialog, Version=8.0.0.0, Culture=Neutral, PublicKeyToken=b03f5f7f11d50a3a"
"Description"="DataProvider_Oracle_Description, SR, Microsoft.Data.ConnectionUI.Dialog, Version=8.0.0.0, Culture=Neutral, PublicKeyToken=b03f5f7f11d50a3a"
"Technology"="{77AB9A9D-78B9-4ba7-91AC-873F5338F1D2}"
"FactoryService"="{F638BEE1-DC22-4401-8A4A-6DB0B13C196C}"
"InvariantName"="System.Data.OracleClient"
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VWDExpress\8.0\DataProviders\{8F5C5018-AE09-42cf-B2CC-2CCCC7CFC2BB}\SupportedObjects]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VWDExpress\8.0\DataProviders\{8F5C5018-AE09-42cf-B2CC-2CCCC7CFC2BB}\SupportedObjects\DataConnectionPromptDialog]
@=""
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VWDExpress\8.0\DataProviders\{8F5C5018-AE09-42cf-B2CC-2CCCC7CFC2BB}\SupportedObjects\DataConnectionProperties]
@=""
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VWDExpress\8.0\DataProviders\{8F5C5018-AE09-42cf-B2CC-2CCCC7CFC2BB}\SupportedObjects\DataConnectionSupport]
@=""
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VWDExpress\8.0\DataProviders\{8F5C5018-AE09-42cf-B2CC-2CCCC7CFC2BB}\SupportedObjects\DataConnectionUIControl]
@=""
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VWDExpress\8.0\DataProviders\{8F5C5018-AE09-42cf-B2CC-2CCCC7CFC2BB}\SupportedObjects\DataObjectSupport]
@=""
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VWDExpress\8.0\DataProviders\{8F5C5018-AE09-42cf-B2CC-2CCCC7CFC2BB}\SupportedObjects\DataSourceSpecializer]
@=""
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VWDExpress\8.0\DataProviders\{8F5C5018-AE09-42cf-B2CC-2CCCC7CFC2BB}\SupportedObjects\DataViewSupport]
@=""
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VWDExpress\8.0\DataProviders\{91510608-8809-4020-8897-FBA057E22D54}]
@=".NET Framework Data Provider for SQL Server"
"DisplayName"="DataProvider_Sql, SR, Microsoft.Data.ConnectionUI.Dialog, Version=8.0.0.0, Culture=Neutral, PublicKeyToken=b03f5f7f11d50a3a"
"ShortDisplayName"="DataProvider_Sql_Short, SR, Microsoft.Data.ConnectionUI.Dialog, Version=8.0.0.0, Culture=Neutral, PublicKeyToken=b03f5f7f11d50a3a"
"Description"="DataProvider_Sql_Description, SR, Microsoft.Data.ConnectionUI.Dialog, Version=8.0.0.0, Culture=Neutral, PublicKeyToken=b03f5f7f11d50a3a"
"Technology"="{77AB9A9D-78B9-4ba7-91AC-873F5338F1D2}"
"FactoryService"="{FCD3F3E8-69AC-42d5-905E-2E131905E708}"
"InvariantName"="System.Data.SqlClient"
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VWDExpress\8.0\DataProviders\{91510608-8809-4020-8897-FBA057E22D54}\SupportedObjects]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VWDExpress\8.0\DataProviders\{91510608-8809-4020-8897-FBA057E22D54}\SupportedObjects\DataConnectionPromptDialog]
@=""
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VWDExpress\8.0\DataProviders\{91510608-8809-4020-8897-FBA057E22D54}\SupportedObjects\DataConnectionProperties]
@=""
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VWDExpress\8.0\DataProviders\{91510608-8809-4020-8897-FBA057E22D54}\SupportedObjects\DataConnectionSupport]
@=""
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VWDExpress\8.0\DataProviders\{91510608-8809-4020-8897-FBA057E22D54}\SupportedObjects\DataConnectionUIControl]
@=""
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VWDExpress\8.0\DataProviders\{91510608-8809-4020-8897-FBA057E22D54}\SupportedObjects\DataObjectSupport]
@=""
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VWDExpress\8.0\DataProviders\{91510608-8809-4020-8897-FBA057E22D54}\SupportedObjects\DataSourceSpecializer]
@=""
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VWDExpress\8.0\DataProviders\{91510608-8809-4020-8897-FBA057E22D54}\SupportedObjects\DataViewSupport]
@=""
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VWDExpress\8.0\DataProviders\{C3D4F4CE-2C48-4381-B4D6-34FA50C51C86}]
@=".NET Framework Data Provider for ODBC"
"DisplayName"="DataProvider_Odbc, SR, Microsoft.Data.ConnectionUI.Dialog, Version=8.0.0.0, Culture=Neutral, PublicKeyToken=b03f5f7f11d50a3a"
"ShortDisplayName"="DataProvider_Odbc_Short, SR, Microsoft.Data.ConnectionUI.Dialog, Version=8.0.0.0, Culture=Neutral, PublicKeyToken=b03f5f7f11d50a3a"
"Description"="DataProvider_Odbc_Description, SR, Microsoft.Data.ConnectionUI.Dialog, Version=8.0.0.0, Culture=Neutral, PublicKeyToken=b03f5f7f11d50a3a"
"Technology"="{77AB9A9D-78B9-4ba7-91AC-873F5338F1D2}"
"FactoryService"="{06D0BE35-FA3A-4ef6-81B9-3EDBB68EF982}"
"InvariantName"="System.Data.Odbc"
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VWDExpress\8.0\DataProviders\{C3D4F4CE-2C48-4381-B4D6-34FA50C51C86}\SupportedObjects]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VWDExpress\8.0\DataProviders\{C3D4F4CE-2C48-4381-B4D6-34FA50C51C86}\SupportedObjects\DataConnectionPromptDialog]
@=""
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VWDExpress\8.0\DataProviders\{C3D4F4CE-2C48-4381-B4D6-34FA50C51C86}\SupportedObjects\DataConnectionProperties]
@=""
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VWDExpress\8.0\DataProviders\{C3D4F4CE-2C48-4381-B4D6-34FA50C51C86}\SupportedObjects\DataConnectionSupport]
@=""
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VWDExpress\8.0\DataProviders\{C3D4F4CE-2C48-4381-B4D6-34FA50C51C86}\SupportedObjects\DataConnectionUIControl]
@=""
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VWDExpress\8.0\DataProviders\{C3D4F4CE-2C48-4381-B4D6-34FA50C51C86}\SupportedObjects\DataObjectSupport]
@=""
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VWDExpress\8.0\DataProviders\{C3D4F4CE-2C48-4381-B4D6-34FA50C51C86}\SupportedObjects\DataSourceSpecializer]
@=""
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VWDExpress\8.0\DataProviders\{C3D4F4CE-2C48-4381-B4D6-34FA50C51C86}\SupportedObjects\DataViewSupport]
@="" -
Wednesday, February 01, 2006 5:01 PM
Hi Gerry,
Thanks for sending us the registry dump. You are right, everything there looks correct. The only remaining registration issue to check is that the ADO .NET providers are correctly installed on the machine. To verify this, locate your .NET Framework directory under the windows directory (typically windows\Microsoft .NET\Framework\v2.0.50727) and look in the config directory. There should be a machine.config file in here. Please send me the contents of the <system.data> section of this XML file.
Thanks,
Stephen -
Thursday, February 02, 2006 3:58 AMHey Stephen,
<system.data> is below.
Thanks.
<system.data>
<DbProviderFactories>
<add name="Odbc Data Provider" invariant="System.Data.Odbc" description=".Net Framework Data Provider for Odbc" type="System.Data.Odbc.OdbcFactory, System.Data, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"/>
<add name="OleDb Data Provider" invariant="System.Data.OleDb" description=".Net Framework Data Provider for OleDb" type="System.Data.OleDb.OleDbFactory, System.Data, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"/>
<add name="OracleClient Data Provider" invariant="System.Data.OracleClient" description=".Net Framework Data Provider for Oracle" type="System.Data.OracleClient.OracleClientFactory, System.Data.OracleClient, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"/>
<add name="SqlClient Data Provider" invariant="System.Data.SqlClient" description=".Net Framework Data Provider for SqlServer" type="System.Data.SqlClient.SqlClientFactory, System.Data, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"/>
</DbProviderFactories>
</system.data> -
Thursday, February 02, 2006 4:51 PM
Ok, this all looks fine too. I am running out of ideas here. Is there a way you can attach a debugger to your VWExpress.exe and before reproducing the problem, tell it to break on common language runtime exceptions? This will identify exactly what the issue is.
Thanks,
Stephen -
Monday, February 06, 2006 3:48 PMStephen,
I'm not sure if I'm doing this correctly b/c VWD is not throwing an error that
appears in the debugger. What I have done is run the Microsoft CLR Debugger and
attached to VWDExpress.exe. I've tried a couple of different ways which I think
will accomplish the same thing, that is, I've selected "Program to Debug" from
the "Debug" menu and launched VWDExpress.exe from there. I've also started VWDExpress.exe
then attached to the process from within the debugger. I've tried setting the
Common Language Runtime Exceptions the break when an exception is "Thrown", "
User-unhandled" and all combinations of the two.
I have tried hand coding the SQL and running the query against the (Access)
db and get probably the most detailed info from w/in VWD, and that is: "Could
not create connection Object reference not set to an instance of an object."
But, I do not receive any exception information in the CLR debugger.
I can copy this project over to another machine and it works fine. In fact, the
other machine automatically sees the Access db under my App_Data folder (
Database Explorer view) w/o me adding it explicitly. I assume that this is
in fact what should happen. The problem machine has never done this.
The problem in a nutshell seems that I am not able to connect to an Access DB.
(I can connect through an ODBC alias)
I'm absolutely stimied.
Gerry -
Monday, February 06, 2006 5:20 PM
Gerry,
Is there any setting in the Microsoft CLR Debugger for debugging "just my code"? If so, and this is checked, uncheck it. This might help in catching the exception.
When you hand coded the SQL and run the query against the DB, what were you using to do this? The query designer or a script editor or something else? Where exactly does the error message show up?
Thanks,
Stephen -
Monday, February 06, 2006 7:32 PMStephen,
Unchecking "just my code" worked.
I have tried both using the script editor and the query builder in order to
test the SQL. However, using the wizard only, I never get that far so I think
it's a connection issue rather and anything having to do with the SQL.
The error/problem has several dispositions depending on what exactly I attempt. I assume
that these dispositions relate to the same root problem.
Disposition 1:
There is a AccessFileName.mdb in the App_Data folder. I have tested this file
on the other machine as well as make sure that it works in Access. The file
appears to be ok.
Using the Database Explorer, I attempt an "Add Connection".
An "Add Connection" Window opens defaulted to a MS ODBC Data Source. (on the working machine, a "Choose Data Source"
window opens). I select "Change" and the "Choose Data Source"
window opens. I select "Microsoft Access Database File" and click "OK". An "
Add Connection" window opens that is generic (working machine "Add Connection"
window is specific for MSAccess file).
Also, the following error(s) appears in the CLR debugger:
A first chance exception of type 'System.NullReferenceException' occurred in Microsoft.VisualStudio.DataTools.dll
A first chance exception of type 'System.NullReferenceException' occurred in Microsoft.VisualStudio.DataTools.dll
Disposition 2:
An AccessDataSource is added to a Webform. I select "Configure Data Source"
from the smart tag drop down list. I browse to the .mdb in the App_Data folder
and click next. The "How would you like to retrieve data from you database?"
screen is skipped and a "Define Custom Statements or Stored Procedure" window
opens with "Select, Update" etc tabs. Also, the following error(s) appears in the
CLR debugger:
A first chance exception of type 'System.NullReferenceException' occurred in Microsoft.VisualStudio.DataTools.dll
A first chance exception of type 'System.NullReferenceException' occurred in Microsoft.VisualStudio.DataTools.dll
A first chance exception of type 'System.NullReferenceException' occurred in Microsoft.VisualStudio.DataTools.dll
A first chance exception of type 'System.NullReferenceException' occurred in Microsoft.VisualStudio.DataTools.dll
If I click on "Query Builder" an error window displays in VS "Object reference
not set to an instance of an object." Also, the following error(s) occur in
the CLR debugger:
A first chance exception of type 'System.NullReferenceException' occurred in Microsoft.VisualStudio.DataTools.dll
A first chance exception of type 'System.NullReferenceException' occurred in Microsoft.VisualStudio.DataTools.dll
Hope this gives you some more info.
Thanks.
Gerry -
Monday, February 06, 2006 7:56 PM
Gerry,
We're getting closer. If you can run the same scenario again under the debugger, particular between choosing a data source and seeing a generic Add Connection window, and for any one of these exceptions capture the call stack and attach that, it will help me isolate the problem. I am beginning to think that the Access OLE DB provider is not properly registered on the machine.
Thanks,
Stephen -
Monday, February 06, 2006 8:58 PMStephen,
Call stack for senario 1 below. Exception was:
"A first chance exception of type 'System.NullReferenceException' occurred in Microsoft.VisualStudio.DataTools.dll"
and broke on:
00000186 mov eax,dword ptr [ebp-24h]
00000000 push ebp
00000001 mov ebp,esp
00000003 push edi
00000004 push esi
00000005 push ebx
00000006 sub esp,28h
00000009 xor eax,eax
0000000b mov dword ptr [ebp-30h],eax
0000000e mov dword ptr [ebp-34h],eax
00000011 xor eax,eax
00000013 mov dword ptr [ebp-18h],eax
00000016 mov dword ptr [ebp-24h],ecx
00000019 mov edi,dword ptr [ebp-24h]
0000001c mov eax,dword ptr [edi+8]
0000001f mov dword ptr [ebp-30h],eax
00000022 mov ecx,dword ptr [ebp-30h]
00000025 call 72BA1789
0000002a xor edx,edx
0000002c mov dword ptr [edi+14h],edx
0000002f mov dword ptr [ebp-28h],edx
00000032 xor ebx,ebx
00000034 mov ecx,dword ptr [edi+8]
00000037 call dword ptr ds:[01340610h]
0000003d mov dword ptr [ebp-2Ch],eax
00000040 mov ecx,dword ptr [ebp-2Ch]
00000043 call dword ptr ds:[01340614h]
00000049 test eax,eax
0000004b je 000000D1
00000051 mov ecx,dword ptr [ebp-2Ch]
00000054 call dword ptr ds:[01340618h]
0000005a mov esi,eax
0000005c test esi,esi
0000005e je 00000078
00000060 cmp dword ptr [esi],790FA3E0h
00000066 jne 0000006A
00000068 jmp 00000078
0000006a mov edx,esi
0000006c mov ecx,790FA3E0h
00000071 call 72C197EC
00000076 mov esi,eax
00000078 mov dword ptr [ebp-28h],esi
0000007b mov ecx,dword ptr [ebp-2Ch]
0000007e call dword ptr ds:[0134061Ch]
00000084 mov esi,eax
00000086 test esi,esi
00000088 je 000000A2
0000008a cmp dword ptr [esi],79108964h
00000090 jne 00000094
00000092 jmp 000000A2
00000094 mov edx,esi
00000096 mov ecx,79108964h
0000009b call 72C197EC
000000a0 mov esi,eax
000000a2 mov ebx,esi
000000a4 mov ecx,ebx
000000a6 mov eax,dword ptr [ecx]
000000a8 call dword ptr [eax+58h]
000000ab mov esi,eax
000000ad test esi,esi
000000af je 000000C9
000000b1 cmp dword ptr [esi],7257D4Ch
000000b7 jne 000000BB
000000b9 jmp 000000C9
000000bb mov edx,esi
000000bd mov ecx,7257D4Ch
000000c2 call 72C197EC
000000c7 mov esi,eax
000000c9 lea edx,[edi+14h]
000000cc call 72BA1666
000000d1 test ebx,ebx
000000d3 je 000000EC
000000d5 mov ecx,ebx
000000d7 mov eax,dword ptr [ecx]
000000d9 call dword ptr [eax+38h]
000000dc test eax,eax
000000de jne 000000EC
000000e0 mov ecx,dword ptr [edi+8]
000000e3 mov edx,dword ptr [ebp-28h]
000000e6 call dword ptr ds:[01340620h]
000000ec mov dword ptr [ebp-1Ch],0
000000f3 mov dword ptr [ebp-18h],0FCh
000000fa push 72D2578h
000000ff jmp 00000101
00000101 mov ecx,dword ptr [ebp-30h]
00000104 call 72BA1A03
00000109 pop eax
0000010a jmp eax
0000010c mov eax,dword ptr [ebp-24h]
0000010f cmp dword ptr [eax+14h],0
00000113 je 00000178
00000115 mov eax,dword ptr [ebp-24h]
00000118 mov ecx,dword ptr [eax+10h]
0000011b push 0
0000011d mov edx,1388h
00000122 mov eax,dword ptr [ecx]
00000124 call dword ptr [eax+4Ch]
00000127 mov eax,dword ptr [ebp-24h]
0000012a mov ecx,dword ptr [eax+14h]
0000012d mov edx,dword ptr [ebp-24h]
00000130 cmp dword ptr [ecx],ecx
00000132 call dword ptr ds:[07257DB0h]
00000138 jmp 0000013F
0000013a call 72CC3F39
0000013f mov eax,dword ptr [ebp-24h]
00000142 mov eax,dword ptr [eax+8]
00000145 mov dword ptr [ebp-34h],eax
00000148 mov ecx,dword ptr [ebp-34h]
0000014b call 72BA1789
00000150 mov eax,dword ptr [ebp-24h]
00000153 xor edx,edx
00000155 mov dword ptr [eax+14h],edx
00000158 mov dword ptr [ebp-1Ch],0
0000015f mov dword ptr [ebp-18h],0FCh
00000166 push 72D256Ch
0000016b jmp 0000016D
0000016d mov ecx,dword ptr [ebp-34h]
00000170 call 72BA1A03
00000175 pop eax
00000176 jmp eax
00000178 mov eax,dword ptr [ebp-24h]
0000017b mov ecx,dword ptr [eax+1Ch]
0000017e or edx,0FFFFFFFFh
00000181 call FFF863A4
00000186 mov eax,dword ptr [ebp-24h]
00000189 mov ecx,dword ptr [eax+1Ch]
0000018c xor edx,edx
0000018e call 7207B850
00000193 test eax,eax
00000195 jne 000001A4
00000197 mov eax,dword ptr [ebp-24h]
0000019a cmp dword ptr [eax+0Ch],0
0000019e jne 00000019
000001a4 lea esp,[ebp-0Ch]
000001a7 pop ebx
000001a8 pop esi
000001a9 pop edi
000001aa pop ebp
000001ab ret
000001ac mov dword ptr [ebp-18h],0
000001b3 jmp 00000019
000001b8 mov dword ptr [ebp-18h],0
000001bf jmp 0000010C
Thanks.
Gerry -
Monday, February 06, 2006 9:03 PM
Gerry,
That's a dump of the disassembly, not a call stack. I'm looking for information on the method that is currently being executed, along with all the methods above it that have got it to that point. It typically looks something like this:
> Microsoft.VisualStudio.DataTools.dll!Microsoft.VisualStudio.DataTools.DataServices.DataProvider.ProviderObjectFactory.get() Line 1092 C#
Microsoft.VisualStudio.DataTools.dll!Microsoft.VisualStudio.DataTools.DataServices.DataProvider.GetAssembly(System.Guid dataSource = {00000000-0000-0000-0000-000000000000}, string assemblyString = "Microsoft.CompactFramework.Design.Data, Version=8.0.0000.0, Culture=Neutral, PublicKeyToken=b03f5f7f11d50a3a") Line 358 + 0x8 bytes C#
Microsoft.VisualStudio.Data.dll!Microsoft.VisualStudio.Data.DataProvider.GetAssembly(string assemblyString = "Microsoft.CompactFramework.Design.Data, Version=8.0.0000.0, Culture=Neutral, PublicKeyToken=b03f5f7f11d50a3a") Line 76 + 0x2a bytes C#
Microsoft.VisualStudio.DataTools.dll!Microsoft.VisualStudio.DataTools.DataServices.DataProvider.GetPackageString(string resourceId = "ConnUI_SqlMobile, Microsoft.CF.Design.Data, Microsoft.CompactFramework.Design.Data, Version=8.0.0000.0, Culture=Neutral, PublicKeyToken=b03f5f7f11d50a3a") Line 963 + 0x12 bytes C#
Thanks,
Stephen -
Monday, February 06, 2006 9:46 PMStephen,
Sorry about that. Is this what you need?
[Managed to Native Transition]
> Microsoft.VisualStudio.Web.dll!Microsoft.VisualStudio.Web.VsClientBuildManager.CBMThreadPool.ThreadProc() + 0x186 bytes
mscorlib.dll!System.Threading.ThreadHelper.ThreadStart_Context(object state) + 0x3b bytes
mscorlib.dll!System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, object state) + 0x81 bytes
mscorlib.dll!System.Threading.ThreadHelper.ThreadStart() + 0x40 bytes
Thanks,
Gerry -
Monday, February 06, 2006 10:58 PM
Gerry,
This is trickier than I thought. This callstack is coming from a different thread than the one I am interested in. It could also be that the exception you hit here is not the right one.
There should be a way in the debugger to look through the various threads. Try and find one that is quite long and looks like it has something to do with data, e.g. Microsoft.VisualStudio.DataTools.dll.
I am guessing at this point that the Access OLE DB provider is not registered correctly on your machine. Do you have an ability to create an application manually that makes a connection to your Access database file and verify that it is working (when the designers are not)?
Thanks,
Stephen -
Tuesday, February 07, 2006 6:06 PMStephen,
I was only able to view these 3 threads: <No Name>, VsCBMThreadPool and VsCBMOnReadyEventQueue.
The "No Name" seems closest to what you're describing:
> System.Windows.Forms.dll!System.Windows.Forms.Application.ThreadContext.LocalModalMessageLoop(System.Windows.Forms.Form form = {Microsoft.Data.ConnectionUI.DataConnectionDialog}) + 0x1e3 bytes
System.Windows.Forms.dll!System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(int reason = 4, System.Windows.Forms.ApplicationContext context = {System.Windows.Forms.Application.ModalApplicationContext}) + 0x1db bytes
System.Windows.Forms.dll!System.Windows.Forms.Application.ThreadContext.RunMessageLoop(int reason, System.Windows.Forms.ApplicationContext context) + 0x53 bytes
System.Windows.Forms.dll!System.Windows.Forms.Form.ShowDialog(System.Windows.Forms.IWin32Window owner) + 0x4ee bytes
Microsoft.Data.ConnectionUI.Dialog.dll!Microsoft.Data.ConnectionUI.DataConnectionDialog.Show(Microsoft.Data.ConnectionUI.DataConnectionDialog dialog = {Microsoft.Data.ConnectionUI.DataConnectionDialog}, System.Windows.Forms.IWin32Window owner = {Microsoft.VisualStudio.UIService.NativeHandleWindow}) + 0x30c bytes
Microsoft.VisualStudio.DataTools.dll!Microsoft.VisualStudio.DataTools.DataServices.DataConnectionDialog.ShowDialog() + 0x5e bytes
Microsoft.VisualStudio.DataTools.dll!Microsoft.VisualStudio.DataTools.DataServices.DataConnectionDialog.ShowDialog(bool connect) + 0x2e bytes
Microsoft.VSDesigner.dll!Microsoft.VSDesigner.ServerExplorer.DataConnectionsNode.PromptConnectionInfo(ref System.Guid provider = {System.Guid}, System.Guid source, ref string connectionString = null, out bool encryptedString = false) + 0x2cd bytes
Microsoft.VSDesigner.dll!Microsoft.VSDesigner.ServerExplorer.DataConnectionsNode.OnAddConnection(object sender, System.EventArgs eevent) + 0x78 bytes
Microsoft.VSDesigner.dll!Microsoft.VSDesigner.ServerExplorer.VsServerExplorer.Exec(ref System.Guid pguidCmdGroup, uint uintCmdID, uint nCmdexecopt, System.IntPtr pvaIn, System.IntPtr pvaOut) + 0x213 bytes
[Native to Managed Transition]
[Managed to Native Transition]
Microsoft.VSDesigner.dll!Microsoft.VSDesigner.ServerExplorer.VsServerExplorer.OnRightClickNode(Microsoft.VSDesigner.ServerExplorer.NodeSite node, object positionObject) + 0x146 bytes
Microsoft.VSDesigner.dll!Microsoft.VSDesigner.ServerExplorer.VsServerExplorer.ExecCommand(uint itemid, ref System.Guid pguidCmdGroup, uint uintCmdID, uint uintCmdexecopt, System.IntPtr pvaIn, System.IntPtr pvaOut) + 0x1ca bytes
[Native to Managed Transition]
Also, I was able to get this code to display records correctly in a DataGridView
control on a winform.
void Button1Click(object sender, System.EventArgs e)
{
DataSet ds = new DataSet();
OleDbDataAdapter da = new OleDbDataAdapter("Select PROB_KEY from B_Prob","Provider=Microsoft.Jet.OLEDB.4.0;" +
"Data Source=Db1.mdb;" +
"User ID=Admin; Password= ");
da.Fill(ds,"B_PROB");
dataGridView1.AutoGenerateColumns = true;
dataGridView1.DataSource = ds;
dataGridView1.DataMember = "B_PROB";
}
Thanks.
Gerry -
Tuesday, February 07, 2006 6:28 PM
Gerry,
Yes, that's the thread I'm looking for. However, it seems that the exception you are breaking on is the wrong one, as this thread is not doing anything very interesting in the call stack you sent. When you are breaking on exceptions, can you continue and hit various other exceptions? If so, see if you can do that until the call stack from the <No Name> thread has a lot more information in it above the "LocalModalMessageLoop" function. I'm looking for some fairly specific function names that will help me identify the function in our dialog code where the exception is occurring.
Since your test code is working, my theory about the OLE DB provider not being registered properly was wrong. So it looks like the problem really is limited to the designers. I don't have any more ideas beyond finding more specific exception info.
Thanks,
Stephen -
Monday, February 13, 2006 10:34 PMStephen,
I don't know if this is helpful or not. I used the 2nd disposion of the problem (
configuring the data source and running a query that was typed) and
broke on just before the error and then just after.
Attempting to test query from "Configure Data Source" screen. Breaking
debugger before "Test Query" button selected:
[Managed to Native Transition]
> System.Windows.Forms.dll!System.Windows.Forms.Application.ThreadContext.LocalModalMessageLoop(System.Windows.Forms.Form form = {System.Web.UI.Design.WebControls.AccessDataSourceWizardForm}) + 0x1e3 bytes
System.Windows.Forms.dll!System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(int reason = 4, System.Windows.Forms.ApplicationContext context = {System.Windows.Forms.Application.ModalApplicationContext}) + 0x1db bytes
System.Windows.Forms.dll!System.Windows.Forms.Application.ThreadContext.RunMessageLoop(int reason, System.Windows.Forms.ApplicationContext context) + 0x53 bytes
System.Windows.Forms.dll!System.Windows.Forms.Form.ShowDialog(System.Windows.Forms.IWin32Window owner) + 0x4ee bytes
Microsoft.VisualStudio.dll!Microsoft.VisualStudio.UIService.System.Windows.Forms.Design.IUIService.ShowDialog(System.Windows.Forms.Form form = {System.Web.UI.Design.WebControls.AccessDataSourceWizardForm}) + 0x75 bytes
System.Design.dll!System.Web.UI.Design.Util.UIServiceHelper.ShowDialog(System.IServiceProvider serviceProvider, System.Windows.Forms.Form form) + 0x3a bytes
System.Design.dll!System.Web.UI.Design.WebControls.SqlDataSourceDesigner.ConfigureDataSourceChangeCallback(object context) + 0xf7 bytes
System.Design.dll!System.Web.UI.Design.ControlDesigner.InvokeTransactedChange(System.IServiceProvider serviceProvider, System.ComponentModel.IComponent component = {System.Web.UI.WebControls.AccessDataSource}, System.Web.UI.Design.TransactedChangeCallback callback, object context, string description, System.ComponentModel.MemberDescriptor member = null) + 0x12a bytes
System.Design.dll!System.Web.UI.Design.ControlDesigner.InvokeTransactedChange(System.ComponentModel.IComponent component, System.Web.UI.Design.TransactedChangeCallback callback, object context, string description, System.ComponentModel.MemberDescriptor member) + 0x3f bytes
System.Design.dll!System.Web.UI.Design.ControlDesigner.InvokeTransactedChange(System.ComponentModel.IComponent component, System.Web.UI.Design.TransactedChangeCallback callback, object context, string description) + 0x2d bytes
System.Design.dll!System.Web.UI.Design.WebControls.SqlDataSourceDesigner.Configure() + 0x58 bytes
System.Design.dll!System.Web.UI.Design.DataSourceDesigner.DataSourceDesignerActionList.Configure() + 0xd bytes
[Native to Managed Transition]
[Managed to Native Transition]
System.Design.dll!System.ComponentModel.Design.DesignerActionMethodItem.Invoke() + 0x4a bytes
Microsoft.VisualStudio.Web.dll!Microsoft.VisualStudio.Web.DesignerActionPanel.MethodLine.OnLinkLabelLinkClicked(object sender, System.Windows.Forms.LinkLabelLinkClickedEventArgs e) + 0x33 bytes
System.Windows.Forms.dll!System.Windows.Forms.LinkLabel.OnLinkClicked(System.Windows.Forms.LinkLabelLinkClickedEventArgs e) + 0x6a bytes
System.Windows.Forms.dll!System.Windows.Forms.LinkLabel.OnMouseUp(System.Windows.Forms.MouseEventArgs e = {X = 61 Y = 5 Button = Left}) + 0x160 bytes
System.Windows.Forms.dll!System.Windows.Forms.Control.WmMouseUp(ref System.Windows.Forms.Message m, System.Windows.Forms.MouseButtons button, int clicks) + 0xf2 bytes
System.Windows.Forms.dll!System.Windows.Forms.Control.WndProc(ref System.Windows.Forms.Message m) + 0x544 bytes
System.Windows.Forms.dll!System.Windows.Forms.Label.WndProc(ref System.Windows.Forms.Message m) + 0x33 bytes
System.Windows.Forms.dll!System.Windows.Forms.LinkLabel.WndProc(ref System.Windows.Forms.Message msg) + 0x11 bytes
System.Windows.Forms.dll!System.Windows.Forms.Control.ControlNativeWindow.OnMessage(ref System.Windows.Forms.Message m) + 0xd bytes
System.Windows.Forms.dll!System.Windows.Forms.Control.ControlNativeWindow.WndProc(ref System.Windows.Forms.Message m) + 0xd6 bytes
System.Windows.Forms.dll!System.Windows.Forms.NativeWindow.DebuggableCallback(System.IntPtr hWnd, int msg = 514, System.IntPtr wparam, System.IntPtr lparam) + 0x75 bytes
Breaking debugger after selecting "Test Query" button and receiving error: "Could not Create Connection. Object reference not set to an
instance of an oject"
[Managed to Native Transition]
> Microsoft.VisualStudio.dll!Microsoft.VisualStudio.UIService.System.Windows.Forms.Design.IUIService.ShowError(string message) + 0x57 bytes
System.Design.dll!System.Web.UI.Design.Util.UIServiceHelper.ShowError(System.IServiceProvider serviceProvider, System.Exception ex, string message) + 0x64 bytes
System.Design.dll!System.Web.UI.Design.WebControls.SqlDataSourceSummaryPanel.OnTestQueryButtonClick(object sender, System.EventArgs e) + 0x211 bytes
System.Windows.Forms.dll!System.Windows.Forms.Control.OnClick(System.EventArgs e) + 0x57 bytes
System.Windows.Forms.dll!System.Windows.Forms.Button.OnClick(System.EventArgs e) + 0x49 bytes
System.Windows.Forms.dll!System.Windows.Forms.Button.OnMouseUp(System.Windows.Forms.MouseEventArgs mevent = {X = 69 Y = 16 Button = Left}) + 0xc3 bytes
System.Windows.Forms.dll!System.Windows.Forms.Control.WmMouseUp(ref System.Windows.Forms.Message m, System.Windows.Forms.MouseButtons button, int clicks) + 0xf2 bytes
System.Windows.Forms.dll!System.Windows.Forms.Control.WndProc(ref System.Windows.Forms.Message m) + 0x544 bytes
System.Windows.Forms.dll!System.Windows.Forms.ButtonBase.WndProc(ref System.Windows.Forms.Message m) + 0xce bytes
System.Windows.Forms.dll!System.Windows.Forms.Button.WndProc(ref System.Windows.Forms.Message m) + 0x2b bytes
System.Windows.Forms.dll!System.Windows.Forms.Control.ControlNativeWindow.OnMessage(ref System.Windows.Forms.Message m) + 0xd bytes
System.Windows.Forms.dll!System.Windows.Forms.Control.ControlNativeWindow.WndProc(ref System.Windows.Forms.Message m) + 0xd6 bytes
System.Windows.Forms.dll!System.Windows.Forms.NativeWindow.DebuggableCallback(System.IntPtr hWnd, int msg = 514, System.IntPtr wparam, System.IntPtr lparam) + 0x75 bytes
[Native to Managed Transition]
[Managed to Native Transition]
System.Windows.Forms.dll!System.Windows.Forms.Application.ThreadContext.LocalModalMessageLoop(System.Windows.Forms.Form form = {System.Web.UI.Design.WebControls.AccessDataSourceWizardForm}) + 0x160 bytes
System.Windows.Forms.dll!System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(int reason = 4, System.Windows.Forms.ApplicationContext context = {System.Windows.Forms.Application.ModalApplicationContext}) + 0x1db bytes
System.Windows.Forms.dll!System.Windows.Forms.Application.ThreadContext.RunMessageLoop(int reason, System.Windows.Forms.ApplicationContext context) + 0x53 bytes
System.Windows.Forms.dll!System.Windows.Forms.Form.ShowDialog(System.Windows.Forms.IWin32Window owner) + 0x4ee bytes
Microsoft.VisualStudio.dll!Microsoft.VisualStudio.UIService.System.Windows.Forms.Design.IUIService.ShowDialog(System.Windows.Forms.Form form = {System.Web.UI.Design.WebControls.AccessDataSourceWizardForm}) + 0x75 bytes
System.Design.dll!System.Web.UI.Design.Util.UIServiceHelper.ShowDialog(System.IServiceProvider serviceProvider, System.Windows.Forms.Form form) + 0x3a bytes
System.Design.dll!System.Web.UI.Design.WebControls.SqlDataSourceDesigner.ConfigureDataSourceChangeCallback(object context) + 0xf7 bytes
System.Design.dll!System.Web.UI.Design.ControlDesigner.InvokeTransactedChange(System.IServiceProvider serviceProvider, System.ComponentModel.IComponent component = {System.Web.UI.WebControls.AccessDataSource}, System.Web.UI.Design.TransactedChangeCallback callback, object context, string description, System.ComponentModel.MemberDescriptor member = null) + 0x12a bytes
System.Design.dll!System.Web.UI.Design.ControlDesigner.InvokeTransactedChange(System.ComponentModel.IComponent component, System.Web.UI.Design.TransactedChangeCallback callback, object context, string description, System.ComponentModel.MemberDescriptor member) + 0x3f bytes
System.Design.dll!System.Web.UI.Design.ControlDesigner.InvokeTransactedChange(System.ComponentModel.IComponent component, System.Web.UI.Design.TransactedChangeCallback callback, object context, string description) + 0x2d bytes
System.Design.dll!System.Web.UI.Design.WebControls.SqlDataSourceDesigner.Configure() + 0x58 bytes
System.Design.dll!System.Web.UI.Design.DataSourceDesigner.DataSourceDesignerActionList.Configure() + 0xd bytes
[Native to Managed Transition]
[Managed to Native Transition]
System.Design.dll!System.ComponentModel.Design.DesignerActionMethodItem.Invoke() + 0x4a bytes
Microsoft.VisualStudio.Web.dll!Microsoft.VisualStudio.Web.DesignerActionPanel.MethodLine.OnLinkLabelLinkClicked(object sender, System.Windows.Forms.LinkLabelLinkClickedEventArgs e) + 0x33 bytes
System.Windows.Forms.dll!System.Windows.Forms.LinkLabel.OnLinkClicked(System.Windows.Forms.LinkLabelLinkClickedEventArgs e) + 0x6a bytes
System.Windows.Forms.dll!System.Windows.Forms.LinkLabel.OnMouseUp(System.Windows.Forms.MouseEventArgs e = {X = 61 Y = 5 Button = Left}) + 0x160 bytes
System.Windows.Forms.dll!System.Windows.Forms.Control.WmMouseUp(ref System.Windows.Forms.Message m, System.Windows.Forms.MouseButtons button, int clicks) + 0xf2 bytes
System.Windows.Forms.dll!System.Windows.Forms.Control.WndProc(ref System.Windows.Forms.Message m) + 0x544 bytes
System.Windows.Forms.dll!System.Windows.Forms.Label.WndProc(ref System.Windows.Forms.Message m) + 0x33 bytes
System.Windows.Forms.dll!System.Windows.Forms.LinkLabel.WndProc(ref System.Windows.Forms.Message msg) + 0x11 bytes
System.Windows.Forms.dll!System.Windows.Forms.Control.ControlNativeWindow.OnMessage(ref System.Windows.Forms.Message m) + 0xd bytes
System.Windows.Forms.dll!System.Windows.Forms.Control.ControlNativeWindow.WndProc(ref System.Windows.Forms.Message m) + 0xd6 bytes
System.Windows.Forms.dll!System.Windows.Forms.NativeWindow.DebuggableCallback(System.IntPtr hWnd, int msg = 514, System.IntPtr wparam, System.IntPtr lparam) + 0x75 bytes
Thanks.
Gerry -
Monday, February 13, 2006 10:42 PM
Gerry,
You've almost got it. What I want is the exception that occurs inbetween the two you gave me. I want the debugger to break right when it hits the exception that causes the "Object reference not set to an instance of an object." This should be after you've clicked "Test Query" but before the error dialog shows up. So get to the screen where you can click "Test Query" then enable catching all exceptions in the debugger. Now click "Test Query". It should break on at least one exception which is a NullReferenceException. This is the one I want the call stack for.
Thanks for persisting with me to figure out this problem!
Stephen
-
Monday, February 13, 2006 10:56 PMStephen,
That took some timing! How's this:
[Managed to Native Transition]
> System.Data.dll!System.Data.OleDb.OleDbEnumerator.GetEnumeratorReader(object value = null) + 0xa2 bytes
System.Data.dll!System.Data.OleDb.OleDbEnumerator.GetEnumeratorFromType(System.Type type) + 0x31 bytes
System.Data.dll!System.Data.OleDb.OleDbEnumerator.GetEnumerator(System.Type type) + 0x3d bytes
Microsoft.VisualStudio.DataTools.dll!Microsoft.VisualStudio.DataTools.Providers.OleDB.OleDBUtilities.GetRegisteredProviders() + 0x54 bytes
Microsoft.VisualStudio.DataTools.dll!Microsoft.VisualStudio.DataTools.Providers.OleDB.OleDBUtilities.ExpandProvider(string provider = "Microsoft.Jet.OLEDB.4.0") + 0x55 bytes
Microsoft.VisualStudio.DataTools.dll!Microsoft.VisualStudio.DataTools.Providers.OleDB.OleDBUtilities.GetDataSource(string provider) + 0x9a bytes
Microsoft.VisualStudio.DataTools.dll!Microsoft.VisualStudio.DataTools.Providers.OleDB.OleDBDataSourceSpecializer.DeriveDataSource(string connectionString = "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=\"C:\\Documents and Settings\\GPolk\\My Documents\\Web Projects\\DebraDavis\\Addictionology\\App_Data\\DavisSurvey.mdb\"") + 0x94 bytes
Microsoft.VisualStudio.DataTools.dll!Microsoft.VisualStudio.DataTools.DataServices.DataProvider.DeriveDataSource(string connectionString) + 0x27 bytes
Microsoft.VisualStudio.DataTools.dll!Microsoft.VisualStudio.DataTools.DataServices.DataConnection.SetConnectionStrings(string connectionString = "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=\"C:\\Documents and Settings\\GPolk\\My Documents\\Web Projects\\DebraDavis\\Addictionology\\App_Data\\DavisSurvey.mdb\"") + 0x2b bytes
Microsoft.VisualStudio.DataTools.dll!Microsoft.VisualStudio.DataTools.DataServices.DataConnection.DataConnection(Microsoft.VisualStudio.DataTools.DataServices.DataProvider provider, object providerObject) + 0x6d bytes
Microsoft.VisualStudio.DataTools.dll!Microsoft.VisualStudio.DataTools.DataServices.DataConnectionFactory.MakeDataConnectionFromImpl(System.Guid provider, object providerObj) + 0x3b bytes
Microsoft.VisualStudio.Data.dll!Microsoft.VisualStudio.Data.DataConnectionFactory.MakeDataConnectionFrom(System.Guid provider, object providerObj) + 0x25 bytes
Microsoft.VisualStudio.DataTools.dll!Microsoft.VisualStudio.DataTools.DataServices.DataConnectionFactory.Microsoft.VisualStudio.Data.Interop.IVsDataConnectionFactory.MakeDataConnectionFrom(ref System.Guid guidProvider, object punkProviderObject) + 0x23 bytes
Microsoft.VisualStudio.Web.dll!Microsoft.VisualStudio.Web.WebForms.DataEnvironment.System.ComponentModel.Design.Data.IDataEnvironment.GetDesignTimeConnection(System.ComponentModel.Design.Data.DesignerDataConnection connection) + 0xe2 bytes
System.Design.dll!System.Web.UI.Design.WebControls.SqlDataSourceDesigner.GetDesignTimeConnection(System.IServiceProvider serviceProvider, System.ComponentModel.Design.Data.DesignerDataConnection connection) + 0xa1 bytes
[Error occurs after this statement]
System.Design.dll!System.Web.UI.Design.WebControls.SqlDataSourceSummaryPanel.OnTestQueryButtonClick(object sender, System.EventArgs e) + 0x1e3 bytes
System.Windows.Forms.dll!System.Windows.Forms.Control.OnClick(System.EventArgs e) + 0x57 bytes
System.Windows.Forms.dll!System.Windows.Forms.Button.OnClick(System.EventArgs e) + 0x49 bytes
System.Windows.Forms.dll!System.Windows.Forms.Button.OnMouseUp(System.Windows.Forms.MouseEventArgs mevent = {X = 41 Y = 10 Button = Left}) + 0xc3 bytes
System.Windows.Forms.dll!System.Windows.Forms.Control.WmMouseUp(ref System.Windows.Forms.Message m, System.Windows.Forms.MouseButtons button, int clicks) + 0xf2 bytes
System.Windows.Forms.dll!System.Windows.Forms.Control.WndProc(ref System.Windows.Forms.Message m) + 0x544 bytes
System.Windows.Forms.dll!System.Windows.Forms.ButtonBase.WndProc(ref System.Windows.Forms.Message m) + 0xce bytes
System.Windows.Forms.dll!System.Windows.Forms.Button.WndProc(ref System.Windows.Forms.Message m) + 0x2b bytes
System.Windows.Forms.dll!System.Windows.Forms.Control.ControlNativeWindow.OnMessage(ref System.Windows.Forms.Message m) + 0xd bytes
System.Windows.Forms.dll!System.Windows.Forms.Control.ControlNativeWindow.WndProc(ref System.Windows.Forms.Message m) + 0xd6 bytes
System.Windows.Forms.dll!System.Windows.Forms.NativeWindow.DebuggableCallback(System.IntPtr hWnd, int msg = 514, System.IntPtr wparam, System.IntPtr lparam) + 0x75 bytes
[Native to Managed Transition]
[Managed to Native Transition]
System.Windows.Forms.dll!System.Windows.Forms.Application.ThreadContext.LocalModalMessageLoop(System.Windows.Forms.Form form = {System.Web.UI.Design.WebControls.AccessDataSourceWizardForm}) + 0x160 bytes
System.Windows.Forms.dll!System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(int reason = 4, System.Windows.Forms.ApplicationContext context = {System.Windows.Forms.Application.ModalApplicationContext}) + 0x1db bytes
System.Windows.Forms.dll!System.Windows.Forms.Application.ThreadContext.RunMessageLoop(int reason, System.Windows.Forms.ApplicationContext context) + 0x53 bytes
System.Windows.Forms.dll!System.Windows.Forms.Form.ShowDialog(System.Windows.Forms.IWin32Window owner) + 0x4ee bytes
Microsoft.VisualStudio.dll!Microsoft.VisualStudio.UIService.System.Windows.Forms.Design.IUIService.ShowDialog(System.Windows.Forms.Form form = {System.Web.UI.Design.WebControls.AccessDataSourceWizardForm}) + 0x75 bytes
System.Design.dll!System.Web.UI.Design.Util.UIServiceHelper.ShowDialog(System.IServiceProvider serviceProvider, System.Windows.Forms.Form form) + 0x3a bytes
System.Design.dll!System.Web.UI.Design.WebControls.SqlDataSourceDesigner.ConfigureDataSourceChangeCallback(object context) + 0xf7 bytes
System.Design.dll!System.Web.UI.Design.ControlDesigner.InvokeTransactedChange(System.IServiceProvider serviceProvider, System.ComponentModel.IComponent component = {System.Web.UI.WebControls.AccessDataSource}, System.Web.UI.Design.TransactedChangeCallback callback, object context, string description, System.ComponentModel.MemberDescriptor member = null) + 0x12a bytes
System.Design.dll!System.Web.UI.Design.ControlDesigner.InvokeTransactedChange(System.ComponentModel.IComponent component, System.Web.UI.Design.TransactedChangeCallback callback, object context, string description, System.ComponentModel.MemberDescriptor member) + 0x3f bytes
System.Design.dll!System.Web.UI.Design.ControlDesigner.InvokeTransactedChange(System.ComponentModel.IComponent component, System.Web.UI.Design.TransactedChangeCallback callback, object context, string description) + 0x2d bytes
System.Design.dll!System.Web.UI.Design.WebControls.SqlDataSourceDesigner.Configure() + 0x58 bytes
System.Design.dll!System.Web.UI.Design.DataSourceDesigner.DataSourceDesignerActionList.Configure() + 0xd bytes
[Native to Managed Transition]
[Managed to Native Transition]
System.Design.dll!System.ComponentModel.Design.DesignerActionMethodItem.Invoke() + 0x4a bytes
Microsoft.VisualStudio.Web.dll!Microsoft.VisualStudio.Web.DesignerActionPanel.MethodLine.OnLinkLabelLinkClicked(object sender, System.Windows.Forms.LinkLabelLinkClickedEventArgs e) + 0x33 bytes
System.Windows.Forms.dll!System.Windows.Forms.LinkLabel.OnLinkClicked(System.Windows.Forms.LinkLabelLinkClickedEventArgs e) + 0x6a bytes
System.Windows.Forms.dll!System.Windows.Forms.LinkLabel.OnMouseUp(System.Windows.Forms.MouseEventArgs e = {X = 61 Y = 5 Button = Left}) + 0x160 bytes
System.Windows.Forms.dll!System.Windows.Forms.Control.WmMouseUp(ref System.Windows.Forms.Message m, System.Windows.Forms.MouseButtons button, int clicks) + 0xf2 bytes
System.Windows.Forms.dll!System.Windows.Forms.Control.WndProc(ref System.Windows.Forms.Message m) + 0x544 bytes
System.Windows.Forms.dll!System.Windows.Forms.Label.WndProc(ref System.Windows.Forms.Message m) + 0x33 bytes
System.Windows.Forms.dll!System.Windows.Forms.LinkLabel.WndProc(ref System.Windows.Forms.Message msg) + 0x11 bytes
System.Windows.Forms.dll!System.Windows.Forms.Control.ControlNativeWindow.OnMessage(ref System.Windows.Forms.Message m) + 0xd bytes
System.Windows.Forms.dll!System.Windows.Forms.Control.ControlNativeWindow.WndProc(ref System.Windows.Forms.Message m) + 0xd6 bytes
System.Windows.Forms.dll!System.Windows.Forms.NativeWindow.DebuggableCallback(System.IntPtr hWnd, int msg = 514, System.IntPtr wparam, System.IntPtr lparam) + 0x75 bytes
Gerry -
Monday, February 13, 2006 11:11 PM
Gerry,
That's the one! The problem is in trying to enumerate the OLE DB data sources on your machine. I can't tell you what the problem is, but I'll pass this thread on to someone that may be able to help you.
Thanks again for working with me to isolate the problem.
Stephen
-
Wednesday, February 15, 2006 12:54 AM
Gerry,
I spoke with Stephen about the problem you're having. I saw the posts that noted that you are able to access the Access database via an OleDbDataAdapter. I agree with Stephen's belief that the problem is due to an issue with the component that enumerates OLE DB services.
There are two things I'd like you to try, to try to determine which component is failing.
Try executing the following code, which should mimic the code running inside of VWDExpress, to generate the list of available OLE DB providers:
Guid guid = new Guid("{C8B522D0-5CF3-11ce-ADE5-00AA0044773D}");
Type type = Type.GetTypeFromCLSID(guidOleDbEnum);
using (OleDbDataReader rdr = OleDbEnumerator.GetEnumerator(type))
{
while (rdr.Read())
Console.WriteLine(rdr[0]);
}
Try using the native OLE DB dialog through COM interop in your project. First you'll need to add a reference to Microsoft OLE DB Service Component 1.0 Type Library, which is on the COM tab in the References dialog. Then try executing the following code:
MSDASC.DataLinksClass datalinks = new MSDASC.DataLinksClass();
datalinks.PromptNew();
Please let me know what you find when you've had a chance to run the code. Understanding which component(s) are failing should make it easier to determine how to fix the problem.
-
Wednesday, February 15, 2006 8:35 PMDavid,
Test 1 results. Following was output:
MediaCatalogDB OLE DB Provider
SQLOLEDB
DTSPackageDSO
SQLReplication.OLEDB
MediaCatalogMergedDB OLE DB Provider
Microsoft.ISAM.OLEDB.1.1
MSDMine
MSDataShape
SQLNCLI Enumerator
ADsDSOObject
MediaCatalogWebDB OLE DB Provider
SQLNCLI
MSDMine Enumerator
MSOLAP
MSOLAP
MSDAIPP.DSO
MSDASQL
MSDASQL Enumerator
MSUSP
Microsoft.Jet.OLEDB.4.0
SQLOLEDB Enumerator
MSDAOSP
MSDAORA
MSIDXS
Test 2 results:
A "Data Link Properties" window displayed with 4 tabs "Provider", "Connection", "
Advanced", "All". Default selection was "Microsoft OLE DB Provider for ODBC
Drivers"
Thanks.
Gerry -
Thursday, February 16, 2006 6:42 PM
Thanks, Gerry.
I'm surprised that the code that calls OleDbEnumerator.GetEnumerator succeeds where VWDExpress fails. Stephen is taking a closer look at the VWDExpress code.
-
Tuesday, February 21, 2006 10:12 PMI really think this has something to do with the IDE not being able to make a
connection to the Access DB. One reason I say this is because when I have an
Access DB in the App_Data folder the DB does not appear in the Database
Explorer. On the working machine, the DB does appear after being added to the
App_Data folder (added outside the IDE). I did not have to perform and "Add Connection"
to be able to see and read the Access file. I assume that this is the correct
disposition.
Gerry -
Tuesday, February 21, 2006 10:36 PM
Gerry,
Maybe you can run the same debugging technique on this scenario that you describe. The likelyhood is that between the time that you add the Access DB in the App_Data folder and the time it does not show up in Database Explorer, some exception(s) is being thrown but it is eaten so you never see it. One of these exceptions will be the reason why it doesn't get added. If you don't see this, then I will need to bring in the owners of the project system to find out why it's not even asking us to open the connection to begin with.
Thanks,
Stephen -
Thursday, February 23, 2006 9:53 PMStephen,
The following exceptions appeared in the CLR debugger (immediate window):
First time the web app is opened in IDE following appears in CLR debugger
immediate window:
A first chance exception of type 'System.ArgumentException' occurred in mscorlib.dll
A first chance exception of type 'System.NullReferenceException' occurred in Microsoft.VisualStudio.DataTools.dll
A first chance exception of type 'System.NullReferenceException' occurred in Microsoft.VisualStudio.DataTools.dll
A first chance exception of type 'System.NullReferenceException' occurred in Microsoft.VisualStudio.DataTools.dll
A first chance exception of type 'System.NullReferenceException' occurred in Microsoft.VisualStudio.DataTools.dll
When Database Explorer is selected and "refresh" is clicked (Access mdb is in App_Data
but is not showing in DB Explorer) the following appears in CLR debugger:
A first chance exception of type 'System.Data.SqlClient.SqlException' occurred in System.Data.dll
A first chance exception of type 'System.Data.SqlClient.SqlException' occurred in System.Data.dll
A first chance exception of type 'System.Data.SqlClient.SqlException' occurred in System.Data.dll
A first chance exception of type 'System.Data.SqlClient.SqlException' occurred in System.Data.dll
A first chance exception of type 'System.Data.SqlClient.SqlException' occurred in Microsoft.VisualStudio.DataTools.dll
A first chance exception of type 'System.MissingMethodException' occurred in mscorlib.dll
A first chance exception of type 'System.MissingMethodException' occurred in mscorlib.dll
A first chance exception of type 'System.MissingMethodException' occurred in mscorlib.dll
A first chance exception of type 'System.MissingMethodException' occurred in mscorlib.dll
A first chance exception of type 'System.Runtime.InteropServices.COMException' occurred in Microsoft.VSDesigner.dll
The above occurs only the first time when "refresh" is clicked. All subsequent "
refresh" clicks produce the following:
A first chance exception of type 'System.Runtime.InteropServices.COMException' occurred in Microsoft.VSDesigner.dll
Thanks.
Gerry -
Thursday, February 23, 2006 10:10 PM
Gerry,
Can you clarify at which point you are adding the Access DB to your project. I think that one set of exceptions you have given is the right one (probably the first), and for this one I'll need to ask you to provide callstacks again to identify exactly where the problem occurs.
Thanks,
Stephen -
Thursday, April 27, 2006 2:00 AM
This is a long story. There has to be something wrong with the IDE's use of the data provider. Just look at this dialog. I have not found any other discussion about this issue.
See my URL... http://www.jpbsolve.com/images/AddConnection.JPG
Jeff Belnap
-
Thursday, April 27, 2006 2:36 PM
I'm having the same problem as the other users with VB 2005 Express. See the screenshot of Jeff Belnap.
I have uninstalled SQL server express and VB express, rebooted, reinstalled VB Express (and skipped sql server since I will not be using that). I am trying to connect to an Access database by clicking on "Add New Data Source" in the Data sources window. After I choose "Microsoft Access Database File (OLE DB)" as the data source, I get the same windows as in Jeff's screenshot.
When I try the same on a different computer (also running Windows XP Prof. SP2) it works just fine (I can then point to a database file).
Any idea how to solve this?
Regards,
Marco -
Thursday, April 27, 2006 4:38 PM
Hi all,
You have re-initiated my interest in this thread now that I see multiple people are having this problem. I tried narrowing the problem down by working with Gerry to get some call stacks, but this didn't help much. So let me try a different method. Did any of you have a working machine which started not working? If so, what kinds of applications did you install/uninstall between the time that it worked and the time it stopped working?
The issue is most likely to be a setup problem, where after you uninstall some application, registry entries for the Access OLE DB provider get corrupted and it is unable to identify that the provider is installed on the machine. But I can't identify exactly what you might need to do to fix the problem.
Thanks,
Stephen -
Thursday, April 27, 2006 7:54 PM
Hi Stephen,
I have a working machine at home and a non-working machine at the office. At the office I uninstalled all VB and SQL software. I even tried uninstalling MyODBC, because I thought that might be the cause.
After reinstalling VBE the problem still exists. I rebooted the machine after every uninstall or install.
If there's anything I can do to help searching for a solution, please let me know.
Regards,
Marco -
Sunday, April 30, 2006 11:48 AM
Hi Stephen,
I've got two machines with exactly the same problem.
The "App_Data -> Add Existing Item -> db.mdb",
"AccessDataSource -> Configure Data Source -> Query Builder" and
"Database Explorer -> Add Connection -> Microsoft Access Database File",
don't work as it used to before I've installed (on both machines):ASP.NET “Atlas” April Community Technology Preview (CTP) and
"Clean Up Scan" from Windows Live Safety Center to "remove invalid registry items" (safety.live.com)
It does not matter if it is project created before these installations or new one. I get the same errors every time (with different Access databases):"Object Reference is not set to an instance of an object" (when I use Add Existing Item -> db.mdb in VWD 2005 Express Edition or Visual C# 2005 Express Edition)
and
"Format of the initialization string does not conform to specification starting at index 0" (when I use Add Connection in VWD 2005 Express Edition).
The interesting thing is that the Gridview and AccessDataSource I created in VWD 2005 Express before this problem occurred work ok when I run my project. The different is that I can not configure the AccessDataSource and add Access Database (what was possible before).
Regards,
Patryk -
Monday, May 01, 2006 7:11 AM
Hi
Just wanted to let you know that I have the same problem, so I am following this thread with great interest.
When using Add Connection there is no option to browse to an existing access db and the error "Format of the initialization string does not conform to specification starting at index 0" when specifying the connection string.
Will not be able to help much as I am quite new to this. I just hope an answer can be found asap so I can continue my project.
Regards
Pete
-
Monday, May 01, 2006 4:40 PM
Hi Patryk,
Thanks for the information. Have you tried uninstalling the Atlas CTP? My guess is that installing that CTP cause some registry items that are actually valid to seem invalid to the "Clean Up Scan" utility, and what you are left with is an incomplete set of registry entries.
I will look into this scenario and see if I can reproduce the issue.
Thanks,
Stephen -
Tuesday, May 02, 2006 7:40 AM
Hi Stephen,
Now, I know it's not because of Atlas CTP. I'm sure because I haven't installed it on my third machine (at work) and I have the same problem. So, there is only one software I have used on all of my machines: Windows Live Safety Scanner - "Clean Up Scan"
Patryk
-
Tuesday, May 02, 2006 4:38 PM
Thanks Patryk - that certainly seems like a program that might cause some problems in the registry. We are looking into this and will see if we can reproduce the issue after running this tool.
Thanks,
Stephen -
Tuesday, May 02, 2006 5:04 PM
Hi everyone,
I have determined what seems to be causing the problem, but I would like to verify that this is the cause for all of you that have seen the problem.
Please run regedit.exe and browse to the following location in the tree:
HKEY_CLASSES_ROOT\CLSID\{F9AE8980-7E52-11d0-8964-00C04FD611D7}
Underneath this key should be a sub-key called "ProgID" with a value of "MSIDXS.1". If you can't find this, it is causing the problem you are seeing. Adding this back should fix the issue.
Please let me know if this does not solve the problem. We will see if it is possible to fix the code that makes some assumptions about the existence of this key to have some default behavior that works even if it does not exist.
Thanks,
Stephen- Proposed As Answer by Rudedog2MVP Monday, February 08, 2010 5:26 PM
-
Tuesday, May 02, 2006 5:48 PMGreat! In my case 100% success! Thank you Stephen.
So, is it time to stop using Microsoft Live "Clean Up Scan"?
Thanks,
Patryk -
Tuesday, May 02, 2006 6:04 PM
Hi Patryk,
Glad that got it working for you. I don't know why the registry cleaner is removing that specific registry key - it is probably a bug in the beta version. I'll follow up with that team to see if they know why. There's no reason to stop using it, you'll just probably need to re-add that registry key after running it each time.
Thanks,
Stephen -
Tuesday, May 02, 2006 8:58 PM
Hello Stephen,
This solution does not work for me, unfortunately. I still get the same message: "Format of the initialization string does not conform to specification starting at index 0."
Any ideas how to solve this yet?
Regards,
Marco -
Tuesday, May 02, 2006 9:03 PM
Marco,
Was the registry key I mentioned missing on your machine? Does the correct UI at least show up now?
Thanks,
Stephen -
Tuesday, May 02, 2006 9:12 PM
Stephen
The registry key I see at HKEY_CLASSES_ROOT\CLSID\{F9AE8980-7E52-11d0-8964-00C04FD611D7} is:
Standaard (Dutch for Standard) with value MSIDXS
Like this:
Windows Registry Editor Version 5.00
[HKEY_CLASSES_ROOT\CLSID\{F9AE8980-7E52-11d0-8964-00C04FD611D7}]
@="MSIDXS"[HKEY_CLASSES_ROOT\CLSID\{F9AE8980-7E52-11d0-8964-00C04FD611D7}\ExtendedErrors]
@="Extended Error Service"[HKEY_CLASSES_ROOT\CLSID\{F9AE8980-7E52-11d0-8964-00C04FD611D7}\ExtendedErrors\{F9AE8981-7E52-11d0-8964-00C04FD611D7}]
@="MSIDXS Error Lookup"[HKEY_CLASSES_ROOT\CLSID\{F9AE8980-7E52-11d0-8964-00C04FD611D7}\InprocServer32]
@="C:\\WINDOWS\\system32\\query.dll"
"ThreadingModel"="Both"[HKEY_CLASSES_ROOT\CLSID\{F9AE8980-7E52-11d0-8964-00C04FD611D7}\OLE DB Provider]
@="Microsoft OLE DB Provider for Indexing Service"[HKEY_CLASSES_ROOT\CLSID\{F9AE8980-7E52-11d0-8964-00C04FD611D7}\VersionIndependentProgID]
@="MSIDXS"So this is not exactly as you described it. But then again, this is my machine at home where everything is working fine... Sorry I did not think of that before. I will look at this when I'm in the office tomorrow morning.
If there's anything else you want me to check, please let me know.
Thanks,
Marco -
Wednesday, May 03, 2006 2:41 AM
Hi Stephen,
Did not work for me either.
The key exists in my registry but I am still getting the same message as Marco.
I regularly use a clean up program called "WinTools.net" to clean out redundant files and supposedly invalid registry entries, so maybe something else has been inadvertantly cleaned up.
Regards,
Pete
-
Wednesday, May 03, 2006 7:12 AM
Stephen,
I just checked the machine at the office, the one where it is not working (I do not get the correct UI). The registry key you mentioned does exist. See this:
Windows Registry Editor Version 5.00
[HKEY_CLASSES_ROOT\CLSID\{F9AE8980-7E52-11d0-8964-00C04FD611D7}]
@="MSIDXS"[HKEY_CLASSES_ROOT\CLSID\{F9AE8980-7E52-11d0-8964-00C04FD611D7}\ExtendedErrors]
@="Extended Error Service"[HKEY_CLASSES_ROOT\CLSID\{F9AE8980-7E52-11d0-8964-00C04FD611D7}\ExtendedErrors\{F9AE8981-7E52-11d0-8964-00C04FD611D7}]
@="MSIDXS Error Lookup"[HKEY_CLASSES_ROOT\CLSID\{F9AE8980-7E52-11d0-8964-00C04FD611D7}\InprocServer32]
@="C:\\WINDOWS\\System32\\query.dll"
"ThreadingModel"="Both"[HKEY_CLASSES_ROOT\CLSID\{F9AE8980-7E52-11d0-8964-00C04FD611D7}\OLE DB Provider]
@="Microsoft OLE DB Provider for Indexing Service"[HKEY_CLASSES_ROOT\CLSID\{F9AE8980-7E52-11d0-8964-00C04FD611D7}\VersionIndependentProgID]
@="MSIDXS"Any other keys I should check?
Regards,
Marco -
Wednesday, May 03, 2006 7:46 AM
Hi Marco,
I have solved this problem adding:
[HKEY_CLASSES_ROOT\CLSID\{F9AE8980-7E52-11d0-8964-00C04FD611D7}\ProgID]
@="MSIDXS.1"So now, it looks like:
Windows Registry Editor Version 5.00
[HKEY_CLASSES_ROOT\CLSID\{F9AE8980-7E52-11d0-8964-00C04FD611D7}]
@="MSIDXS"[HKEY_CLASSES_ROOT\CLSID\{F9AE8980-7E52-11d0-8964-00C04FD611D7}\ExtendedErrors]
@="Extended Error Service"[HKEY_CLASSES_ROOT\CLSID\{F9AE8980-7E52-11d0-8964-00C04FD611D7}\ExtendedErrors\{F9AE8981-7E52-11d0-8964-00C04FD611D7}]
@="MSIDXS Error Lookup"[HKEY_CLASSES_ROOT\CLSID\{F9AE8980-7E52-11d0-8964-00C04FD611D7}\InprocServer32]
@="C:\\WINDOWS\\system32\\query.dll"
"ThreadingModel"="Both"[HKEY_CLASSES_ROOT\CLSID\{F9AE8980-7E52-11d0-8964-00C04FD611D7}\OLE DB Provider]
@="Microsoft OLE DB Provider for Indexing Service"[HKEY_CLASSES_ROOT\CLSID\{F9AE8980-7E52-11d0-8964-00C04FD611D7}\ProgID]
@="MSIDXS.1"[HKEY_CLASSES_ROOT\CLSID\{F9AE8980-7E52-11d0-8964-00C04FD611D7}\VersionIndependentProgID]
@="MSIDXS"
Regards
Patryk- Proposed As Answer by UldisV Friday, May 08, 2009 8:21 AM
-
Wednesday, May 03, 2006 8:42 AM
Hello Patryk,
Yes, it works! Thanks a lot!
I added this key to the registry and now I see the the correct UI when I try to add a new connection to a MSAccess database.Only question is: Why was this registry entry missing?
Regards,
Marco -
Wednesday, May 03, 2006 2:25 PMI'm sorry to say that I had given up. The "HKEY_CLASSES_ROOT\CLSID\{F9AE8980-7E52-11d0-8964-00C04FD611D7}" solution did solve the problem for me. Halleluiah !!
Gerry -
Wednesday, May 03, 2006 5:39 PM
Hi Pete,
I tried using WinTools.net to clean the registry and I can reproduce the problem, but it is because the same registry key I already pointed out was being removed. Just to be sure you tried out the right thing, let me be more explicit about the steps in examining and modifying the registry.
To examine the registry:
1) Run regedit.exe;
2) Browse to the location "HKEY_CLASSES_ROOT\CLSID\{F9AE8980-7E52-11d0-8964-00C04FD611D7}" in the tree;
3) If there is a child node in the tree called "ProgID", then you are indeed experiencing a different problem - let me know if this is the case.Otherwise, follow these steps to modify the registry:
1) Right click the node and select "New > Key";
2) Enter "ProgID" as the name;
3) Go to the main window and double click "(Default)";
4) Enter the value "MSIDXS.1";Now if you run Visual Studio, it should be working.
Thanks,
Stephen -
Wednesday, May 03, 2006 10:02 PM
Hi Stephen
Sorry, I had not seen your reply to Marco, forgot to refresh the page before posting. I was also looking at the registry value under the VersionIndependentProgID node.
Adding the new key has solved the problem and I can now select and add a new Access db to my project.
Does this mean though, that if I continue to use WinTools.net to clean the registry this problem might happen again?
Many thanks for your help.
Regards,
Pete
-
Wednesday, May 03, 2006 10:23 PM
Hi Pete,
Glad it solved the problem. It seems there is a problem in the setup of this MSIDXS provider (I don't know much at all about it) that even when set up correctly, registry cleanup programs think the ProgID is orphaned and thus safe to remove. So if you continue to use WinTools.net it will continue to clean away this ProgID. I think I saw an option to to exclude certain keys or names; if you add this key there, then it might stop cleaning it up.
Stephen
-
Sunday, June 11, 2006 7:43 PM
The fix also corrected the problem for me.
Thanks a million...
-
Tuesday, July 11, 2006 6:30 PMthanks a lot Stephen it rescued my whole project.
-
Wednesday, August 02, 2006 1:19 PMThanks alot!!!
-
Wednesday, August 23, 2006 10:00 PM
3 cheers for Stephen!
I've been having this same issue and have been looking around and asking around on a bunch of forums (including this one - I wish the search engine would've worked better
). Someone on a different forum pointed me to this thread and I'm happy to say this worked for me too. I was using RegVac. -
Tuesday, September 19, 2006 2:11 AMWell done. I had the same error trying to connect to an old SQL 7 db. Adding this subkey fixed the problem. THANK YOU!!!
-
Monday, September 25, 2006 12:37 PM
Thank you, Stephen and all.
The registry key fix worked for me. I had previous run regclean.exe - might this have caused the problem to occur?
-
Monday, October 23, 2006 8:33 PMI have the same or similar problem, but I have the MSIDXS.1 in my Registry. Is there anything else?
-
Thursday, November 02, 2006 11:37 PMI was getting the same error message. I checked my registry and found it was set as suggested above. The error occurred on some projects but not on others. After a bit of investigation I figured that I only got this error message in projects with no classes in the "root" directory of the project. I only got this error message in projects where all of the classes are in sub-directories. To get round this I simply added a dummy empty class to the root at KABOOM it worked!
-
Wednesday, December 13, 2006 10:06 PMThis worked for me as well. Could probably remove the tangents from this thread to make it easier to get the solution.
-
Tuesday, January 09, 2007 8:38 AMI was having this problem, and adding the ProgID key to the registry solved the problem. I am using WinCleaner as there seems to be a common view that registry cleaners are removing the necessary key(s).
-
Thursday, February 08, 2007 8:46 PM
I would like to say thanks. I also solved my issue with this registry entry. Long term solution - What is causing this issue? Why the reg cleaners are removing this entry? Why it is found to orphaned reg key?
Thanks
Jansen
-
Wednesday, February 21, 2007 1:59 PM
Hi,
Thanks for this. I have spent 2 nights trying to work out why something that I thought worked the other day no longer did. I have in the meantime run the Windows Live cleanup tool. Added the key back in the registry and voila! it all worked again.
The frustrating thing is that there are several other posts where this problem has been explained explicitly and the "so called experts" have been ignoring what the users with this problem are writing. They have not been addressing the problem.
Thankfully you have, your solution is very much appreciated.
I cannot thank you enough!
Greg J
-
Monday, February 26, 2007 6:14 AM
Hi,
I experienced the same problem using SQL Server 2000. There appears a green mark in the break line (...Instead of yellow, as we are familier with). Now my questions are: what does the green mark mean for vb.net debugging(it will be found only selecting all BREAK options in Debug>Exception in the .net IDE menu)? and of course the solution for the problem.
I have tried in the following location
HKEY_CLASSES_ROOT\CLSID\{F9AE8980-7E52-11d0-8964-00C04FD611D7}
for the sub-key called "ProgID" with a value of "MSIDXS.1" and it is found. But still the problem persists.
please help.
thanks
-
Tuesday, June 12, 2007 2:49 AM
Thanks for this tip. For me the problem showed when I tried to add an MS Access database as a datasource. I chose a new connection and tried to use an MS Access database file it show a dialog screen with just a place to enter the connection string instead of the choose database dialog box that I get with other pcs. I checked the registry as suggested and did have an entry called programindepentProgID, but the value was missing the .1 at the end. I added the .1 to the end of the key value and also added the registry key of ProgID as suggested. The correct dialog box now displays and I can build the datasource.
I know the response was long, but I wanted to describe the exact problem so other people having the same problem could find the answer easier than I did.
-
Wednesday, June 13, 2007 10:14 PMVery Helpful! Thanks!
-
Friday, July 13, 2007 4:11 AM
Hi Steven,
I am having this problem couple days now. I went through all the previous check made here with no results.
My installation is Visual C# 2005 Express Edition, my OS is Windows XP with SP2.
I also try by installing MDAC 2.8 SDK.
The registry key for F9AE8980-7E52-11d0-8964-00C04FD611D7 is according to your specs (ProgID with MSIDXS.1).
When try to use the Jet 4.0 provider in connection string it returns with the initialization failure at String 0.
When running this test:
Guid mygui = new Guid("C8B522D0-5CF3-11ce-ADE5-00AA0044773D");
Type mytype = Type.GetTypeFromCLSID(mygui);
using (OleDbDataReader rdr = OleDbEnumerator.GetEnumerator(mytype)){
while (rdr.Read()) Console.WriteLine(rdr[0]);}
I get this error: "Error creating COM instance componnet with CLSID {C8B522D0-5CF3-11CE-ADE5-00AA0044773D} from IClassFactory deu to following error: 80040154"
The Second test works fine.
Can you please, Help
Thanks
-
Thursday, July 19, 2007 10:15 PM
Hi, I'm currently experiencing the same issue. All my registry keys are as described in these posts, but the wizard is still not working correctly. Is there another way to fix this issue?
-
Friday, July 27, 2007 7:43 AM
Hi,
I just followed this tread becouse I had the same problem but now evrything works fine again.
Thanks all.
Rob
-
Monday, September 17, 2007 7:40 AM
Great!! This worked for me. I'm using Visual Studio 2008 Beta 2 with Vista Ultimate.
Many thanks.
n1kh3l
-
Thursday, October 04, 2007 6:55 PM
Thank You. Although its been over a year later, I just ran into this problem. The solution that you offered worked completely (100%)
Thanks again,
John
-
Wednesday, October 24, 2007 6:16 PM
sorry for tagging to your post
if you have read all the post and still got a problem
do this check your system date in the task bar if the date is set before 2007 it causes the same problem
thats the problem i had and is now fixed
-
Monday, November 05, 2007 4:46 AM
I'm having the same problem, and also I have the registry key that is missing, but still have same behaivor when I trying to create a new DataSet from Wizard.
And when I try to open one dataset previuos created I'm getting this error:
Failed to load dataset because of the following error:
The system cannot find the specified file
Does anyone know something about this kind of problem?
-
Thursday, November 08, 2007 7:53 PMHi Richard,
I'm getting the same error "Error creating COM instance componnet with CLSID {C8B522D0-5CF3-11CE-ADE5-00AA0044773D}........"
Was this ever resolved? Can you tell me as I've been researching and nobody can help at all? -
Tuesday, November 13, 2007 2:11 PM
I am getting this error message, but I have the registry key and do not use a registry cleaner. Any other suggestions?
Thanks,
Ben
-
Thursday, December 20, 2007 3:38 AM
My situation is the same only with Access 2000. I also have uninstalled and re-installed both programs. No good. Funny thing is it was working at one point on this computer.
-
Thursday, December 20, 2007 2:39 PM
hwmjr - give the registry solution a shot. I had this problem about 5 years ago w/ Access and had no idea why my computer didn't follow the wizard example in the book. NOW I know what it was because I used a registry cleaner back then too.
Good luck!
-
Tuesday, January 08, 2008 9:20 AM
Simply fantastic.
Resolved a 2-day stop.
I used CCleaner for cleaning.
Thanks.
Luigi
-
Wednesday, February 06, 2008 6:04 PM
Stephen Provine wrote: Hi everyone,
I have determined what seems to be causing the problem, but I would like to verify that this is the cause for all of you that have seen the problem.
Please run regedit.exe and browse to the following location in the tree:
HKEY_CLASSES_ROOT\CLSID\{F9AE8980-7E52-11d0-8964-00C04FD611D7}
Underneath this key should be a sub-key called "ProgID" with a value of "MSIDXS.1". If you can't find this, it is causing the problem you are seeing. Adding this back should fix the issue.
Please let me know if this does not solve the problem. We will see if it is possible to fix the code that makes some assumptions about the existence of this key to have some default behavior that works even if it does not exist.
Thanks,
Stephen
Wonderful! - after a whole day spent repairing MDAC and re-installing Visual Studio - all to no avail - this fix worked immediately.
Thanks, Stephen -
Friday, February 08, 2008 6:24 PM
I had the same problem and it worked too. It is just like you said "it is time to stop using Microsoft Live Clean Up Scan" and any other registry cleaner.
Thanks everybody who helped solving this problem.
-
Wednesday, March 12, 2008 5:47 AM
I installed Visual Basic 2008 Express edition on my laptop. Whenever I try to open the "Database Connection Wizard" from any project, the wizard fails to open and I get an error message "the error log is full." The very same version runs fine on my Desktop PC. I did check the registry for the value suggested in this thread and it is there on my laptop. Any Sugestions?
-
Sunday, June 08, 2008 11:51 AMI had the same problem with the Add Data Source dialog not displaying correctly. I tried numerous updates and new components. Nothing worked.
The registry key addition fixed it in a matter of minutes. Thanks for that suggestion. -
Friday, January 23, 2009 10:28 PM
Thanks, the registry ky works for me.
Programming will be easier now :)
++
-
Friday, February 06, 2009 7:08 PMI was having the same bloody problem with add connection wizard not showing up everything as supposed. The problem was in the registry values carelessly deleted by System Cleaner 5 software. I restored the registry backup, and everything went fine again.
-
Thursday, May 07, 2009 2:43 AMI was having the same problem... it appeared out of the blue. The Registry Key fix worked. Thanks
-
Thursday, December 24, 2009 7:12 PMHere it is, 3 1/2 years later, I'm running Vista and using VS 8 and this STILL resolved my problem. THANKS!!!!
-
Monday, February 08, 2010 4:47 PMFantastic Stephen, thanks very much for this. This post has saved my bacon twice and is now a permanent fixture in my favorites :D
-
Wednesday, September 22, 2010 7:02 PMWhat is the difference between ProgID >> MSIDXS.1 (suggested here) and REG_SZ >> MSIDXS Error Lookup? I have the latter on my computer.
