It is not recommended to truncate the transaction log. Instead initiate a Transaction Log backup for that database and then issue SHRINKFILE on the transaction log file.

Some good information about...

Please install Windows Installer 4.5 and try installing SQL Server 2008. More details here

It always recommended to have the FULL backup of all databases (if size and time permits), especially the system databases. You never know when one runs into some problems.

Like Marco mentioned it could be due to compressed folders. Please go through this discussion

Here is one

DBCC LOGINFO has information about VLFs. Read on

Yes there are two Error Logs. SQL Server Error Log and SQL Server Agent error log. You can easily read them using sp_readerrorlog stored procedure. More information here[/url]

There is an option in the GUI itself to change the Protection Level. You may find this article useful.

Did a restart of the SQL Server service help?

Good to know that it was fixed!

Does running the query inside "collection_set_1_noncached_collect_and_upload" job in SSMS complete successfully?

You may find this link useful where MS is acknowledging that connecting from SSMS 2008 to SSIS 2005 is not possible.

If the Login "domainname" has System Admin privileges on the instance as stated earlier, then the issue has to be outside of SQL Server. Do you see any error messages...

Can you please post the complete error message?

To add to what Lowell has mentioned, copy that shortcut to the below folder. Since you don't have "Microsoft SQL Server" folder create it manually before copying the shortcut. This...