MS Service Pack frustrations: ctp

Showing posts with label ctp. Show all posts

Friday, March 23, 2012

MS SQL Server 2005 June CTP Setup Error

Hello,
I'm trying to setup MS SQL Server 2005 June CTP. Everything seemed to be
fine except Reporting Services failed to install, blow is the Setup Log with
the section that has the relavent failure:
CreateAspApp: start time: 11:44:01
CreateAspApp: CustomActionData: /LM/W3SVC/1/Root/Reports
CreateAspApp: Error 0x8004e00f: failed to create web application:
/LM/W3SVC/1/Root/Reports
MSI (s) (38!B0) [11:44:12:625]: Product: Microsoft SQL Server 2005 Reporting
Services CTP -- Error 25619. The setup failed to create web application:
/LM/W3SVC/1/Root/Reports. The error code is -2147164145.
Error 25619. The setup failed to create web application:
/LM/W3SVC/1/Root/Reports. The error code is -2147164145.
CreateAspApp: end time: 11:44:12, elapsed: 38475601.000000 (seconds)
Can someone shed some light on this?
--
GeorgeWorked fine for me.
--
Thanks,
ID
"George P boutwell" wrote:
> Hello,
> I'm trying to setup MS SQL Server 2005 June CTP. Everything seemed to be
> fine except Reporting Services failed to install, blow is the Setup Log with
> the section that has the relavent failure:
> CreateAspApp: start time: 11:44:01
> CreateAspApp: CustomActionData: /LM/W3SVC/1/Root/Reports
> CreateAspApp: Error 0x8004e00f: failed to create web application:
> /LM/W3SVC/1/Root/Reports
> MSI (s) (38!B0) [11:44:12:625]: Product: Microsoft SQL Server 2005 Reporting
> Services CTP -- Error 25619. The setup failed to create web application:
> /LM/W3SVC/1/Root/Reports. The error code is -2147164145.
> Error 25619. The setup failed to create web application:
> /LM/W3SVC/1/Root/Reports. The error code is -2147164145.
> CreateAspApp: end time: 11:44:12, elapsed: 38475601.000000 (seconds)
> Can someone shed some light on this?
> --
> George|||Great! Now if only I could get it to work for me, I could get back to real
coding and getting some real work done...
I did some digging there isn't really and 2005 documentation that covers
this problem, there is some SQL 2000 that says to ensure the
IWAM_computername user isn't disabled and the DTC (Distributed Transaction
Coordinator) service is running. That could be my problem DTC is not
running, however, when I try to run it it gives me an error:
The Distributed Transaction Coordinator service terminated with
service-specific error 3221229584 (0xC0001010).
So I'm back to still not able to do it. :(
--
George
"exkievan" wrote:
> Worked fine for me.
> --
> Thanks,
> ID
>
> "George P boutwell" wrote:
> > Hello,
> >
> > I'm trying to setup MS SQL Server 2005 June CTP. Everything seemed to be
> > fine except Reporting Services failed to install, blow is the Setup Log with
> > the section that has the relavent failure:
> >
> > CreateAspApp: start time: 11:44:01
> > CreateAspApp: CustomActionData: /LM/W3SVC/1/Root/Reports
> > CreateAspApp: Error 0x8004e00f: failed to create web application:
> > /LM/W3SVC/1/Root/Reports
> > MSI (s) (38!B0) [11:44:12:625]: Product: Microsoft SQL Server 2005 Reporting
> > Services CTP -- Error 25619. The setup failed to create web application:
> > /LM/W3SVC/1/Root/Reports. The error code is -2147164145.
> >
> > Error 25619. The setup failed to create web application:
> > /LM/W3SVC/1/Root/Reports. The error code is -2147164145.
> > CreateAspApp: end time: 11:44:12, elapsed: 38475601.000000 (seconds)
> >
> > Can someone shed some light on this?
> >
> > --
> > George|||On Wed, 22 Jun 2005 06:31:08 -0700, George P Boutwell wrote:
> Great! Now if only I could get it to work for me, I could get back to real
> coding and getting some real work done...
> I did some digging there isn't really and 2005 documentation that covers
> this problem, there is some SQL 2000 that says to ensure the
> IWAM_computername user isn't disabled and the DTC (Distributed Transaction
> Coordinator) service is running. That could be my problem DTC is not
> running, however, when I try to run it it gives me an error:
> The Distributed Transaction Coordinator service terminated with
> service-specific error 3221229584 (0xC0001010).
> So I'm back to still not able to do it. :(
I tried several searches on KnowledgeBase and come-up empty, till I tried
an search on service-specified error 3221229584, which produced the
following:
http://news.gmane.org/gmane.linux.colinux.devel/cutoff=2420
this seemed to have fixed my DTC service, it now runs as expected. And
after uninstalling, rebooting, and re-installing SQL Server 2005 June CTP,
I now have the Report Services working.
Georgesql

MS SQL Server 2005 EE & MS SQL Server 2005 Express Manager

I recently installed SQL Server 2005 Express Edition CTP (It appears to be working fine). I then found the SQL Server 2005 Express Manager, and tried to load it, but I keep getting the error:

This computer must have at least Windows 2000 SP4 and the user must have administrator privileges in order to continue. Also, you must first install the SMO Components and the .NET Framework version 2.0.

Well, the machine is Windows XP Pro SP2 (fully patched), the account I am installing with is a member of the local admin group, my machine has both .Net framework 1.1 and 2.0 loaded (could this be the issue?). I guessed that installing 2.0 would upgrade 1.1. but that does not appear to be the case. I also went back and reinstalled SQL Server, unselected "Hide advanced configuration options", clicked on Client Components and selected "Entire feature will be installed on local hard drive", and finished the install. The docs I found on SQL 2005 indicate that this would install the SMO Components. Thus, I should have all of the bases covered, but the Express Manager install still errors out with the message above.

Any help on this would be greatly appreciated,
JonLooking at the Product page for SQL Express, the Management App is not included with the CTP. To use it you are going to have to use the beta 2 version.

MS SQL Express product page
http://lab.msdn.microsoft.com/express/sql/|||I have installed the latest SQL Server 2005 Express, and even with the problems with remote connections(a new port number by default) I also recieve the error about the SMO components and .Net Framework version 2.0. .Net Framework version 2.0 is installed, and functioning, according the the install I have the SMO components; BUT I still receive the message when attempting to install the Express Manager.

I have not installed any beta versions.

Is it possible that the SMO components are not registered correctly? Any suggestions would be appreciated.

MS SQL Server 2005 EE & MS SQL Server 2005 Express Manager

I recently installed SQL Server 2005 Express Edition CTP (It appears to be working fine). I then found the SQL Server 2005 Express Manager, and tried to load it, but I keep getting the error:

I have not installed any beta versions.

Is it possible that the SMO components are not registered correctly? Any suggestions would be appreciated.

MS SQL Server 2005 64 bit CTP:[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist o

I am facing a problem with SQL Server 2005 64-bit CTP June 2005 on Windows 2003 64 Bit.

When i try to connect to the SQL Server Instance using any of Windows/SQL Server Authentication from My Application using SQLOLEDB interfaces (From Win32 Code) it is not able to connect and throws following error:

"[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied."

When in the same code I use SQL Native Client (SQLNCLI), it is able to Create and Initialize the interfaces.

When i tried to research on this issue, i found out in Books Online SQL Server 2005 CTP June 2005. That this release only supports SQLNCLI and MDAC support has been removed for this release on 64 bit Windows.

The article says:
"SQL Native Client (SNAC) is available on the 64-bit platform. MDAC has been removed for this release."

Reference:
Books Online Microsoft SQL Server 2005 CTP June 2005
See Topic: "Differences Between 32-bit and 64-bit Editions of SQL Server 2005"

(ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/instsql9/html/e0556daa-19cb-4c08-af02-f542641365a5.htm)

Please let me know if any of you have similar problem. Is there any solution to this other than using SQLNCLI.

I did have similar issue that could not register several Yukon servers from one big brother server. After a little research, solution to the issue was Windows 2003 SP1.

Now, I am facing another issue which is deal with MDAC in 64 bit environment. I've got Win 2003 SP1 64bit and Yukon April CTP i64. One of developer trying to deal with distribute query against to an excel file, it returns an error

"The OLE DB provider "Microsoft.Jet.OLEDB.4.0" has not been registered. "

I looked around and realized that we don't have much ODBC driver available from that 64 bit box. Only available drivers are SQL Native Client and SQL server.

I ran Component checker and it found MDAC2.8 SP2. I also tried to install Jet40 SP8 64 bit, but it say no install needed because there is a newer verion found on system. When I try to create a new data source, I don't have much selections but only two.

As you stated that we don't have much control on MDAC nor Jet40 at this stage. And I've been look for a workaround but no luck yet last two days.

I am keep looking and will post here to imform you if I find some thing.

Thanks
Sunny

|||Hi, Deepak,

Thank you for reporting the problem. Can you tell us:

- is your SQL Server 2005 a default instance or a named instance?
- How do you specify the server in your connection string (the server name, ".", "(local)", etc.)?
- What protocols are enabled on your SQL Server 2005 (TCP/IP, Named Pipes, Shared Memory)?

Thank you,
Peter|||

iam facing this error message kindly assit

Thank you