i think you want to use a different function right?

this page from Microsoft has a decent example:
https://docs.microsoft.com/en-us/sql/relational-databases/system-functions/getfilenamespacepath-transact-sql

what does this return for you?
SELECT...

Probably not enough information...what, specifically, is the package doing?
i would be looking at performance in the database first and foremost, assuming the package is doing something in the database....

i'll help with the slightly more difficult one(#2)
for number 1, sys.databases has a create_date column.

for #2, i put this together, and it returns serveruptime, vs service uptime.

youll need basically three commands for each identity insert, because you have to toggle the setting off on one table, before you set it ON for the next.

i could not tell you; the logic looks strange.
if rows get inserted, that is considered an error? IF ( @Count <> 0 ) INSERT INTO dbo.Log(Error....

designwise, the procedure itself...

CREATE PROCEDURE outputParamTest(@Count int OUTPUT)
AS
BEGIN
--do something that affects some number of rows.
SELECT * INTO #temp FROM sys.tables
SELECT @Count = @@ROWCOUNT

END

most likely you are looking for the HAVING function.

so something like this:
SELECT cust_id,sum(orderAmount) As TheSum
From SomeTable
Group by cust_id
HAVING sum(orderAmount) > 1000

maybe using row_number will get what you are after?
With LatestGUIDBasedOnCompDate
AS
(
SELECT Row_number() OVER(Partition BY ID ORDER BY ISNULL(CompDate,'1900-01-01') DESC) AS RW,
ID,
CUST_ID,
CompDate
FROM...

I went through the effort to get the MCSA for SQL 2012/2014. That let me take a single test to get the MCSA for 2016 So I've got TWO MCSAs....

i believe what the error is saying is in the operating system on the machine that hosts SSRS, you have to be a local admin on the box...typically you'd add...

you have to convert all your fields to the same explicit data type.
here's a full example, based on your copy/paste:
note my CTE, which represents your data, has three...

That Msg 0/State 0/Line 0 is upsetting; i expect better error reporting than that.

it might be a known issue, that requires updating to the latest patches for 2005;...