In SQL Server 2012R2 I found that my Log files were always getting so big that they would fill the L drive. So I wrote a script that will Truncate all the Log files. You can also do this on each individual database by right clicking, select Shrink, then Files. Click OK. See below for more details.
Also Check this URL: What is the command to truncate a SQL Server log file? - Stack Overflow
In management studio:
- Don't do this on a live environment, but to ensure you shrink your dev db as much as you can:
- Right-click the database, choose Properties then Options
- Make sure "Recovery model" is set to "Simple" not "Full"
- Click OK
- Right-click the database again, choose Tasks -> Shrink -> Files
- Change file type to "Log"
- Click OK.
Alternatively, the SQL to do it:
USE DatabaseName
ALTER DATABASE DatabaseName SET RECOVERY SIMPLE
DBCC SHRINKFILE (DatabaseName_Log, 1)
ALTER DATABASE DatabaseName SET RECOVERY FULL
SharePoint 2010 CU update error: CanUpgrade [Microsoft.SharePoint.Administration.SPIisWebSite] failed.
https://social.msdn.microsoft.com/Forums/en-US/f6f30ede-b614-4773-be98-0c9fac29ca37/upgrade-session-failed-100-complete?forum=sharepointadmin
Steps to Resolve:
-----------------------------------
Open Central Admin - Manage Web Applications - Select web application - Click on Delete Drop Down (Do not click on Delete Button) - Select Remove SharePoint from IIS Web site - Click following drop down - Remove SharePoint from IIS - Select IIS web site and zone to remove - Check if you see any web site which is not present in IIS - If you see any web site which is not under IIS then just select that and remove it from SharePoint.
Note:- Follow above steps on all SharePoint web servers.
Once above steps are done you can again run the PSConfig upgrade wizard and it should be successfull.
Upgrade command: psconfig.exe -cmd upgrade -inplace b2b -wait -force
The solution is here: [SOLVED] Relocate Virtual Machine Files - Spiceworks
Basically, shut down the VM. Right-Click on it and Select Move. Then Move the Configuration. Done!
From here: https://serverfault.com/questions/396722/your-system-administrator-does-not-allow-the-use-of-saved-credentials-to-log-on
If you don't want to change local or server side GPOs:
Go to Control Panel
-> Credential Manager
on the local computer you are trying to connect from.
You will see three sections:
- Windows Credentials
- Certificate-Based Credentials
- Generic Credentials
Remove the credentials from Windows Credentials
and add it to Generic Credentials
.
From here: https://superuser.com/questions/579900/why-cant-excel-open-a-file-when-run-from-task-scheduler
1. Open Component Services (Start -> Run, type in dcomcnfg)
2. Drill down to Component Services -> Computers -> My Computer and click on DCOM Config
3. Right-click on Microsoft Excel Application and choose Properties
4. In the Identity tab select This User and enter the ID and password of an interactive user account (domain or local) and click Ok
Keeping it as the interactive user or the launching doesn't work with the task scheduler unfortunately, even when setting the task up to run under an account that has admin access to the machine.
From here: https://www.access-programmers.co.uk/forums/threads/subreport-headers.256308/
In the Subreport do the following and you will have the Report header on subsequent pages.
1. Click on "Add a Group"
2. Select "Expression"
3. When the Expression Window appears, type in "=0" and click OK
4. Make this group only have a header section
5. Click on the group's header section
6. Go to Property Sheet and make sure "Repeat Section" is set to "Yes"
Done!
Question and solution here: https://superuser.com/questions/402070/run-task-scheduler-task-on-demand-from-limited-user-account-in-windows-7
Go to C:\Windows\System32\Tasks find the related task and assign "read and execute" rights to the user you want to be able to access it. Be sure to assign to "current object only." Then the task will be visible and runnable from the limited user, and it will work if you saved your credentials in it and checked "run whether user is logged on or not."
a) Commented out the line where the phantom breakpoint appears
b) Copied the same line to the next line.
c) Saved the file.
d) Reran.