October 8, 2010 at 8:07 am
Hi Folks,
I have another question today. I was trying to get analysis by Microsoft Baseline Configuration Analyzer 2.0 for our SQL Server 2008 installation using SQL Server 2008Rs BPA.
Now, I am running this BCA from my workstation, so I am selecting "connect to another computer" option, I am sure that I am administrator of that remote machine and this local machine. But to be sure, I feed my ID and PWD in required fields too.
After this much configuration when I try to run BPA, it gives me error
The specified module "baselineconfigurationanalyzer" Was not loaded because no valid module file was found in any module directory
I have checked that everything is 64bit (my workstation, remote server, BPA). I have also setup WinRM to accept remote connection to remote server. I tried to google this error but it seem that nobody had this before (or it displays lots of wrong results because of my long string)
Is there any suggestion for me ??
Thanks,
-Jack
October 8, 2010 at 1:48 pm
I ran into the same issue. It's a little convoluted to scan another server.
After you select local server and SQL Server 2008 R2 BPA on the Home page, select Start Scan.
On the "Enter Parameters" page you can specify a remote server to scan "Alternate_Server_to_Scan"
July 31, 2013 at 6:37 pm
Thanks SSCrazy. Your fix worked for me. I was getting the same error, but clicking start scan and putting it in the alternate server to scan field worked. I also had to add my login and make is specifically an SA role....using a group does not work...many things in SQL still don't really always understand AD groups from my experience.
Before I ever go to this error, I had WinRM issues, but after running(on the target)
winrm e winrm/config/listener
and seeing none existed on my target, I ran
winrm qc
which opened a default listener
I also had to open 5985 5986 tcp from my scanning system in the firewalls etc.
A simple telnet to 5985 etc can help determine if you have that working, and also
New-PSSession -ComputerName <yourcomputer>
can also help determine basic connectivity.
This tool was never this hard to get working 5-8 years ago, but it was a real hassle this go around.
Another prerequisite is perhaps having SSMS of the version /module your are scanning installed on the client as well.
Microsoft could do a lot better job doing some prerequisite checks and installer improvements and error messages on both this tool and the SQL upgrade advisors. I have had numerous issues in the last few years trying to find the right combination to get these seemingly simple tools to work. SQL is pervasive now and has been so MS could do a lot more simple checks for the things they know don't work with these tools, e.g. putting UA for 2005(to scan an old server) on a system with 2008 installed...all the .dlls are out of sync and you get errors etc. Anyway, you have to google like crazy to find these obscure workarounds. All of us tend to have a couple of versions of OS and SQL running nowadays so it is nightmare trying to figure out the combo every time.
March 12, 2014 at 6:03 am
Thanks it worked form me.
it was giving error while connecting to remote computer but worked fine after start scan and adding remote computer name in parameter.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply