Activity overview
Latest activity by tdietrich
You don't need to really change the URL, you just need to have the link on that menu append a / to it. overviews/cluster/whatever.ad/ will work with default IIS settings.
Frankly, I can change the settings, but .ad is a reasonably well used and recommended suffix for domains from what I know, so I wanted to alert you guys to the possible issue. / comments
You don't need to really change the URL, you just need to have the link on that menu append a / to it. overviews/cluster/whatever.ad/ will work with default IIS settings.
Frankly, I can change the ...
404.7 exception when trying to get a cluster overview.
Our domain name ends with .ad, which is one of the blocked file extensions in the default configuration of IIS7.
Because of this, when I try to browse from the main menu to our cluster (url=overvie...
The issue was isolated to a configuration setting preventing connections to the remote registry at the SQL cluster's address.
Our network administrator found the solution: http://social.technet.microsoft.com/Forums/eu/configmgrsetup/thread/8b4a2246-1cff-4d31-9513-c1239c1e694b
Of the tests we conducted above the root cause of the short file name error during the Pre-req checks was found to be the fact that we were not able to remotely access the registry using the SQL Virtual name which we should have been able to do. On contacting Microsoft Support we were informed that there are known issues around NoRemap registry key needing to be set if you are using Network Name resource that is dependent on a separate new IP Address resource – see http://support.microsoft.com/?id=306985
The final solution was to add a new REG_MULTI_SZ registry key to BOTH cluster nodes called:-
NoRemapPipes to:-
HKLM\SYSTEM\CurrentControlSet\Services\lanmanserver\parameters\
This key should contain the values of:-
WINREG
EVENTLOG
svcctl
After adding the above key and values we needed to reboot both cluster nodes and then we were able to connect to the SQL Virtual names (CLUSQL02 + CLUSQL01) using Regedit (Remote registry). Running the SCCM Pre –req checker now returns no errors.
Hope this soluton helps someone else.
/ comments
The issue was isolated to a configuration setting preventing connections to the remote registry at the SQL cluster's address.
Our network administrator found the solution: http://social.technet.mic...
I've ran though every step in this test: http://www.red-gate.com/supportcenter/C ... 469857.htm
They all worked properly. Now I'm really stumped.
Edit:
Actually, I can not remote connect to the registry at the SQL cluster's address, but I can at the Windows cluster, the DTC cluster, or either node of the cluster's address. / comments
I've ran though every step in this test:http://www.red-gate.com/supportcenter/C ... 469857.htm
They all worked properly. Now I'm really stumped.
Edit:
Actually, I can not remote connect to the regi...
Error monitoring Clustered SQL server
Getting the error: Unreachable (Cannot connect)
The log reads as follows:
18 Jun 2012 9:12 AM SQL Ping Connected
18 Jun 2012 9:12 AM Registry OpenRegistryHive: PerformanceData Cannot connect Win32E...
Incompatibility with v4.0 app pools on server?
Running SQL Monitor 3.1 on a v4.0 app pool, I get this error on browsing to the site:
There is a duplicate 'system.web.extensions/scripting/scriptResourceHandler' section defined
If I change the...
Good information, thanks! Looking forward to seeing this fixed and maybe seeing Git become more of a first party to the tool. / comments
Good information, thanks! Looking forward to seeing this fixed and maybe seeing Git become more of a first party to the tool.
I find your lack of git disturbing
Pardon the StarWars reference.
Your implementation of git integration in this product is somewhat flawed.
First item:
When committing changes, you run the command "git checkout -q {filename}".
Chec...