errors installing SQL Server Express 2005

I've been having horrific problems installing and working with SQL Server Express 2005. I installed SSE with the Visual Web Developer tool so I assumed that the instance would synch up; but it didn't (see log contents at end) so I opened up permissions wide open to all users, and even that didn't help. I don't know for sure but I suspect that the problem probably relates to my deleting SQL Server entries from the registry and all directories and files related to it on disk. After going through the process of uninstalling and reinstalling Express 2005 numerous times, I became frustrated and decided to pull out all stops.

After reading and following all MSDN instructions and every blog and forum I could possibly locate on the subject, I could never resolve the problem of not reaching my database. I enabled all pipes and TCP/IP, etc. in the Configuration Manager, in both instances I had created; had run all command-line procedures recommended; and used cleanup programs that I could find, before reinstalling. I couldn't even get success in doing a test connection. I did get to a point where my ASP returned the message that it had connected but that the user didn't have permissions.

I think I'm destined to working with Access, which is a shame since I have encouraged students in a Web development class I teach to work with the more powerful SQL Server products. They've had success with SQL Server, so I'm setting a bad example.

Thanks in advance for help any of you can suggest.

Microsoft SQL Server 2005 Setup beginning at Sun Feb 05 23:48:08 2006
Process ID : 2036
c:\6645bd818fccc8ef0bad80e6a12f5b\setup.exe Version: 2005.90.1399.0
Running: LoadResourcesAction at: 2006/1/5 23:48:6
Complete: LoadResourcesAction at: 2006/1/5 23:48:6, returned true
Running: ParseBootstrapOptionsAction at: 2006/1/5 23:48:6
Loaded DLL:c:\6645bd818fccc8ef0bad80e6a12f5b\xmlrw.dll Version:2.0.3604.0
Complete: ParseBootstrapOptionsAction at: 2006/1/5 23:48:8, returned true
Running: ValidateWinNTAction at: 2006/1/5 23:48:8
Complete: ValidateWinNTAction at: 2006/1/5 23:48:8, returned true
Running: ValidateMinOSAction at: 2006/1/5 23:48:8
Complete: ValidateMinOSAction at: 2006/1/5 23:48:8, returned true
Running: PerformSCCAction at: 2006/1/5 23:48:8
Complete: PerformSCCAction at: 2006/1/5 23:48:8, returned true
Running: ActivateLoggingAction at: 2006/1/5 23:48:8
Complete: ActivateLoggingAction at: 2006/1/5 23:48:8, returned true
Running: DetectPatchedBootstrapAction at: 2006/1/5 23:48:8
Complete: DetectPatchedBootstrapAction at: 2006/1/5 23:48:8, returned true
Action "LaunchPatchedBootstrapAction" will be skipped due to the following restrictions:
Condition "EventCondition: __STP_LaunchPatchedBootstrap__2036" returned false.
Running: PerformSCCAction2 at: 2006/1/5 23:48:8
Loaded DLL:C:\WINDOWS\system32\msi.dll Version:3.1.4000.2435
Loaded DLL:C:\WINDOWS\system32\msi.dll Version:3.1.4000.2435
Complete: PerformSCCAction2 at: 2006/1/5 23:48:9, returned true
Running: PerformDotNetCheck at: 2006/1/5 23:48:9
Complete: PerformDotNetCheck at: 2006/1/5 23:48:9, returned true
Running: ComponentUpdateAction at: 2006/1/5 23:48:9
Complete: ComponentUpdateAction at: 2006/1/5 23:48:30, returned true
Running: DetectLocalBootstrapAction at: 2006/1/5 23:48:30
Complete: DetectLocalBootstrapAction at: 2006/1/5 23:48:30, returned true
Running: LaunchLocalBootstrapAction at: 2006/1/5 23:48:30

To my comment "I suspect that the problem probably relates to my deleting SQL Server entries from the registry and all directories and files related to it on disk," I should append the following: "...after I uninstalled everything."

Errors installing MSDE desktop

HELP! this is driving me mad!!

I installed MSDE desktop with no problems... months later when creating a database, I stupidily forgot the "sa" password that I set during setup... So I decided to unistall MSDE and reinstall it, this time documenting the username and password... BUT now it is giving me errors which I am unable to solve... is there anyone out there that might be able to help me??

I go to a command-line, locate the directory where the install program lives and type in "setup SAPWD=(a password) SecurityMode=SQL" and it returns the follow error message:
"Setup Failed to configure the server. Refer to the server error logs and setup error logs"

My problem is I don't know where to locate these error logs. Please if anyone can help me with this problem I would greatly appreciate it.

thanks, Donald - email = pizzazzz@.cox.netPlease refer to my post in this section under the subject: "Overcoming MSDE Setup Problems". Link: http://www.asp.net/Forums/ShowPost.aspx?tabindex=1&PostID=739042

errors in ssis package execution

i have sql server 2005 standard edition(9.0.3054) with sp2, My ssis packages
were initially working fine,After installing sql server 2008 ctp, all ssis
packages stopped executing and giving error "Could not create DTS.Application
because of error 0x80040154", also import export wizard in sql 2005 is not
working.
After that i uninstalled sql server 2008 ctp and integration
service of sql 2005, and again installed integrtaion service of sql 2005 but
still i am getting error in ssis package execution.Please suggest me a
solution asap , as it is on a production server.
Thanks
Rupesh Mondal.
I had already removed and reinstalled "ssis" but it didnt worked ok,and i
already had sp2 installed on my database server.
Thanks and Regards,
Rupesh Mondal.
"John Bell" wrote:

> "Rupesh Mondal" <RupeshMondal@.discussions.microsoft.com> wrote in message
> news:CF99A5D6-B6C6-4484-9BD2-B6237A1A3D05@.microsoft.com...
> Hi Rupesh
> Error Code 0x80040154 relates to class not registered, therefore it looks
> like a SSIS component has been corrupted. The easiest solution may be to
> remove and re-install SSIS or SQL Server. If you are not on SP2 then you may
> just get away with installing that.
> John
>
>

errors in ssis package execution

i have sql server 2005 standard edition(9.0.3054) with sp2, My ssis packages
were initially working fine,After installing sql server 2008 ctp, all ssis
packages stopped executing and giving error "Could not create DTS.Application
because of error 0x80040154", also import export wizard in sql 2005 is not
working.
After that i uninstalled sql server 2008 ctp and integration
service of sql 2005, and again installed integrtaion service of sql 2005 but
still i am getting error in ssis package execution.Please suggest me a
solution asap , as it is on a production server.
Thanks
Rupesh Mondal."Rupesh Mondal" <RupeshMondal@.discussions.microsoft.com> wrote in message
news:CF99A5D6-B6C6-4484-9BD2-B6237A1A3D05@.microsoft.com...
>i have sql server 2005 standard edition(9.0.3054) with sp2, My ssis
>packages
> were initially working fine,After installing sql server 2008 ctp, all ssis
> packages stopped executing and giving error "Could not create
> DTS.Application
> because of error 0x80040154", also import export wizard in sql 2005 is not
> working.
> After that i uninstalled sql server 2008 ctp and integration
> service of sql 2005, and again installed integrtaion service of sql 2005
> but
> still i am getting error in ssis package execution.Please suggest me a
> solution asap , as it is on a production server.
> Thanks
> Rupesh Mondal.
Hi Rupesh
Error Code 0x80040154 relates to class not registered, therefore it looks
like a SSIS component has been corrupted. The easiest solution may be to
remove and re-install SSIS or SQL Server. If you are not on SP2 then you may
just get away with installing that.
John|||I had already removed and reinstalled "ssis" but it didnt worked ok,and i
already had sp2 installed on my database server.
Thanks and Regards,
Rupesh Mondal.
"John Bell" wrote:
> "Rupesh Mondal" <RupeshMondal@.discussions.microsoft.com> wrote in message
> news:CF99A5D6-B6C6-4484-9BD2-B6237A1A3D05@.microsoft.com...
> >i have sql server 2005 standard edition(9.0.3054) with sp2, My ssis
> >packages
> > were initially working fine,After installing sql server 2008 ctp, all ssis
> > packages stopped executing and giving error "Could not create
> > DTS.Application
> > because of error 0x80040154", also import export wizard in sql 2005 is not
> > working.
> > After that i uninstalled sql server 2008 ctp and integration
> > service of sql 2005, and again installed integrtaion service of sql 2005
> > but
> > still i am getting error in ssis package execution.Please suggest me a
> > solution asap , as it is on a production server.
> >
> > Thanks
> > Rupesh Mondal.
> Hi Rupesh
> Error Code 0x80040154 relates to class not registered, therefore it looks
> like a SSIS component has been corrupted. The easiest solution may be to
> remove and re-install SSIS or SQL Server. If you are not on SP2 then you may
> just get away with installing that.
> John
>
>|||Hi
Have you re-installed .NET? Otherwise I would re-install from scratch.
Hopefully this is not a production server!
John
"Rupesh Mondal" <RupeshMondal@.discussions.microsoft.com> wrote in message
news:81A467AD-B56B-44FC-92C9-D4FA96019C87@.microsoft.com...
>I had already removed and reinstalled "ssis" but it didnt worked ok,and i
> already had sp2 installed on my database server.
> Thanks and Regards,
> Rupesh Mondal.
> "John Bell" wrote:
>> "Rupesh Mondal" <RupeshMondal@.discussions.microsoft.com> wrote in message
>> news:CF99A5D6-B6C6-4484-9BD2-B6237A1A3D05@.microsoft.com...
>> >i have sql server 2005 standard edition(9.0.3054) with sp2, My ssis
>> >packages
>> > were initially working fine,After installing sql server 2008 ctp, all
>> > ssis
>> > packages stopped executing and giving error "Could not create
>> > DTS.Application
>> > because of error 0x80040154", also import export wizard in sql 2005 is
>> > not
>> > working.
>> > After that i uninstalled sql server 2008 ctp and
>> > integration
>> > service of sql 2005, and again installed integrtaion service of sql
>> > 2005
>> > but
>> > still i am getting error in ssis package execution.Please suggest me a
>> > solution asap , as it is on a production server.
>> >
>> > Thanks
>> > Rupesh Mondal.
>> Hi Rupesh
>> Error Code 0x80040154 relates to class not registered, therefore it looks
>> like a SSIS component has been corrupted. The easiest solution may be to
>> remove and re-install SSIS or SQL Server. If you are not on SP2 then you
>> may
>> just get away with installing that.
>> John
>>

Errors after installing Server 2000 DTS Designer Components

Hello,

After Having installed the SQL Server 2000 DTS Designer Components necessary
to edit legacy DTS packages on 2005 server, I keep getting the following message when trying to open SQL Server 200 Enterprise Manager:

"The procedure entry point
?ProcessExecute@.@.YAXPAUHWND_@.@.PBG1@.Z could not be located in teh dynamic link library SEMSFC.dll."

Is there a way to fix so that I can open Enterprise manager?

Thanks!

If you have both SQL 2000 and 2005 client tools installed, you do not need the "SQL Server 2000 DTS Designer Components" package installed.

First, uninstall them. Then figure out why 2005 is telling you to install them, when you don't need them.

Make sure you have run 2000 SP4 on your CLIENT machine to update the tools to the current version.

In my case, the error appears to be related to having SQL 7 client tools installed. When I uninstalled them the error in 2005 went away.

|||

Thanks for the info. I really appreciate it.

|||

Good info. Fixed what I thought was a very cryptic error message.

Thanks for the details!

|||

Tom,

How do you install SP4 on a client machine. How do you specify the instance and user id if I don't have one installed on my machine?

Thanks,
Joseph

Errors after installing Server 2000 DTS Designer Components

Hello,

After Having installed the SQL Server 2000 DTS Designer Components necessary
to edit legacy DTS packages on 2005 server, I keep getting the following message when trying to open SQL Server 200 Enterprise Manager:

"The procedure entry point
?ProcessExecute@.@.YAXPAUHWND_@.@.PBG1@.Z could not be located in teh dynamic link library SEMSFC.dll."

Is there a way to fix so that I can open Enterprise manager?

Thanks!

If you have both SQL 2000 and 2005 client tools installed, you do not need the "SQL Server 2000 DTS Designer Components" package installed.

First, uninstall them. Then figure out why 2005 is telling you to install them, when you don't need them.

Make sure you have run 2000 SP4 on your CLIENT machine to update the tools to the current version.

In my case, the error appears to be related to having SQL 7 client tools installed. When I uninstalled them the error in 2005 went away.

|||

Thanks for the info. I really appreciate it.

|||

Good info. Fixed what I thought was a very cryptic error message.

Thanks for the details!

|||

Tom,

How do you install SP4 on a client machine. How do you specify the instance and user id if I don't have one installed on my machine?

Thanks,
Joseph

Errors after installing Server 2000 DTS Designer Components

Hello,

After Having installed the SQL Server 2000 DTS Designer Components necessary
to edit legacy DTS packages on 2005 server, I keep getting the following message when trying to open SQL Server 200 Enterprise Manager:

"The procedure entry point
?ProcessExecute@.@.YAXPAUHWND_@.@.PBG1@.Z could not be located in teh dynamic link library SEMSFC.dll."

Is there a way to fix so that I can open Enterprise manager?

Thanks!

If you have both SQL 2000 and 2005 client tools installed, you do not need the "SQL Server 2000 DTS Designer Components" package installed.

First, uninstall them. Then figure out why 2005 is telling you to install them, when you don't need them.

Make sure you have run 2000 SP4 on your CLIENT machine to update the tools to the current version.

In my case, the error appears to be related to having SQL 7 client tools installed. When I uninstalled them the error in 2005 went away.

|||

Thanks for the info. I really appreciate it.

|||

Good info. Fixed what I thought was a very cryptic error message.

Thanks for the details!

|||

Tom,

How do you install SP4 on a client machine. How do you specify the instance and user id if I don't have one installed on my machine?

Thanks,
Joseph

Error:... it requires a higher level edition.

I've read some threads on this topic and all have been solved by installing the SSIS service. This would be fine except for the fact that I already have SSIS installed and working on the server the package is being called from.

I have several scheduled packages that work without error and a few that fail, telling me "Error: ... it requires a higher level edition." Does SSIS need to be installed on the target server as well? Do I need to do a reinstall? Please advise. Thanks.

-Matt
The error should indicate which component requires higher level edition. Some components (like Fuzzy Grouping) do require Enterprise edition, and would not run on Standard edition of SSIS.