Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 750
  • Last Modified:

Reinstalled Windows 8.1. Now get errors in Visual Studio.

I came into my office one Monday morning and my computer had crashed.  After a couple of days attempting to get it to boot back up, I finally reinstalled Windows 8 and then did the upgrade to 8.1 from the Microsoft Store.

This was a fresh install, but I did not format the drive.  I ended up with a new Windows and the old Windows folder was renamed to Windows.old.  All per normal.

I reinstalled Visual Studio 2012 then loaded up one of my websites.  All my .aspx pages, from every web site on our server has a blue squiggly under this line:
<%@ Page Language="VB" AutoEventWireup="false" CodeFile="Default.aspx.vb" Inherits="_Default" %>
...that say: Runtime Error. Could not load file or assembly 'Microsoft.AnalysisServices.AdomdClient, Version=10.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies The system cannot find the file specified. (P:\Webfolder\web.config line 43)

Line 43 of the web.config is:
<add assembly="Microsoft.AnalysisServices.AdomdClient, Version=10.0.0.0, Culture=neutral, PublicKeyToken=89845DCD8080CC91" />

One simple test site with only a default.aspx with a couple of controls on it show the error on that declaration line that says:  Failed to map the path '/'.

I haven't attempted any corrective action yet.  I don't want of mess anything up that's not broken.  One forum post recommended doing some drastic things to the SQL Server, which in my case has not changed.  Only my development desktop computer crashed and I reinstalled windows and all the software.  Well, Visual Studio is the only thing I've reinstalled so far.

I hope it's something very simple, like registering a .dll or something.  

I sure could use some help or advice.

Thanks.
0
megnin
Asked:
megnin
  • 14
  • 5
  • 4
1 Solution
 
John HurstBusiness Consultant (Owner)Commented:
(P:\Webfolder\web.config line 43  <-- Why is it looking on drive P: for a file?

Did you install all .NET Framework versions (2 through 4.5) on your system. Some live in recommended (not critical) updates so make sure all your updates are done.
0
 
megninAuthor Commented:
Oh, thank you for that.  I'll check and make sure all the Framework versions are installed and try again.  I'll let you know how it goes.  It's the end of the day so I won't get much more than just checking and updating today.
0
 
megninAuthor Commented:
In Windows Features / Turn Windows features on or off:

.NET Framework 3.5 (includes .NET 2.0 and 3.0) is checked, but the two items under that are not: Windows Communication Foundation HTTP Activation and Non-HTTP Activation

.NET Framework 4.5 Advanced Services is checked and under it,
ASP.NET 4.5 is also checked.

WCF Services is checked and under it TCP Port Sharing is checked but,
HTTP Activation, Message Queuing, Named Pipe Activation, and TCP Activation are not checked.

Internet Information Services is not installed... Hostable Web Core is not, Legacy Components is not.  Just trying to list some things that may or may not have any bearing.
0
Efficient way to get backups off site to Azure

This user guide provides instructions on how to deploy and configure both a StoneFly Scale Out NAS Enterprise Cloud Drive virtual machine and Veeam Cloud Connect in the Microsoft Azure Cloud.

 
John HurstBusiness Consultant (Owner)Commented:
I do not use Visual Studio now on my Windows 8 machine. I did have it installed on my Windows 7 Desktop

For .NET 3.5, I do not have either Communication Foundation items checked on either machine.

For .NET 4.5, I have Advanced Services checked on Windows 8 but not ASP.NET. No harm in you having it checked so far as I can see.

I do not have Internet Information Services installed on either machine.

What I was looking for was Windows Updates. Make sure all the recommended updates are done and see if that makes any difference.

And also please let us know about the use of Drive P: (seems strange to me).
0
 
megninAuthor Commented:
I had run Windows update several times.  I'll doublecheck and make sure I've got all the recommended ones as well.  

Oh, I just mapped my \\WebServer\E$\Inetpub\ folder to P:  We have a bunch of network shares so that was just the next available letter.  ;-)

THanks.
0
 
John HurstBusiness Consultant (Owner)Commented:
It is the network drive where it is erroring out above. Is something in your code referring to a different drive?  This is also something to check.
0
 
megninAuthor Commented:
It says my PC is up to date.
0
 
Paul JacksonCommented:
Install ADOMD.net from the SQL Server Feature pack from :

http://www.microsoft.com/en-us/download/details.aspx?id=16978
0
 
megninAuthor Commented:
It seems like I had this issue when I first got this computer and installed Visual Studio on it.  I had been working on another computer before that.  I either installed something, perhaps SQL Server Management Studio, or just registered a .dll in the GAC or something.  I don't really remember.
0
 
John HurstBusiness Consultant (Owner)Commented:
One thing I would like you to do is answer why you get the P drive error in your first post. That seems to be where the error is. It seems the Windows 8 reinstall changed the drive letter and something else did not change with it.
0
 
megninAuthor Commented:
Yeah, the P drive letter issue may be because I used to have the Inetpub folder on the server mapped to W, but now there's a Dell recovery folder or something taking up "W", so I made it "P."  I'll see if I can fix that.

The other issue.... Could not load file or assembly 'Microsoft.AnalysisServices.AdomdClient, is across all my ASP.Net websites, a bunch of in-house web forms for different programs and projects.

That was happening before I mapped the drive to P.
0
 
Paul JacksonCommented:
Have you installed ADOMD.net as I suggested?
0
 
megninAuthor Commented:
Hi Paul,

I got caught up with something.  I'm working on that now.  It seems like I did something of that sort the last time.
0
 
megninAuthor Commented:
Thank you very much for including the link to the feature pack.  I'd have never found the right one.  Googling yesterday I did come across a reference pointing to this solution, but it took me to the SQL Server 2012 version.  2008 R2, which your link points to is the correct one for me.
0
 
megninAuthor Commented:
This looks like what I need.   Is there anything else in here that I should install?

Microsoft® SQL Server® 2008 R2 ADOMD.NET  ADOMD.NET is a Microsoft .NET Framework object model that enables software developers to create client-side applications that browse metadata and query data stored in Microsoft SQL Server 2008 R2 Analysis Services. ADOMD.NET is a Microsoft ADO.NET provider with enhancements for online analytical processing (OLAP) and data mining.

Note:The English ADOMD.NET setup package installs support for all SQL Server 2008 R2 languages.

 Audience(s): Customer, Partner, Developer

X86 Package(SQLSERVER2008_ASADOMD10.msi)
For our system --> X64 Package (SQLSERVER2008_ASADOMD10.msi)
IA64 Package(SQLSERVER2008_ASADOMD10.msi)
0
 
megninAuthor Commented:
Do you think I need to install this, too?  Sorry for the noob questions.

Microsoft® SQL Server® 2008 R2 Native Client   ?
0
 
Paul JacksonCommented:
Yes you are likely to need that if it wasn't already installed when you installed visual studio.
0
 
megninAuthor Commented:
Okay.  I have those two packages installed and rebooted my computer even though a reboot was not indicated after the installation.  I figure it couldn't hurt.  I'm about to load up VS 2012 and see how it looks.

Do you recommend any of the packages in that list?  Like maybe this one and its associated requirements?

Microsoft® SQL Server® 2008 R2 Shared Management Objects
The SQL Server Management Objects (SMO) is a .NET Framework object model that enables software developers to create client-side applications to manage and administer SQL Server objects and services. This object model will work with SQL Server 2000, SQL Server 2005, SQL Server 2008 and SQL Server 2008 R2.
Note: Microsoft SQL Server 2008 R2 Management Objects Collection requires Microsoft Core XML Services (MSXML) 6.0, Microsoft SQL Server Native Client, and Microsoft SQL Server System CLR Types. These are available on this page.

I'll report back after I load up my web site solutions and see how they look.
0
 
Paul JacksonCommented:
You shouldn't need that unless you are planning on having apps manage sql server directly, probably worth installing Microsoft Core XML Services that tends to be used by a lot of things.
Of the others you may need SQL Server Report Builder if any of your apps are using SQL Server reports.
0
 
megninAuthor Commented:
Opening the web site using the mapped drive letter for the path resulted in an error stating:
DirectoryNotFoundException: Could not find a part of the path X:\blablabla

Googling got me this forum post:

"As wata suggests, each user gets their own mapped drives. This means that your L: drive is not the same as your app pool account's L: drive."

I opened the web site using the UNC path:  \\WebServer\C$\Inetpub\MyWebsite and it looks just fine so far; no blue squiggles.

Maybe I should just continue to use the UNC path to open web sites/application in Visual Studio.
0
 
megninAuthor Commented:
Yeah, I agree with the XML Services and Report builder.  I do occasionally use an XML file as a data source and we use SSRS for many reports on the same data my forms enter and manage the data for.

Thanks.  I'll install those two, also.

Question related to my post just above this one...  I've never been very clear on the advantages disadvantages or repercussions of using either a mapped drive letter or the UNC path to open a web site in Visual Studio.  Do you have any information or experience you could share with me about that?
0
 
Paul JacksonCommented:
I don't have a great deal of experience of using mapped drives and unc paths for connecting to websites  but I would of thought there would be issues using mapped drives because of the file paths that then get saved in the project properties, it much easier to use a unc path then you should avoid such issues.
0
 
megninAuthor Commented:
Thank you very much, Paul.  That seems to have solved the problem.  I'll continue to use UNC paths.  I used to use UNC paths then I started using mapped drive letters.  There was something about debugging that didn't work with UNC paths but did with mapped drives.

John, thank you for your assistance as well.
0

Featured Post

Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

  • 14
  • 5
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now