New answers tagged sharepoint
To go around this issue, modify the tm1web_config.xml file like so: change this <add key="CrossDomainAccessList" value="" /> to <add key="CrossDomainAccessList" value="*" /> and restart the Application Server service.
With netlogon debugging enabled I found the same result in my Win7 SP1 machines (domain controllers are 2008r2SP1). It also caused an 8 second delay in processing so far as I can tell. Looks like a faulty API call from netlogon to me. You can replicate the same 1355 error by running the following on a workstation: nltest ...
This screencast (link only, can't copy video content here) shows how to overcome the 10GB SQLEXP limit by using the file system.
You need to enable Desktop Experience feature after that you can map as drive that SharePoint url. The steps are here.
I removed the sql server from the domain server and readded it again now everything is working.
Ah got it. In SharePoint's central administration web app there's settings for how this gets populated in monitoring, as well as two jobs which tidy it on a schedule. They can be run now with a button, and then dbcc shrinkdatabase tidies it up.
Can you check the default gateway on the servers, then double check the firewall on the SQL server. When you enable RDP on a server, it can add a rule to the firewall which would explain why that is working and not Ping/ICMP. Can you ping the other two servers from the SQL server?
check firewall in guest, disable it if you could just for test.
Top 50 recent answers are included