Showing posts with label sqlexpress. Show all posts
Showing posts with label sqlexpress. Show all posts

Tuesday, March 27, 2012

Can't start SQLEXPRESS so that I can't install latest SQLEXPRESS security updates.

I can't start SQLEXPRESS.

The SQL ERRORLOG shows: Error is 3414, Severity 21, State 2 and says: "An error occurred during recovery, preventing the database 'model' (database ID 3) from restarting." Just prior to this, I get a warning: "did not see LP_CKPT_END".

Any thoughts why this might be and how I can fix this?

Seems like something happened to your master database, check out the BOL topic on restoring master for starters.

Mike

|||

Thank you for your thoughts.

Unfortunately, I am not able to restore the database because I can't start SQLEXPRESS. I have even tried the command line sqlservr -s SQLEXPRESS command line command without success.

I continue to get this warning "did not see LP_CKPT_END" Error:3414, Severity:21, State: 1.

It might help to know that I have never used the SQLEXPRESS database on my box before. (I also have an instance of MSSQLSERVER and that is what I have been using. MSSQLSERVER starts up without issue.)

I'm not sure what it is that I would be restoring as I haven't created any databases in SQLEXPRESS.

The issue began when I update MSSQLSERVER with SP2 (KB 933508) install package. It seemed to take fine. I also did the install after March 5, 2007 -- a critical date for this update.

When the SQL 2005 Express SP2 (KB 921896) came out, it would load because it couldn't start an instance of SQLEXPRESS.

Does this help explain the background better? Your further suggestions would be helpful.

|||

This one is beyond me. Moving to the setup forum to ask the experts.

Mike

Thursday, March 22, 2012

Cant seem to find IUSR_MachineName in users using SQLEXPRESS 2005

Hello,

I have an ASP web app with an SQL back end. I am currently migrating to a
new Windows 2003 Server machine and SQL Server 2005 Express. When I import
the old database, I'm trying to grant the IUSR_MachineName account access to
the database, but I can't seem to find that user account. I'm clicking new
users, and when I type this user in, SQL doesn't recognize it, and when I
click "Browse" all I see is BUILTIN/Administrators, BUILTIN/Users NT
Authority/System SA (which is not in use) and a long name that includes a
lot of dollar signs, the machine name and SQL express in it (it's a big
cryptic looking thing). Any idea how I get this to work again?

Thanks!"Rico" <r c o l l e n s @. h e m m i n g w a y . c o mREMOVE THIS PART IN
CAPS> wrote in news:jqQDf.291171$tl.48607@.pd7tw3no:

> When I import the old database, I'm trying to grant the
> IUSR_MachineName account access to the database, but I can't seem to
> find that user account.

I can't find that account either, unless...

On one Server 2003, I do not have IIS6 installed/activated (I have not yet
indentified any roles this server will have). On another Server 2003, I do.
In Computer Management control panel, Local Users and Groups, Users, I see
IUSR_<machinename>.

On the third hand, this built-in name will not show when searching for
objects when adding names to the Security tab of Folder Properties, nor, I
would imagine, any other place where you can pick names of Users or Groups.

I think it's just a name you have to know about.

Now, SQL Server 2005 Express - I just finished installing that. What a
fracking nightmare!

--
Remove INVALID from e-mail address.

Brian Smither
Smither Consulting|||ARGH! Thanks Brian,

I managed to fight through that (was my inexperience with SQL 2005,
(defining the Logins before defining the Users).

Now I'm faced with a different issue. I finally got my ASP.Net app working
using an ADO interface to SQL Server 2005 to create a crystal report,
exporting to a pdf file (phew!). I was screaming for joy when I finally got
this all working. I began testing, starting with the first report, it ran
for a long time and didn't produce anything. I went back to the first
report I ran, and it ran a long time and didn't produce anything. I opened
up management studio, and IT wouldn't even connect! I got a "Cannot
generate SSPI context" error, out of the blue, after it was already working.
nothing had changed in the meantime, I'm always careful about that.

Anyway, if you have any idea what might have occured, please let me know. I
hope this is not indicative of an unreliable database system.

"Brian Smither" <bsmitherINVALID@.INVALIDcitlink.net> wrote in message
news:Xns975FEE24E4A1SmithCon@.67.98.68.13...
> "Rico" <r c o l l e n s @. h e m m i n g w a y . c o mREMOVE THIS PART IN
> CAPS> wrote in news:jqQDf.291171$tl.48607@.pd7tw3no:
>> When I import the old database, I'm trying to grant the
>> IUSR_MachineName account access to the database, but I can't seem to
>> find that user account.
> I can't find that account either, unless...
> On one Server 2003, I do not have IIS6 installed/activated (I have not yet
> indentified any roles this server will have). On another Server 2003, I
> do.
> In Computer Management control panel, Local Users and Groups, Users, I see
> IUSR_<machinename>.
> On the third hand, this built-in name will not show when searching for
> objects when adding names to the Security tab of Folder Properties, nor, I
> would imagine, any other place where you can pick names of Users or
> Groups.
> I think it's just a name you have to know about.
>
> Now, SQL Server 2005 Express - I just finished installing that. What a
> fracking nightmare!
>
> --
> Remove INVALID from e-mail address.
> Brian Smither
> Smither Consultingsql

Friday, February 10, 2012

Can't get SQL Manager to connect to server instance SQLEXPRESS

I installed SQL Server Express and SQL Server manager, then tried to start manager. SQL Service is running, but SQL Manager attempt to connect to SQL Server instance times-out even though I correctly identify instance as SQLEXPRESS? Everything seems to be normal - both SQL Server and Manager are on a single Windows XP home machine. Any suggestions. ThanksHi,
Try using .\SQLEXPRESS as the instance name...

cheers,
Paul June A. Domag|||Great - It Works! Thanks|||After reading this thread and another one I've tried entering the following in express manager and I still can't connect:

.\MSSQLSERVER
(local)\MSSQLSERVER

I am running SQL Server Express June CTP on a Win2K3 box. SQL Express Manager is also running on the same Win2K3 box.

I have opened all the network protocols for SQL Server Express, I've also enabled the SQL Server browser. There are no firewalls involved. This is probably the most insecure setup, yet I still cannot connect locally Tongue Tied

Any ideas?

I followed all the instructions here:
http://download.microsoft.com/download/a/6/3/a63ec922-913e-4228-93e3-970abff3fd66/ReadmeSQLExpMgr.htm
and here
http://blogs.msdn.com/sqlexpress/archive/2005/05/05/415084.aspx

Nothing seems to work.
|||Hi,
Actually its .\SQLServer not .\MSSQLSERVER.
Have you tried it? got any versions installed before the June CTP?
cheers,
Paul June A. Domag|||Unfortunately that didn't work either.
All I have installed is June CTP on a fresh install of Win2K3 Standard.
In the SQL Server Configuration Manager under "name" it says: SQL Server (MSSQLSERVER).
This would indicate the name of the SQL server is "MSSQLSERVER" correct? I chose "default" instance during the install and that is the name it gave itself.
This is getting frustrating... I thought programming with MS stuff would be easy. I could have connected to MySQL a hundred different ways by now.
|||Just a two cents worth general comment - the MS beta's tend to have problems that the production versions don't - having used SQL Server from the time it was Sybase Server to date I can say it is great software that occassionally suffers from growing pains. PS|||Yeah, I don't expect Beta software to be 100% functional but I do expect the basic functionality to be working and straightforward. Connecting to the server shouldn't be this difficult. Especially if you consider the target market for this product.
|||Hi,
Oops, I guess I had a typo. Its .\SqlExpress, If you choose default instance...
cheers,
Paul June A. Domag|||After all that I accidently stumbled upon a solution.
The only thing that works for my installation is just plain ".\" (no quotes) and nothing else. Go figure. Hopefully this post saves someone else a lot of time.
|||Hi,
Weird... Could you report a bug in Product Feedback? So that Microsoft would be aware of this...

cheers,
Paul June A. Domag|||thanks a lot this helped!!!!!

Paul Domag wrote:

Hi,
Try using .\SQLEXPRESS as the instance name...

cheers,
Paul June A. Domag

|||Thanks!!!! I have been pulling my hair out all night trying to figure out why I couldn't connect. That did the trick. Why doesn't MS tell you about these important details.|||

I'm getting error like

SqlDateTime overflow. Must be between 1/1/1753 12:00:00 AM and 12/31/9999 11:59:59 PM.

I want to set it bet 1/1/0001 to 31/12/9999. how to do this?

So do u have any solution over it pls.

I think u have solution over it because I have seen same problem u had .

At last Happy New Year 2006 at this first meet ing with u

Balasaheb

|||Hi,

There are only two datatypes that could handle date and time values in sqlserver. These are DateTime and SmallDateTime. Both of these types cold not handle data between 1/1/0001 to 31/12/9999. But you can store these dates as a varchar and just parse the dates to calculate them in your program...

cheers,

Paul June A. Domag