Friday, March 30, 2012
Migrating Foxpro table with memo fields to SQL Server
Here is the issue : Getting error while transferring
foxpro data with memo fields. If I omit memo field, its
fine.
Could anyone know, how can I overcome this issue ?
Thanks in advance,
SKHow are you importing the data? Which version of FoxPro? What's the error
message?
The Visual FoxPro ODBC Driver supports memo fields (upto at least Fox 6.0)
and the DTS Import Wizard will automatically import them as Text columns if
you let it create the table for you. Fox 7.0 and 8.0 come with the newer
OLEDB driver. I haven't tried it with memo fields in DTS but I would expect
it to support Memo since the older driver does.
--
David Portas
--
Please reply only to the newsgroup
--
migrating DTS TO SSIS
Hi ,
Getting error even remove Text (Source) task in DTS.
Pl. help me .
Thanks,
Raja
Error:
LogID=23
#Time=11:32 AM
#Level=DTSMW_LOGLEVEL_ERR
#Source=Microsoft.SqlServer.Dts.MigrationWizard.Framework.Framework
#Message=Microsoft.SqlServer.Dts.Runtime.DtsRuntimeException: Failed to save package file "C:\PONE_SSIS_PACKAGES\PONE_SSIS_SELLTHRU\PONE_DTS_SELLTHRU_TEST.dtsx" with error 0x80004005 "Unspecified error".
> System.Runtime.InteropServices.COMException (0xC001100E): Failed to save package file "C:\PONE_SSIS_PACKAGES\PONE_SSIS_SELLTHRU\PONE_DTS_SELLTHRU_TEST.dtsx" with error 0x80004005 "Unspecified error".
at Microsoft.SqlServer.Dts.Runtime.Wrapper.ApplicationClass.SaveToXML(String FileName, IDTSPersist90 pPersistObj, IDTSEvents90 pEvents)
at Microsoft.SqlServer.Dts.Runtime.Application.SaveToXml(String fileName, Package package, IDTSEvents events)
End of inner exception stack trace
at Microsoft.SqlServer.Dts.Runtime.Application.SaveToXml(String fileName, Package package, IDTSEvents events)
at Microsoft.SqlServer.Dts.MigrationWizard.DTS9HelperUtility.DTS9Helper.SaveToXML(Package pkg, String sFileLocation)
at Microsoft.SqlServer.Dts.MigrationWizard.Framework.Framework.StartMigration(PackageInfo pInfo)
I cannot help you with your specific issue but I recomend that you do not use the DTS SSIS migration wizard. I have tried it several times but it ended with creating new SSIS packages from scratch...
/Erik
|||
Here are some other resources taht talk about DTS-SSIS migration:
http://www.google.com/search?hl=en&q=dts+to+ssis+migration
http://forums.microsoft.com/MSDN/Search/Search.aspx?words=DTS+migration&localechoice=9&SiteID=1&searchscope=forumscope&ForumID=80
|||Hi Raja,
Did you get it fixed ? I have the similar issue scratching my head arround for several hrs.
Regards,
Rahim.
|||Hi Rahim,
I started new SSIS and copy and paste to create second SSIS. It is easy way to start than DTS to SSIS migration. I don't find any DTS to SSIS conversion with out error.
Regards,
Raja
|||
we found that embedding legacy DTS packages in SSIS worked fine. Just create a new package and add an "Execute DTS 2000 Package Task". You can then load the old package in and embed it permenantly. We've had no problems running our old packages in this way Going forward we will rewrite as and when required.
Good luck.
|||Hi Jez,
Thanks a lot for your response. I did as you suggested and it worked.
Regards,
Rahim
|||Hi Raja,
Greetings!
Thank you for your response. Since we have many packages and some of them are big we couldn't copy and paste it.
Instead we created new SSIS package and then added the problem packages as DTS 2000 tasks.
Regards,
Rahim.
migrating DTS TO SSIS
Hi ,
Getting error even remove Text (Source) task in DTS.
Pl. help me .
Thanks,
Raja
Error:
LogID=23
#Time=11:32 AM
#Level=DTSMW_LOGLEVEL_ERR
#Source=Microsoft.SqlServer.Dts.MigrationWizard.Framework.Framework
#Message=Microsoft.SqlServer.Dts.Runtime.DtsRuntimeException: Failed to save package file "C:\PONE_SSIS_PACKAGES\PONE_SSIS_SELLTHRU\PONE_DTS_SELLTHRU_TEST.dtsx" with error 0x80004005 "Unspecified error".
> System.Runtime.InteropServices.COMException (0xC001100E): Failed to save package file "C:\PONE_SSIS_PACKAGES\PONE_SSIS_SELLTHRU\PONE_DTS_SELLTHRU_TEST.dtsx" with error 0x80004005 "Unspecified error".
at Microsoft.SqlServer.Dts.Runtime.Wrapper.ApplicationClass.SaveToXML(String FileName, IDTSPersist90 pPersistObj, IDTSEvents90 pEvents)
at Microsoft.SqlServer.Dts.Runtime.Application.SaveToXml(String fileName, Package package, IDTSEvents events)
End of inner exception stack trace
at Microsoft.SqlServer.Dts.Runtime.Application.SaveToXml(String fileName, Package package, IDTSEvents events)
at Microsoft.SqlServer.Dts.MigrationWizard.DTS9HelperUtility.DTS9Helper.SaveToXML(Package pkg, String sFileLocation)
at Microsoft.SqlServer.Dts.MigrationWizard.Framework.Framework.StartMigration(PackageInfo pInfo)
I cannot help you with your specific issue but I recomend that you do not use the DTS SSIS migration wizard. I have tried it several times but it ended with creating new SSIS packages from scratch...
/Erik
|||
Here are some other resources taht talk about DTS-SSIS migration:
http://www.google.com/search?hl=en&q=dts+to+ssis+migration
http://forums.microsoft.com/MSDN/Search/Search.aspx?words=DTS+migration&localechoice=9&SiteID=1&searchscope=forumscope&ForumID=80
|||Hi Raja,
Did you get it fixed ? I have the similar issue scratching my head arround for several hrs.
Regards,
Rahim.
|||Hi Rahim,
I started new SSIS and copy and paste to create second SSIS. It is easy way to start than DTS to SSIS migration. I don't find any DTS to SSIS conversion with out error.
Regards,
Raja
|||
we found that embedding legacy DTS packages in SSIS worked fine. Just create a new package and add an "Execute DTS 2000 Package Task". You can then load the old package in and embed it permenantly. We've had no problems running our old packages in this way Going forward we will rewrite as and when required.
Good luck.
|||Hi Jez,
Thanks a lot for your response. I did as you suggested and it worked.
Regards,
Rahim
|||Hi Raja,
Greetings!
Thank you for your response. Since we have many packages and some of them are big we couldn't copy and paste it.
Instead we created new SSIS package and then added the problem packages as DTS 2000 tasks.
Regards,
Rahim.
migrating DTS TO SSIS
Hi ,
Getting error even remove Text (Source) task in DTS.
Pl. help me .
Thanks,
Raja
Error:
LogID=23
#Time=11:32 AM
#Level=DTSMW_LOGLEVEL_ERR
#Source=Microsoft.SqlServer.Dts.MigrationWizard.Framework.Framework
#Message=Microsoft.SqlServer.Dts.Runtime.DtsRuntimeException: Failed to save package file "C:\PONE_SSIS_PACKAGES\PONE_SSIS_SELLTHRU\PONE_DTS_SELLTHRU_TEST.dtsx" with error 0x80004005 "Unspecified error".
> System.Runtime.InteropServices.COMException (0xC001100E): Failed to save package file "C:\PONE_SSIS_PACKAGES\PONE_SSIS_SELLTHRU\PONE_DTS_SELLTHRU_TEST.dtsx" with error 0x80004005 "Unspecified error".
at Microsoft.SqlServer.Dts.Runtime.Wrapper.ApplicationClass.SaveToXML(String FileName, IDTSPersist90 pPersistObj, IDTSEvents90 pEvents)
at Microsoft.SqlServer.Dts.Runtime.Application.SaveToXml(String fileName, Package package, IDTSEvents events)
End of inner exception stack trace
at Microsoft.SqlServer.Dts.Runtime.Application.SaveToXml(String fileName, Package package, IDTSEvents events)
at Microsoft.SqlServer.Dts.MigrationWizard.DTS9HelperUtility.DTS9Helper.SaveToXML(Package pkg, String sFileLocation)
at Microsoft.SqlServer.Dts.MigrationWizard.Framework.Framework.StartMigration(PackageInfo pInfo)
I cannot help you with your specific issue but I recomend that you do not use the DTS SSIS migration wizard. I have tried it several times but it ended with creating new SSIS packages from scratch...
/Erik
|||
Here are some other resources taht talk about DTS-SSIS migration:
http://www.google.com/search?hl=en&q=dts+to+ssis+migration
http://forums.microsoft.com/MSDN/Search/Search.aspx?words=DTS+migration&localechoice=9&SiteID=1&searchscope=forumscope&ForumID=80
|||Hi Raja,
Did you get it fixed ? I have the similar issue scratching my head arround for several hrs.
Regards,
Rahim.
|||Hi Rahim,
I started new SSIS and copy and paste to create second SSIS. It is easy way to start than DTS to SSIS migration. I don't find any DTS to SSIS conversion with out error.
Regards,
Raja
|||
we found that embedding legacy DTS packages in SSIS worked fine. Just create a new package and add an "Execute DTS 2000 Package Task". You can then load the old package in and embed it permenantly. We've had no problems running our old packages in this way Going forward we will rewrite as and when required.
Good luck.
|||Hi Jez,
Thanks a lot for your response. I did as you suggested and it worked.
Regards,
Rahim
|||Hi Raja,
Greetings!
Thank you for your response. Since we have many packages and some of them are big we couldn't copy and paste it.
Instead we created new SSIS package and then added the problem packages as DTS 2000 tasks.
Regards,
Rahim.
Monday, March 12, 2012
Migrate Access 2002 to SQL Express 2005
I'm trying to migrate my access mdb (XP version) to SqlExpress 2005. I use Updating wizzard from Access and i get an error saying that my sql server is not compatible and that i have to use SQL 6,5 SP 5 or later. What i'm doing wrong?The best way to migrate your data would be to use the new integration services in sql server 2005. However, I'm not sure what Express edition offers in this way.|||I believe that you are right but this feature is not supported in SQL Express
Thanks|||Well you can download demo version of the full sql server 2005. Perhaps you should look at purchasing the developer version or an MSDN subscription to get the tools you need.|||This is possible but not in the default configuration. See the blog post at http://blogs.msdn.com/sqlexpress/archive/2004/07/23/192044.aspx for more info on how to configure to do this. Thanks< MJ
migraiton from Analysis Service 2000 to 2005
I get this error during migraiton from Analysis Services 2000 to 2005
Unable to cast COM object of type 'System.__ComObject' to interface type 'Interop.Dso.IDbGroup90Ex'. This operation failed because the QueryInterface call on the COM component for the interface with IID '{CE55E9E9-9597-4214-B21F-30C7683467B1}' failed due
to the following error: No such interface supported (Exception from HRESULT: 0x80004002 (E_NOINTERFACE)).
IMRAN
Recently I successfully migrated OLAP database from 2000 to 2005 didn't see this error even I had to run few times migration wizards. Best guess, may be some thing not installed or configured correctly. However if you give at what step of migration you get this error that will help.
-Ashok
|||Databases:FoodMart 2000
Data sources:
FoodMart
Dimensions:
Account
Category
Customer Pattern
Customers
Department
Education Level
Employees
Gender
HR^Pay Type
Marital Status
Position
Product
Promotion Media
Promotions
Store
Store Size in SQFT
Store Type
Time
Warehouse
Yearly Income
Years in the Company
Cubes:
Budget
HR
Sales
Trained Cube
Warehouse
Warehouse and Sales
Mining models:
Customer Pattern Discovery
Member Card RDBMS
Unable to cast COM object of type 'System.__ComObject' to interface type 'Interop.Dso.IDbGroup90Ex'. This operation failed because the QueryInterface call on the COM component for the interface with IID '{CE55E9E9-9597-4214-B21F-30C7683467B1}' failed due
to the following error: No such interface supported (Exception from HRESULT: 0x80004002 (E_NOINTERFACE)).|||
Try upgrading your AS 2005 to SP2.
Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
migraiton from Analysis Service 2000 to 2005
I get this error during migraiton from Analysis Services 2000 to 2005
Unable to cast COM object of type 'System.__ComObject' to interface type 'Interop.Dso.IDbGroup90Ex'. This operation failed because the QueryInterface call on the COM component for the interface with IID '{CE55E9E9-9597-4214-B21F-30C7683467B1}' failed due
to the following error: No such interface supported (Exception from HRESULT: 0x80004002 (E_NOINTERFACE)).
IMRAN
Recently I successfully migrated OLAP database from 2000 to 2005 didn't see this error even I had to run few times migration wizards. Best guess, may be some thing not installed or configured correctly. However if you give at what step of migration you get this error that will help.
-Ashok
|||Databases:FoodMart 2000
Data sources:
FoodMart
Dimensions:
Account
Category
Customer Pattern
Customers
Department
Education Level
Employees
Gender
HR^Pay Type
Marital Status
Position
Product
Promotion Media
Promotions
Store
Store Size in SQFT
Store Type
Time
Warehouse
Yearly Income
Years in the Company
Cubes:
Budget
HR
Sales
Trained Cube
Warehouse
Warehouse and Sales
Mining models:
Customer Pattern Discovery
Member Card RDBMS
Unable to cast COM object of type 'System.__ComObject' to interface type 'Interop.Dso.IDbGroup90Ex'. This operation failed because the QueryInterface call on the COM component for the interface with IID '{CE55E9E9-9597-4214-B21F-30C7683467B1}' failed due
to the following error: No such interface supported (Exception from HRESULT: 0x80004002 (E_NOINTERFACE)).|||
Try upgrading your AS 2005 to SP2.
Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Friday, March 9, 2012
Microsoft_Time_Series DMX parser error
Can anyone tell me why my syntax is wrong and a fix? Obviously it's the PERIODICITY_HINT, but I'm doing what the BOL says...
ALTERMININGSTRUCTURE [zzz]
ADDMININGMODEL [xxx]
(
...
)
UsingMicrosoft_Time_Series (
PERIODICITY_HINT = {12},
AUTO_DETECT_PERIODICITY=0.1
)
I get this error:
Query (9, 24) Parser: The syntax for '{' is incorrect.
The parameter type of PERIODICITY_HINT is string, therefore it needs to be quoted, e.g.
ALTERMININGSTRUCTURE [zzz]
ADDMININGMODEL [xxx]
(
...
)
UsingMicrosoft_Time_Series (
PERIODICITY_HINT = '{12}',
AUTO_DETECT_PERIODICITY=0.1
)
Microsoft.SQLServer.ManagedDTS.dll reference error in VB.Net 2002
I am using VB.NET 2002 and we have set up a test environment running SQL Server 2005.
I am trying to add a reference to Microsoft.SQLServer.ManagedDTS.dll which is required to run a DTS/SSIS package from VB.NET.
However the dll does not show in my add reference listing so when I select BROWSE and select the actual DLL I get a rather long error message telling me that only 'dll' and COM components can be referenced.
The exact message is:
A reference to 'C:\Programs Files\Microsoft SQL Server\90\SDK\Assemblies\Microsoft.SQLServer.ManagedDTS.dll' could not be added. This is not a valid assembly or COM component. Only assemblies with extension 'dll' and COM components can be referenced. Please make sure that the file is accessible, and that it is a valid assembly or COM component.
Any suggestions?
thanks
AFAIK, you never will be able to add such assembly from Framework 1.0/1.1
|||
Correct. He would need to use Visual Basic 2005 (which implements .NET 2.0) instead.|||enric vives wrote:
AFAIK, you never will be able to add such assembly from Framework 1.0/1.1
Thank you. I thought that may be the case. I will load up VS 2005 and go from there.
Thanks again!
Microsoft.ReportingServices.ReportProcessing.ReportProcessingException
Processing.ReportProcessingException" when trying to run a report with
a fairly large amount of data. Encountering this error quite often.
I changed the memory limit in the RSReportServer Configuration file to
120, but I am still getting this error.It could as well be a timeout issue.
Try changing the SQLCommandTimeoutSeconds to a higher
value.
>--Original Message--
>Getting an error "Microsoft.ReportingServices.Report
>Processing.ReportProcessingException" when trying to run
a report with
>a fairly large amount of data. Encountering this error
quite often.
>I changed the memory limit in the RSReportServer
Configuration file to
>120, but I am still getting this error.
>.
>
Wednesday, March 7, 2012
Microsoft.Jet.OLEDB.4.0 has not been registered. ?
We've got SQL2005 April CTP i64 running on Win2003 with SP1 appied (Itenium Proc). Last week, one of developer sent me an email with error msg,
: Msg 7403, Level 16, State 1, Line 1
The OLE DB provider "Microsoft.Jet.OLEDB.4.0" has not been registered.
I ran Component Checker against that box and it found that MDAC2.8 with SP2 installed. I also found from MS site that Jet 4.0 SP8 i64 version available but the installation aborted due to newer version installed on the box. I am stucked. Any advice would be appreciated.
Sunny
Sunny,It sounds like the developer is executing code in a 64-bit application, and is looking for the Jet OLE DB Provider. There is no 64-bit OLE DB Provider for Jet databases. Your developer would need to use a 32-bit application.
I hope this information proves helpful.
David Sceppa
ADO.NET Program Manager
Microsoft|||
Does MS have some kind of plans for x64 based 64-bit .net apps to connect to Access 2007 or this a permanent solution?
|||David Sceppa - Microsoft wrote:
Sunny, It sounds like the developer is executing code in a 64-bit application, and is looking for the Jet OLE DB Provider. There is no 64-bit OLE DB Provider for Jet databases. Your developer would need to use a 32-bit application.
I hope this information proves helpful.
David Sceppa
ADO.NET Program Manager
Microsoft
Would this also be revelant for OPENROWSET queries that use the driver? For example, the following select runs fine on my dev box (32bit SQL 2005), yet fails on our live box ((SQL 2005 64 bit)) .(it is part of a greater process that *should* bein in SSIS, but is being pushed in as a 'quick fix')
select [User Name],[Password], [Store Number] ,getdate(),''2008-12-31 00:00:00.000'',''1980-01-01 00:00:00.000''
from OPENROWSET(''Microsoft.Jet.OLEDB.4.0'',''Excel 8.0;Database=c:\Username and passwords v1.1.xls'',''SELECT * FROM [staff login details$]'')
version info from live:
7 FileDescription SQL Server Windows NT - 64 Bit
8 FileVersion 2005.090.2153.00
Microsoft.Jet.OLEDB.4.0 has not been registered. ?
We've got SQL2005 April CTP i64 running on Win2003 with SP1 appied (Itenium Proc). Last week, one of developer sent me an email with error msg,
: Msg 7403, Level 16, State 1, Line 1
The OLE DB provider "Microsoft.Jet.OLEDB.4.0" has not been registered.
I ran Component Checker against that box and it found that MDAC2.8 with SP2 installed. I also found from MS site that Jet 4.0 SP8 i64 version available but the installation aborted due to newer version installed on the box. I am stucked. Any advice would be appreciated.
Sunny
Sunny,It sounds like the developer is executing code in a 64-bit application, and is looking for the Jet OLE DB Provider. There is no 64-bit OLE DB Provider for Jet databases. Your developer would need to use a 32-bit application.
I hope this information proves helpful.
David Sceppa
ADO.NET Program Manager
Microsoft|||
Does MS have some kind of plans for x64 based 64-bit .net apps to connect to Access 2007 or this a permanent solution?
|||David Sceppa - Microsoft wrote:
Sunny, It sounds like the developer is executing code in a 64-bit application, and is looking for the Jet OLE DB Provider. There is no 64-bit OLE DB Provider for Jet databases. Your developer would need to use a 32-bit application.
I hope this information proves helpful.
David Sceppa
ADO.NET Program Manager
Microsoft
Would this also be revelant for OPENROWSET queries that use the driver? For example, the following select runs fine on my dev box (32bit SQL 2005), yet fails on our live box ((SQL 2005 64 bit)) .(it is part of a greater process that *should* bein in SSIS, but is being pushed in as a 'quick fix')
select [User Name],[Password], [Store Number] ,getdate(),''2008-12-31 00:00:00.000'',''1980-01-01 00:00:00.000''
from OPENROWSET(''Microsoft.Jet.OLEDB.4.0'',''Excel 8.0;Database=c:\Username and passwords v1.1.xls'',''SELECT * FROM [staff login details$]'')
version info from live:
7 FileDescription SQL Server Windows NT - 64 Bit
8 FileVersion 2005.090.2153.00
Microsoft.Jet.OLEDB.4.0 has not been registered. ?
We've got SQL2005 April CTP i64 running on Win2003 with SP1 appied (Itenium Proc). Last week, one of developer sent me an email with error msg,
: Msg 7403, Level 16, State 1, Line 1
The OLE DB provider "Microsoft.Jet.OLEDB.4.0" has not been registered.
I ran Component Checker against that box and it found that MDAC2.8 with SP2 installed. I also found from MS site that Jet 4.0 SP8 i64 version available but the installation aborted due to newer version installed on the box. I am stucked. Any advice would be appreciated.
Sunny
Sunny,It sounds like the developer is executing code in a 64-bit application, and is looking for the Jet OLE DB Provider. There is no 64-bit OLE DB Provider for Jet databases. Your developer would need to use a 32-bit application.
I hope this information proves helpful.
David Sceppa
ADO.NET Program Manager
Microsoft|||
Does MS have some kind of plans for x64 based 64-bit .net apps to connect to Access 2007 or this a permanent solution?
|||David Sceppa - Microsoft wrote:
Sunny, It sounds like the developer is executing code in a 64-bit application, and is looking for the Jet OLE DB Provider. There is no 64-bit OLE DB Provider for Jet databases. Your developer would need to use a 32-bit application.
I hope this information proves helpful.
David Sceppa
ADO.NET Program Manager
Microsoft
Would this also be revelant for OPENROWSET queries that use the driver? For example, the following select runs fine on my dev box (32bit SQL 2005), yet fails on our live box ((SQL 2005 64 bit)) .(it is part of a greater process that *should* bein in SSIS, but is being pushed in as a 'quick fix')
select [User Name],[Password], [Store Number] ,getdate(),''2008-12-31 00:00:00.000'',''1980-01-01 00:00:00.000''
from OPENROWSET(''Microsoft.Jet.OLEDB.4.0'',''Excel 8.0;Database=c:\Username and passwords v1.1.xls'',''SELECT * FROM [staff login details$]'')
version info from live:
7 FileDescription SQL Server Windows NT - 64 Bit
8 FileVersion 2005.090.2153.00
Microsoft.Data.SqlXml not found
I have VS.net 2003 and the .Net framework 1.1. Are there any other dependencies.
Thanks.
You need to install SQLXML 3.0
(http://www.microsoft.com/downloads/d...33a9-cf10-4e22
-8004-477098a407ac&DisplayLang=en)
Cheers,
Graeme
Graeme Malcolm
Principal Technologist
Content Master Ltd.
"Asim" <anonymous@.discussions.microsoft.com> wrote in message
news:29F448E9-8387-4D04-8E37-87E43CA66619@.microsoft.com...
> I keep getting the error that: File or assembly name
Microsoft.Data.SqlXml, or one of its dependencies, was not found from a c#
application.
> I have VS.net 2003 and the .Net framework 1.1. Are there any other
dependencies.
> Thanks.
Microsoft.Data.Odbc.OdbcException: ERROR [42000] [Microsoft][ODBC SQL Server Driver][SQL S
On localhost this application works fine but when I put on remote server. I am getting following errors. For both localhost and server, I am using same remote sql 2000. I will appreciate any help.
Thanks,
Arif
Server Error in '/' Application.
------------------------
ERROR [42000] [Microsoft][ODBC SQL Server Driver][SQL Server]Line 1: Incorrect syntax near ')'.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: Microsoft.Data.Odbc.OdbcException: ERROR [42000] [Microsoft][ODBC SQL Server Driver][SQL Server]Line 1: Incorrect syntax near ')'.
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Stack Trace:
[OdbcException: ERROR [42000] [Microsoft][ODBC SQL Server Driver][SQL Server]Line 1: Incorrect syntax near ')'.]
Microsoft.Data.Odbc.OdbcConnection.HandleError(IntPtr hHandle, SQL_HANDLE hType, RETCODE retcode) +27
Microsoft.Data.Odbc.OdbcCommand.ExecuteReaderObject(CommandBehavior behavior, String method) +838
Microsoft.Data.Odbc.OdbcCommand.ExecuteNonQuery() +80
Calgary.venues.Page_Load(Object sender, EventArgs e) in c:\inetpub\wwwroot\Calgary\Site\venues\venues.aspx.vb:32
System.Web.UI.Control.OnLoad(EventArgs e) +67
System.Web.UI.Control.LoadRecursive() +35
System.Web.UI.Page.ProcessRequestMain() +731are you using ODBC to connect to sql server ??if so you should be using sqlclient...its much better integrated into .net...
hth|||Hi,
Thanks for reply. I am doing some maintaince on some existing code. Somebody else wrote the code. Application was runing againt MySQL but I am converting over to SQL 2000.
Thanks,
Arif|||Here are the Code: Its failing on myCommand.ExecuteNonQuery(). It was working fine before. Even now its works fine on my localhost.
Thanks,
Arif
Dim strSQL As String
' strSQL = "SELECT * from tblbands where name = "
' strSQL = "SELECT tblAdminUsers_ID as Expr1, RealName as Expr2 From tblAdminUsers order by RealName"
Dim sBandName = Request("bandID")
If sBandName = "09" Then
strSQL = "select name, location, genre from tblbands,tbllocation,tblgenre
WHERE(tblbands.Location_ID = tbllocation.tblLocation_ID)AND tblgenre.tblGenre_ID =
tblbands.Genre_ID and tblbands.isapproved=1 and tblbands.name between '0'
AND '9'ORDER BY name "
End If
If sBandName = "AK" Then
strSQL = "select name, location, genre from tblbands,tbllocation,tblgenre
WHERE(tblbands.Location_ID = tbllocation.tblLocation_ID)AND tblgenre.tblGenre_ID =
tblbands.Genre_ID and tblbands.isapproved=1 and tblbands.name between 'A' AND 'K'
ORDER BY name"
End If
If sBandName = "LZ" Then
strSQL = "select name, location, genre from tblbands,tbllocation,tblgenre
WHERE(tblbands.Location_ID = tbllocation.tblLocation_ID)AND tblgenre.tblGenre_ID =
tblbands.Genre_ID and tblbands.isapproved=1 and tblbands.name between 'L' AND 'Z'
ORDER BY name "
End If
Dim myConnString = ConfigurationSettings.AppSettings("ConnectionString")
Dim myConn As New OdbcConnection(myConnString)
Dim myCommand As New OdbcCommand(strSQL, myConn)
myConn.Open()
myCommand.ExecuteNonQuery()
Dim myReader As OdbcDataReader = myCommand.ExecuteReader()
Repeater1.DataSource = myReader
Repeater1.DataBind()
myReader.Close()
myConn.Close()|||remove tht line...you are already using the execute reader...
comment out this line
myCommand.ExecuteNonQuery()
hth|||Same code was working before. Thanks and let me test again.
best regards,
arif
Microsoft.Data.Odbc on 64-Bit Server
Hi!
Today we installed our ASP.NET Application on a 64-bit server for the first time. We got the error'Unable to find entry point named 'InterlockedIncrement' in DLL 'kernel32.dll''.
This error comes when we make a database query using Microsoft.Data.Odbc. I think it does not run on 64-bit machines.
Does anybody know something about this?
KaaN
I don't know why you need it with ODBC datasource but the link below Microsoft explains the reason for you error. Hope this helps.
(The variable pointed to by the Addend parameter must be aligned on a 32-bit boundary; otherwise, this function will behave unpredictably on multiprocessor x86 systems and any non-x86 systems.)
http://msdn2.microsoft.com/en-us/library/ms683614.aspx
|||Thanks for your answer.
Actually I don't need this xxIncrement method, I only need the .Net Odbc Provider and probably this provider is using this function. Now I have to refactor my code to native providers or find another .Net ODBC Provider.
Microsoft.AnalysisServices.Viewers.DLL Microsoft SQL Server 2005 Datamining Viewer Controls
Hi
I am trying to use Association Viewer Control in
Microsoft.AnalysisServices.Viewers.DLL dll in VS 2005 but sometimes it gives an error.
"Code generatio for property 'ConnecitonManager'" failed. Error was:'Property accesor 'ConnectionManager' on object 'AssosiactionViewer1' threw the following exception:'Object referance not set to instance of an object"
Is there anyone here who use
"Microsoft SQL Server 2005 Datamining Viewer Controls" in SQLServer2005 FeaturePack ?
http://www.microsoft.com/downloads/details.aspx?FamilyID=50b97994-8453-4998-8226-fa42ec403d17&DisplayLang=en
i am using VS2005 Version 8.0.50727.762 (SP.050727-7600)
and SQL Server 2005 SP2
thanks from now.
Cem üney
Thanks for reporting this issue. We are trying to reproduce this problem and will provide an update soon.|||Thank you very much for your reply.
i hope you can see the same problem.
|||Cem,
It would be very helpful if you could tell us a little bit more about your problem. Have you found any particular conditions when you hit the error? Are you getting the error when creating the viewer? or after? What are you doing before invoking the viewer? This will save us a lot guessing and we will be able to find the problem and work a solution earlier.
Thanks,
Fernando Godinez, SQL Server Data Mining
|||ok sir,
i am sending you the pictures that shows my problem. thanks for your interest.
viewer1.jpg
http://img517.imageshack.us/my.php?image=viewer1sz6.jpg
i just open new VBProject.
viewer2.jpg
http://img478.imageshack.us/img478/4223/viewer2jp1.jpg
i add the Microsoft.AnalysisServices.Viewers.dll controls to ToolBox
viewer3.jpg
http://img504.imageshack.us/img504/2976/viewer3qd4.jpg
i just drag and drop the AssociationViewer control to my empty form. When i click properties after 2-3 seconds, it gives me the error at the image.
viewer4.jpg
http://img504.imageshack.us/img504/7746/viewer4ho7.jpg
Connection Manager error and my referances. Maybe i have to some more references but which one?
viewer5.jpg
http://img504.imageshack.us/img504/9749/viewer5if8.jpg
When i close the project and open it again i saw this message
All pictures are here
http://rapidshare.com/files/38900865/viewer.rar.html
|||Cem,
I was able to reproduce the error and we will work on it. In the meantime here is what you need to do to get you application running:
1. Create a form with a Panel on it.
2. From the code part you will have to create a new AssociatonViewer
3. Set the ConnectionString property for you association viewer manually
4. Set the mining model name that you want to view
5. Add the viewer to the panel controls collection
6. Call the LoadViewerData method from the viewer (context parameter can be null).
* Note: You connection string must have the form "Provider=MSOLAP.3;Data Source= your server name;Initial Catalog=your catalog". Where you must provide your server name and your catalog name.
You can see an implementation on the use of the controls in http://www.sqlserverdatamining.com/dmcommunity/_downloads/1361.aspx
All the code in that sample is in C# but I'm sure you can get the grasp without much trouble.
Hope this helped,
Fernando
|||ok fernando,
i know the example before, and i adapted it to VB.
control does not give error when its created at runtime.
thanks for your interest again.
Cem üney
Microsoft VBScript Runtime error 800a001c
all to no avail. Then I began getting the following error message:
Microsoft VBScript runtime error '800a001c'
Out of stack space: 'Val'
/admin/content/pages.asp, line 7
The part in /admin/content/pages.asp, line 7 reads:
For I = 0 To UBound(arrArray)
If Val(arrArray(I)) = Val(varValue) Then
Array_Exists = True
Exit Function
End If
Next
Array_Exists = False
End Function
I have no idea what to do about it. Any hint or link to the right direction
will be appreciated.
Thanks.
Answered elseewhere. Pick a more appropriate NG and don't post the same
message independently to multiple newsgroups.
Microsoft VBScript Runtime error 800a001c
all to no avail. Then I began getting the following error message:
Microsoft VBScript runtime error '800a001c'
Out of stack space: 'Val'
/admin/content/pages.asp, line 7
The part in /admin/content/pages.asp, line 7 reads:
For I = 0 To UBound(arrArray)
If Val(arrArray(I)) = Val(varValue) Then
Array_Exists = True
Exit Function
End If
Next
Array_Exists = False
End Function
I have no idea what to do about it. Any hint or link to the right direction
will be appreciated.
Thanks.Answered elseewhere. Pick a more appropriate NG and don't post the same
message independently to multiple newsgroups.
Friday, February 24, 2012
Microsoft VBScript Runtime error 800a001c
all to no avail. Then I began getting the following error message:
Microsoft VBScript runtime error '800a001c'
Out of stack space: 'Val'
/admin/content/pages.asp, line 7
The part in /admin/content/pages.asp, line 7 reads:
For I = 0 To UBound(arrArray)
If Val(arrArray(I)) = Val(varValue) Then
Array_Exists = True
Exit Function
End If
Next
Array_Exists = False
End Function
I have no idea what to do about it. Any hint or link to the right direction
will be appreciated.
Thanks.Answered elseewhere. Pick a more appropriate NG and don't post the same
message independently to multiple newsgroups.