Thursday, March 29, 2012
Error reporting against Oracle 10g
run fine for a while, and then for some reason they will error out with the
error:
ORA-12154: TNS:could not resolve the connect identifier specified
If I restart the World Wide Web Publishing Service the reports will again
run fine for a while, and then the error out again.
Has anyone seen a similar issue?*Think* I found it.
The yahoo running their network had the server looking for itself (ala dns)
at an unresolvable external IP. Some wierd / inconsistent things were
happening tyring to access the server by name when on the server.
One entry to the hosts file, and we'll see if it does the trick.
"Jack" <anonymous@.microsoft.com> wrote in message
news:uIHh3OU5FHA.4076@.tk2msftngp13.phx.gbl...
> I've got RS SP2 reporting against an Oracle 10g database. The reports
> will run fine for a while, and then for some reason they will error out
> with the error:
> ORA-12154: TNS:could not resolve the connect identifier specified
> If I restart the World Wide Web Publishing Service the reports will again
> run fine for a while, and then the error out again.
> Has anyone seen a similar issue?
>sql
Tuesday, March 27, 2012
Error received in 2005 but not in 2000
I'm in the process of upgrading to SQL Server 2005. I have been
getting the following error when trying to run a few reports that have
been upgraded from Reporting Services 2000 to Reporting Services 2005:
The Hidden expression used in table 'tblGeneral' returned a data
type that is not valid. (rsInvalidExpressionDataType)
The same reports still run fine under Reporting Services 2000. Has
anyone run into this or a similar issue?
Thanks,
ChadDid you convert the reports to RS 2005 or just convert a server to RS 2005.
When I upgraded my server I from time to time had some weird errors, not
many but some. I then opened up each report in RS 2005 report designer and
converted the report to RS 2005 format and then redeployed and my problems
went away.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Chad" <chad.poplawski@.gmail.com> wrote in message
news:1157482665.855011.138110@.h48g2000cwc.googlegroups.com...
> Hi All,
> I'm in the process of upgrading to SQL Server 2005. I have been
> getting the following error when trying to run a few reports that have
> been upgraded from Reporting Services 2000 to Reporting Services 2005:
>
> The Hidden expression used in table 'tblGeneral' returned a data
> type that is not valid. (rsInvalidExpressionDataType)
> The same reports still run fine under Reporting Services 2000. Has
> anyone run into this or a similar issue?
> Thanks,
> Chad
>|||I converted the server and the reports.
Bruce L-C [MVP] wrote:
> Did you convert the reports to RS 2005 or just convert a server to RS 2005.
> When I upgraded my server I from time to time had some weird errors, not
> many but some. I then opened up each report in RS 2005 report designer and
> converted the report to RS 2005 format and then redeployed and my problems
> went away.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Chad" <chad.poplawski@.gmail.com> wrote in message
> news:1157482665.855011.138110@.h48g2000cwc.googlegroups.com...
> > Hi All,
> >
> > I'm in the process of upgrading to SQL Server 2005. I have been
> > getting the following error when trying to run a few reports that have
> > been upgraded from Reporting Services 2000 to Reporting Services 2005:
> >
> >
> > The Hidden expression used in table 'tblGeneral' returned a data
> > type that is not valid. (rsInvalidExpressionDataType)
> >
> > The same reports still run fine under Reporting Services 2000. Has
> > anyone run into this or a similar issue?
> >
> > Thanks,
> > Chad
> >|||Same problem here
Any solution?
orbit
Chad wrote:
> I converted the server and the reports.
> Bruce L-C [MVP] wrote:
> > Did you convert the reports to RS 2005 or just convert a server to RS 2005.
> > When I upgraded my server I from time to time had some weird errors, not
> > many but some. I then opened up each report in RS 2005 report designer and
> > converted the report to RS 2005 format and then redeployed and my problems
> > went away.
> >
> >
> > --
> > Bruce Loehle-Conger
> > MVP SQL Server Reporting Services
> >
> > "Chad" <chad.poplawski@.gmail.com> wrote in message
> > news:1157482665.855011.138110@.h48g2000cwc.googlegroups.com...
> > > Hi All,
> > >
> > > I'm in the process of upgrading to SQL Server 2005. I have been
> > > getting the following error when trying to run a few reports that have
> > > been upgraded from Reporting Services 2000 to Reporting Services 2005:
> > >
> > >
> > > The Hidden expression used in table 'tblGeneral' returned a data
> > > type that is not valid. (rsInvalidExpressionDataType)
> > >
> > > The same reports still run fine under Reporting Services 2000. Has
> > > anyone run into this or a similar issue?
> > >
> > > Thanks,
> > > Chad
> > >
error Pumping data from ODBC
Hi, there;
I created a package that pump data from ODBC to SQL2005.
When I run my package, I got error:
SSIS package "Package.dtsx" starting.
Information: 0x4004300A at Data Flow Task, DTS.Pipeline: Validation phase is beginning.
Information: 0x40043006 at Data Flow Task, DTS.Pipeline: Prepare for Execute phase is beginning.
Information: 0x40043007 at Data Flow Task, DTS.Pipeline: Pre-Execute phase is beginning.
Information: 0x4004300C at Data Flow Task, DTS.Pipeline: Execute phase is beginning.
Error: 0xC02090F5 at Data Flow Task, DataReader Source [1350]: The component "DataReader Source" (1350) was unable to process the data.
Error: 0xC0047038 at Data Flow Task, DTS.Pipeline: The PrimeOutput method on component "DataReader Source" (1350) returned error code 0xC02090F5. The component returned a failure code when the pipeline engine called PrimeOutput(). The meaning of the failure code is defined by the component, but the error is fatal and the pipeline stopped executing.
Error: 0xC0047021 at Data Flow Task, DTS.Pipeline: Thread "SourceThread0" has exited with error code 0xC0047038.
Error: 0xC0047039 at Data Flow Task, DTS.Pipeline: Thread "WorkThread0" received a shutdown signal and is terminating. The user requested a shutdown, or an error in another thread is causing the pipeline to shutdown.
Error: 0xC0047021 at Data Flow Task, DTS.Pipeline: Thread "WorkThread0" has exited with error code 0xC0047039.
Information: 0x40043008 at Data Flow Task, DTS.Pipeline: Post Execute phase is beginning.
Information: 0x402090DF at Data Flow Task, OLE DB Destination [1527]: The final commit for the data insertion has started.
Information: 0x402090E0 at Data Flow Task, OLE DB Destination [1527]: The final commit for the data insertion has ended.
Information: 0x40043009 at Data Flow Task, DTS.Pipeline: Cleanup phase is beginning.
Information: 0x4004300B at Data Flow Task, DTS.Pipeline: "component "OLE DB Destination" (1527)" wrote 0 rows.
Task failed: Data Flow Task
SSIS package "Package.dtsx" finished: Success.
Did I do something wrong when I created this package?
Thanks.
Did you use the ADO.NET connection manager to connect to your ODBC source? Can you use the ODBC source in other applications, outside of SSIS?|||Yes, I am using ADO.NET. It works for other other tables. I just imported data from two other tables with same connection.
Haven't tried to use this ODBC source yet. But I will use it with C# application out of SSIS.
Thanks.
|||Try your ODBC connection against this table with an outside application. Sounds like you've set these up successfully before, so I would think you've got it setup correctly this time.What ODBC driver are you using? (Against what database)|||Yes, I will.
It shows "D3 ODBC Driver".
Strange thing is that I can pump data for other tables with same connection.
Cheers.|||
Qiuwei wrote:
Yes, I will.
It shows "D3 ODBC Driver".Strange thing is that I can pump data for other tables with same connection.
Cheers.
Maybe you don't have permission to select against this table.|||
Qiuwei wrote:
Yes, I will.
It shows "D3 ODBC Driver".Strange thing is that I can pump data for other tables with same connection.
Cheers.
Trying Incresing the TimeOut property in the datareader. I was able to fix a similar issue before, in my case I had many packages running against the same ODBC source; and I was receiving *I belive* the same error in the 2 packages extracting the biggest set of data. Just a thought....
|||Thanks.
Phil, yes, I have permission to select data from that ODBC source.
Rafael, I set to timeout to 600. It still doesn't want to work. It only has about 9,000 rows.
The problem SSIS users are facing is that the error message is almost useless and very easy to be crashed!
Does anybody know if MS has a web resource for those error code?
Cheers.
sql
error plz help
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) can any one tell me why that error
)Hi,
Please try this article on support.microsoft.com.
Article ID is 926929.
OR.
Make sure that the SQL Browser Service is started and make sure the password is correct, Because in my case customer had changed his passwords and we made sure that he changes his passwords from SSCM rather than
Services and then he was able to connect with no problems.
If you have any further issues please let me know on my e-mail ID.
Subject sould be Error code.
Thanks and Best Regards.
Farhat Nishat.
|||i am sure that the SQL Browser Service is started and the password is correct i think that there steps done before running the web parts
because i think that web parts runs only on sql 2005 so do you know what to do to run web parts on sql2000 ?plz reply
|||Can you check this blog? http://blogs.msdn.com/sql_protocols/archive/2007/05/13/sql-network-interfaces-error-26-error-locating-server-instance-specified.aspx
If you still have problem, please copy/paste your connection string here?
Monday, March 26, 2012
error parsing the query
hi all
I try to run the query below it throw me an exception, error parsing , is there anywat to resolve it?
SELECT TYPE2.list_price as 'TYPE2'
FROM TBL_MST_PRICE TYPE2
WHERE
price_grp_code = (SELECT price_grp_code FROM TBL_MST_PRICE_GRP WHERE prd_code = '' AND cust_code = '')
Error opening datafile: The filename, directory name, or volume labe syntax inco
"Error opening datafile: The filename, directory name, or volume labe syntax is incorrect."
I set the file name property of the Text File (Source) to a valid file, but when I run the package and it returns the above error message, it sets the file name property to <not displayable>.
Does anyone have any experience with such a problem? If so please help!!! ThanksRunning scheduled or manual?|||it's run manually triggerred from an ASP page.|||bump|||Well...
It's running under the context of the login that calls it...but how are you executing from an asp page?
From a job or sproc?
Usually when it runs under the contect of the server the file paths and names have to exists ON the server, not the client.
Is that your understanding?|||It throws the afforementioned error when I call it from ASP or from the Enterprise Manager.
I'm executing it from asp like:
Set oPkg = Server.CreateObject("DTS.Package")
oPkg.Execute
But the fact that it throws the error from EM on the server is most alarming. I just returned from vacation and I have no idea what could be causing this.
The file names do exist on the local server, but when the package is run it sets the file name property to "<not displayable>"sql
Error opening datafile: filename, directory, volume syntax incorrect
package:
"Error opening datafile: The filename, directory name, or
volume label syntax is incorrect."
I set the file name property of the Text File (Source) to
a valid file, but when I run the package and it returns
the above error message, it sets the file name property
to <not displayable>.
Does anyone have any experience with such a problem? If
so please help!!! ThanksIt throws the afforementioned error when I call it from ASP or from the Enterprise Manager.
I'm executing it from asp like:
Set oPkg = Server.CreateObject("DTS.Package")
oPkg.Execute
But the fact that it throws the error from EM on the server is most alarming. I just returned from vacation and I have no idea what could be causing this.
The file names do exist on the local server, but when the package is run it sets the file name property to "<not displayable>"
Friday, March 23, 2012
Error on this query- worked until recently
today:
When I run the following:
SELECT "Account"."OpenDt", "CustRelation"."RelationCode",
"CustRelation"."FullName", "Userfield"."UDFCuthr5", "Userfield"."UDFCufiv1",
"Userfield"."UDFCufiv2", "Account"."AcctId", "CustRelation"."Sequence",
"Account"."OpenedById_CustLoginId", "ViewSessionEvents"."OpenDt",
"ViewSessionEvents"."AcctId", "ViewSessionEvents"."ProdId",
"ViewSessionEvents"."EventStatus", "ViewSessionEvents"."EventCode",
"ViewSessionEvents"."EventTime", "SalesSession"."BranchID",
"Customer"."EvePhone", "Customer"."DayPhone"
FROM ((((("CBSDesktop"."dbo"."ViewSessionEvents" "ViewSessionEvents"
INNER JOIN "CBSDesktop"."dbo"."Account" "Account" ON
"ViewSessionEvents"."AcctId"="Account"."AcctId") INNER JOIN
"CBSDesktop"."dbo"."SalesSession" "SalesSession" ON
"ViewSessionEvents"."SalesSessionId"="SalesSession"."SalesSessionID") INNER
JOIN "CBSDesktop"."dbo"."CustRelation" "CustRelation" ON
("Account"."AccountID"="CustRelation"."AccountId") AND
("Account"."PrimCustId_CustPermId"="CustRelation"."CustPermId")) INNER JOIN
"CBSDesktop"."dbo"."Person" "Person" ON
"CustRelation"."CustPermId"="Person"."CustPermId") INNER JOIN
"CBSDesktop"."dbo"."Userfield" "Userfield" ON
"Person"."PersonID"="Userfield"."CustomerId") INNER JOIN
"CBSDesktop"."dbo"."Customer" "Customer" ON
"Userfield"."CustomerId"="Customer"."CustomerID"
WHERE "ViewSessionEvents"."EventCode"=N'ACCTADD' AND
"ViewSessionEvents"."EventStatus"=N'Complete' AND
"ViewSessionEvents"."AcctId"<>N'null' AND
("CustRelation"."RelationCode"=N'JAF' OR "CustRelation"."RelationCode"=N'JOF
'
OR "CustRelation"."RelationCode"=N'OWN' OR
"CustRelation"."RelationCode"=N'SOW') AND
("ViewSessionEvents"."EventTime">={ts '2005-10-02 00:00:00'} AND
"ViewSessionEvents"."EventTime"<{ts '2005-10-09 00:00:00'}) AND NOT
("ViewSessionEvents"."ProdId"=N'546126' OR
"ViewSessionEvents"."ProdId"=N'587403' OR
"ViewSessionEvents"."ProdId"=N'987001')
ORDER BY "SalesSession"."BranchID", "Account"."OpenedById_CustLoginId",
"Account"."OpenDt", "Account"."AcctId", "CustRelation"."Sequence"
I get:
Server: Msg 512, Level 16, State 1, Line 1
Subquery returned more than 1 value. This is not permitted when the
subquery follows =, !, <, <=, >, =>, or when the subquery is used as an
expression"Pancho" <Pancho@.discussions.microsoft.com> wrote in message
news:A2D04ADB-523A-4B82-9D99-BB81292EA90F@.microsoft.com...
> This is the T-SQL I scraped out of a Crystal Report that worked until 4pm
> today:
> . . .
When rows were added causing a subquery which previously returned a single
row to return more than one value:
Server: Msg 512, Level 16, State 1, Line 1
Subquery returned more than 1 value. This is not permitted when the
subquery follows =, !, <, <=, >, =>, or when the subquery is used as an
expression
It this query appears to lack subqueries, but there could be some in the
views on which it's based.
David
error on report server
Intelligence Development Studio). I got the following message:
======================================================================= TITLE: Microsoft Report Designer
--
A connection could not be made to the report server
http://localhost/ReportServer2005.
--
ADDITIONAL INFORMATION:
Client found response content type of 'text/html; charset=utf-8', but
expected 'text/xml'.
The request failed with the error message:
--
<html>
<head>
<title>
SQL Server Reporting Services
</title><meta name="Generator" content="Microsoft SQL Server Reporting
Services 9.00.1399.00" />
<meta name="HTTP Status" content="500" />
<meta name="ProductLocaleID" content="9" />
<meta name="CountryLocaleID" content="1033" />
<meta name="StackTrace" content=" at
Microsoft.ReportingServices.Diagnostics.RSConfiguration.Load()
at
Microsoft.ReportingServices.Diagnostics.RSConfiguration.Construct(String
configFileName)
at Microsoft.ReportingServices.Diagnostics.RSConfiguration..ctor(String
configFileName, String location)
at
Microsoft.ReportingServices.Diagnostics.RSConfigurationManager..ctor(String
configFileName, String configLocation)
at Microsoft.ReportingServices.Library.Global.get_ConfigurationManager()
at Microsoft.ReportingServices.WebServer.Global.StartApp()
at
Microsoft.ReportingServices.WebServer.Global.Application_BeginRequest(Object
sender, EventArgs e)" />
<style>
BODY {FONT-FAMILY:Verdana; FONT-WEIGHT:normal; FONT-SIZE: 8pt;
COLOR:black}
H1 {FONT-FAMILY:Verdana; FONT-WEIGHT:700; FONT-SIZE:15pt}
LI {FONT-FAMILY:Verdana; FONT-WEIGHT:normal; FONT-SIZE:8pt;
DISPLAY:inline}
.ProductInfo {FONT-FAMILY:Verdana; FONT-WEIGHT:bold; FONT-SIZE: 8pt;
COLOR:gray}
A:link {FONT-SIZE: 8pt; FONT-FAMILY:Verdana; COLOR:#3366CC;
TEXT-DECORATION:none}
A:hover {FONT-SIZE: 8pt; FONT-FAMILY:Verdana; COLOR:#FF3300;
TEXT-DECORATION:underline}
A:visited {FONT-SIZE: 8pt; FONT-FAMILY:Verdana; COLOR:#3366CC;
TEXT-DECORATION:none}
A:visited:hover {FONT-SIZE: 8pt; FONT-FAMILY:Verdana; color:#FF3300;
TEXT-DECORATION:underline}
</style>
</head><body bgcolor="white">
<h1>
Reporting Services Error<hr width="100%" size="1" color="silver" />
</h1><ul>
<li>The report server has encountered a configuration error. See the
report server log files for more information. (rsServerConfigurationError)
</li><ul>
<li>Access to the path 'C:\Program Files\Microsoft SQL
Server\MSSQL.3\Reporting Services\ReportServer\RSReportServer.config' is
denied.</li>
</ul>
</ul><hr width="100%" size="1" color="silver" /><span
class="ProductInfo">SQL Server Reporting Services</span>
</body>
</html>
--. (Microsoft.ReportingServices.Designer)
--
BUTTONS:
OK
--
=======================================================================
This is the error message I got when I try to run
http:\\localhost\reportserver2005 in IE. I got same error message when I run
http:\\MachineName\reportserver2005.
======================================================================= Reporting Services Error
----
a.. The report server has encountered a configuration error. See the
report server log files for more information. (rsServerConfigurationError)
a.. Access to the path 'C:\Program Files\Microsoft SQL
Server\MSSQL.3\Reporting Services\ReportServer\RSReportServer.config' is
denied.
----
SQL Server Reporting Services
=======================================================================
Please help!
Thank you very much
Darren L.Can you access http://localhost/Reports ? This is the default setting.
It looks like some setting problem. What does the log file say?|||Hi,
I ran http://localhost/Reports2005, I got following error:
The report server is not responding. Verify that the report server is
running and can be accessed from this computer.
I am thinking the problem maybe the setup (installation). I have SQL
Server 2000 Reports Service on my machine. When I installed the SQL Server
2005 Report Service. It simply tells me that report service has been
installed. So I created a new instance Reports2005 and ReportServer2005. Is
this the reason why it is not working? And what should I do to fix it?
Thanks
Darren
"Nick" <nick_1394@.yahoo.com.cn> wrote in message
news:1137696210.625104.289820@.g49g2000cwa.googlegroups.com...
> Can you access http://localhost/Reports ? This is the default setting.
> It looks like some setting problem. What does the log file say?
>|||Not sure if I am in the right log:
ReportingServicesService!library!4!1/19/2006-10:02:52:: i INFO: Initializing
ConnectionType to '0' as specified in Configuration file.
ReportingServicesService!library!4!1/19/2006-10:02:52:: i INFO: Initializing
IsSchedulingService to 'True' as specified in Configuration file.
ReportingServicesService!library!4!1/19/2006-10:02:52:: i INFO: Initializing
IsNotificationService to 'True' as specified in Configuration file.
ReportingServicesService!library!4!1/19/2006-10:02:52:: i INFO: Initializing
IsEventService to 'True' as specified in Configuration file.
ReportingServicesService!library!4!1/19/2006-10:02:52:: i INFO: Initializing
PollingInterval to '10' second(s) as specified in Configuration file.
ReportingServicesService!library!4!1/19/2006-10:02:52:: i INFO: Initializing
WindowsServiceUseFileShareStorage to 'False' as specified in Configuration
file.
ReportingServicesService!library!4!1/19/2006-10:02:52:: i INFO: Initializing
MemoryLimit to '60' percent as specified in Configuration file.
ReportingServicesService!library!4!1/19/2006-10:02:52:: i INFO: Initializing
RecycleTime to '720' minute(s) as specified in Configuration file.
ReportingServicesService!library!4!1/19/2006-10:02:52:: i INFO: Initializing
MaximumMemoryLimit to '80' percent as specified in Configuration file.
ReportingServicesService!library!4!1/19/2006-10:02:52:: i INFO: Initializing
MaxAppDomainUnloadTime to '30' minute(s) as specified in Configuration file.
ReportingServicesService!library!4!1/19/2006-10:02:52:: i INFO: Initializing
MaxQueueThreads to '0' thread(s) as specified in Configuration file.
ReportingServicesService!library!4!1/19/2006-10:02:52:: i INFO: Initializing
IsWebServiceEnabled to 'True' as specified in Configuration file.
ReportingServicesService!configmanager!4!1/19/2006-10:02:52:: w WARN:
WebServiceAccount is not specified in the config file. Using default:
DL-DELL700M\ASPNET
ReportingServicesService!library!4!1/19/2006-10:02:52:: i INFO: Initializing
MaxActiveReqForOneUser to '20' requests(s) as specified in Configuration
file.
ReportingServicesService!library!4!1/19/2006-10:02:52:: i INFO: Initializing
MaxScheduleWait to '5' second(s) as specified in Configuration file.
ReportingServicesService!library!4!1/19/2006-10:02:52:: i INFO: Initializing
DatabaseQueryTimeout to '120' second(s) as specified in Configuration file.
ReportingServicesService!library!4!1/19/2006-10:02:52:: i INFO: Initializing
ProcessRecycleOptions to '0' as specified in Configuration file.
ReportingServicesService!library!4!1/19/2006-10:02:52:: i INFO: Initializing
RunningRequestsScavengerCycle to '60' second(s) as specified in
Configuration file.
ReportingServicesService!library!4!1/19/2006-10:02:52:: i INFO: Initializing
RunningRequestsDbCycle to '60' second(s) as specified in Configuration file.
ReportingServicesService!library!4!1/19/2006-10:02:52:: i INFO: Initializing
RunningRequestsAge to '30' second(s) as specified in Configuration file.
ReportingServicesService!library!4!1/19/2006-10:02:52:: i INFO: Initializing
CleanupCycleMinutes to '10' minute(s) as specified in Configuration file.
ReportingServicesService!library!4!1/19/2006-10:02:52:: i INFO: Initializing
DailyCleanupMinuteOfDay to default value of '120' minutes since midnight
because it was not specified in Configuration file.
ReportingServicesService!library!4!1/19/2006-10:02:52:: i INFO: Initializing
WatsonFlags to '1064' as specified in Configuration file.
ReportingServicesService!library!4!1/19/2006-10:02:52:: i INFO: Initializing
WatsonDumpOnExceptions to
'Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException,Microsoft.ReportingServices.Modeling.InternalModelingException'
as specified in Configuration file.
ReportingServicesService!library!4!1/19/2006-10:02:52:: i INFO: Initializing
WatsonDumpExcludeIfContainsExceptions to
'System.Data.SqlClient.SqlException,System.Threading.ThreadAbortException'
as specified in Configuration file.
ReportingServicesService!library!4!1/19/2006-10:02:52:: i INFO: Initializing
SecureConnectionLevel to '0' as specified in Configuration file.
ReportingServicesService!library!4!1/19/2006-10:02:52:: i INFO: Initializing
DisplayErrorLink to 'True' as specified in Configuration file.
ReportingServicesService!library!4!1/19/2006-10:02:52:: i INFO: Initializing
WebServiceUseFileShareStorage to 'False' as specified in Configuration
file.
ReportingServicesService!servicecontroller!9!1/19/2006-10:02:57:: Total
Physical memory: 1055309824
ReportingServicesService!servicecontroller!4!1/19/2006-10:02:58:: i INFO:
RPC Server started. Endpoint name ='ReportingServices$MSSQL.3'
ReportingServicesService!library!3!1/19/2006-10:21:54:: i INFO: Catalog SQL
Server Edition = Developer
ReportingServicesService!resourceutilities!3!1/19/2006-10:21:54:: i INFO:
Reporting Services starting SKU: Standard
ReportingServicesService!resourceutilities!3!1/19/2006-10:21:54:: i INFO:
Evaluation copy: 0 days left
ReportingServicesService!library!3!1/19/2006-10:21:54:: e ERROR: restricted
SKUs: Workgroup Express Developer Evaluation - actual SKU Developer
ReportingServicesService!library!3!1/19/2006-10:21:54:: e ERROR: Throwing
Microsoft.ReportingServices.Diagnostics.Utilities.OperationNotSupportedException:
The feature: "Using other editions of SQL Server for report data sources
and/or the report server database" is not supported in this edition of
Reporting Services., ;
Info:
Microsoft.ReportingServices.Diagnostics.Utilities.OperationNotSupportedException:
The feature: "Using other editions of SQL Server for report data sources
and/or the report server database" is not supported in this edition of
Reporting Services.
ReportingServicesService!library!a!1/19/2006-10:21:54:: i INFO: Catalog SQL
Server Edition = Developer
ReportingServicesService!library!a!1/19/2006-10:21:54:: e ERROR: restricted
SKUs: Workgroup Express Developer Evaluation - actual SKU Developer
ReportingServicesService!library!a!1/19/2006-10:21:54:: e ERROR: Throwing
Microsoft.ReportingServices.Diagnostics.Utilities.OperationNotSupportedException:
The feature: "Using other editions of SQL Server for report data sources
and/or the report server database" is not supported in this edition of
Reporting Services., ;
Info:
Microsoft.ReportingServices.Diagnostics.Utilities.OperationNotSupportedException:
The feature: "Using other editions of SQL Server for report data sources
and/or the report server database" is not supported in this edition of
Reporting Services.
ReportingServicesService!library!3!1/19/2006-10:21:55:: i INFO: Catalog SQL
Server Edition = Developer
ReportingServicesService!library!3!1/19/2006-10:21:55:: e ERROR: restricted
SKUs: Workgroup Express Developer Evaluation - actual SKU Developer
ReportingServicesService!library!3!1/19/2006-10:21:55:: e ERROR: Throwing
Microsoft.ReportingServices.Diagnostics.Utilities.OperationNotSupportedException:
The feature: "Using other editions of SQL Server for report data sources
and/or the report server database" is not supported in this edition of
Reporting Services., ;
Info:
Microsoft.ReportingServices.Diagnostics.Utilities.OperationNotSupportedException:
The feature: "Using other editions of SQL Server for report data sources
and/or the report server database" is not supported in this edition of
Reporting Services.
There are few error statements at the buttom. But...
Thanks
Darren L.
"Nick" <nick_1394@.yahoo.com.cn> wrote in message
news:1137696210.625104.289820@.g49g2000cwa.googlegroups.com...
> Can you access http://localhost/Reports ? This is the default setting.
> It looks like some setting problem. What does the log file say?
>
Thursday, March 22, 2012
Error on replication
when i try to run an push-replication on MS SQL 2000
i get the error "Log file is full" on the subscriber.
I tried to make this grow VERY much, but it doesnt help.
The table that fails has over 75000 posts, so maybe that is an issue.
The error occurs when i for the first time tries to sync it...
Any ideas?
// PeterTry breaking your task into smaller units of work.
You would normally be using "BeginTrans" and "CommitTrans" to free up the log space in a program after a unit of work has been completed.
Good Luck,|||Well, the thing is... i only want to replicate this to a server, and not
run any scripts. Shouldnt MS-SQL handle this?
I tried the push-operation without the LARGE-table (75000 posts)
and it worked. So it has something to do with that.
Any more suggestions?
Please?!!
// Peter
Originally posted by Bruce A. Baasch
Try breaking your task into smaller units of work.
You would normally be using "BeginTrans" and "CommitTrans" to free up the log space in a program after a unit of work has been completed.
Good Luck,sql
Wednesday, March 21, 2012
Error on one of SQL Reporting Services Samples
I am running the reports that comes with the samples one and I'm getting
this error when I run this code;
="SELECT c.firstname, c.lastname, e.title, d.departmentID " &
"From HumanResources.EmployeeDepartmentHistory D " &
"INNER JOIN HumanResources.Employee E " &
"ON D.EmployeeID = E.EmployeeID " &
"INNER JOIN Person.Contact C " &
"ON E.ContactID = C.ContactID " &
Iif(Parameters!Department.Value = 0, "", "WHERE D.DepartmentID = " &
Parameters!Department.Value) &
"ORDER BY C.LastName"
The error is saying that all those columns can not be bounded. can anybody
tells me where the error is this piece of code?
Thanks very much in advance.
Midway.The IIF in there is for internal RS expressions and not T-SQL. This appears
to have been modified ('). Which report and dataset is this from?
SalesEmps within the Employee Sales Summary report looks similiar:
SELECT E.EmployeeID, C.FirstName + N' ' + C.LastName AS Employee
FROM HumanResources.Employee E INNER JOIN
Sales.SalesPerson SP ON E.EmployeeID = SP.SalesPersonID INNER JOIN
Person.Contact C ON E.ContactID = C.ContactID
ORDER BY C.LastName, C.FirstName
RDA Corp
Business Intelligence Evangelist Leader
www.rdacorp.com
"Midway" wrote:
> Hi there,
> I am running the reports that comes with the samples one and I'm getting
> this error when I run this code;
> ="SELECT c.firstname, c.lastname, e.title, d.departmentID " &
> "From HumanResources.EmployeeDepartmentHistory D " &
> "INNER JOIN HumanResources.Employee E " &
> "ON D.EmployeeID = E.EmployeeID " &
> "INNER JOIN Person.Contact C " &
> "ON E.ContactID = C.ContactID " &
> Iif(Parameters!Department.Value = 0, "", "WHERE D.DepartmentID = " &
> Parameters!Department.Value) &
> "ORDER BY C.LastName"
> The error is saying that all those columns can not be bounded. can anybody
> tells me where the error is this piece of code?
> Thanks very much in advance.
> Midway.
Error on Migrating to V2000 SQL from V7
when trying to run an Stored Procedure I am getting the following error.
Syntax error converting the varchar value '2165.05' to a column of data type
int.
The Stored Proc just selects values into a Table, the wierd thing is this
works on v7 (same data / schema everything, but not on 2000) I can code
around it with Convert etc but was wondering if its a common problem and if
there is anything more I should know.
Cheers
Stumpy
Message posted via http://www.droptable.com
Without seeing a repro, I can only guess. It could be that datatype precedence has changed. Say, for
instance, you have a column of datatype varchar and a variable of datatype nvarchar, and then do:
WHERE col = @.a
7.0 would convert the value side to the column sides datatype. But 2000 will go by the rules
specified in Books Online "Datatype Precedence", and above would result in converting the column
side to the value sides datatype.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"stumpy_uk via droptable.com" <u15773@.uwe> wrote in message news:75df584d107f7@.uwe...
>I have just upgraded to SQL 2000 as per the companies allowed versions and
> when trying to run an Stored Procedure I am getting the following error.
> Syntax error converting the varchar value '2165.05' to a column of data type
> int.
> The Stored Proc just selects values into a Table, the wierd thing is this
> works on v7 (same data / schema everything, but not on 2000) I can code
> around it with Convert etc but was wondering if its a common problem and if
> there is anything more I should know.
> Cheers
> Stumpy
> --
> Message posted via http://www.droptable.com
>
|||MS changed the rules for implicit date type converstion between V7 and 2000.
There is nothing you can do about it.
If you use a char data type in a context in which a numeric type is
required, the char value will be converted to int, unless the context
explicitly implies (sic!) that decimal or float is requied. Since 2165.05 is
not an int, but a decimal, the conversion will fail. Since you fail to
provide the SQL code, there's no chance of my giving more details.
Use CAST (val as decimal (18, 2)) [or whatever data type you want] to
resolve. Note: CONVERT is an MS-specific function, so CAST is preferable.
"stumpy_uk via droptable.com" <u15773@.uwe> wrote in message
news:75df584d107f7@.uwe...
>I have just upgraded to SQL 2000 as per the companies allowed versions and
> when trying to run an Stored Procedure I am getting the following error.
> Syntax error converting the varchar value '2165.05' to a column of data
> type
> int.
> The Stored Proc just selects values into a Table, the wierd thing is this
> works on v7 (same data / schema everything, but not on 2000) I can code
> around it with Convert etc but was wondering if its a common problem and
> if
> there is anything more I should know.
> Cheers
> Stumpy
> --
> Message posted via http://www.droptable.com
>
|||Thanks all for your help, sorry I didn't post the DDL etc, the problem was
ownership of the Database in the end.I did a ChangeDBOwner on all the tables
and the problem went away.
Cheers for all the help..
Lee
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums.aspx/sql-server/200707/1
Error on Migrating to V2000 SQL from V7
when trying to run an Stored Procedure I am getting the following error.
Syntax error converting the varchar value '2165.05' to a column of data type
int.
The Stored Proc just selects values into a Table, the wierd thing is this
works on v7 (same data / schema everything, but not on 2000) I can code
around it with Convert etc but was wondering if its a common problem and if
there is anything more I should know.
Cheers
Stumpy
Message posted via http://www.droptable.comWithout seeing a repro, I can only guess. It could be that datatype preceden
ce has changed. Say, for
instance, you have a column of datatype varchar and a variable of datatype n
varchar, and then do:
WHERE col = @.a
7.0 would convert the value side to the column sides datatype. But 2000 will
go by the rules
specified in Books Online "Datatype Precedence", and above would result in c
onverting the column
side to the value sides datatype.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"stumpy_uk via droptable.com" <u15773@.uwe> wrote in message news:75df584d107f7@.uwe...[vbcol
=seagreen]
>I have just upgraded to SQL 2000 as per the companies allowed versions and
> when trying to run an Stored Procedure I am getting the following error.
> Syntax error converting the varchar value '2165.05' to a column of data ty
pe
> int.
> The Stored Proc just selects values into a Table, the wierd thing is this
> works on v7 (same data / schema everything, but not on 2000) I can code
> around it with Convert etc but was wondering if its a common problem and i
f
> there is anything more I should know.
> Cheers
> Stumpy
> --
> Message posted via http://www.droptable.com
>[/vbcol]|||MS changed the rules for implicit date type converstion between V7 and 2000.
There is nothing you can do about it.
If you use a char data type in a context in which a numeric type is
required, the char value will be converted to int, unless the context
explicitly implies (sic!) that decimal or float is requied. Since 2165.05 is
not an int, but a decimal, the conversion will fail. Since you fail to
provide the SQL code, there's no chance of my giving more details.
Use CAST (val as decimal (18, 2)) [or whatever data type you want] to
resolve. Note: CONVERT is an MS-specific function, so CAST is preferable.
"stumpy_uk via droptable.com" <u15773@.uwe> wrote in message
news:75df584d107f7@.uwe...
>I have just upgraded to SQL 2000 as per the companies allowed versions and
> when trying to run an Stored Procedure I am getting the following error.
> Syntax error converting the varchar value '2165.05' to a column of data
> type
> int.
> The Stored Proc just selects values into a Table, the wierd thing is this
> works on v7 (same data / schema everything, but not on 2000) I can code
> around it with Convert etc but was wondering if its a common problem and
> if
> there is anything more I should know.
> Cheers
> Stumpy
> --
> Message posted via http://www.droptable.com
>|||Thanks all for your help, sorry I didn't post the DDL etc, the problem was
ownership of the Database in the end.I did a ChangeDBOwner on all the tables
and the problem went away.
Cheers for all the help..
Lee
Message posted via droptable.com
http://www.droptable.com/Uwe/Forum...server/200707/1sql
Error on Migrating to V2000 SQL from V7
when trying to run an Stored Procedure I am getting the following error.
Syntax error converting the varchar value '2165.05' to a column of data type
int.
The Stored Proc just selects values into a Table, the wierd thing is this
works on v7 (same data / schema everything, but not on 2000) I can code
around it with Convert etc but was wondering if its a common problem and if
there is anything more I should know.
Cheers
Stumpy
--
Message posted via http://www.sqlmonster.comWithout seeing a repro, I can only guess. It could be that datatype precedence has changed. Say, for
instance, you have a column of datatype varchar and a variable of datatype nvarchar, and then do:
WHERE col = @.a
7.0 would convert the value side to the column sides datatype. But 2000 will go by the rules
specified in Books Online "Datatype Precedence", and above would result in converting the column
side to the value sides datatype.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"stumpy_uk via SQLMonster.com" <u15773@.uwe> wrote in message news:75df584d107f7@.uwe...
>I have just upgraded to SQL 2000 as per the companies allowed versions and
> when trying to run an Stored Procedure I am getting the following error.
> Syntax error converting the varchar value '2165.05' to a column of data type
> int.
> The Stored Proc just selects values into a Table, the wierd thing is this
> works on v7 (same data / schema everything, but not on 2000) I can code
> around it with Convert etc but was wondering if its a common problem and if
> there is anything more I should know.
> Cheers
> Stumpy
> --
> Message posted via http://www.sqlmonster.com
>|||MS changed the rules for implicit date type converstion between V7 and 2000.
There is nothing you can do about it.
If you use a char data type in a context in which a numeric type is
required, the char value will be converted to int, unless the context
explicitly implies (sic!) that decimal or float is requied. Since 2165.05 is
not an int, but a decimal, the conversion will fail. Since you fail to
provide the SQL code, there's no chance of my giving more details.
Use CAST (val as decimal (18, 2)) [or whatever data type you want] to
resolve. Note: CONVERT is an MS-specific function, so CAST is preferable.
"stumpy_uk via SQLMonster.com" <u15773@.uwe> wrote in message
news:75df584d107f7@.uwe...
>I have just upgraded to SQL 2000 as per the companies allowed versions and
> when trying to run an Stored Procedure I am getting the following error.
> Syntax error converting the varchar value '2165.05' to a column of data
> type
> int.
> The Stored Proc just selects values into a Table, the wierd thing is this
> works on v7 (same data / schema everything, but not on 2000) I can code
> around it with Convert etc but was wondering if its a common problem and
> if
> there is anything more I should know.
> Cheers
> Stumpy
> --
> Message posted via http://www.sqlmonster.com
>|||Thanks all for your help, sorry I didn't post the DDL etc, the problem was
ownership of the Database in the end.I did a ChangeDBOwner on all the tables
and the problem went away.
Cheers for all the help..
Lee
--
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200707/1
Monday, March 12, 2012
Error occured while reading data from the query result set
EXEC spRS_ShopPAP '2004-03-16', '2004-04-14'
and data returns perfectly. Try and run this from the data preview window in reporting services and you get "Error occured while reading data from the query result set. OLE DB Provider MDSASQL reported an error"
Has anyone seen this before ? Shouldn't it work in the data preview window ?
Thanks, Steve.
Would a stored proc run fine in the preview window without parameters? I'm
curious...
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.
Error occured while reading data from the query result set
.
EXEC spRS_ShopPAP '2004-03-16', '2004-04-14'
and data returns perfectly. Try and run this from the data preview window in
reporting services and you get "Error occured while reading data from the q
uery result set. OLE DB Provider MDSASQL reported an error"
Has anyone seen this before ? Shouldn't it work in the data preview window ?
Thanks, Steve.Would a stored proc run fine in the preview window without parameters? I'm
curious...
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.
Error occured while establishing connection with sql server
I am new learner of ASP.NET and SQL server.So there might be any mistake in writing code.
When I tried to run my project I got following error.I am uisng SQL 2005 server.
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, 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)
connection string used is
<addname ="ConnectionString"connectionString="Data Source=BLUESTAR\\SQLEXPRESS;Initial Catalog=KnowledgeAssetManagement;Integrated Security=True"/>
I have also tried by setting local & remote connection options from the SQL server surface Area Configuration and connections option from server properties of sql server management studio.
Please help me ,my work get stucked due this problem.
Hi Bluestar123
In your connection string you do not need to have to forward slashes after bluestar see connection string below
<add name ="ConnectionString" connectionString="Data Source=BLUESTAR\SQLEXPRESS;Initial Catalog=KnowledgeAssetManagement;Integrated Security=True"/>
Hope this helps
Regards
ScottyB
|||Hi ScottyB,
Actually I have given only one slash after bluestar in connection string but it gives me error 'Unrecognized Escape Sequence' so after searching on google I have given that double slashes which removes that error.
Thanks for your reply ,
can you suggest any other solution?
Error number: 2812 - Transaction Replication
I am trying transactional replication between two servers with a remote
distributor. I am getting following error each time I run the distribution
agent
Last Command : {CALL sp_MSupd_Customers (NULL,N'Alfreds Futterkiste -
test',NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL ,N'ALFKI',0x0200)}
Transaction sequence number and command ID of last execution batch are
0x0000001A00000082000900000000 and 1.
Error Message :Could not find stored procedure 'sp_MSupd_Customers'.
Error details : Could not find stored procedure 'sp_MSupd_Customers'.
(Source: L000646\AA03 (Data source); Error number: 2812)
Can some one help please
If you have used @.sync_type = None in sp_addsubscription or in the
subscription wizard, Initialize subscription page, you select 'no, the
subscriber already has the schema and data' you may get this error. The
system tables for replication will be created on the subscriber in either
case but you'll need to manually create the stored procedures on the
subscriber if you use this option otherwise you'll have the above error when
you change a row on the publisher. Use sp_scriptpublicationcustomprocs
(assuming you have >= sp1) to create a script which creates the procedures
and run this script on the subscriber.
HTH,
Paul Ibison
|||Thanks for that Paul. It is all working now.
regards
"Paul Ibison" wrote:
> If you have used @.sync_type = None in sp_addsubscription or in the
> subscription wizard, Initialize subscription page, you select 'no, the
> subscriber already has the schema and data' you may get this error. The
> system tables for replication will be created on the subscriber in either
> case but you'll need to manually create the stored procedures on the
> subscriber if you use this option otherwise you'll have the above error when
> you change a row on the publisher. Use sp_scriptpublicationcustomprocs
> (assuming you have >= sp1) to create a script which creates the procedures
> and run this script on the subscriber.
> HTH,
> Paul Ibison
>
>
Sunday, March 11, 2012
Error number 8941
when I run a stored procedure thru Query Analyzer, I get this error msg.
Server: Msg 8941, Level 22, State 102, Line 5
Table error: Object ID 5810549, index ID 1, page (0:782677886). Test (offset
+ len < PAGESIZE) failed. Slot 25, offset 0x1089 is invalid.
But when I tried to find out which object is throwing error I could not find
out.
I used the following code :
Select * from sysobjects where id = 5810549
go
Select object_name(5810549)
Any thoughts...
Thanks,
PradI've not seen that error before first hand. I'd personally try running the
DBCC CHECKDB command to check the integrity of the objects within the
database. If this flags up problems, post them back and I'll try to offer a
fix for them.
Hope this helps
--
Adam J Warne, MCDBA
"Pradeep Kutty" wrote:
> Hi All,
> when I run a stored procedure thru Query Analyzer, I get this error msg.
> Server: Msg 8941, Level 22, State 102, Line 5
> Table error: Object ID 5810549, index ID 1, page (0:782677886). Test (offs
et
> + len < PAGESIZE) failed. Slot 25, offset 0x1089 is invalid.
> But when I tried to find out which object is throwing error I could not fi
nd
> out.
> I used the following code :
> Select * from sysobjects where id = 5810549
> go
> Select object_name(5810549)
> Any thoughts...
> Thanks,
> Prad
>
>
>
Friday, March 9, 2012
Error msg when installing
configure) roughly like this: "...instance name is invalid" - how come?
Very grateful for help!
Hi,
Try running the setup from command line to install the MSDE.
1. Run command prompt.
2. Change the directory to the MSDE install extract folder
3. Run the following command:
setup.exe INSTANCENAME="testmsde" DISABLEROLLBACK=1 SAPWD="password" /L*v
c:\temp\setup.log
Thanks
Hari
"Black Eagle" <BlackEagle@.discussions.microsoft.com> wrote in message
news:F0709E51-93C5-42D3-98B6-DB32FB7B0127@.microsoft.com...
> When I try to run MSDE setup, i get a msg (after a msg about starting to
> configure) roughly like this: "...instance name is invalid" - how come?
> Very grateful for help!
>