By David W. Dee - 5/19/2006
I'm getting an error message box when I launch the Business Object Mapper. Trying to create my
first business object... After the error it doesn't show the tutorial project (or any project) in its
list.--------------------
Here's the error text: SqlException
Implicit conversion from data type text to nvarchar is not allowed. Use the CONVERT function to run this query. Source : .Net SqlClient Data Provider Stack Trace:
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlDataReader.ConsumeMetaData()
at System.Data.SqlClient.SqlDataReader.get_MetaData()
at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)
at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method)
at System.Data.SqlClient.SqlCommand.ExecuteDbDataReader(CommandBehavior behavior)
at System.Data.Common.DbCommand.System.Data.IDbCommand.ExecuteReader(CommandBehavior behavior)
at System.Data.Common.DbDataAdapter.FillInternal(DataSet dataset, DataTable[] datatables, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior)
at System.Data.Common.DbDataAdapter.Fill(DataTable[] dataTables, Int32 startRecord, Int32 maxRecords, IDbCommand command, CommandBehavior behavior)
at System.Data.Common.DbDataAdapter.Fill(DataTable dataTable)
at MicroFour.StrataFrame.Data.DbDataSourceItem.GetDataTable(DbCommand Command, OnChangeEventHandler CallBack)
at MicroFour.StrataFrame.Data.SqlDataSourceItem.GetDataTable(DbCommand Command, OnChangeEventHandler CallBack)
at MicroFour.StrataFrame.Data.DataLayer.GetDataTable(DbCommand Command, Boolean RegisterNotification)
at MicroFour.StrataFrame.Business.BusinessLayer.FillDataTable(DbCommand CommandToExecute)
at MicroFour.StrataFrame.AddIns.DTEprojectsBO.FillProjects(String[] ProjectPaths)
at MicroFour.StrataFrame.AddIns.PartialClassBuilderDialog.BuildProjectNode(PartialClassBuilderVSProject Prj)
at MicroFour.StrataFrame.AddIns.PartialClassBuilderDialog.BuildTreeView()
at MicroFour.StrataFrame.AddIns.PartialClassBuilderDialog.InitForm()
|
By StrataFrame Team - 5/19/2006
What version of SQL Server are you running on? And if you could list the service pack if it's 2000, that would also be helpful. Thanks.
|
By David W. Dee - 5/19/2006
Thanks for the very rapid response.It's SQL Server 2000 (SP3). I believe that it has all patches/etc. at least up to a month or
so ago.
|
By StrataFrame Team - 5/19/2006
Hrm... we have several people using that version of SQL Server for their StrataFrame database.Do you have any special characters in the paths to your project files? Probably not, if you're just trying to open the tutorial, but it seems that when passing the project paths to SQL Server to retrieve the project records, it's trying to convert it from an AnsiString (ASCII) to unicode... not sure why. What happens if you create a new project using the StrataFrame Windows Application template (either C# or VB, doesn't matter) and try to open the BOMapper?
|
By David W. Dee - 5/19/2006
I tried various combinations, making sure there were no spaces or "_" that I could find. No luck.The database tables are on another machine, but I have programs that can access other data stored
there without a problem.
|
By StrataFrame Team - 5/19/2006
Yes, having a remote database isn't a problem... there's something else fishy here. Can you open up the StrataFrame database within Enterprise Manager and check the structure of the DTEprojects table. Would probably be easiest if you took a screenshot of the structure and posted it here.
|
By David W. Dee - 5/19/2006
Here it is (I hope) sent as a DOC attachment.
|
By StrataFrame Team - 5/19/2006
The structure looks fine. I'm not sure why it's having problems converting the data type. I changed the code where we were specifying the length of the input parameter, but it will be next week before we can get a new install built, so this change will be lumped in with the DevExpress wrappers and other BOMapper changes that have been made.
|
By David W. Dee - 5/19/2006
No problem. How will I know when the new build is available?Also, just in case there's something that I did wrong during the install, would it make any sense
to do the entire install over from scratch. -------------------------------------------------------------------------- I don't know whether you remember me, but you did an online demo for me a couple of weeks ago.
I'm enthused to dig into it some more.
|
By StrataFrame Team - 5/19/2006
Yeppers, I do remember you from the demo  I'm not sure there would be any reason for you to do an install from scratch. If you want to be able to work over the weekend, you could get your hands on SQL Server 2005 Express and install it on your local workstation, then reinstall StrataFrame and tell the deployment process to deploy the StrataFrame database to that instance. There's just something with the way we're parameterizing commands within our bo (not the whole framework, but the BO used within the BOMapper) that SQL Server 2000 sp3 doesn't like... and I could have sworn that at least one of our users was on 2000 sp3. Oh well. So, yes, if you want to use 2005 Express, then you can reinstall and you'll be up and running, otherwise, it wouldn't do you any good 
|
By David W. Dee - 5/19/2006
I do have SQL Server Express here (it comes with Visual Studio, right?) I'll give it a try and post
back here whether it's successful or not. It might be tomorrow sometime before I get back to it.
Thanks.
|
By StrataFrame Team - 5/19/2006
(it comes with Visual Studio, right?) Correct, it comes with VS Standard and up, not the express versions; however if you get an express version, you can dowload the standalone install for SQL 2005 Express from Microsoft. It might be tomorrow sometime before I get back to it. No problem... I'll should be keeping tabs on the forum this weekend, so just let me know how you fair
|
By StrataFrame Team - 5/19/2006
Oh, and we do mass emails through the forum to notify users of the new updates that are available. So, you should receive an email from forum@strataframe.net to indicate that the update is available.
|
By David W. Dee - 5/23/2006
I'm glad to report that got a local version of SQL Server 2005 running, and re-installed StrataFrame
using for the sample data, and everything's working good. It didn't seem to like my SQL Server 2000.
I'm not familiar with SQL Server Express (because I'm used to Enterprise Manager in SQL Server and
wasn't quite sure how to work without it...)I thought you might like to hear how the SQL Server version issue worked out. FYI. Thanks.
|
By StrataFrame Team - 5/23/2006
I'm glad to hear that you have it working. I'm not sure if it comes with Visual Studio or not, but there is a SQL Server Express Manager that you can download for free from Microsoft. And, if you have an MSDN subscription (which chances are good you do with the way Microsoft has been pushing VS2005 to its customers), you can download the SQL Server 2005 tools containing SQL Server Management Studio (the new replacement for Enterprise Manager). SSMS is a WONDERFUL app, and is quite a good ways beyond the capabilities and ease of use of Enterprise Manager. Not to mention that it works great with existing pre-2005 SQL Server machines. There's also some functionality within VS itself to open databases, build queries and such, but I don't use it much since I have the other tools.
|
|