Execution ' GUID ' not found during SSRS

Running a SQL Server Reporting Services Report and stumbled upon this error for every report.

Execution ' GUID ' not found

This is how I fixed it.

Created a Text file and named it sessionTimeout.rss

Public Sub Main() Dim props() as [Property] props = new [Property] () { new [Property](), new [Property]() } props(0).Name = "SessionTimeout" props(0).Value = timeout props(1).Name = "SessionAccessTimeout" props(1).Value = timeout rs.SetSystemProperties(props) End Sub

Save the file to the C:.

Then Run this command in command prompt:

rs -i sessionTimeout.rss -s http://localhost/reportserver -v timeout="6000"

(You might need to change the url if you did not keep it defaulted).

Your reports should now run.

Script to delete everything in all tables in database.

select

'Delete from ' + convert(varchar(max),name)

from sys.tables

Great Site for SSRS Inormation

Here is a site that I used to determine how many times a specific report was ran.

Security 101 - Seven Ways You Give Thieves Dibs On Your Database

http://www.darkreading.com/database-security/167901020/security/news/231601414/seven-ways-you-give-thieves-dibs-on-your-database.html?pgno=1#articleArea

How to strip spaces.

UPDATE [TABLE]

SET [COLUMN] = LTRIM(RTRIM([COLUMN]))

WHERE LEN([COLUMN]) <> DATALENGTH([COLUMN])

Free Stanford Introduction class on Databases

Stanford is teaching a free class on databases. You should check it out.

Ran into a new error today when working with Linked Servers.

The operation could not be performed because OLE DB provider "SQLNCLI10" for linked server " " was unable to begin a distributed transaction.

OLE DB provider "SQLNCLI10" for linked server " " returned message "The partner transaction manager has disabled its support for remote/network transactions."

As the error mentioned above this is a distributed transaction error.

1st I verified that the "Distributed Transaction Coordinator" service was started, which it was but still got the error. I then verified in the properties of the service and made sure that all the security information was checked to allow inbound and outbound communication, still had error.

What ended up happening was my IT team cloned the servers which caused these issue.

Solution:

The cloned servers copied the same DTC names to the linked servers. To fix the issue you need to uninstall and reinstall DTC.

Ran the following command prompt commands:

Net stop medic

Msdtc –uninstall

Msdtc –install

Net start medic

The key now which is not in any other article that I have found is to:

Restart SQL Server