cannot login to SQLExpress 2005 help please!!

I just installed SQL express couple of days ago.

Then I tried using SQL Management Express Studio CTP. I select

SQL Authetication, key in the correct password but

it says "A connection was succesfully established with the server, but then an error occurred during the login process. (provider: Shared Memory Provider, error:0 - No process is on the other end of the pipe). (Microsoft Sql Error: 233)

When i tried windows authetication, it say cannot initialise SSPI package.

I went to download the windows fix after reading this article

http://www.pcreview.co.uk/forums/thread-1714474-2.php

since google on SSPI has no useful results.... I will be grateful if microsoft people fix this bug with SQL Server 2005 express cos newbies will not be able to understand what

SSPI means.... and failure to install and use an easy software like MS SQL Server will lead to people running to Mysql . sighed.

Cannot get SSCE 3.5 beta 2 to work

I'm running VS2008 beta2. I've succefully added a SDF database file to my project and created a couple of tables in it from VS. I added a reference to the System.Data.SqlCeConnection. When I try to create a new instance of the SqlCeConnection class I get a nasty error that states I'm missing the 'sqlceme35.dll' file. I copy all of the files .dll into by bin folder. Now I'm getting a BadImageFormat error when I create an instance. Does anyone know what that means? or why I had to copy those files to begin with? This is very odd. Any help would be appreciated. I am new to SqlCe.

Hi

I can't help - having the same problem but getting this error

Unable to load DLL 'sqlceme35.dll': The specified module could not be found. (Exception from HRESULT: 0x8007007E)

when I try and add

C:\Program Files (x86)\Microsoft SQL Server Compact Edition\v3.5\sqlceme35.dll

as a reference then I get another error

Microsoft Visual Studio

A reference to 'C:\Program Files (x86)\Microsoft SQL Server Compact Edition\v3.5\sqlceme35.dll' could not be added. Please make sure that the file is accessible, and that it is a valid assembly or COM component.

OK

Hoping for an answer as well

Mike
|||

Mike,

I'm starting to think it has something to do with x64. I'm only getting this error Windows Server 2003 x64 and on Vista x64. However, when I install VS2008 on Vista x86, I have not seen the issue (at least not so far). What platform are you running on?

Jon

|||

This DLL is not a COM object or .NET assembly so it can't be added as reference and it should not be. It should be simply located in your %WINDIR%\System32 or in your application folder.

Also make sure to mark your application as x86 (platform target in project properties or you won't be able to use SQL CE in 64 bit OS.

|||Arg.. That sucks no SQL CE for 64-bit.. Why does VS install all of the tools and SDKs for SQL CE on 64-bit if you can't use it ?

|||

You can - in 32 bit mode. That's the way most applications work on 64 bit OS today.

|||

Jon

Looks like it - I am running Vista 64

All seeems fine ov XP 32

Hope there is a work round

Mike

|||

Hi Ilya

Thanks - I can get a compile and successfull run once I switch to x86 in Orcas Beta 2

but I still can't run SQLMetal in Vista64 either the 32bit version of sqlmetal

Any advice ?

Thanks again

Mike

|||

Go ahead and file a bug here.

Cannot find column errors

Greetings!

I have a project that has been in production for a couple years now. It's a v1.1 ASP.NET web farm hitting a SQL database. The last couple weeks, the website has been erroring out on various pages for about 1-2 hours at a time twice a week. While the error messages are occurring, I cannot reproduce the errors myself.

Here are some of the error messages I recieve:

Cannot find column [ColumnName][ColumnName]is neither a DataColumn nor a DataRelation for table RESULT.[ColumnName] (Thisis a wierd one. The error message returned is just a column name)No record foundColumn '[ColumnName]' does not belong to table RESULT.

I come to a dead end when I follow the Stack Trace to find a programmatic error. I'm able to hit the same page with all the same form fields at the error occured on and I cannot reproduce.

The only consistentcy in these errors is that they come all at once and they are database related.

Anyone have an issue like this before?

Are you saying you can't replicate the problem "later" or on the same webserver at the same time as other users are having the problem?

|||

I cannot replicate the problem at either time.

I have the error messages emailed to me as they occur with information about the error and a link with URL parameters to the page. During the last incident, I was hitting pages where the error just occured moments before.

Any help is greatly appreciated... even if it's another question.

josh

|||

You must use column name from the ASP.net, not from Database.

For example, in my database, the column is [Closed Num]. But asp.net create the name [Closed_Num] for me. When you use filter expression, use [Close_Num] no problem. If you use the column name in the database, you will get the similar error!

Hope it is helpful.

MSVSBoy