January 24, 2007 at 7:04 am
I have the following:
Windows Server 2003 STD + SP1
SQL Server 2005 Seveloper Edition + SP1
The install fails at the same spot everytime - at the end when installing workstation components and books online. Yes, I am installing the SQL Server as administrator.
Error in the event log: Event ID: 11304 Source: MsInstaller
Description: Product Microsoft SQL Server 2005 Tools - Error writing to file: Microsoft.SqlServer.Edition.dll. Verify that you have access to that directory.
The server obviously fails the install, but will come up. Microsoft SQL Server Management does not install however.
I've searched the net looking for a solution, but none have worked thus far.
Any help would be greatly appreciated.
John
January 24, 2007 at 7:44 am
are you installing from CD? maybe it's scratched? Try copying all the files to the HD or somewhere on the network and installing from there
January 24, 2007 at 7:48 am
Yes, and I've done what you said also, copied to a share. Then again, maybe the contents of the cd are corrupt and then corrupt on the share also.
I have seen alot of people with the symptom that I am experiencing, ie: Management Studio does not get installed. Going to try and uninstall and reinstall with a fresh set of cd's that a coworker has. thanks
January 24, 2007 at 12:06 pm
try copying the install files locally, i had an issue a few times when installing from a share
January 24, 2007 at 12:19 pm
ok, thanks, will do. Also, I stumbled upon something, maybe others might run into this, my download from MSDN and subsequent copy of the ISO images to cd's failed to make the necessary folders, server and tools. That might be the problem. here's a post that I found describing this. My cd's didnt have these folders. hope this helps others who download dev edition for development work.
I am currently using SQL Server 2005 Developer Edition, and the installation disk directory hierarchy should be the following:
2005-10-19 05:47 <DIR> SQL Server Itanium
2005-10-19 05:48 <DIR> SQL Server x64
2005-10-19 05:47 <DIR> SQL Server x86
2005-09-22 16:11 77 autorun.inf
2005-10-19 05:03 9,258 default.htm
2005-09-22 16:11 4,282 splash.hta
3 File(s) 13,617 bytes
3 Dir(s) 0 bytes free
and in the "SQL Server X86" directory, you can find:
2005-10-19 05:47 <DIR> .
2005-10-19 05:48 <DIR> ..
2005-10-19 05:47 <DIR> Servers
2005-10-19 05:48 <DIR> Tools
2005-07-29 16:13 76 autorun.inf
1 File(s) 76 bytes
4 Dir(s) 0 bytes free
so management studio's installer is in the "Tools" directory, hopefully this can help.
January 25, 2007 at 3:29 am
You have hit the 2 CD problem.
The SQL 2005 install media are divided into 2 CDs. CD 1 contains the server components, and CD 2 contains the client components. For DVD install media, the CD 1 relates to the Servers folder, and CD 2 relates to the Tools folder.
If you install from real CDs the install process prompts you to put the tools CD into the drive after it has done with the server components. In a DVD install, the switch is done automatically. If you copy the install media to disk, the swap does not get done, and your install fails when it needs files from the tools media.
It is possible to create a single install folder on disk. Step 1 - copy the tools CD to your install folder. Step 2 - copy the server CD to the same folder. You can now run an install from that folder that will install both the server and client components. (If you copy the CDs in the wrong order you can only install client components!) We have set up a single disk install folder here and it works fine.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
January 25, 2007 at 12:27 pm
Got the new cd's and tried what you said, it worked!!!
Thanks everyone
John
January 31, 2009 at 3:25 pm
EdVassie (1/25/2007)
You have hit the 2 CD problem.
The SQL 2005 install media are divided into 2 CDs. CD 1 contains the server components, and CD 2 contains the client components. For DVD install media, the CD 1 relates to the Servers folder, and CD 2 relates to the Tools folder.
If you install from real CDs the install process prompts you to put the tools CD into the drive after it has done with the server components. In a DVD install, the switch is done automatically. If you copy the install media to disk, the swap does not get done, and your install fails when it needs files from the tools media.
It is possible to create a single installfolder on disk. Step 1 - copy the tools CD to your install folder. Step 2 - copy the server CD to the same folder. You can now run an install from that folder that will install both the server and client components. (If you copy the CDs in the wrong order you can only install client components!) We haveset up a single disk install folder here and it works fine.
Hey, Ed, we have our installation media copied to folders just called CD1 and CD2 and haven't hit a problem with installs, so does it really matter what the folders are called?
Do you know why it matters that the tools folder is copied first, seeing as there is no overlap? I don't know in which order our folders were created.
regards
george
---------------------------------------------------------------------
February 4, 2009 at 5:14 am
George,
Maybe it does not matter what the folders are called, I have not tried different folder names.
Provided that the CD1 media is in a different folder to the CD2 media, it does not matter which gets copied to disk first. If you are copying media for different editions, then have a parent folder for each edition.
e.g. SQL2005-Dev\CD1 and SQL2005-Dev\CD2, SQL2005-EE\CD1 and SQL2005-EE\CD2. The SQL Install program will look in sibling folders for Server or Tools components, but will not search further.
This means that if you set up media in the form CD1\SQL2005-Dev, CD1\SQL2005-EE, CD2\SQL2005-Dev, CD2\SQL2005-EE then the install routine will not find the right components.
If you merge the contents of CD1 and CD2 to the same folder, then the Tools media must be copied first, otherwise the install files for the server media will be overwritten. However, it is far better to keep the CD1 and CD2 folders separate when they are copied to disk.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
February 4, 2009 at 5:28 am
cheers Ed. Thanks for the clarification. I was wondering about naming convention because all references to copying CDs I found referred to calling the folders servers and tools, and I wondered if i was missing something even though i was not hitting problems.
regards
george
our folders are called CD1 and CD2, works fine.
---------------------------------------------------------------------
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply