I have a new VPS account, whereas before I’ve always been running my sites on a shared server.
I have «Enable Robust Exception Information» checked, and «Enable Request Debugging Output» checked.
I’m getting a 500 — Internal server error, which isn’t very helpful.
And I can see in the application.log the following error:
Error Executing Database Query.[Macromedia][SQLServer JDBC
Driver][SQLServer]The column name ‘AttachmentDesc’ is specified more
than once in the SET clause.
So I see the error, but it would be better if the page displayed the error rather than me having to find it in the application.log.
Q: Is there another setting that I’m missing to help display errors on the page itself?
asked Nov 17, 2012 at 2:11
Phillip SennPhillip Senn
46.8k90 gold badges257 silver badges373 bronze badges
Looks like IIS is hiding the errors from you. Under ‘Error Pages’ in IIS, select the 500 error and click ‘Edit feature settings’ and select ‘Detailed errors’ — you should now see the full error info (provided debugging is on n CF).
answered Nov 19, 2012 at 10:24
1
IIS may be hiding the errors from you (see azawaza’s answer). You can stop this at ColdFusion layer, by disabling the ColdFusion Administrator -> Settings -> «Enable HTTP status codes». Then even the error pages will give code 200 for success, and IIS won’t replace the output.
answered Feb 19, 2013 at 16:58
krubokrubo
5,9894 gold badges37 silver badges47 bronze badges
1
I had a similar issue (500 error instead of detailed debugging) but on shared hosting. Setting
<httpErrors errorMode="Detailed" />
in web.config did the job.
answered Jun 30, 2016 at 13:12
ITfeeITfee
314 bronze badges
I have a new VPS account, whereas before I’ve always been running my sites on a shared server.
I have «Enable Robust Exception Information» checked, and «Enable Request Debugging Output» checked.
I’m getting a 500 — Internal server error, which isn’t very helpful.
And I can see in the application.log the following error:
Error Executing Database Query.[Macromedia][SQLServer JDBC
Driver][SQLServer]The column name ‘AttachmentDesc’ is specified more
than once in the SET clause.
So I see the error, but it would be better if the page displayed the error rather than me having to find it in the application.log.
Q: Is there another setting that I’m missing to help display errors on the page itself?
asked Nov 17, 2012 at 2:11
Phillip SennPhillip Senn
46.8k90 gold badges257 silver badges373 bronze badges
Looks like IIS is hiding the errors from you. Under ‘Error Pages’ in IIS, select the 500 error and click ‘Edit feature settings’ and select ‘Detailed errors’ — you should now see the full error info (provided debugging is on n CF).
answered Nov 19, 2012 at 10:24
1
IIS may be hiding the errors from you (see azawaza’s answer). You can stop this at ColdFusion layer, by disabling the ColdFusion Administrator -> Settings -> «Enable HTTP status codes». Then even the error pages will give code 200 for success, and IIS won’t replace the output.
answered Feb 19, 2013 at 16:58
krubokrubo
5,9894 gold badges37 silver badges47 bronze badges
1
I had a similar issue (500 error instead of detailed debugging) but on shared hosting. Setting
<httpErrors errorMode="Detailed" />
in web.config did the job.
answered Jun 30, 2016 at 13:12
ITfeeITfee
314 bronze badges
I’m about to give up the ghost here.. I’ve got Reporting Services installed, the IIS default website is accessible, and it appears the virtual directories «Reports» and «ReportServer» are there, but when I try to access either of these paths via a browser
I get the following:
Reports — «The report server is not responding. Verify that the report server is running and can be accessed from this computer.»
ReportServer — Internal Error 500
When reviewing the logs I see this:
«w3wp!ui!7!9/1/2010-11:13:39:: e ERROR: The report server is not responding. Verify that the report server is running and can be accessed from this computer.
w3wp!ui!7!9/1/2010-11:13:40:: e ERROR: HTTP status code —> 500″
I’ve tried the start stop of ReportServices and IIS…no good…
I’ve checked all permissions and can’t seem to find any that are lacking…
I’m running this on SQL Server 2005 (64bit edition), on a Windows 2008 R2 server… any help would be appreciated… I’m getting gray hairs as I type this
Jill
Error | Severity | Description |
1 | 10 | Version date of last upgrade: 10/11/90. |
21 | 10 | Warning: Fatal error %d occurred at %S_DATE. Note the error and time, and contact your system administrator. |
53 | 10 | An error has occurred while establishing a connection to the server. When connecting to SQL Server, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 — Could not open a connection to SQL Server ) (.Net SqlClient Data Provider). |
101 | 15 | Query not allowed in Waitfor. |
102 | 15 | Incorrect syntax near ‘%.*ls’. |
103 | 15 | The %S_MSG that starts with ‘%.*ls’ is too long. Maximum length is %d. |
104 | 15 | ORDER BY items must appear in the select list if the statement contains a UNION operator. |
105 | 15 | Unclosed quotation mark before the character string ‘%.*ls’. |
106 | 16 | Too many table names in the query. The maximum allowable is %d. |
107 | 15 | The column prefix ‘%.*ls’ does not match with a table name or alias name used in the query. |
108 | 15 | The ORDER BY position number is out of range of the number of items in the select list. |
109 | 15 | There are more columns in the INSERT statement than values specified in the VALUES clause. The number of values in the VALUES clause must match the number of columns specified in the INSERT statement. |
110 | 15 | There are fewer columns in the INSERT statement than values specified in the VALUES clause. The number of values in the VALUES clause must match the number of columns specified in the INSERT statement. |
111 | 15 | ‘CREATE FUNCTION’ must be the first statement in a query batch. |
112 | 15 | Variables are not allowed in the %ls statement. |
113 | 15 | Missing end comment mark ‘*/’. |
114 | 15 | Browse mode is invalid for a statement that assigns values to a variable. |
115 | 15 | The FOR UPDATE clause is invalid for statements containing set operators. |
116 | 15 | Only one expression can be specified in the select list when the subquery is not introduced with EXISTS. |
117 | 15 | The object name «Object Name» contains more than the maximum number of prefixes. The maximum is 2. |
118 | 15 | Only members of the sysadmin role can specify the %ls option for the %ls statement. |
119 | 15 | Must pass parameter number %d and subsequent parameters as ‘@name = value’. After the form ‘@name = value’ has been used, all subsequent parameters must be passed in the form ‘@name = value’. |
120 | 15 | The select list for the INSERT statement contains fewer items than the insert list. The number of SELECT values must match the number of INSERT columns. |
121 | 15 | The select list for the INSERT statement contains more items than the insert list. The number of SELECT values must match the number of INSERT columns. |
122 | 15 | The %ls option is allowed only with %ls syntax. |
123 | 15 | Batch/procedure exceeds maximum length of %d characters. |
124 | 15 | CREATE PROCEDURE contains no statements. |
125 | 15 | Case expressions may only be nested to level %d. |
126 | 15 | Invalid pseudocolumn «%.*ls». |
127 | 15 | A TOP N value may not be negative. |
128 | 15 | The name ‘<Column Name>’ is not permitted in this context. Only constants, expressions, or variables allowed here. Column names are not permitted. |
129 | 15 | Fillfactor %d is not a valid percentage; fillfactor must be between 1 and 100. |
130 | 16 | Cannot perform an aggregate function on an expression containing an aggregate or a subquery. |
131 | 15 |
The size (<Data Type Size>) given to the type ‘varchar / char / nvarchar / nchar / binary / varbinary’ exceeds the maximum allowed for any data type (8000). The size (<Data Type Size>) given to the column ‘<Column Name>’ exceeds the maximum allowed for any data type (8000). |
132 | 15 | The label ‘%.*ls’ has already been declared. Label names must be unique within a query batch or stored procedure. |
133 | 15 | A GOTO statement references the label ‘<Label Name>’ but the label has not been declared. |
134 | 15 | The variable name ‘%.*ls’ has already been declared. Variable names must be unique within a query batch or stored procedure. |
135 | 15 | Cannot use a BREAK statement outside the scope of a WHILE statement. |
136 | 15 | Cannot use a CONTINUE statement outside the scope of a WHILE statement. |
137 | 15 | Must declare the scalar variable ‘<Variable Name>’. |
138 | 15 | Correlation clause in a subquery not permitted. |
139 | 15 | Cannot assign a default value to a local variable. |
140 | 15 | Can only use IF UPDATE within a CREATE TRIGGER statement. |
141 | 15 | A SELECT statement that assigns a value to a variable must not be combined with data-retrieval operations. |
142 | 15 | Incorrect syntax for definition of the ‘%ls’ constraint. |
143 | 15 | A COMPUTE BY item was not found in the order by list. All expressions in the compute by list must also be present in the order by list. |
144 | 15 | Cannot use an aggregate or a subquery in an expression used for the group by list of a GROUP BY clause. |
145 | 15 | ORDER BY items must appear in the select list if SELECT DISTINCT is specified. |
146 | 15 | Could not allocate ancillary table for a subquery. Maximum number of tables in a query (%d) exceeded. |
147 | 15 | An aggregate may not appear in the WHERE clause unless it is in a subquery contained in a HAVING clause or a select list, and the column being aggregated is an outer reference. |
148 | 15 | Incorrect time syntax in time string ‘<Wait Time>’ used with WAITFOR. |
149 | 15 | Time value ‘%.*ls’ used with WAITFOR is not a valid value. Check date/time syntax. |
150 | 15 | Both terms of an outer join must contain columns. |
151 | 15 | ‘%.*ls’ is an invalid money value. |
152 | 15 | The same large data placement option «%.*ls» has been specified twice. |
153 | 15 | Invalid usage of the option %.*ls in the %ls statement. |
154 | 15 | a COMPUTE clause is not allowed in a SELECT INTO statement. |
155 | 15 | ‘<DATEADD option>’ is not a recognized DATEADD option. |
156 | 15 | Incorrect syntax near the keyword ‘%.*ls’. |
157 | 15 | An aggregate may not appear in the set list of an UPDATE statement. |
158 | 15 | An aggregate may not appear in the OUTPUT clause. |
159 | 15 |
SQL Server 2005, SQL Server 2008 — Must specify the table name and index name for the DROP INDEX statement. SQL Server 2000 — For DROP INDEX, you must give both the table and the index name, in the form tablename.indexname. |
160 | 15 | Rule does not contain a variable. |
161 | 15 | Rule contains more than one variable. |
162 | 15 | Invalid expression in the TOP clause. |
163 | 15 | The compute by list does not match the order by list. |
164 | 15 | Each GROUP BY expression must contain at least one column that is not an outer reference. GROUP BY expressions must refer to column names that appear in the select list. |
165 | 16 | Privilege %ls may not be granted or revoked. |
166 | 15 | ‘CREATE VIEW’ does not allow specifying the database name as a prefix to the object name. |
167 | 16 | Cannot create a trigger on a temporary object. |
168 | 15 | The %S_MSG ‘%.*ls’ is out of the range of computer representation (%d bytes). |
169 | 15 | A column has been specified more than once in the order by list. Columns in the order by list must be unique. |
170 | 15 | Line %d: Incorrect syntax near ‘%.*ls’. |
171 | 15 | Cannot use SELECT INTO in browse mode. |
172 | 15 | Cannot use HOLDLOCK in browse mode. |
173 | 15 | The definition for column <Column Name> must include a data type. |
174 | 15 | The dateadd function requires 3 arguments. |
175 | 15 | An aggregate may not appear in a computed column expression or check constraint. |
176 | 15 | The FOR BROWSE clause is no longer supported in views. Set the database compatibility level to 80 or lower for this statement to be allowed. |
177 | 15 | The IDENTITY function can only be used when the SELECT statement has an INTO clause. |
178 | 15 | A RETURN statement with a return value cannot be used in this context. |
179 | 15 | Cannot use the OUTPUT option when passing a constant to a stored procedure. |
180 | 15 | There are too many parameters in this %ls statement. The maximum number is %d. |
181 | 15 |
SQL Server 2008 — Cannot use the OUTPUT option in a DECLARE, CREATE AGGREGATE or CREATE FUNCTION statement. SQL Server 2005 — Cannot use the OUTPUT option in a DECLARE or CREATE FUNCTION statement. SQL Server 2000 — Cannot use the OUTPUT option in a DECLARE statement. |
182 | 15 | Table and column names must be supplied for the READTEXT or WRITETEXT utility. |
183 | 15 | The scale (<Scale Value>) for column ‘<Column Name>’ must be within the range 0 to <Precision Value>. |
184 | 15 | DEFAULT cannot be specified more than once for filegroups of the same content type. |
185 | 15 | Data stream is invalid for WRITETEXT statement in bulk form. |
186 | 15 | Data stream missing from WRITETEXT statement. |
187 | 16 | The valid range for MAX_QUEUE_READERS is 0 to 32767. |
188 | 15 | Cannot specify a log device in a CREATE DATABASE statement without also specifying at least one non-log device. |
189 | 15 | The %ls function requires %d to %d arguments. |
190 | 15 | An invalid date or time was specified in the statement. |
191 | 15 | Some part of your SQL statement is nested too deeply. Rewrite the query or break it up into smaller queries. |
192 | 16 | The scale must be less than or equal to the precision. |
193 | 15 | The object or column name starting with ‘%.*ls’ is too long. The maximum length is %d characters. |
194 | 15 | A SELECT INTO statement cannot contain a SELECT statement that assigns values to a variable. |
195 | 15 | ‘Function Name’ is not a recognized function name. |
196 | 15 | SELECT INTO must be the first query in an SQL statement containing a UNION, INTERSECT or EXCEPT operator. |
197 | 15 | EXECUTE cannot be used as a source when inserting into a table variable. |
198 | 15 | Browse mode is invalid for statements containing a UNION operator. |
199 | 15 | An INSERT statement cannot contain a SELECT statement that assigns values to a variable. |
201 | 16 | Procedure ‘<Procedure Name>’ expects parameter ‘<Parameter Name>’, which was not supplied. |
202 | 16 | Invalid type ‘%s’ for WAITFOR. Supported data types are CHAR/VARCHAR, NCHAR/NVARCHAR, and DATETIME. WAITFOR DELAY supports the INT and SMALLINT data types. |
203 | 16 | The name ‘%.*ls’ is not a valid identifier. |
204 | 20 | Normalization error in node %ls. |
205 | 16 | All queries in an SQL statement containing a UNION operator must have an equal number of expressions in their target lists. |
206 | 16 | Operand type clash: %ls is incompatible with %ls |
207 | 16 | Invalid column name ‘%.*ls’. |
208 | 16 | Invalid object name ‘%.*ls’. |
209 | 16 | Ambiguous column name ‘%.*ls’. |
210 | 16 | Syntax error converting datetime from binary/varbinary string. |
211 | 12 | SyntaxPossible schema corruption. Run DBCC CHECKCATALOG. |
212 | 16 | Expression result length exceeds the maximum. %d max, %d found. |
213 | 16 | Insert Error: Column name or number of supplied values does not match table definition. |
214 | 16 | Procedure expects parameter ‘%ls’ of type ‘%ls’. |
215 | 16 | Parameters supplied for object ‘%.*ls’ which is not a function. If the parameters are intended as a table hint, a WITH keyword is required. |
216 | 16 | Parameters were not supplied for the function ‘%.*ls’. |
217 | 16 | Maximum stored procedure, function, trigger, or view nesting level exceeded (limit %d). |
218 | 16 | Could not find the type ‘%.*ls’. Either it does not exist or you do not have the necessary permission. |
219 | 16 | The type ‘%.*ls’ already exists, or you do not have permission to create it. |
220 | 16 | Arithmetic overflow error for data type %ls, value = %ld. |
221 | 10 | FIPS Warning: Implicit conversion from %ls to %ls. |
222 | 16 | The base type «%.*ls» is not a valid base type for the alias data type. |
223 | 11 | Object ID %ld specified as a default for table ID %ld, column ID %d is missing or not of type default. |
224 | 11 | Object ID %ld specified as a rule for table ID %ld, column ID %d is missing or not of type default. |
225 | 16 | The parameters supplied for the %ls «%.*ls» are not valid. |
226 | 16 | %ls statement not allowed within multi-statement transaction. |
227 | 15 | %.*ls is not a valid function, property, or field. |
228 | 15 | Method ‘%.*ls’ of type ‘%.*ls’ in assembly ‘%.*ls’ does not return any value. |
229 | 14 | %ls permission denied on object ‘%.*ls’, database ‘%.*ls’, owner ‘%.*ls’. |
230 | 14 | %ls permission denied on column ‘%.*ls’ of object ‘%.*ls’, database ‘%.*ls’, owner ‘%.*ls’. |
231 | 11 | No such default. ID = %ld, database ID = %d. |
232 | 16 | Arithmetic overflow error for type %ls, value = %f. |
233 | 16 | The column ‘%.*ls’ in table ‘%.*ls’ cannot be null. |
234 | 16 | There is insufficient result space to convert a money value to varchar / nvarchar / char / nchar. |
235 | 16 | Cannot convert a char value to money. The char value has incorrect syntax. |
236 | 16 | The conversion from char data type to money resulted in a money overflow error. |
237 | 16 | There is insufficient result space to convert a money value to int / smallint / tinyint. |
238 | 16 | There is insufficient result space to convert the %ls value (= %d) to the money data type. |
239 | 16 | Duplicate common table expression name ‘%.*ls’ was specified. |
240 | 16 | Types don’t match between the anchor and the recursive part in column «<Column Name>» of recursive query «<Recursive CTE>». |
241 | 16 | Syntax error converting datetime from character string. |
242 | 16 | The conversion of a char data type to a datetime data type resulted in an out-of-range datetime value. |
243 | 16 | Type <Data Type> is not a defined system type. |
244 | 16 | The conversion of the %ls value ‘%.*ls’ overflowed an %hs column. Use a larger integer column. |
245 | 16 | Syntax error converting the varchar value to a column of data type int. |
246 | 16 | No anchor member was specified for recursive query «%.*ls». |
247 | 16 | An anchor member was found in the recursive part of recursive query «%.*ls». |
248 | 16 | The conversion of the %ls value ‘%.*ls’ overflowed an int column. Maximum integer value exceeded. |
249 | 16 | The type «%ls» is not comparable. It cannot be used in the %ls clause. |
Error | Severity | Description |
251 | 16 | Could not allocate ancillary table for query optimization. Maximum number of tables in a query (%d) exceeded. |
252 | 16 | Recursive common table expression ‘<Common Table Expression Name>’ does not contain a top-level UNION ALL operator. |
253 | 16 | Recursive member of a common table expression ‘<Common Table Expression Name>’ has multiple recursive references. |
254 | 16 | Prefixed columns are not allowed in the column list of a PIVOT operator. |
255 | 16 | Pseudocolumns are not allowed in the column list of a PIVOT operator. |
256 | 16 | The data type int is invalid for the substring function. Allowed types are: char/varchar, nchar/nvarchar, and binary/varbinary. |
257 | 16 | Implicit conversion from data type %ls to %ls is not allowed. Use the CONVERT function to run this query. |
258 | 16 | Cannot call methods on %ls. |
259 | 16 | Ad hoc updates to system catalogs are not enabled. The system administrator must reconfigure SQL Server to allow this. |
260 | 16 | Disallowed implicit conversion from data type %ls to data type %ls, table ‘%.*ls’, column ‘%.*ls’. Use the CONVERT function to run this query. |
261 | 16 | ‘%.*ls’ is not a recognized function. |
262 | 16 | %ls permission denied in database ‘%.*ls’. |
263 | 16 | Must specify table to select from. |
264 | 16 | Column name ‘%.*ls’ appears more than once in the result column list. |
265 | 16 | The column name «%.*ls» specified in the %ls operator conflicts with the existing column name in the %ls argument. |
266 | 16 | Transaction count after EXECUTE indicates that a COMMIT or ROLLBACK TRANSACTION statement is missing. Previous count = %ld, current count = %ld. |
267 | 16 | Object ‘%.*ls’ cannot be found. |
268 | 16 | Cannot run SELECT INTO in this database. The database owner must run sp_dboption to enable this option. |
270 | 16 | Object ‘%.*ls’ cannot be modified. |
271 | 16 |
SQL Server 2005, SQL Server 2008, SQL Server 2012 — The column ‘<Column Name>’ cannot be modified because it is either a computed column or is the result of a UNION operator. SQL Server 2000 — Column ‘<Column Name>’ cannot be modified because it is a computed column. |
272 | 16 | Cannot update a timestamp column. |
273 | 16 | Cannot insert a non-null value into a timestamp column. Use INSERT with a column list or with a default of NULL for the timestamp column. |
275 | 16 | Prefixes are not allowed in value or pivot columns of an UNPIVOT operator. |
276 | 16 | Pseudocolumns are not allowed as value or pivot columns of an UNPIVOT operator. |
277 | 16 | The column «%.*ls» is specified multiple times in the column list of the UNPIVOT operator. |
278 | 16 | The text, ntext, and image data types cannot be used in a GROUP BY clause. |
279 | 16 | The text, ntext, and image data types are invalid in this subquery or aggregate expression. |
280 | 16 | Only text, ntext, and image columns are valid with the TEXTPTR function. |
281 | 16 | <Style number> is not a valid style number when converting from %ls to a character string. |
282 | 10 | The ‘%.*ls’ procedure attempted to return a status of NULL, which is not allowed. A status of 0 will be returned instead. |
283 | 16 | READTEXT cannot be used on inserted or deleted tables within an INSTEAD OF trigger. |
284 | 16 | Rules cannot be bound to text, ntext, or image data types. |
285 | 16 | The READTEXT, WRITETEXT, and UPDATETEXT statements cannot be used with views or functions. |
286 | 16 | The logical tables INSERTED and DELETED cannot be updated. |
287 | 16 | The %ls statement is not allowed within a trigger. |
288 | 16 | The PATINDEX function operates on char, nchar, varchar, nvarchar, text, and ntext data types only. |
290 | 16 | Invalid EXECUTE statement using object «%ls», method «%ls». |
291 | 16 | CAST or CONVERT: invalid attributes specified for type ‘%.*ls’ |
292 | 16 | There is insufficient result space to convert a smallmoney value to varchar/nvarchar. |
293 | 16 | Cannot convert char value to smallmoney. The char value has incorrect syntax. |
294 | 16 | The conversion from char data type to smallmoney data type resulted in a smallmoney overflow error. |
295 | 16 | Syntax error converting character string to smalldatetime data type. |
296 | 16 | The conversion of char data type to smalldatetime data type resulted in an out-of-range smalldatetime value. |
297 | 16 | The user does not have permission to perform this action. |
298 | 16 | The conversion from datetime data type to smalldatetime data type resulted in a smalldatetime overflow error. |
299 | 16 | The DATEADD function was called with bad type %ls. |
300 | 14 | %ls permission was denied on object ‘%.*ls’, database ‘%.*ls’. |
301 | 16 | Query contains an outer-join request that is not permitted. |
302 | 16 | The newsequentialid() built-in function can only be used in a DEFAULT expression for a column of type ‘uniqueidentifier’ in a CREATE TABLE or ALTER TABLE statement. It cannot be combined with other operators to form a complex scalar expression. |
303 | 16 | The table ‘%.*ls’ is an inner member of an outer-join clause. This is not allowed if the table also participates in a regular join clause. |
304 | 16 | ‘%d’ is out of range for index option ‘%.*ls’. See sp_configure option ‘%ls’ for valid values. |
305 | 16 | The XML data type cannot be compared or sorted, except when using the IS NULL operator. |
306 | 16 | The text, ntext, and image data types cannot be compared or sorted, except when using IS NULL or LIKE operator. |
307 | 16 | Index ID %d on table ‘%.*ls’ (specified in the FROM clause) does not exist. |
308 | 16 | Index ‘%.*ls’ on table ‘%.*ls’ (specified in the FROM clause) does not exist. |
309 | 16 | Cannot use index «%.*ls» on table «%.*ls» in a hint. XML indexes are not allowed in hints. |
310 | 16 | The value <MAXRECURSION value> specified for the MAXRECURSION option exceeds the allowed maximum of %d. |
311 | 16 | Cannot use text, ntext, or image columns in the ‘inserted’ and ‘deleted’ tables. |
312 | 16 | Cannot reference text, ntext, or image columns in a filter stored procedure. |
313 | 16 | An insufficient number of arguments were supplied for the procedure or function %.*ls. |
314 | 16 | Cannot use GROUP BY ALL with the special tables INSERTED or DELETED. |
315 | 16 | Index «%.*ls» on table «%.*ls» (specified in the FROM clause) is disabled or resides in a filegroup which is not online. |
316 | 16 | The index ID %d on table «%.*ls» (specified in the FROM clause) is disabled or resides in a filegroup which is not online. |
317 | 16 | Table-valued function ‘<Function Name>’ cannot have a column alias. |
318 | 16 | The table (and its columns) returned by a table-valued method need to be aliased. |
319 | 16 | Incorrect syntax near the keyword ‘with’. If this statement is a common table expression, an xmlnamespaces clause or a change tracking context clause, the previous statement must be terminated with a semicolon. |
320 | 16 | The compile-time variable value for ‘%.*ls’ in the OPTIMIZE FOR clause must be a literal. |
321 | 15 | %.*ls is not a recognized table hints option. If it is intended as a parameter to a table-valued function or to the CHANGETABLE function, ensure that your database compatibility mode is set to 90. |
322 | 16 | The variable «%.*ls» is specified in the OPTIMIZE FOR clause, but is not used in the query. |
323 | 16 | The ‘COMPUTE’ clause is not allowed in a statement containing an INTERSECT or EXCEPT operator. |
324 | 15 | The ‘ALL’ version of the %.*ls operator is not supported. |
325 | 15 | Incorrect syntax near ‘%.*ls’. You may need to set the compatibility level of the current database to a higher value to enable this feature. See help for the SET COMPATIBILITY_LEVEL option of ALTER DATABASE. |
326 | 16 | Multi-part identifier ‘%.*ls’ is ambiguous. Both columns ‘%.*ls’ and ‘%.*ls’ exist. |
327 | 16 | Function call ‘%.*ls’ is ambiguous: both a user-defined function and a method call with this name exist. |
328 | 16 | A cursor plan could not be generated for the given statement because the textptr() function was used on a LOB column from one of the base tables. |
329 | 16 | Each GROUP BY expression must contain at least one column reference. |
330 | 15 | The target ‘<Object Name>’ of the OUTPUT INTO clause cannot be a view or common table expression. |
331 | 15 | The target table ‘<Table Name>’ of the OUTPUT INTO clause cannot have any enabled triggers. |
332 | 15 | The target table ‘<Table Name>’ of the OUTPUT INTO clause cannot be on either side of a (primary key, foreign key) relationship. Found reference constraint ‘<Primary Key or Foreign Key Constraint Name>’. |
333 | 15 | The target table ‘<Table Name>’ of the OUTPUT INTO clause cannot have any enabled check constraints or any enabled rules. Found check constraint or rule ‘<CHECK Constraint Name>’. |
334 | 15 | The target table ‘<Table Name>’ of the DML statement cannot have any enabled triggers if the statement contains an OUTPUT clause without INTO clause. |
335 | 16 | Function call cannot be used to match a target table in the FROM clause of a DELETE or UPDATE statement. Use function name ‘%.*ls’ without parameters instead. |
336 | 15 | Incorrect syntax near ‘%.*ls’. If this is intended to be a common table expression, you need to explicitly terminate the previous statement with a semi-colon. |
337 | 10 | Warning: the floating point value ‘%.*ls’ is too small. It will be interpreted as 0. |
338 | 16 | READEXT, WRITETEXT, and UPDATETEXT statements cannot be used with views, remote tables, and inserted or deleted tables inside triggers. |
339 | 16 | DEFAULT or NULL are not allowed as explicit identity values. |
340 | 16 | Cannot create the trigger «%.*ls» on view «%.*ls». AFTER triggers cannot be created on views. |
341 | 16 | Replication filter procedures may not contain columns of large object, large value, XML or CLR type. |
342 | 16 | Column «%.*ls» is not allowed in this context, and the user-defined function or aggregate «%.*ls» could not be found. |
343 | 16 | Unknown object type ‘%.*ls’ used in a CREATE, DROP, or ALTER statement. |
344 | 16 | Remote function reference ‘%.*ls’ is not allowed, and the column name ‘%.*ls’ could not be found or is ambiguous. |
345 | 16 | Function ‘%.*ls’ is not allowed in the OUTPUT clause, because it performs user or system data access, or is assumed to perform this access. A function is assumed by default to perform data access if it is not schemabound. |
346 | 15 | The parameter «<Parameter Name>» can not be declared READONLY since it is not a table-valued parameter. |
347 | 16 | The table-valued parameter «%.*ls» cannot be declared as an OUTPUT parameter. |
348 | 16 | The table variable «%.*ls» can not be passed to a stored procedure with the OUTPUT option. |
349 | 16 | The procedure «%.*ls» has no parameter named «%.*ls». |
350 | 16 | The column «%.*ls» does not have a valid data type. A column cannot be of a user-defined table type. |
351 | 16 | Column, parameter, or variable %.*ls. : Cannot find data type %.*ls. |
352 | 15 | The table-valued parameter «%.*ls» must be declared with the READONLY option. |
353 | 16 | Function ‘%.*ls’ is not allowed in the %S_MSG clause when the FROM clause contains a nested INSERT, UPDATE, DELETE, or MERGE statement. This is because the function performs user or system data access, or is assumed to perform this access. By default, a function is assumed to perform data access if it is not schema-bound. |
354 | 15 | The target ‘%.*ls’ of the INSERT statement cannot be a view or common table expression when the FROM clause contains a nested INSERT, UPDATE, DELETE, or MERGE statement. |
355 | 15 | The target table ‘<Table Name>’ of the INSERT statement cannot have any enabled triggers when the FROM clause contains a nested INSERT, UPDATE, DELETE, or MERGE statement. |
356 | 15 | The target table ‘%.*ls’ of the INSERT statement cannot be on either side of a (primary key, foreign key) relationship when the FROM clause contains a nested INSERT, UPDATE, DELETE, or MERGE statement. Found reference constraint ‘%ls’. |
357 | 15 | The target table ‘%.*ls’ of the INSERT statement cannot have any enabled rules when the FROM clause contains a nested INSERT, UPDATE, DELETE, or MERGE statement. Found rule ‘%ls’. |
358 | 15 | The target table ‘%.*ls’ of the MERGE statement cannot have any enabled rules. Found rule ‘%ls’. |
359 | 15 | The target ‘%.*ls’ of an OUTPUT INTO clause has an index with the ignore_dup_key option and cannot be used when an OUTPUT clause is also used. |
360 | 15 | The target column list of an INSERT, UPDATE, or MERGE statement cannot contain both a sparse column and the column set that contains the sparse column. Rewrite the statement to include either the sparse column or the column set, but not both. |
361 | 16 | The number of target columns that are specified in an INSERT, UPDATE, or MERGE statement exceeds the maximum of %d. This total number includes identity, timestamp, and columns that have default values. To correct this error, change the query to target a sparse column set instead of single sparse columns. |
362 | 16 | The query processor could not produce a query plan because the name ‘%.*ls’ in the FORCESEEK hint on table or view ‘<Object Name>’ did not match the key column names of the index ‘<Index Name>’. |
363 | 16 | The query processor could not produce a query plan because the FORCESEEK hint on table or view ‘<Object Name>’ cannot be used with the %S_MSG specified by index ‘%.*ls’. |
364 | 16 | The query processor could not produce a query plan because the FORCESEEK hint on view ‘<View Name>’ is used without a NOEXPAND hint. Resubmit the query with the NOEXPAND hint or remove the FORCESEEK hint on the view. |
365 | 16 | The query processor could not produce a query plan because the FORCESEEK hint on table or view ‘<Object Name>’ specified more seek columns than the number of key columns in index ‘%.*ls’. |
366 | 16 | The query processor could not produce a query plan because the FORCESEEK hint on table or view ‘<Object Name>’ cannot be used with the column store index ‘%.*ls’. |
401 | 16 | Unimplemented statement or expression %ls. |
402 | 16 | The data types %s and %s are incompatible in the %s operator. |
403 | 16 | Invalid operator for data type. Operator equals add, type equals text. |
404 | 16 | The column reference «inserted.%.*ls» is not allowed because it refers to a base table that is not being modified in this statement. |
405 | 16 | A remote table cannot be used as a DML target in a statement which includes an OUTPUT clause or a nested DML statement. |
406 | 16 | %ls cannot be used in the PIVOT operator because it is not invariant to NULLs. |
407 | 16 | Internal error. The string routine in file %hs, line %d failed with HRESULT 0x%x. |
408 | 16 | A constant expression was encountered in the ORDER BY list, position %i. |
409 | 16 | The %ls operation cannot take a %ls data type as an argument. |
410 | 20 | COMPUTE clause #%d ‘BY’ expression #%d is not in the order by list. |
411 | 16 | COMPUTE clause #%d, aggregate expression #%d is not in the select list. |
412 | 16 | The column «%.*ls» is not updatable because it is derived or constant. |
413 | 16 | Correlated parameters or sub-queries are not supported by the inline function «%.*ls». |
414 | 16 | UPDATE is not allowed because the statement updates view «%.*ls» which participates in a join and has an INSTEAD OF UPDATE trigger. |
415 | 16 | DELETE is not allowed because the statement updates view «%.*ls» which participates in a join and has an INSTEAD OF DELETE trigger. |
416 | 16 | The service queue «%.*ls» cannot be directly updated. |
417 | 16 | TOP is not allowed in an UPDATE or DELETE statement against a partitioned view. |
418 | 16 | Objects exposing CLR type columns are not allowed in distributed queries. Use a pass-through query to access the remote object ‘%.*ls’. |
420 | 16 | The text, ntext, and image data types cannot be used in an ORDER BY clause. |
421 | 16 | The text/ntext/image data type cannot be selected as DISTINCT because it is not comparable. |
422 | 16 | Common table expression defined but not used. |
423 | 16 | Xml data type methods are not supported in check constraints. Create a scalar user-defined function to wrap the method invocation. The error occurred at table «%.*ls». |
424 | 16 | Xml data type methods are not supported in computed column definitions of table variables and return tables of table-valued functions. The error occurred at column «%.*ls», table «%.*ls», in the %ls statement. |
425 | 16 | Data type %ls of receiving variable is not equal to the data type %ls of column ‘%.*ls’. |
426 | 16 | The length %d of the receiving variable is less than the length %d of the column ‘%.*ls’. |
427 | 20 | Could not load sysprocedures entries for constraint ID %d in database ID %d. |
428 | 20 | Could not find row in sysconstraints for constraint ID %d in database ID %d. |
429 | 20 | Could not find new constraint ID %d in sysconstraints, database ID %d, at compile time. |
430 | 20 | Could not resolve table name for object ID %d, database ID %d, when compiling foreign key. |
431 | 19 | Could not bind foreign key constraint. Too many tables involved in the query. |
432 | 16 | Xml data type methods are not supported in check constraints anymore. Please drop the constraint or create a scalar user-defined function to wrap the method invocation. The error occurred at table «%.*ls». |
433 | 20 | Could not find CHECK constraint for ‘%.*ls’, although the table is flagged as having one. |
434 | 16 | Function ‘%ls’ is not allowed in the OUTPUT clause. |
435 | 16 | Xml data type methods are not supported in computed column definitions. Create a scalar user-defined function to wrap the method invocation. The error occurred at column «%.*ls», table «%.*ls», in the %ls statement. |
436 | 20 | Could not open referenced table ID %d in database ID %d. |
437 | 20 | Could not resolve the referenced column name in table ID %d. |
438 | 20 | Could not resolve the referencing column name in table ID %d. |
439 | 20 | Could not find FOREIGN KEY constraints for table ‘%.*ls’ in database ID %d although the table is flagged as having them. |
440 | 16 | Internal query compilation error. The stack overflow could not be handled. |
441 | 16 | Cannot use the ‘%ls’ function on a remote data source. |
442 | 16 | The NEST argument must be a column reference. Expressions are not allowed. |
443 | 16 | Invalid use of ‘getdate’ within a function. Invalid use of ‘INSERT’ within a function. Invalid use of ‘UPDATE’ within a function. |
444 | 16 | Select statements included within a function cannot return data to a client. |
445 | 16 | COLLATE clause cannot be used on expressions containing a COLLATE clause. |
446 | 16 | Cannot resolve collation conflict for %ls operation. |
447 | 16 | Expression type %ls is invalid for COLLATE clause. |
448 | 16 | Invalid collation ‘%.*ls’. |
449 | 16 | Collation conflict caused by collate clauses with different collation ‘%.*ls’ and ‘%.*ls’. |
450 | 16 | Code page translations are not supported for the text data type. From: %d To: %d. |
451 | 16 | Cannot resolve collation conflict for column %d in %ls statement. |
452 | 16 | COLLATE clause cannot be used on user-defined data types. |
453 | 16 | Collation ‘%.*ls’ is supported on Unicode data types only and cannot be set at the database or server level. |
454 | 16 | The UNNEST argument must be a nested table column. |
455 | 16 | The last statement included within a function must be a return statement. |
456 | 16 | Implicit conversion of %ls value to %ls cannot be performed because the resulting collation is unresolved due to collation conflict. |
457 | 16 | Implicit conversion of %ls value to %ls cannot be performed because the collation of the value is unresolved due to a collation conflict. |
458 | 16 | Cannot create the SELECT INTO target table «%.*ls» because the xml column «%.*ls» is typed with a schema collection «%.*ls» from database «%.*ls». Xml columns cannot refer to schemata across databases. |
459 | 16 | Collation ‘%.*ls’ is supported on Unicode data types only and cannot be applied to char, varchar or text data types. |
460 | 16 | DISTINCT operator is not allowed in the recursive part of a recursive common table expression ‘<Common Table Expression Name>’. |
461 | 16 | TOP operator is not allowed in the recursive part of a recursive common table expression ‘<Common Table Expression Name>’. |
462 | 16 | Outer join is not allowed in the recursive part of a recursive common table expression ‘<Common Table Expression Name>’. |
463 | 16 | Functions with parameters are not allowed in the recursive part of a recursive common table expression ‘%.*ls’. |
464 | 16 | Functions with side effects are not allowed in the recursive part of a recursive common table expression ‘%.*ls’. |
465 | 16 | Recursive references are not allowed in subqueries. |
466 | 16 | UNION operator is not allowed in the recursive part of a recursive common table expression ‘%.*ls’. |
467 | 16 | GROUP BY, HAVING, or aggregate functions are not allowed in the recursive part of a recursive common table expression ‘<CTE Name>’. |
468 | 16 | Cannot resolve the collation conflict between «%.*ls» and «%.*ls» in the %ls operation. |
469 | 16 | An explicit column list must be specified for target table ‘%.*ls’ when table hint KEEPIDENTITY is used and the table contains an identity column. |
470 | 16 | The synonym «<Synonym Name>» referenced synonym «<Synonym Name>». Synonym chaining is not allowed. |
471 | 16 | Only one of the three options, SINGLE_BLOB, SINGLE_CLOB or SINGLE_NCLOB, can be specified. |
472 | 16 | Either a format file or one of the three options SINGLE_BLOB, SINGLE_CLOB, or SINGLE_NCLOB must be specified. |
473 | 16 | The incorrect value «%.*ls» is supplied in the PIVOT operator. |
474 | 16 | Unable to load the computed column definitions for table «%.*ls». |
475 | 16 | Invalid SAMPLE clause. Only table names in the FROM clause of SELECT, UPDATE, and DELETE queries may be sampled. |
476 | 16 | Invalid PERCENT tablesample size «<sample_number>» for table «<Table Name>». The PERCENT tablesample size must be between 0 and 100. |
477 | 16 | Invalid ROWS value or REPEATABLE seed in the TABLESAMPLE clause for table «<Table Name>». The value or seed must be an integer. |
478 | 16 | The TABLESAMPLE clause cannot be used in a view definition or inline table function definition. |
479 | 16 | Invalid ROWS value or REPEATABLE seed «%I64d» in the TABLESAMPLE clause for table «%.*ls». The value or seed must be greater than 0. |
480 | 16 | The TABLESAMPLE clause cannot be used with the table function «%.*ls». |
481 | 16 | The TABLESAMPLE clause cannot be used with the linked server table «%.*ls». |
482 | 16 | Non-constant or invalid expression is in the TABLESAMPLE or the REPEATABLE clause. |
483 | 16 | The OUTPUT clause cannot be used in an INSERT…EXEC statement. |
484 | 16 | Cannot declare more than %d local variables. |
485 | 16 | Views and inline functions cannot return xml columns that are typed with a schema collection registered in a database other than current. Column «%.*ls» is typed with the schema collection «%.*ls», which is registered in database «%.*ls». |
486 | 16 | %.*ls does not allow specifying a schema name as a prefix to the assembly name. |
487 | 16 | An invalid option was specified for the statement «%.*ls». |
488 | 16 | %s columns must be comparable. The type of column «%.*ls» is «%s», which is not comparable. |
489 | 16 | The OUTPUT clause cannot be specified because the target view «%.*ls» is a partitioned view. |
490 | 16 | The resync functionality is temporarily disabled. |
491 | 16 | A correlation name must be specified for the bulk rowset in the from clause. |
492 | 16 | Duplicate column names are not allowed in result sets obtained through OPENQUERY and OPENROWSET. The column name «%.*ls» is a duplicate. |
493 | 16 | The column ‘%.*ls’ that was returned from the nodes() method cannot be used directly. It can only be used with one of the four XML data type methods, exist(), nodes(), query(), and value(), or in IS NULL and IS NOT NULL checks. |
494 | 16 | The TABLESAMPLE clause can only be used with local tables. |
495 | 16 | The return table column «%.*ls» is not the same type as the type it was created with. Drop and recreate the module using a two-part name for the type, or use sp_refreshsqlmodule to refresh its parameters metadata. |
496 | 16 | The parameter «%.*ls» is not the same type as the type it was created with. Drop and recreate the module using a two-part name for the type, or use sp_refreshsqlmodule to refresh its parameters metadata. |
497 | 16 | Variables are not allowed in the TABLESAMPLE or REPEATABLE clauses. |
498 | 16 | Invalid value in the TABLESAMPLE or the REPEATABLE clause. |
499 | 16 | Invalid parameter for the getchecksum function. |
500 | 16 | Trying to pass a table-valued parameter with %d column(s) where the corresponding user-defined table type requires %d column(s). |
I’m very new to Reporting Services and I’m not even sure what to ask.
I was given a server where it was installed. I can run the Reporting Services Configuration Manager and connect. However when I attempt to access the urls (web service and report manager) I get a 500 error.
I don’t see anything in the event viewer. Are there log files somewhere?
I’m suspicious of the IIS setup. In particular, the virtual directories. How should these look?
I know this question is broad, but general guidance is appreciated.
Update:
After examining the logs, here is the first error:
servicecontroller!WindowsService_0!358!09/07/2010-13:30:52:: e ERROR: Exception caught loading and setting code permissions policy level: System.NotSupportedException: This method explicitly uses CAS policy, which has been obsoleted by the .NET Framework. In order to enable CAS policy for compatibility reasons, please use the NetFx40_LegacySecurityPolicy configuration switch. Please see http://go.microsoft.com/fwlink/?LinkID=155570 for more information.
at System.AppDomain.SetAppDomainPolicy(PolicyLevel domainPolicy)
at Microsoft.ReportingServices.Library.ServiceController.SetAppDomainPolicy()
library!WindowsService_0!358!09/07/2010-13:30:52:: e ERROR: ServiceStartThread: Exception caught while starting service. Error: System.NotSupportedException: This method explicitly uses CAS policy, which has been obsoleted by the .NET Framework. In order to enable CAS policy for compatibility reasons, please use the NetFx40_LegacySecurityPolicy configuration switch. Please see http://go.microsoft.com/fwlink/?LinkID=155570 for more information.
at System.AppDomain.SetAppDomainPolicy(PolicyLevel domainPolicy)
at Microsoft.ReportingServices.Library.ServiceController.SetAppDomainPolicy()
at Microsoft.ReportingServices.Library.ServiceController.ServiceStartThread(Object firstStart)
After fixing the CAS issue, I now find this error in the log (after my initial attempt to access the web service):
appdomainmanager!DefaultDomain!f6c!09/07/2010-14:32:20:: e ERROR: AppDomain ReportServer_11 failed to start. Error: The configuration system has already been initialized.
library!DefaultDomain!f6c!09/07/2010-14:32:20:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerHttpRuntimeInternalException: Failed to create HTTP Runtime, Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerHttpRuntimeInternalException: An internal or system error occurred in the HTTP Runtime object for application domain ReportServer_11. ---> System.InvalidOperationException: The configuration system has already been initialized.
at System.Configuration.ConfigurationManager.SetConfigurationSystem(IInternalConfigSystem configSystem, Boolean initComplete)
at System.Web.Configuration.HttpConfigurationSystem.EnsureInit(IConfigMapPath configMapPath, Boolean listenToFileChanges, Boolean initComplete)
at System.Web.Hosting.HostingEnvironment.Initialize(ApplicationManager appManager, IApplicationHost appHost, IConfigMapPathFactory configMapPathFactory, HostingEnvironmentParameters hostingParameters, PolicyLevel policyLevel, Exception appDomainCreationException)
at System.Web.Hosting.HostingEnvironment.Initialize(ApplicationManager appManager, IApplicationHost appHost, IConfigMapPathFactory configMapPathFactory, HostingEnvironmentParameters hostingParameters, PolicyLevel policyLevel, Exception appDomainCreationException)
at System.Web.Hosting.ApplicationManager.CreateAppDomainWithHostingEnvironment(String appId, IApplicationHost appHost, HostingEnvironmentParameters hostingParameters)
at System.Web.Hosting.ApplicationManager.CreateAppDomainWithHostingEnvironmentAndReportErrors(String appId, IApplicationHost appHost, HostingEnvironmentParameters hostingParameters)
at System.Web.Hosting.ApplicationManager.GetAppDomainWithHostingEnvironment(String appId, IApplicationHost appHost, HostingEnvironmentParameters hostingParameters)
at System.Web.Hosting.ApplicationManager.CreateObjectInternal(String appId, Type type, IApplicationHost appHost, Boolean failIfExists, HostingEnvironmentParameters hostingParameters)
at System.Web.Hosting.ApplicationManager.CreateObject(String appId, Type type, String virtualPath, String physicalPath, Boolean failIfExists, Boolean throwOnError)
at ReportingServicesHttpRuntime.RsHttpRuntime.Create(RsAppDomainType type, String vdir, String pdir, Int32& domainId)
--- End of inner exception stack trace ---;