use [WSS_Content]
select * FROM sys.database_files
ALTER DATABASE [WSS_Content] SET RECOVERY SIMPLE WITH NO_WAIT
DBCC SHRINKFILE(WSS_Content_log, 1)
ALTER DATABASE [WSS_Content] SET RECOVERY FULL WITH NO_WAIT
Archive for the 'Chris' Category
When you are in anonymous mode, published, you dont want any of the SharePoint scripts to be running like named.dll. The way to hide it is to wrapped the SharePoint scripts in a security tab. Thus security trimming the scripts and SharePoint overriding CSS classes.
<Sharepoint:SPSecurityTrimmedControl PermissionsString=”BrowseDirectories” runat=”server”>
<!–showing sharepoint scripts –>
<SharePoint:ScriptLink name=”init.js” runat=”server”/>
<Sharepoint:CssLink runat=”server”/>
</Sharepoint:SPSecurityTrimmedControl>
24
Jul
This product requires ASP.NET v2.0 to be set to ‘Allow’ in the list of IIS Web Server Extensions
I think there might be an issue with .NET 2.0 SP2 that causes my normal fix of “click the reinstall button on .NET 2.0″ to fix this issue. i recently ran into this issue again and it didnt work. What did work is the commands below. Bascially it is uninstalling and reinstalling via regiis.
C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727>aspnet_regiis -u (uninstall)
C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727>aspnet_regiis -i (reinstall)
Why did this happen? No idea. How did I fix it, read below.
- Open central admin
- Goto Operations
- Goto Services on server and located your index server
- On “Office SharePoint Server Search” click “Stop”. This deconfigures it.
- Now click “start”
- Then click “Shared Services Administration”, hover over the failing SSP and select edit.
- You will notice now the indexer is not selected. Select it from the drop down.
- HERE IS THE IMPORTANT PART. The server you have selected is probably the same server as you used before. If it is, go to that server and locate the indexer files. It is in the textbox right below the drop down you just used. For me it was “F:\Program Files\Microsoft Office Servers\12.0\Data\Office Server\Applications”. In there you will find a folder with Guid name. At the end of that folder add “_old”. Now go back to your SSP and click OK. Wait 1 minute and the index will recreate the guid folder.
- Tada, all fixed.
For what ever reason server 2008 creates a file on the OS drive for hybrinating the same size as the RAM that is in the server. Not sure how many servers hybrinate, but not mine.
To turn it off just run this from command line
powercfg -h off
Enjoy.
Open you local GPO using MMC or using the GPO editor in your AD. Then enable “Only allow local user profiles” in Computer Config -> Administrative Templates -> System -> User Profiles
If you completly want to disable roaming profiles on your Terminal Server
you also have to enable “Prevent Roaming Profile changes from propagating to
the server”.
I ran into an issue recently with a log file that would not shrink. All the DB Truncates that I ran would not shrink it. The fix is to just detach the DB, rename the log file and reattach. That will create a new log file from scratch.
Detail are here
sp_detach_db [YourDatabaseName]
then
sp_attach_db @dbname = N‘YourDatabaseName’,
@filename1 = N‘D:\Microsoft SQL Server1\MSSQL\Data\YourDatabaseName.MDF’
I have no idea why, but more and more I am seeing search crawls result in error of “access is denied”. The issue is that the web server is not allowing authentication to sites that are localhost (or local). The fix is simple, but I wish I knew why this was creeping up more.
Fix is here
In short do the follow. The reboot is necessary.
Method 2: Disable the loopback check
Follow these steps:
- Click Start, click Run, type regedit, and then click OK.
- In Registry Editor, locate and then click the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
- Right-click Lsa, point to New, and then click DWORD Value.
- Type DisableLoopbackCheck, and then press ENTER.
- Right-click DisableLoopbackCheck, and then click Modify.
- In the Value data box, type 1, and then click OK.
- Quit Registry Editor, and then restart your computer.
Sometime in a non AD environment you need a user to run an App Pool so you can do cross server work (i.e. SQL). Before you can use the user in the App Pool identity you have to tell ASP.NET that they should be allow to run ASP.NET.
Simple command to run from the C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727 directory
aspnet_regiis.exe –ga [UserName]
This will tell ASP.NET to allow this user to access temp directories and the assembly code.
Just run the tool from here to see if your server or PC can support virtual technology and allow your virtual servers directly access your hardware.
