Error 444 - Permission denied.

OK, I'm at a complete loss. Any advice on the following would be greatly
appreciated. What I've got is multiple reports that are heavy process
intensive(multiple datasets, multiple joins, etc). Reports usually take
between 25 and 35 minutes. All was fine until yesterday. Now the reports seem
to run forever. Then finally after an hour we get a 444 error and a
permission denied dialog box. These reports have been running for months
without issue. We've even gone so far as to switch to a new server and still
get the same errors.
Any suggestions?Can you launch SQL Profiler and run a trace and see what connection
credentials are being presented to the dataserver and what the
queries/sprocs are? After capturing the trace you should be able to open
the trace and replay it. My guess is that it is not a SQL issue but this
will help confirm that.
I tried to do some looking up on what error 444 means, is that from MS SQL,
or DB2? or from IIS? Also can you open the Add/Remove Programs, check the
'show updates' box and look for updates installed around the same time as
when the problem started occuring. I've been keeping our machines up to
date and haven't had issue, so not much help here, sorry.
Steve MunLeeuw
"dbutler" <dbutler@.discussions.microsoft.com> wrote in message
news:52C330E6-AEBE-4B59-91C6-99F4E8FD5574@.microsoft.com...
> OK, I'm at a complete loss. Any advice on the following would be greatly
> appreciated. What I've got is multiple reports that are heavy process
> intensive(multiple datasets, multiple joins, etc). Reports usually take
> between 25 and 35 minutes. All was fine until yesterday. Now the reports
> seem
> to run forever. Then finally after an hour we get a 444 error and a
> permission denied dialog box. These reports have been running for months
> without issue. We've even gone so far as to switch to a new server and
> still
> get the same errors.
> Any suggestions?|||I'd also use the RS 2005 Configuration tool to check what accounts are used,
and if they have had a password change or expire. Maybe it's a private key
backup issue...grasping at straws.
Steve MunLeeuw
"dbutler" <dbutler@.discussions.microsoft.com> wrote in message
news:52C330E6-AEBE-4B59-91C6-99F4E8FD5574@.microsoft.com...
> OK, I'm at a complete loss. Any advice on the following would be greatly
> appreciated. What I've got is multiple reports that are heavy process
> intensive(multiple datasets, multiple joins, etc). Reports usually take
> between 25 and 35 minutes. All was fine until yesterday. Now the reports
> seem
> to run forever. Then finally after an hour we get a 444 error and a
> permission denied dialog box. These reports have been running for months
> without issue. We've even gone so far as to switch to a new server and
> still
> get the same errors.
> Any suggestions?|||Thanks Steve. It ended up being exactly that. We switched to a new server,
but our network guy swapped one of the harddrives so it was still 'linked' to
the old server. Once we updated a few keys and played around with RS, we got
it back to working.
"Steve MunLeeuw" wrote:
> I'd also use the RS 2005 Configuration tool to check what accounts are used,
> and if they have had a password change or expire. Maybe it's a private key
> backup issue...grasping at straws.
> Steve MunLeeuw
> "dbutler" <dbutler@.discussions.microsoft.com> wrote in message
> news:52C330E6-AEBE-4B59-91C6-99F4E8FD5574@.microsoft.com...
> > OK, I'm at a complete loss. Any advice on the following would be greatly
> > appreciated. What I've got is multiple reports that are heavy process
> > intensive(multiple datasets, multiple joins, etc). Reports usually take
> > between 25 and 35 minutes. All was fine until yesterday. Now the reports
> > seem
> > to run forever. Then finally after an hour we get a 444 error and a
> > permission denied dialog box. These reports have been running for months
> > without issue. We've even gone so far as to switch to a new server and
> > still
> > get the same errors.
> >
> > Any suggestions?
>
>

Error 2571 - not permission to run DBCC TRACEON

Hi,
I am trying to connect to SQL Server 2005 via Excel/ODBC. (ODBC Test IS
successfull) and get the following error after entering Login ID and Password:
Connection failed:
SQLState: '37000'
SQL Server Error: 2571
.....does not have permission to run DBCC TRACEON
Security setup on SQL Server seems to be fine (I can connect to SQL Server
from Reporting Services on same Login/Password).
Any idears?
Best regards,
Soren
To run DBCC Traceon you requires membership in the sysadmin fixed
server role.
Regards
Amish
|||That did it! Thanks !!!
"amish" wrote:

> To run DBCC Traceon you requires membership in the sysadmin fixed
> server role.
>
> Regards
> Amish
>
|||I had the same problem, but there are multiple users who use that
spreadsheet using Windows authentication. I did not want any of them to
be sysadmins. They only had SLECT permissions to certain tables. In my
case, deleting the Application name (from the SQL Server Login dialog)
fixed it. You need to click the Options button on the dialog to see
this. The application name seems to be an issue if it has certain
characters (like =AE in Microsoft=AE Query). Depending on the MS Office
version, the default value may be Microsoft=AE Query/MS Office XP/?.
You can also programmatically change the connection string (and even
the command text if necessary). Here is a sample.
'ChangeConnection
Sub ChangeConnection()
Dim sh As Worksheet
Dim qt As QueryTable
Dim sConnection As String
For Each sh In ActiveWorkbook.Sheets
For Each qt In sh.QueryTables
'Show current connectionstring
MsgBox ("Tab: " & sh.Name & vbCr & " Current Connection: "
& vbCr & qt.Connection)
'Show current query
MsgBox ("Tab: " & sh.Name & vbCr & "Current Query: " & vbCr
& qt.CommandText)
'Change Connection
qt.Connection =3D "ODBC;DRIVER=3DSQL
Server;SERVER=3Dmyserver;DATABASE=3DmyDB;Trusted_C onnection=3DYes;APP=3DExc=
el_TopCustomers;"
'Change Qry text (the owner for instance)
qt.CommandText =3D Replace(qt.CommandText, "DB.dbo.",
"DB.Me")
qt.SavePassword =3D False
'Show new connectionstring
MsgBox ("Tab: " & sh.Name & vbCr & "Connection: " & vbCr &
qt.Connection)
'Show new query
MsgBox ("Tab: " & sh.Name & vbCr & "Query: " & vbCr &
qt.CommandText)
Next qt
Next sh
End Sub
|||I have the exact same problem using Excel 97/MS-Query8. I tried your
suggestion, it did not work. I am still getting the error.
Ade
"preddy" wrote:

> I had the same problem, but there are multiple users who use that
> spreadsheet using Windows authentication. I did not want any of them to
> be sysadmins. They only had SLECT permissions to certain tables. In my
> case, deleting the Application name (from the SQL Server Login dialog)
> fixed it. You need to click the Options button on the dialog to see
> this. The application name seems to be an issue if it has certain
> characters (like ? in Microsoft? Query). Depending on the MS Office
> version, the default value may be Microsoft? Query/MS Office XP/?.
> You can also programmatically change the connection string (and even
> the command text if necessary). Here is a sample.
> 'ChangeConnection
> Sub ChangeConnection()
> Dim sh As Worksheet
> Dim qt As QueryTable
> Dim sConnection As String
> For Each sh In ActiveWorkbook.Sheets
> For Each qt In sh.QueryTables
> 'Show current connectionstring
> MsgBox ("Tab: " & sh.Name & vbCr & " Current Connection: "
> & vbCr & qt.Connection)
> 'Show current query
> MsgBox ("Tab: " & sh.Name & vbCr & "Current Query: " & vbCr
> & qt.CommandText)
> 'Change Connection
> qt.Connection = "ODBC;DRIVER=SQL
> Server;SERVER=myserver;DATABASE=myDB;Trusted_Conne ction=Yes;APP=Excel_TopCustomers;"
> 'Change Qry text (the owner for instance)
> qt.CommandText = Replace(qt.CommandText, "DB.dbo.",
> "DB.Me")
> qt.SavePassword = False
> 'Show new connectionstring
> MsgBox ("Tab: " & sh.Name & vbCr & "Connection: " & vbCr &
> qt.Connection)
> 'Show new query
> MsgBox ("Tab: " & sh.Name & vbCr & "Query: " & vbCr &
> qt.CommandText)
> Next qt
> Next sh
> End Sub
>
|||Sorry my mistake, it does work. You have to replace the string "Microsoft?
Query" with something else.
Ade
"Ade" wrote:
[vbcol=seagreen]
> I have the exact same problem using Excel 97/MS-Query8. I tried your
> suggestion, it did not work. I am still getting the error.
> --
> Ade
>
> "preddy" wrote:

Error 2571 - not permission to run DBCC TRACEON

Hi,
I am trying to connect to SQL Server 2005 via Excel/ODBC. (ODBC Test IS
successfull) and get the following error after entering Login ID and Passwor
d:
Connection failed:
SQLState: '37000'
SQL Server Error: 2571
....does not have permission to run DBCC TRACEON
Security setup on SQL Server seems to be fine (I can connect to SQL Server
from Reporting Services on same Login/Password).
Any idears?
Best regards,
SorenTo run DBCC Traceon you requires membership in the sysadmin fixed
server role.
Regards
Amish|||That did it! Thanks !!!
"amish" wrote:

> To run DBCC Traceon you requires membership in the sysadmin fixed
> server role.
>
> Regards
> Amish
>|||I had the same problem, but there are multiple users who use that
spreadsheet using Windows authentication. I did not want any of them to
be sysadmins. They only had SLECT permissions to certain tables. In my
case, deleting the Application name (from the SQL Server Login dialog)
fixed it. You need to click the Options button on the dialog to see
this. The application name seems to be an issue if it has certain
characters (like =AE in Microsoft=AE Query). Depending on the MS Office
version, the default value may be Microsoft=AE Query/MS Office XP/'.
You can also programmatically change the connection string (and even
the command text if necessary). Here is a sample.
'ChangeConnection
Sub ChangeConnection()
Dim sh As Worksheet
Dim qt As QueryTable
Dim sConnection As String
For Each sh In ActiveWorkbook.Sheets
For Each qt In sh.QueryTables
'Show current connectionstring
MsgBox ("Tab: " & sh.Name & vbCr & " Current Connection: "
& vbCr & qt.Connection)
'Show current query
MsgBox ("Tab: " & sh.Name & vbCr & "Current Query: " & vbCr
& qt.CommandText)
'Change Connection
qt.Connection =3D "ODBC;DRIVER=3DSQL
Server;SERVER=3Dmyserver;DATABASE=3DmyDB
;Trusted_Connection=3DYes;APP=3DExc=
el_TopCustomers;"
'Change Qry text (the owner for instance)
qt.CommandText =3D Replace(qt.CommandText, "DB.dbo.",
"DB.Me")
qt.SavePassword =3D False
'Show new connectionstring
MsgBox ("Tab: " & sh.Name & vbCr & "Connection: " & vbCr &
qt.Connection)
'Show new query
MsgBox ("Tab: " & sh.Name & vbCr & "Query: " & vbCr &
qt.CommandText)
Next qt
Next sh
End Sub|||I have the exact same problem using Excel 97/MS-Query8. I tried your
suggestion, it did not work. I am still getting the error.
--
Ade
"preddy" wrote:

> I had the same problem, but there are multiple users who use that
> spreadsheet using Windows authentication. I did not want any of them to
> be sysadmins. They only had SLECT permissions to certain tables. In my
> case, deleting the Application name (from the SQL Server Login dialog)
> fixed it. You need to click the Options button on the dialog to see
> this. The application name seems to be an issue if it has certain
> characters (like ? in Microsoft? Query). Depending on the MS Office
> version, the default value may be Microsoft? Query/MS Office XP/'.
> You can also programmatically change the connection string (and even
> the command text if necessary). Here is a sample.
> 'ChangeConnection
> Sub ChangeConnection()
> Dim sh As Worksheet
> Dim qt As QueryTable
> Dim sConnection As String
> For Each sh In ActiveWorkbook.Sheets
> For Each qt In sh.QueryTables
> 'Show current connectionstring
> MsgBox ("Tab: " & sh.Name & vbCr & " Current Connection: "
> & vbCr & qt.Connection)
> 'Show current query
> MsgBox ("Tab: " & sh.Name & vbCr & "Current Query: " & vbCr
> & qt.CommandText)
> 'Change Connection
> qt.Connection = "ODBC;DRIVER=SQL
> Server;SERVER=myserver;DATABASE=myDB;Tru
sted_Connection=Yes;APP=Excel_TopC
ustomers;"
> 'Change Qry text (the owner for instance)
> qt.CommandText = Replace(qt.CommandText, "DB.dbo.",
> "DB.Me")
> qt.SavePassword = False
> 'Show new connectionstring
> MsgBox ("Tab: " & sh.Name & vbCr & "Connection: " & vbCr &
> qt.Connection)
> 'Show new query
> MsgBox ("Tab: " & sh.Name & vbCr & "Query: " & vbCr &
> qt.CommandText)
> Next qt
> Next sh
> End Sub
>|||Sorry my mistake, it does work. You have to replace the string "Microsoft?
Query" with something else.
--
Ade
"Ade" wrote:
[vbcol=seagreen]
> I have the exact same problem using Excel 97/MS-Query8. I tried your
> suggestion, it did not work. I am still getting the error.
> --
> Ade
>
> "preddy" wrote:
>

Error 2571 - not permission to run DBCC TRACEON

Hi,
I am trying to connect to SQL Server 2005 via Excel/ODBC. (ODBC Test IS
successfull) and get the following error after entering Login ID and Password:
Connection failed:
SQLState: '37000'
SQL Server Error: 2571
....does not have permission to run DBCC TRACEON
Security setup on SQL Server seems to be fine (I can connect to SQL Server
from Reporting Services on same Login/Password).
Any idears?
Best regards,
SorenTo run DBCC Traceon you requires membership in the sysadmin fixed
server role.
Regards
Amish|||That did it! Thanks !!!
"amish" wrote:
> To run DBCC Traceon you requires membership in the sysadmin fixed
> server role.
>
> Regards
> Amish
>|||I had the same problem, but there are multiple users who use that
spreadsheet using Windows authentication. I did not want any of them to
be sysadmins. They only had SLECT permissions to certain tables. In my
case, deleting the Application name (from the SQL Server Login dialog)
fixed it. You need to click the Options button on the dialog to see
this. The application name seems to be an issue if it has certain
characters (like =AE in Microsoft=AE Query). Depending on the MS Office
version, the default value may be Microsoft=AE Query/MS Office XP/'.
You can also programmatically change the connection string (and even
the command text if necessary). Here is a sample.
'ChangeConnection
Sub ChangeConnection()
Dim sh As Worksheet
Dim qt As QueryTable
Dim sConnection As String
For Each sh In ActiveWorkbook.Sheets
For Each qt In sh.QueryTables
'Show current connectionstring
MsgBox ("Tab: " & sh.Name & vbCr & " Current Connection: "
& vbCr & qt.Connection)
'Show current query
MsgBox ("Tab: " & sh.Name & vbCr & "Current Query: " & vbCr
& qt.CommandText)
'Change Connection
qt.Connection =3D "ODBC;DRIVER=3DSQL
Server;SERVER=3Dmyserver;DATABASE=3DmyDB;Trusted_Connection=3DYes;APP=3DExc=el_TopCustomers;"
'Change Qry text (the owner for instance)
qt.CommandText =3D Replace(qt.CommandText, "DB.dbo.",
"DB.Me")
qt.SavePassword =3D False
'Show new connectionstring
MsgBox ("Tab: " & sh.Name & vbCr & "Connection: " & vbCr &
qt.Connection)
'Show new query
MsgBox ("Tab: " & sh.Name & vbCr & "Query: " & vbCr &
qt.CommandText)
Next qt
Next sh
End Sub|||I have the exact same problem using Excel 97/MS-Query8. I tried your
suggestion, it did not work. I am still getting the error.
--
Ade
"preddy" wrote:
> I had the same problem, but there are multiple users who use that
> spreadsheet using Windows authentication. I did not want any of them to
> be sysadmins. They only had SLECT permissions to certain tables. In my
> case, deleting the Application name (from the SQL Server Login dialog)
> fixed it. You need to click the Options button on the dialog to see
> this. The application name seems to be an issue if it has certain
> characters (like ® in Microsoft® Query). Depending on the MS Office
> version, the default value may be Microsoft® Query/MS Office XP/'.
> You can also programmatically change the connection string (and even
> the command text if necessary). Here is a sample.
> 'ChangeConnection
> Sub ChangeConnection()
> Dim sh As Worksheet
> Dim qt As QueryTable
> Dim sConnection As String
> For Each sh In ActiveWorkbook.Sheets
> For Each qt In sh.QueryTables
> 'Show current connectionstring
> MsgBox ("Tab: " & sh.Name & vbCr & " Current Connection: "
> & vbCr & qt.Connection)
> 'Show current query
> MsgBox ("Tab: " & sh.Name & vbCr & "Current Query: " & vbCr
> & qt.CommandText)
> 'Change Connection
> qt.Connection = "ODBC;DRIVER=SQL
> Server;SERVER=myserver;DATABASE=myDB;Trusted_Connection=Yes;APP=Excel_TopCustomers;"
> 'Change Qry text (the owner for instance)
> qt.CommandText = Replace(qt.CommandText, "DB.dbo.",
> "DB.Me")
> qt.SavePassword = False
> 'Show new connectionstring
> MsgBox ("Tab: " & sh.Name & vbCr & "Connection: " & vbCr &
> qt.Connection)
> 'Show new query
> MsgBox ("Tab: " & sh.Name & vbCr & "Query: " & vbCr &
> qt.CommandText)
> Next qt
> Next sh
> End Sub
>|||Sorry my mistake, it does work. You have to replace the string "Microsoft®
Query" with something else.
--
Ade
"Ade" wrote:
> I have the exact same problem using Excel 97/MS-Query8. I tried your
> suggestion, it did not work. I am still getting the error.
> --
> Ade
>
> "preddy" wrote:
> > I had the same problem, but there are multiple users who use that
> > spreadsheet using Windows authentication. I did not want any of them to
> > be sysadmins. They only had SLECT permissions to certain tables. In my
> > case, deleting the Application name (from the SQL Server Login dialog)
> > fixed it. You need to click the Options button on the dialog to see
> > this. The application name seems to be an issue if it has certain
> > characters (like ® in Microsoft® Query). Depending on the MS Office
> > version, the default value may be Microsoft® Query/MS Office XP/'.
> >
> > You can also programmatically change the connection string (and even
> > the command text if necessary). Here is a sample.
> >
> > 'ChangeConnection
> > Sub ChangeConnection()
> >
> > Dim sh As Worksheet
> > Dim qt As QueryTable
> >
> > Dim sConnection As String
> >
> > For Each sh In ActiveWorkbook.Sheets
> > For Each qt In sh.QueryTables
> >
> > 'Show current connectionstring
> > MsgBox ("Tab: " & sh.Name & vbCr & " Current Connection: "
> > & vbCr & qt.Connection)
> > 'Show current query
> > MsgBox ("Tab: " & sh.Name & vbCr & "Current Query: " & vbCr
> > & qt.CommandText)
> >
> > 'Change Connection
> > qt.Connection = "ODBC;DRIVER=SQL
> > Server;SERVER=myserver;DATABASE=myDB;Trusted_Connection=Yes;APP=Excel_TopCustomers;"
> >
> > 'Change Qry text (the owner for instance)
> > qt.CommandText = Replace(qt.CommandText, "DB.dbo.",
> > "DB.Me")
> >
> > qt.SavePassword = False
> >
> > 'Show new connectionstring
> > MsgBox ("Tab: " & sh.Name & vbCr & "Connection: " & vbCr &
> > qt.Connection)
> > 'Show new query
> > MsgBox ("Tab: " & sh.Name & vbCr & "Query: " & vbCr &
> > qt.CommandText)
> >
> > Next qt
> > Next sh
> >
> > End Sub
> >
> >

ERROR 229: SELECT permission denied on object sysobjects, database ....

Hi,

I granted all the rights on the database to the user (db_owner, public, db_datawriter, etc...) However, I didn't grant the "System Administrators" role. I also specifically granted the select on those tables (sysobjects and sysindexes) for the user and checked through sp_helprotect sysobjects command whether there are no specific revokes for for that user.

However, the user is still getting the below error while trying to expand the "Tables" view in the Enterprise Manager.

ERROR 229: SELECT permission denied on object 'sysobjects', database 'My_test', owner 'dbo', SELECT permission denied on object 'sysindexes', database 'My_test', owner 'dbo'.

Also, the user claims that he cant seem to do anything with the database, he cant view any objects, and, when he goes to Query Analyzer, if he tries to run a SELECT query on a table (that he know that this table exists), he gets this error:



SELECT permission denied on object 'tblBillingTrans', database 'My_Test', owner 'dbo'.

Any help would be greatly appreciated!
Thanks,
AllaPlease disregard this question... I granted the db_denydatareader option... :p