Problems installing MSDE

I was in the process of installing the MSDE program when I came upon an error message. Here are the steps I performed to install the MSDE on my computer.

1. Downloaded the program from the Microsoft website.
2. Extracted the files to the "C" directory.
3. Used command prompt to set password and security mode. Rebooted computer after process was completed.
4. To complete the installation, I opened up the setup.exe. However, I got the error message "The instance named specified is invalid" when I opened the program.

Any solutions? (and yes, I already have the Web Matrix and the .Net platorm and am running on Windows 2000 SP4 .)I just finished dealing with this problem myself.

This is what I did and it FINALLY WORKED.

To install the MSDE:

go to the DOS prompt and navigate to C:\sql2ksp3\MSDE (or wherever you unpacked to).

Type this: setup INSTANCENAME="anyname" SECURITYMODE=SQL SAPWD="somepwd"

If you are like me you were thinking "what is the instance name?!". Well in this setup command you are naming it whatever you want, same with the SAPWD. Previously mine was blank (I know this is bad bad bad).

Anyway, once I ran it this way it installed fine!

Good Luck|||Well this may sound really stupid, but I;m a real newbie...

I've read dozens of setup instruction posts..I've started over and done what was suggested in this post, and everything seems to have gone well. SO FAR

Where do I go from here? Do I have to activate the database somehow? Where is this database anyway, after the I run the command, what was installed and where?

The startkit 'congifuration' still fails everytime. Says I don't have either .NET, MSDE, or IIS. I KNOW I have all of this installed..the only weak link could be the MSDE, because I have no idea what is going on with it.

I've installed SQL Server2000 in the past and got to a point where it configured and coulnd fidn the database..

Anyway, are there STEP BY STEP instructions ANYWHERE on this crap. I'm getting sick of reading random posts, web documentation, program documentation, and trying to compile this in to a process to follow..|||As Cheyjey mentioned, use this parameters:
INSTANCENAME="anyname" SECURITYMODE=SQL SAPWD="somepwd"

But you said installed it once, i have to mention that one the major reasons for getting the error you said, is that you have already installed MSDE on your system...|||i mean MSDE SP3a|||And Dear Mickey,

it's not as hard as you say, MSDE is a kind of a server, you can use it either as a server and an interface between applications and SQL Server 2000|||Amins2s,

I've read many post regarding the installation of MSDE, and i'm having the same problems.

I'm new at this and have followed instructions, and am using MSDE for school project.

I have installed VS 2002 Enterprise Architect, then uninstalled it to upgrade to VS 2003
I download the MSDE SP3a service pack from MS, and try to install it.

I'm suppose to use SAPWD=itm and SECURITYMODE=SQL, but upon typing this, i get the speciefed instance is invalid.

How am i suppose to recitfy this. How do i know what the instance i have on it is?

Also you said that you might be getting this error because you have already installed it once before. But i don't remember installing it, since the only thing i have installed is the VS2002 and VS2003, plus the Framework.

If you've installed it once before, how can you correct it so that you can properly install it now?

Even when i go to the MS .net/Frameworksdk/samples/setup/ there is no msde file to execute, which i read from other post should be there.

Thank You.

Nick|||Hello dear Nick,

ok... give this solution a try: do not indicate the SECURITYMODE parameter. Just run it from the Start>Run and use the SAPWD=itm parameter only!
And from the point that my FrameworkSDK doesn't work (the CD is corrupted), unfotunately I can't answer the question.
Please try it and tell me if it worked or not.
If it didn't, then send a feedback (Reply) and this time with more details about your system info...

Problems connecting to SSAS instance over HTTP in Excel 2003

Our Biz users are all running Excel 2003, and we've recently set up a bunch of cubes that we'd like to open up to them.

I followed the steps here: http://www.microsoft.com/technet/prodtechnol/sql/2005/httpasws.mspx
to set up HTTP access to SSAS2005. It works great from my machine, I figured because I had SQL 05 installed locally and all the requisite drivers, etc.

On our biz users' desktops, however, it wasn't as peachy.

I first figured out I had to install MSXML6 and the SSAS 9.0 driver on their machine to connect to the cube. I downloaded those from here:

http://www.microsoft.com/downloads/details.aspx?familyid=d09c1d60-a13c-4479-9b91-9e8b9d835cdc&displaylang=en

Once I was able to set up the connection to the cube, and about to create a pivot table in Excel, the Query wizard failed, with this error:

"XML parsing failed at line 1, column 9: DTD is prohibited"

Googling didn't seem to uncover anything useful, has anyone seen this before?

Not sure how google works, but using Windows Live Search (www.live.com) discovered the following thread:

http://www.topxml.com/MS-XML-Analysis/rn-132023_HTTP-XML/A-access-to-AS2005-cause-an-error.aspx

In the thread user Jeje attached the HTTP trace, which is pretty helpful - it shows that first client components tried to use 9.0 driver, but then falled back to 8.0 driver, which is probably the reason for the error. Why did it fall back to 8.0 - perhaps a permission issue ?

|||Whoops, now I feel bad for not using Live . I'll have to be sure to use both now!

Mosha - security sounds like it could be a probable cause. I'll try experimenting with permission issues tomorrow. Also, on a related thread in the same forum a MS employee noted:

Sent date: 01/06/2006
From: "Akshai Mirchandani [MS]" <(email address - cut out)>
Message:
This is a known issue -- a hotfix should be available soon from support.

Thanks,

Akshai

(http://cc.msnscache.com/cache.aspx?q=4937159748319&lang=en-US&mkt=en-US&FORM=CVRE2)

Are you aware of any related hotfixes that address this issue?|||Argh, I tried completely loosening security on the olap/ folder and its children, but this doesn't seem to help at all. I checked our IIS logs and like in Mosha's link the client seems to be attempting the 9.0 driver and then falling back to the 8.0 driver, which of course doesn't work.

Anyone know if there's a hotfix for this?|||Interesting. Changing IIS auth to anonymous seems like it completely solves this problem...although I'm unsure of the security implications -

Client -> IIS (msmdpump.dll) -> SSAS

If IIS is not using windows auth, does SSAS just use the anonymous user's credentials (ie the IUSR_ acct) to authenticate?|||

If you run Profiler against the Analysis Server, you can see which user attempted to connect -- if it was the IUSR_xxx or similar user then you know it is a security issue and the Pump is not able to delegate the user credentials to the Analysis Server for some reason.

I believe the hotfix was about using Basic authentication which doesn't seem to be your scenario.

Thanks,

Akshai

|||

Hi all,

I've also been encountering issues with HTTP access to SSAS 2005, but with excel 2007.

Although it's working from excel 2003 (but only if the option to save the username/password is checked when creating the data source for the pivot table), it won't let me access it from excel 2007. I always get an access denied-like message when i try to set up the connection to the data source.

We haven't been able to identify where is the issue. We set the HTTP access as via the link mentionned before, but that won't let us access from excel 2007.

We've also been facing some backward compatibility issues using excel 2003 with OLE DB provider for analysis services 9.0 installed.

With it we can not connect to our SSAS 2000 cubes (again via http) anymore, the error is the response returned via the HTTP server is not valid (even though we try using the OPAL 8.0 driver).

Any idea how we could solve that issue? did we miss a component to install to ensure compatibility with both version of SSAS?

thanks in advance for your help.

Cheers, and happy new year!

sql