Data tab works great but i can't get it work in Preview tab in reporting services

This code works great in data tab but when i go to preview it i get a len function error.
I am passing possible BLANK values in all the strings not NULL. Do you think its an parameter expression issue? If so, how do I write a expression for each parameter that will reflect this logic. NOTE: As you can see states and program are multi param, and I don't know ahead of time what values will be entered. So if some could please help.
SELECT DISTINCT A.RECIPIENT_STATE, B.FISCAL_YEAR, B.FEDERAL_SHARE, B.NON_FEDERAL_SHARE
FROM Tab_Awards AS A JOIN TAB_Amendments AS B ON A.AWARD_NUMBER = B.AWARD_NUMBER JOIN Tab_Program AS C
ON A.FPO_ID = C.FPO_ID
WHERE (LEN(@.keywords)<1 OR (FREETEXT(A.*,@.keywords)))
AND (LEN(@.states)<1 OR A.RECIPIENT_STATE IN (@.states))
AND (LEN(@.program) <1 OR C.PROGRAM IN (@.program))
AND (LEN(@.fromYear)<1 OR B.FISCAL_YEAR >= @.fromYear)
AND (LEN(@.toYear)<1 OR B.FISCAL_YEAR <= @.toYear)
AND (LEN(@.year)<1 OR LEN(@.year)>=1)
AND (LEN(@.organization)<1 OR LEN(@.organization)>=1
From http://www.developmentnow.com/g/115_0_0_0_0_0/sql-server-reporting-services.ht
Posted via DevelopmentNow.com Group
http://www.developmentnow.comWhat exactly is the error ? Why I am asking is that len must be evaluating
some numeric value e.g year parameter must be having numeric and Len will
take string expression only. So Just have a look at all the parameters again
and see their data type.
Amarnath
"Dre" wrote:
> This code works great in data tab but when i go to preview it i get a len function error.
> I am passing possible BLANK values in all the strings not NULL. Do you think its an parameter expression issue? If so, how do I write a expression for each parameter that will reflect this logic. NOTE: As you can see states and program are multi param, and I don't know ahead of time what values will be entered. So if some could please help.
> SELECT DISTINCT A.RECIPIENT_STATE, B.FISCAL_YEAR, B.FEDERAL_SHARE, B.NON_FEDERAL_SHARE
> FROM Tab_Awards AS A JOIN TAB_Amendments AS B ON A.AWARD_NUMBER = B.AWARD_NUMBER JOIN Tab_Program AS C
> ON A.FPO_ID = C.FPO_ID
> WHERE (LEN(@.keywords)<1 OR (FREETEXT(A.*,@.keywords)))
> AND (LEN(@.states)<1 OR A.RECIPIENT_STATE IN (@.states))
> AND (LEN(@.program) <1 OR C.PROGRAM IN (@.program))
> AND (LEN(@.fromYear)<1 OR B.FISCAL_YEAR >= @.fromYear)
> AND (LEN(@.toYear)<1 OR B.FISCAL_YEAR <= @.toYear)
> AND (LEN(@.year)<1 OR LEN(@.year)>=1)
> AND (LEN(@.organization)<1 OR LEN(@.organization)>=1)
> From http://www.developmentnow.com/g/115_0_0_0_0_0/sql-server-reporting-services.htm
> Posted via DevelopmentNow.com Groups
> http://www.developmentnow.com
>

Data SWITCH partition fails with primary key constraint Error

Hi champs,

I am trying to use SWITCH partitions from one fact table out to another identical table. On some tables this does not work as I get an ERROR conserning primary key constraints; is there a way around this without deleting the primary key constraint?

ERROR:

"SWITCH PARTITION 1 TO my_switch_out_table PARTITION 1 " failed with the following error: "ALTER TABLE SWITCH statement failed. SWITCH is not allowed because source table 'my_fact_table' contains primary key for constraint "

/Many thanks

Please post some sample DDL that demonstrates the problem. It will be easier to suggest the solution. You should also take a look at the BOL topic below:

http://msdn2.microsoft.com/en-gb/library/ms191160.aspx

It lists the table, index and constraint requirements for the switch to work.

|||

I have one table that has a two colums as a PK and this table has a PK constraint to one other table and other constraints to 5 other tables.

I've constructed the "OLD_DATA" table as a exact duplicate, including index, of the source table.

However I cannot create the exact same constraints on the destination table, as these already exists in the database.

when I run the following SWITCH, I get an error that

ALTER TABLE dbo.source_table_fact
SWITCH PARTITION 1
TO dbo.OLD_DATA_source_table_fact
PARTITION 1
go

[Execute SQL Task] Error: Executing the query "ALTER TABLE dbo.Ordination_fact SWITCH PARTITION 1 TO dbo.OLD_DATA_MYtable_fact PARTITION 1 " failed with the following error: "ALTER TABLE SWITCH statement failed. SWITCH is not allowed because source table 'dbo.MYtable_fact' contains primary key for constraint 'FK_fact_Mytable_fact'.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.

This works fine on most of my fact tables but some SWITCHES will not work.

/Many thanks

|||

Here is the script
/* script start */
USE master
go
IF EXISTS (SELECT name FROM sys.databases WHERE name = N'testdb')
BEGIN
ALTER DATABASE [testdb] SET SINGLE_USER WITH ROLLBACK IMMEDIATE
DROP DATABASE [testdb]
END
go
CREATE DATABASE [testdb]
GO
USE [testdb]
GO

CREATE PARTITION FUNCTION [RangeMonth] (datetime)
AS RANGE RIGHT FOR VALUES (
N'2006-12-01 00:00:00',
N'2007-01-01 00:00:00',
N'2007-02-01 00:00:00',
N'2007-03-01 00:00:00',
N'2007-04-01 00:00:00',
N'2007-05-01 00:00:00'
);
GO

CREATE PARTITION SCHEME [RangeM]
AS PARTITION [RangeMonth] all
TO ([Primary]);

CREATE TABLE dbo.test1
(
A uniqueidentifier NOT NULL,
B uniqueidentifier NULL,
C uniqueidentifier NULL,
ST Datetime NOT NULL,

CONSTRAINT test1_pk
PRIMARY KEY NONCLUSTERED (A ,ST) ON [RangeM] (ST),
) on [RangeM] (ST)
;

CREATE TABLE dbo.Lefttest1
(
A uniqueidentifier NOT NULL,
B uniqueidentifier NULL,
C uniqueidentifier NULL,
ST Datetime NOT NULL,

CONSTRAINT Lefttest1_pk
PRIMARY KEY NONCLUSTERED (A,ST) ON [Primary]
) ON [Primary]
;

CREATE TABLE dbo.test2
(
D uniqueidentifier NOT NULL,
E uniqueidentifier NOT NULL,
F uniqueidentifier NOT NULL,
PartKey Datetime NOT NULL

CONSTRAINT test2_pk
PRIMARY KEY NONCLUSTERED (D,PartKey) ON [RangeM] ([PartKey]),
) ON [RangeM] ([PartKey])
go

CREATE TABLE dbo.Lefttest2
(
D uniqueidentifier NOT NULL,
E uniqueidentifier NOT NULL,
F uniqueidentifier NOT NULL,
PartKey Datetime NOT NULL

CONSTRAINT Lefttest2_pk
PRIMARY KEY NONCLUSTERED (D,PartKey) ON [Primary],
) ON [Primary]

;

CREATE TABLE dbo.test3 (
G uniqueidentifier NOT NULL,
D uniqueidentifier NOT NULL,
PartKey Datetime NOT NULL,
AnotherTime Datetime NOT NULL,

constraint test3_pk
primary key nonclustered (G),

constraint test3_D_PartKey_ref
foreign key (D,PartKey)
references test2(D,PartKey)
on delete cascade
)
;
GO
CREATE TABLE dbo.Lefttest3 (
G uniqueidentifier NOT NULL,
D uniqueidentifier NOT NULL,
PartKey Datetime NOT NULL,
AnotherTime Datetime NOT NULL,

constraint Lefttest3_pk
primary key nonclustered (G) ON [Primary],

constraint Lefttest3_D_PartKey_ref
foreign key (D,PartKey)
references Lefttest2(D,PartKey)
on delete cascade
) ON [Primary]
;
GO

-- Try to switch out the first partition
-- on test1

ALTER TABLE test1
SWITCH PARTITION 1
TO Lefttest1;

-- Try to switch out the first partition
-- on test2
-- Fails with
-- Msg 4967, Level 16, State 1, Line 1
-- ALTER TABLE SWITCH statement failed.
-- SWITCH is not allowed because source table 'testdb.dbo.test2'
-- contains primary key for constraint 'test3_did_ref'.

ALTER TABLE test2
SWITCH PARTITION 1
TO Lefttest2;

Data Source Security

When a paticular user runs a report, she is getting an error that refers to
not having security to the data source.
I went to the Report Manager and added her to the properties>security of the
datasource. Also, I went into sql and gave her db.readerwrites to the
databases.
Am I missing something else? I have this problem on another project as
well. Any ideas?On Aug 14, 6:02 pm, Ryan Mcbee <RyanMc...@.discussions.microsoft.com>
wrote:
> When a paticular user runs a report, she is getting an error that refers to
> not having security to the data source.
> I went to the Report Manager and added her to the properties>security of the
> datasource. Also, I went into sql and gave her db.readerwrites to the
> databases.
> Am I missing something else? I have this problem on another project as
> well. Any ideas?
If you have default SQL authentication set for the datasource in the
Report Manager, you may want to make sure that the SQL account has
adequate permissions to execute stored procedures/queries in the
database, etc that the report is accessing and the correct password
and connection string. Hope this helps.
Regards,
Enrique Martinez
Sr. Software Consultant

Data Source Provider Error: The event log file is full

I'm trying to process one of my cubes and am getting this error, see subject
line. Mt configuration is this: Development Web server Dul09 holds the cube
s. The data lives on a SQL server DryHou10. I have had my sysadmin check the
event logs on both serv
ers, neither of which is full. This setup has been working just fine for the
last few years. Other cubes on Dul09, using different SQL servers for data,
process just fine.
All servers are running SQL 2000TJSully wrote:
> *I'm trying to process one of my cubes and am getting this error, see
> subject line. Mt configuration is this: Development Web server Dul09
> holds the cubes. The data lives on a SQL server DryHou10. I have had
> my sysadmin check the event logs on both serv
> ers, neither of which is full. This setup has been working just fine
> for the last few years. Other cubes on Dul09, using different SQL
> servers for data, process just fine.
> All servers are running SQL 2000 *
annieckl
---
Posted via http://www.mcse.ms
---
View this thread: http://www.mcse.ms/message441896.html|||Are you sure that they are not full...I got the same error once and emptied
all my logs (you can put them into files if
you want to keep them) - it worked again after that.
--Michael
"annieckl" <annieckl.1dtcei@.mail.mcse.ms> skrev i en meddelelse
news:annieckl.1dtcei@.mail.mcse.ms...
> TJSully wrote:
>
> --
> annieckl
> ---
> Posted via http://www.mcse.ms
> ---
> View this thread: http://www.mcse.ms/message441896.html
>

Data source name not found and no default driver specified - When the website was publishe

ERROR [IM002] [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified

Description:An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details:System.Data.Odbc.OdbcException: ERROR [IM002] [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified
Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:

[OdbcException (0x80131937): ERROR [IM002] [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified] System.Data.Odbc.OdbcConnection.HandleError(OdbcHandle hrHandle, RetCode retcode) +35 System.Data.Odbc.OdbcConnectionHandle..ctor(OdbcConnection connection, OdbcConnectionString constr, OdbcEnvironmentHandle environmentHandle) +131 System.Data.Odbc.OdbcConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningObject) +98 System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup poolGroup) +27 System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection) +47 System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory) +105 System.Data.Odbc.OdbcConnection.Open() +37 DBConnection.open() +12 ASP.global_asax.Session_Start(Object sender, EventArgs e) +35 System.Web.SessionState.SessionStateModule.RaiseOnStart(EventArgs e) +2163182 System.Web.SessionState.SessionStateModule.CompleteAcquireState() +154 System.Web.SessionState.SessionStateModule.BeginAcquireState(Object source, EventArgs e, AsyncCallback cb, Object extraData) +542 System.Web.AsyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +90 System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +155

Version Information: Microsoft .NET Framework Version:2.0.50727.42; ASP.NET Version:2.0.50727.42

ODBC version 3.526.1830.0
strconn ="DSN=testserver;uid=tester;pwd=tester;DATABASE=Test_Database"

I've Test_Database on 2 machines (same data in both machines), one is in SQL 2005 server and another one is in SQL 2000 server.
When the website was published, it can't work. (with both database). But it work in debug mode in Visual Studio2005.

The website can't work when use ODBC connection but it work when use SqlClient.

Help me solve this problem please. T_T

Thanks in advance,

Did you create the ODBC DSN in your local machine?|||Yes sir , I've use ODBC while I develop this website. It can run in debug mode sir !|||

Ok, just let me know if you are getting this error on localhost or on a hosting server?

Also don't call me Sir

|||

I get this error nn localhost.

Database is on localhost(SQL2005) and other one is on another machine(SQL2000).

|||

Ok, check

www.connectionstrings.com

And make sure your connectionstring is correct.

Regards

|||

Yeah , It's resolved.

I added wrong DSN. I added it in User DSN. T_T

So I add new DSN in File DSN and the website work.

Thanks for your advice,

Regards,

|||

buabanz:

So I add new DSN in File DSN and the website work.

Oh sorry, I've added it in System DSN.

sql

Data source name not found and no default driver specified

On the database server, when I try to connect my SQL Server registration, I
get the error on the subject line. WHen I check my SQL Server Services using
SQL Server Services Manager, I do not see my server name in the drop down box
- I have to type it in. SQL Server Agent and server services are started. My
jobs failed because of the error. I have never had to set up a DSN on the
server to get a connection to the database. PLease help to resolve
Hmmm...Is this a clean installation, an upgrade, etc...
Might be related (and I emphasize might) to MDAC. Check out:
http://support.microsoft.com/?kbid=301202
and
http://www.microsoft.com/downloads/d...displaylang=en
HTH
Jerry
"spoons" <spoons@.discussions.microsoft.com> wrote in message
news:CD4E905C-F6B5-4B1F-A1F8-8D205580DB35@.microsoft.com...
> On the database server, when I try to connect my SQL Server registration,
> I
> get the error on the subject line. WHen I check my SQL Server Services
> using
> SQL Server Services Manager, I do not see my server name in the drop down
> box
> - I have to type it in. SQL Server Agent and server services are started.
> My
> jobs failed because of the error. I have never had to set up a DSN on the
> server to get a connection to the database. PLease help to resolve
>

Data source name not found and no default driver specified

Data source name not found and no default driver specified
This is the error I get when attempting to install my copy of SQL Server
2000 developer edition.
I had SQL Server installed on my workstation, functioning correctly. My
computer crashed and it appears that there is some sort of registry
corruption because I could not open up my local instance in Enterprise
Manager.
Checking ODBCAD32, it did not appear that I had any drivers installed for
any source (MS Access, standard ODBC, SQL Server, etc.)
I attempted to execute the MDAC on the Microsoft web site with no results.
The component Checker determined that I had MDAC 2.8 SP1 on Windows XP SP2.
I uninstalled and reinstalled SQL Server and on the final step, the above
message appeared.
How do I get the default SQL Server driver reinstalled to my workstation. My
network techs indicate that I have to reinstall my OS to get the drivers
back. This seems a little extreme.
Thank you in advance.
Any joy there ? I was demoing a client install of SQL 2000 when I
canceled it and "poof" all my ODBC drivers disappeared.
I had previously installed and removed SQL 2005 Beta, so the only option
I had was to re-install connectivity to SQL 2005 and use "SQL Native
Client"
It looks like a re-build.
I've seen a few posts like this but never any response.
yay.
In article <u8fOB7fFFHA.4016@.TK2MSFTNGP09.phx.gbl>,
sxcostanzo@.hotmail.com says...
> Data source name not found and no default driver specified
> This is the error I get when attempting to install my copy of SQL Server
> 2000 developer edition.
> I had SQL Server installed on my workstation, functioning correctly. My
> computer crashed and it appears that there is some sort of registry
> corruption because I could not open up my local instance in Enterprise
> Manager.
> Checking ODBCAD32, it did not appear that I had any drivers installed for
> any source (MS Access, standard ODBC, SQL Server, etc.)
> I attempted to execute the MDAC on the Microsoft web site with no results.
> The component Checker determined that I had MDAC 2.8 SP1 on Windows XP SP2.
> I uninstalled and reinstalled SQL Server and on the final step, the above
> message appeared.
> How do I get the default SQL Server driver reinstalled to my workstation. My
> network techs indicate that I have to reinstall my OS to get the drivers
> back. This seems a little extreme.
> Thank you in advance.
>
>

Data source name not found and no default driver specified

On the database server, when I try to connect my SQL Server registration, I
get the error on the subject line. WHen I check my SQL Server Services using
SQL Server Services Manager, I do not see my server name in the drop down box
- I have to type it in. SQL Server Agent and server services are started. My
jobs failed because of the error. I have never had to set up a DSN on the
server to get a connection to the database. PLease help to resolveHmmm...Is this a clean installation, an upgrade, etc...
Might be related (and I emphasize might) to MDAC. Check out:
http://support.microsoft.com/?kbid=301202
and
http://www.microsoft.com/downloads/details.aspx?FamilyID=6c050fe3-c795-4b7d-b037-185d0506396c&displaylang=en
HTH
Jerry
"spoons" <spoons@.discussions.microsoft.com> wrote in message
news:CD4E905C-F6B5-4B1F-A1F8-8D205580DB35@.microsoft.com...
> On the database server, when I try to connect my SQL Server registration,
> I
> get the error on the subject line. WHen I check my SQL Server Services
> using
> SQL Server Services Manager, I do not see my server name in the drop down
> box
> - I have to type it in. SQL Server Agent and server services are started.
> My
> jobs failed because of the error. I have never had to set up a DSN on the
> server to get a connection to the database. PLease help to resolve
>sql

Data source name not found and no default driver specified

Data source name not found and no default driver specified
This is the error I get when attempting to install my copy of SQL Server
2000 developer edition.
I had SQL Server installed on my workstation, functioning correctly. My
computer crashed and it appears that there is some sort of registry
corruption because I could not open up my local instance in Enterprise
Manager.
Checking ODBCAD32, it did not appear that I had any drivers installed for
any source (MS Access, standard ODBC, SQL Server, etc.)
I attempted to execute the MDAC on the Microsoft web site with no results.
The component Checker determined that I had MDAC 2.8 SP1 on Windows XP SP2.
I uninstalled and reinstalled SQL Server and on the final step, the above
message appeared.
How do I get the default SQL Server driver reinstalled to my workstation. My
network techs indicate that I have to reinstall my OS to get the drivers
back. This seems a little extreme.
Thank you in advance.Any joy there ? I was demoing a client install of SQL 2000 when I
canceled it and "poof" all my ODBC drivers disappeared.
I had previously installed and removed SQL 2005 Beta, so the only option
I had was to re-install connectivity to SQL 2005 and use "SQL Native
Client"
It looks like a re-build.
I've seen a few posts like this but never any response.
yay.
In article <u8fOB7fFFHA.4016@.TK2MSFTNGP09.phx.gbl>,
sxcostanzo@.hotmail.com says...
> Data source name not found and no default driver specified
> This is the error I get when attempting to install my copy of SQL Server
> 2000 developer edition.
> I had SQL Server installed on my workstation, functioning correctly. My
> computer crashed and it appears that there is some sort of registry
> corruption because I could not open up my local instance in Enterprise
> Manager.
> Checking ODBCAD32, it did not appear that I had any drivers installed for
> any source (MS Access, standard ODBC, SQL Server, etc.)
> I attempted to execute the MDAC on the Microsoft web site with no results.
> The component Checker determined that I had MDAC 2.8 SP1 on Windows XP SP2
.
> I uninstalled and reinstalled SQL Server and on the final step, the above
> message appeared.
> How do I get the default SQL Server driver reinstalled to my workstation.
My
> network techs indicate that I have to reinstall my OS to get the drivers
> back. This seems a little extreme.
> Thank you in advance.
>
>

Data source name not found and no default driver specified

On the database server, when I try to connect my SQL Server registration, I
get the error on the subject line. WHen I check my SQL Server Services using
SQL Server Services Manager, I do not see my server name in the drop down bo
x
- I have to type it in. SQL Server Agent and server services are started. My
jobs failed because of the error. I have never had to set up a DSN on the
server to get a connection to the database. PLease help to resolveHmmm...Is this a clean installation, an upgrade, etc...
Might be related (and I emphasize might) to MDAC. Check out:
http://support.microsoft.com/?kbid=301202
and
http://www.microsoft.com/downloads/...&displaylang=en
HTH
Jerry
"spoons" <spoons@.discussions.microsoft.com> wrote in message
news:CD4E905C-F6B5-4B1F-A1F8-8D205580DB35@.microsoft.com...
> On the database server, when I try to connect my SQL Server registration,
> I
> get the error on the subject line. WHen I check my SQL Server Services
> using
> SQL Server Services Manager, I do not see my server name in the drop down
> box
> - I have to type it in. SQL Server Agent and server services are started.
> My
> jobs failed because of the error. I have never had to set up a DSN on the
> server to get a connection to the database. PLease help to resolve
>

Data Source expression not working

Hello, I am trying to use a data source expression but I'm getting an error. Here is my data source expression:

="data source=" & Parameters!ServerName.Value & ";initial catalog=AdventureWorks"

I have created a report parameter called ServerName. However, when I deploy the report and report viewer opens, I get the following error:

An error has occurred during report processing. (rsProcessingAborted) Error during processing of the ConnectString expression of datasource ‘AdventureWorks’. (rsDataSourceConnectStringProcessingError)

Is there some really obvious step I am missing here? The relevant parts of my rdl are below.

Thanks in advance

<DataSources>

<DataSource Name="AdventureWorks">

<ConnectionProperties>

<ConnectString>="data source=" &amp; Parameters!ServerName.Value &amp; ";initial catalog=AdventureWorks"</ConnectString>

<DataProvider>SQL</DataProvider>

</ConnectionProperties>

<rdataSourceID>(some stuff here)</rdataSourceID>

</DataSource>

</DataSources>

...

<ReportParameters>

...

<ReportParameter Name="ServerName">

<DataType>String</DataType>

<Prompt>ServerName</Prompt>

</ReportParameter>

</ReportParameters>

Found the solution in another thread...

(quoting)

Very simple solution, it turns out... just make sure the ServerName and DBName parameters appear above all other parameters in the report definition.

Would be great if this msdn article were edited to mention that!

Data Source error?

Hey everyone,

Just wondering if anyone could answer a simple question for me. Here is a brief background on what I'm trying to do and my setup. I'm working with .net studio 2005 and Windows Mobile 2005. I'm just doing some testing with SQLCE for future projects that I plan to implement with it. I'm somewhat new to .net, however I have experience in VS6.0. I wrote a simple app that contains Data Binding and was attempting at Datasets on a Mobile device, but I ran across some error. However that error I'm not concerned with yet. The error that I'm concerned with is tring to implement the same project except connecting to a mobile database on the desktop. I created a database called Tech that is a mobile database sitting in MyDocuments. In the Server Explorer window the database shows that I'm connected to it. I can using Databinding just fine, however when I try to connect through code I get an error saying "Data Source not found". At first I thought maybe my connection string is wrong .. well I don't think it is. If I look at the project window Tech.sdf shows up but it looks as if the icon is a unknown file type. I don't think this would be the case being that DataBinding works however .. you never now. This is how I'm attempting to connect with out any trys and catches though.

Dim Conn As SqlServerCe.SqlCeConnection

Dim DA As SqlServerCe.SqlCeDataAdapter

Dim DS As New DataSet

Conn = New SqlServerCe.SqlCeConnection("Data Source = Tech.sdf")

DS = New SqlServerCe.SqlCeDataAdapter("Select * from User", Conn)

Conn.Open()

Nothing advance just tring to do a simple connection so that I can fill a DataSet. I have also tried placing the complete file path for the connection string with no luck. The DB has no password or anything. Just keeping it straight forward as possible while I try to conquer this learning curve. Any clue?

I know you might have tried a lot to get out of this problem. But this error simply means that it can not find the file Tech.sdf!

Please try to put Tech.sdf in the very root folder (\Tech.sdf) and try out that path!

Thanks,

Laxmi Narsimha Rao ORUGANTI, MSFT, SQL Mobile, Microsoft Corporation

|||

Thank you for the response, however I have already tried placing the complete path for the Data Source. I went ahead placed the file in the root directory also to see if that would work by chance, but no luck. I believe the problem exist becuase the .sdf is a unknown file type on my desktop or maybe the .sdf needs to be on the Device Emulator to work? I have used Virtual PC before and I'm not sure if the same concept applies with this Emulator where you have to copy the files over to that device. The Pocket PC 2003 Emulator seems to have it's on seperate files structure but I'm not sure where I can access this.

|||Figured it out. I needed to have the .sdf on the Emulator. There is a tool in the CE Remote Tools folder called ccfilevw that allows me to export a file to the Emulator. I'm not sure if there is a easier way or better way but this works.

data source error Login Failed

I am using Analysis Services and SQL 2000. On my Analysis Services machine I
define my data source to point to a remote SQL 2000 server using windows
authentication with my domain admin account. I can create the cube and
everything looks great but when I process the cube I get login errors. data
source provider error Login failed for user '\\domain\computer$' 42000.
Surely, this is an easy fix.
Thanks,
Kevin E.
Processing is actually done by the MSSQLServerOLAPService service
(msmdsrv.exe).
It is not based on your interactive credentials (like browsing, etc.)
You need to modify the service to use your domain account.
Dave Wickert [MSFT]
dwickert@.online.microsoft.com
Program Manager
BI SystemsTeam
SQL BI Product Unit (Analysis Services)
This posting is provided "AS IS" with no warranties, and confers no rights.
"KevinE" <eckart_612@.hotmail.com> wrote in message
news:i8Sdnbpqcc1h0hbfRVn-sA@.centurytel.net...
>I am using Analysis Services and SQL 2000. On my Analysis Services machine
>I define my data source to point to a remote SQL 2000 server using windows
>authentication with my domain admin account. I can create the cube and
>everything looks great but when I process the cube I get login errors.
>data source provider error Login failed for user '\\domain\computer$'
>42000. Surely, this is an easy fix.
> Thanks,
> Kevin E.
>
|||I'm having the same problem now... how do you modify this
MSSQLServerOLAPService service? thanks.
"Dave Wickert [MSFT]" wrote:

> Processing is actually done by the MSSQLServerOLAPService service
> (msmdsrv.exe).
> It is not based on your interactive credentials (like browsing, etc.)
> You need to modify the service to use your domain account.
> --
> Dave Wickert [MSFT]
> dwickert@.online.microsoft.com
> Program Manager
> BI SystemsTeam
> SQL BI Product Unit (Analysis Services)
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "KevinE" <eckart_612@.hotmail.com> wrote in message
> news:i8Sdnbpqcc1h0hbfRVn-sA@.centurytel.net...
>
>
|||Go into your services on the computer that is accessing the data source and
go to the properties of MSSQLServerOLAPService. In the login tab, change the
user from local system account to a domain level account.
KevinE.
"G. Kumar" <GKumar@.discussions.microsoft.com> wrote in message
news:607F313E-A43E-494C-B8F7-214C8320C013@.microsoft.com...[vbcol=seagreen]
> I'm having the same problem now... how do you modify this
> MSSQLServerOLAPService service? thanks.
> "Dave Wickert [MSFT]" wrote:

data source error Login Failed

I am using Analysis Services and SQL 2000. On my Analysis Services machine I
define my data source to point to a remote SQL 2000 server using windows
authentication with my domain admin account. I can create the cube and
everything looks great but when I process the cube I get login errors. data
source provider error Login failed for user '\\domain\computer$' 42000.
Surely, this is an easy fix.
Thanks,
Kevin E.Processing is actually done by the MSSQLServerOLAPService service
(msmdsrv.exe).
It is not based on your interactive credentials (like browsing, etc.)
You need to modify the service to use your domain account.
--
Dave Wickert [MSFT]
dwickert@.online.microsoft.com
Program Manager
BI SystemsTeam
SQL BI Product Unit (Analysis Services)
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"KevinE" <eckart_612@.hotmail.com> wrote in message
news:i8Sdnbpqcc1h0hbfRVn-sA@.centurytel.net...
>I am using Analysis Services and SQL 2000. On my Analysis Services machine
>I define my data source to point to a remote SQL 2000 server using windows
>authentication with my domain admin account. I can create the cube and
>everything looks great but when I process the cube I get login errors.
>data source provider error Login failed for user '\\domain\computer$'
>42000. Surely, this is an easy fix.
> Thanks,
> Kevin E.
>|||I'm having the same problem now... how do you modify this
MSSQLServerOLAPService service? thanks.
"Dave Wickert [MSFT]" wrote:

> Processing is actually done by the MSSQLServerOLAPService service
> (msmdsrv.exe).
> It is not based on your interactive credentials (like browsing, etc.)
> You need to modify the service to use your domain account.
> --
> Dave Wickert [MSFT]
> dwickert@.online.microsoft.com
> Program Manager
> BI SystemsTeam
> SQL BI Product Unit (Analysis Services)
> --
> This posting is provided "AS IS" with no warranties, and confers no rights
.
>
> "KevinE" <eckart_612@.hotmail.com> wrote in message
> news:i8Sdnbpqcc1h0hbfRVn-sA@.centurytel.net...
>
>|||Go into your services on the computer that is accessing the data source and
go to the properties of MSSQLServerOLAPService. In the login tab, change the
user from local system account to a domain level account.
KevinE.
"G. Kumar" <GKumar@.discussions.microsoft.com> wrote in message
news:607F313E-A43E-494C-B8F7-214C8320C013@.microsoft.com...[vbcol=seagreen]
> I'm having the same problem now... how do you modify this
> MSSQLServerOLAPService service? thanks.
> "Dave Wickert [MSFT]" wrote:
>

Data Source Error

When I click on a report, the following error occurs.
How should I resolve this matter?
ERROR:
An error has occurred during report processing.
Cannot create a connection to data source 'IPC_VISION_DEV'.
For more information about this error navigate to the report server on the
local server machine, or enable remote errorsAre you sure that the specified credentials for that data set are valid?|||Thanks!
However, the user did not have dbread/write on backend database.
Again, thanks!
"F. Dwarf" wrote:
> Are you sure that the specified credentials for that data set are valid?

data source connection error...

Guess this was already posted somewhere...
My connection string to connect to sybase: DRIVER={Sybase ASE ODBC
Driver};SRVR=<server_name>;DB=<db_name>
Data source type : ODBC
Works on the Designer but not on the server.
I get a system error 126 - specified driver could not be loaded.
?If its of interest to anybody, this problem was resolved once the MDAC
components were upgraded to 2.8.
"NU" <vidhuvaradan@.rediffmail.com> wrote in message
news:eW$MlA9ZEHA.3596@.tk2msftngp13.phx.gbl...
> Guess this was already posted somewhere...
> My connection string to connect to sybase: DRIVER={Sybase ASE ODBC
> Driver};SRVR=<server_name>;DB=<db_name>
> Data source type : ODBC
> Works on the Designer but not on the server.
> I get a system error 126 - specified driver could not be loaded.
> ?
>
>

Data Source / ODBC error

Hi all,

My replication of those SQL 2000 servers gave errors: Data source (11): General Network Error. Check your network documentation... and ODBC (08S01): Communication link failure. The replication was across the WAN. I don't know where to start to troubleshoot this problem. Please help!

Thanks in advance.

John

Communication link failure means some network or communication problem between the Publisher/Distributor and Subscriber. Check the connection between them. Try connecting to the other servers from each of the servers and ensure that you are able to connect and then retry the Sync.

Also note for any firewalls that need to be taken care of or if the ports are different or enabled.

See if the domains are different and if so ensure trust or use SQL authentication.

Also is this the first time the sync ran or it previously used to succeed?

|||

Hi,

This is not the first time the replication failed. It worked perfect before.

DNS is fine since I did check.

Since this is a site to site interconnected (site2site VPN across internet). Therefore, the domains are different.

It has failed several times a day.

I don't know if we have any testing tools for replication available so I can narrow down the problems and troubleshoot more efficiently.

thanks much for your help!!!

|||This mostly has to do with network connectivity then. For merge agent to run successfully, the connection needs to be established. Try rerunning it and see if it succeeds. Also see if there are any other external factors affecting the connection. Peak load, network flakiness, disconnects or downtime during certain periods of time etc.|||On the machine where the failure occurred, try creating a UDL file (create a new text document, then rename it to "test.udl"). Open the UDL file by double-clicking it, then try to establish a connection to your database using the same sorts of parameters (ie provider [SQL Server native / ODBC etc.], server name, login parameters). You can use this to narrow down the cause of the problem (eg. whether it's the DB provider, or a lack of connectivity which can be checked using other means such as a traceroute etc.).|||

Thanks much. I will implement this method. In the meantime, is the packet from replication UDP or TCP when it is sent to the subcribed machine from distributed machine. I have thought my network is being flooding at the switch before data reached the nodes of the cluster. Therefore, it is redirected elsewhere but the destination. What I did was trying to send data from host inside network through that switch to the gateway...and I was only successful 35%. This means packets drops no matter incoming or outgoing through that switch.

Having some methods to test the replication directly will help a lot.

Thanks for your helps, guys.

|||Doesn't UDP run on top of TCP, hence they're both going to be TCP? Also, it'd depend on whether you've got the IIS machine on the Publisher machine, the Subscriber machine, or another machine?
Also try playing around with the configuration of the Client/Server Network Protocol - if you're having problems using TCP/IP, then try using Named Pipes instead. Make sure to configure this on both the publisher and subscriber machine.|||

Problem Fixed, Guys. It was just network problem. The Fixwall is misconfigured so that it operated half duplex instead of full. There Ain't nothin to do with the replication!!!

However, I have to deal with new problem......queue reader failed with the error message: Queue reader aborting. The steps failed. What does it mean? Where should I start to troubleshoot this error?

Thanks a lot!

|||Is there anything more helpful in the Event log?|||What I 've got is Failed while applying queued message to publisher!|||

I'm not an expert in SQL Server replication, so I can't help you more with your specific error (I've just recently spent a few days reading lots about SQL Mobile replication, hence the reason I came across your post).

If I was in your position, however, I'd start by getting everything working on on one box (even if it's just a staging box), and once it all works, you can move bit by bit elsewhere (eg. Publisher DB / IIS virtual dir / IIS server / Subscriber DB).

As you try to move things bit by bit you'll realise where the problem is. Sometimes the 'longest' way is the shortest because by being systematic, you don't end up pulling your hair out looking at something that 'should work', but doesn't!

|||

Oh, by the way, if you can't get it to work, I suggest starting a new thread, because some people will see this thread as answered, and not read it.

Cheers.

sql

Data Source / ODBC error

Hi all,

My replication of those SQL 2000 servers gave errors: Data source (11): General Network Error. Check your network documentation... and ODBC (08S01): Communication link failure. The replication was across the WAN. I don't know where to start to troubleshoot this problem. Please help!

Thanks in advance.

John

Communication link failure means some network or communication problem between the Publisher/Distributor and Subscriber. Check the connection between them. Try connecting to the other servers from each of the servers and ensure that you are able to connect and then retry the Sync.

Also note for any firewalls that need to be taken care of or if the ports are different or enabled.

See if the domains are different and if so ensure trust or use SQL authentication.

Also is this the first time the sync ran or it previously used to succeed?

|||

Hi,

This is not the first time the replication failed. It worked perfect before.

DNS is fine since I did check.

Since this is a site to site interconnected (site2site VPN across internet). Therefore, the domains are different.

It has failed several times a day.

I don't know if we have any testing tools for replication available so I can narrow down the problems and troubleshoot more efficiently.

thanks much for your help!!!

|||This mostly has to do with network connectivity then. For merge agent to run successfully, the connection needs to be established. Try rerunning it and see if it succeeds. Also see if there are any other external factors affecting the connection. Peak load, network flakiness, disconnects or downtime during certain periods of time etc.|||On the machine where the failure occurred, try creating a UDL file

(create a new text document, then rename it to "test.udl"). Open the

UDL file by double-clicking it, then try to establish a connection to

your database using the same sorts of parameters (ie provider [SQL

Server native / ODBC etc.], server name, login parameters). You can use

this to narrow down the cause of the problem (eg. whether it's the DB

provider, or a lack of connectivity which can be checked using other

means such as a traceroute etc.).|||

Thanks much. I will implement this method. In the meantime, is the packet from replication UDP or TCP when it is sent to the subcribed machine from distributed machine. I have thought my network is being flooding at the switch before data reached the nodes of the cluster. Therefore, it is redirected elsewhere but the destination. What I did was trying to send data from host inside network through that switch to the gateway...and I was only successful 35%. This means packets drops no matter incoming or outgoing through that switch.

Having some methods to test the replication directly will help a lot.

Thanks for your helps, guys.

|||Doesn't UDP run on top of TCP, hence they're both going to be TCP?

Also, it'd depend on whether you've got the IIS machine on the

Publisher machine, the Subscriber machine, or another machine?

Also try playing around with the configuration of the Client/Server

Network Protocol - if you're having problems using TCP/IP, then try

using Named Pipes instead. Make sure to configure this on both the

publisher and subscriber machine.|||

Problem Fixed, Guys. It was just network problem. The Fixwall is misconfigured so that it operated half duplex instead of full. There Ain't nothin to do with the replication!!!

However, I have to deal with new problem......queue reader failed with the error message: Queue reader aborting. The steps failed. What does it mean? Where should I start to troubleshoot this error?

Thanks a lot!

|||Is there anything more helpful in the Event log?|||What I 've got is Failed while applying queued message to publisher!|||

I'm not an expert in SQL Server replication, so I can't help you more with your specific error (I've just recently spent a few days reading lots about SQL Mobile replication, hence the reason I came across your post).

If I was in your position, however, I'd start by getting everything working on on one box (even if it's just a staging box), and once it all works, you can move bit by bit elsewhere (eg. Publisher DB / IIS virtual dir / IIS server / Subscriber DB).

As you try to move things bit by bit you'll realise where the problem is. Sometimes the 'longest' way is the shortest because by being systematic, you don't end up pulling your hair out looking at something that 'should work', but doesn't!

|||

Oh, by the way, if you can't get it to work, I suggest starting a new thread, because some people will see this thread as answered, and not read it.

Cheers.

Data Source / ODBC error

Hi all,

My replication of those SQL 2000 servers gave errors: Data source (11): General Network Error. Check your network documentation... and ODBC (08S01): Communication link failure. The replication was across the WAN. I don't know where to start to troubleshoot this problem. Please help!

Thanks in advance.

John

Communication link failure means some network or communication problem between the Publisher/Distributor and Subscriber. Check the connection between them. Try connecting to the other servers from each of the servers and ensure that you are able to connect and then retry the Sync.

Also note for any firewalls that need to be taken care of or if the ports are different or enabled.

See if the domains are different and if so ensure trust or use SQL authentication.

Also is this the first time the sync ran or it previously used to succeed?

|||

Hi,

This is not the first time the replication failed. It worked perfect before.

DNS is fine since I did check.

Since this is a site to site interconnected (site2site VPN across internet). Therefore, the domains are different.

It has failed several times a day.

I don't know if we have any testing tools for replication available so I can narrow down the problems and troubleshoot more efficiently.

thanks much for your help!!!

|||This mostly has to do with network connectivity then. For merge agent to run successfully, the connection needs to be established. Try rerunning it and see if it succeeds. Also see if there are any other external factors affecting the connection. Peak load, network flakiness, disconnects or downtime during certain periods of time etc.|||On the machine where the failure occurred, try creating a UDL file

(create a new text document, then rename it to "test.udl"). Open the

UDL file by double-clicking it, then try to establish a connection to

your database using the same sorts of parameters (ie provider [SQL

Server native / ODBC etc.], server name, login parameters). You can use

this to narrow down the cause of the problem (eg. whether it's the DB

provider, or a lack of connectivity which can be checked using other

means such as a traceroute etc.).|||

Thanks much. I will implement this method. In the meantime, is the packet from replication UDP or TCP when it is sent to the subcribed machine from distributed machine. I have thought my network is being flooding at the switch before data reached the nodes of the cluster. Therefore, it is redirected elsewhere but the destination. What I did was trying to send data from host inside network through that switch to the gateway...and I was only successful 35%. This means packets drops no matter incoming or outgoing through that switch.

Having some methods to test the replication directly will help a lot.

Thanks for your helps, guys.

|||Doesn't UDP run on top of TCP, hence they're both going to be TCP?

Also, it'd depend on whether you've got the IIS machine on the

Publisher machine, the Subscriber machine, or another machine?

Also try playing around with the configuration of the Client/Server

Network Protocol - if you're having problems using TCP/IP, then try

using Named Pipes instead. Make sure to configure this on both the

publisher and subscriber machine.|||

Problem Fixed, Guys. It was just network problem. The Fixwall is misconfigured so that it operated half duplex instead of full. There Ain't nothin to do with the replication!!!

However, I have to deal with new problem......queue reader failed with the error message: Queue reader aborting. The steps failed. What does it mean? Where should I start to troubleshoot this error?

Thanks a lot!

|||Is there anything more helpful in the Event log?|||What I 've got is Failed while applying queued message to publisher!|||

I'm not an expert in SQL Server replication, so I can't help you more with your specific error (I've just recently spent a few days reading lots about SQL Mobile replication, hence the reason I came across your post).

If I was in your position, however, I'd start by getting everything working on on one box (even if it's just a staging box), and once it all works, you can move bit by bit elsewhere (eg. Publisher DB / IIS virtual dir / IIS server / Subscriber DB).

As you try to move things bit by bit you'll realise where the problem is. Sometimes the 'longest' way is the shortest because by being systematic, you don't end up pulling your hair out looking at something that 'should work', but doesn't!

|||

Oh, by the way, if you can't get it to work, I suggest starting a new thread, because some people will see this thread as answered, and not read it.

Cheers.

Data Set returns but Report doesn't display

I'm returning a data set from a stored procedure. When I go to preview the
report I'm getting an error: An error has occured during report processing.
Invalid attempt to read when no data is present. I made a minor change
(added a parameter) to the stored procedure that wouldn't impact the data set
being returned and the data set returns. The report parameter is set up
correctly in the report but is not displayed anywhere on the report. The
build succeeded. Does this error mean I need to drag & drop my fields back
onto the report layout again?I was able to fix this issue. Re-ran the stored procedure and then re-added
all of the fields. For some reason it didn't want to work when I tried it
before.
"patty" wrote:
> I'm returning a data set from a stored procedure. When I go to preview the
> report I'm getting an error: An error has occured during report processing.
> Invalid attempt to read when no data is present. I made a minor change
> (added a parameter) to the stored procedure that wouldn't impact the data set
> being returned and the data set returns. The report parameter is set up
> correctly in the report but is not displayed anywhere on the report. The
> build succeeded. Does this error mean I need to drag & drop my fields back
> onto the report layout again?