Answered by:
SQL Server install error 1310 system error 80

Question
-
When installing SQl server 2008 I am getting a 1310 error, system error 80 on the Microsft.analyisservices.adomdclient.dll.
The install is being done by the adminstrator but is being carried out from a remote terminal.
Multiple other installs have completed fine on the server and admin rights appear fine.
see log entries below for detail. Is this because we are installing remotely? or is there another reason that anyone can suggest
Thanks.AssemblyCopy(SourceName=tgns2gue.dll|Microsoft.AnalysisServices.AdomdClient.dll,SourceCabKey=AS_Microsoft_AnalysisServices_AdomdClient_dll_32,DestName=Microsoft.AnalysisServices.AdomdClient.dll,Attributes=0,FileSize=549912,PerTick=32768,,VerifyMedia=1,,,,,ComponentId={14537205-2B1A-4615-B8F3-7247E33A7485},IsManifest=1,,,AssemblyMode=0,)
MSI (s) (C8:14) [16:07:09:728]: Source for file 'tgns2gue.dll' is uncompressed, at 'E:\x64\setup\sql_common_core_msi\Windows\Gac_32\'.
MSI (s) (C8:14) [16:07:09:728]: Note: 1: 1305 2: E:\x64\setup\sql_common_core_msi\Windows\Gac_32\tgns2gue.dll 3: 1
MSI (s) (C8:14) [16:07:09:728]: Note: 1: 1310 2: 80 3: Microsoft.AnalysisServices.AdomdClient.dll
MSI (s) (C8:4C) [16:07:48:759]: I/O on thread 6100 could not be cancelled. Error: 1168
MSI (s) (C8:4C) [16:07:48:759]: I/O on thread 5992 could not be cancelled. Error: 1168
MSI (s) (C8:4C) [16:07:48:759]: I/O on thread 3996 could not be cancelled. Error: 1168
MSI (s) (C8:4C) [16:07:48:759]: I/O on thread 3860 could not be cancelled. Error: 1168
MSI (s) (C8:4C) [16:07:48:759]: I/O on thread 6088 could not be cancelled. Error: 1168
MSI (s) (C8:4C) [16:07:48:759]: I/O on thread 1072 could not be cancelled. Error: 1168
MSI (s) (C8:4C) [16:07:48:759]: I/O on thread 5716 could not be cancelled. Error: 1168
MSI (s) (C8:4C) [16:07:48:759]: I/O on thread 1812 could not be cancelled. Error: 1168
MSI (s) (C8:14) [16:07:48:759]: Product: Microsoft SQL Server 2008 Common Files -- Error 1310. Error writing to file: Microsoft.AnalysisServices.AdomdClient.dll. System error 80. Verify that you have access to that directory.Error 1310. Error writing to file: Microsoft.AnalysisServices.AdomdClient.dll. System error 80. Verify that you have access to that directory.
Wednesday, September 16, 2009 4:24 PM
Answers
-
In my case even though the media was 'known good copy', it was still a permissions issues on the Microsoft.AnalysisServices.AdomdClient.dll file. Here is what I did to move around the issue; either Copy the contents of the Media Locally or Download the executable from Microsoft.com locally and restart the intsallation.
I tried both solutions offered above, and no issues were experienced.
Note: This was the first time I experienced the Microsoft.AnalysisServices.AdomdClient.dll permissions issue while installing SQL2K8 on a VM out of 8 successful deployments.
Grock- Proposed as answer by Grock90 Thursday, October 1, 2009 6:44 PM
- Marked as answer by Ed Price - MSFTMicrosoft employee Thursday, April 11, 2013 9:39 AM
Thursday, October 1, 2009 6:43 PM
All replies
-
It seems you do not have Admin access to the server where youa re installing...
Rajesh Kasturi Please click the Mark as Answer button if my post solves your problem.Thursday, September 17, 2009 12:12 PM -
Have you come up a with a resolution to this issue by chance? I have pretty similar issue:
Host: Win2K8 Enterprise Hyper-V Enabled
VM: Win2K8R2 Enterprise
While installing SQL Server 2008 on the VM I get the Following:
Product: Microsoft SQL Server 2008 Common Files -- Error 1310. Error writing to file: Microsoft.AnalysisServices.AdomdClient.dll. System error 80. Verify that you have access to that directory.
Logged into Host over RDP as Administrator, Logged into VM using vmconnect.exe as Administrator.
Captured Media Device of Host Server to VM.
Grock- Edited by Grock90 Thursday, October 1, 2009 6:33 PM Additional info
Wednesday, September 30, 2009 10:17 PM -
In my case even though the media was 'known good copy', it was still a permissions issues on the Microsoft.AnalysisServices.AdomdClient.dll file. Here is what I did to move around the issue; either Copy the contents of the Media Locally or Download the executable from Microsoft.com locally and restart the intsallation.
I tried both solutions offered above, and no issues were experienced.
Note: This was the first time I experienced the Microsoft.AnalysisServices.AdomdClient.dll permissions issue while installing SQL2K8 on a VM out of 8 successful deployments.
Grock- Proposed as answer by Grock90 Thursday, October 1, 2009 6:44 PM
- Marked as answer by Ed Price - MSFTMicrosoft employee Thursday, April 11, 2013 9:39 AM
Thursday, October 1, 2009 6:43 PM -
We also faced the same problem...
But it was because of the downloaded image which was ISO was incomplete download.
Please chaeck the consistancy of the downloaded file for the size.
I redownloaded the image 3.03 GB, this was downloaded from Microsoft Volume Licensing Site.
Then it was installed properly. But now it is giving me error in installing the SP1 for the same.
This was fresh installation, on Windows 2008 R2.
Let me know any one has faced the same...
I will keep on posting on same, till I successfully install the SQL2008 with SP1 on windows 2008 R2.Friday, February 19, 2010 4:32 PM -
My media was gud and I tried thru Terminal console only. It was successful. Only I used the Virtual Media.
Friday, February 19, 2010 4:35 PM -
Hello,
Same issue grock90 , i redownload the image with dowload manager wich has a file integrity checker , and it worked for me.
(Microsoft.AnalysisServices.AdomdClient.dll) SQL 2008 ED x64
Regards
Thursday, April 22, 2010 3:05 PM -
Have you come up a with a resolution to this issue by chance? I have pretty similar issue:
Host: Win2K8 Enterprise Hyper-V Enabled
VM: Win2K8R2 Enterprise
While installing SQL Server 2008 on the VM I get the Following:
Product: Microsoft SQL Server 2008 Common Files -- Error 1310. Error writing to file: Microsoft.AnalysisServices.AdomdClient.dll. System error 80. Verify that you have access o that directory.
Logged into Host over RDP as Administrator, Logged into VM using vmconnect.exe as Administrator.
Captured Media Device of Host Server to VM.
Grock
I still wonder why though I already got it solved, Thanks!Thursday, September 16, 2010 12:23 PM