Can't find PInvoke DLL 'sqlceme30.dll'

I am developing for an ipaq handheld. I just upgraded to Windows Mobile 5.0 and tried to run my application and I get this message.

Can't find PInvoke DLL 'sqlceme30.dll'

I am using a sql Mobile DB and vs2005
found fix here: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=220816&SiteID=1
sql

Cant find error

I am developing a new report in VS 2005 with Reporting Services 2005
installed. I go to preview the report, and I get this:
"The definition of report blah is invalid. An internal error occurred on
the report server. See the error log for more details."
I have been looking everywhere for these error logs, and cant seem to find
one. I have checked my local event viewer and program files\mssql.3\logs, as
well as the remote Sql Server's event logs, rs logs, etc.
All the docs on Google point me to where the web server keeps their logs at
, but I am just tryign to preview a dev version locally.
Any help would be greatly appreciated.
thanks!On Aug 20, 4:50 pm, Carl Henthorn
<CarlHenth...@.discussions.microsoft.com> wrote:
> I am developing a new report in VS 2005 with Reporting Services 2005
> installed. I go to preview the report, and I get this:
> "The definition of report blah is invalid. An internal error occurred on
> the report server. See the error log for more details."
> I have been looking everywhere for these error logs, and cant seem to find
> one. I have checked my local event viewer and program files\mssql.3\logs, as
> well as the remote Sql Server's event logs, rs logs, etc.
> All the docs on Google point me to where the web server keeps their logs at
> , but I am just tryign to preview a dev version locally.
> Any help would be greatly appreciated.
> thanks!
In general, this is a very vague error. If you can remember the last
thing you changed before you got the error, that's the first place to
start. Also, depending on the number of SQL Services you have
installed (i.e., SSRS, SSIS, SSAS), it could be located in a different
MSSQL. directory. On my local machine, the SSRS logs are located in
the following location:
C:\Program Files\Microsoft SQL Server\MSSQL.2\Reporting Services
\LogFiles
Hope this is helpful.
Regards,
Enrique Martinez
Sr. Software Consultant

Can't export report to CSV,XMl correctly, sql 2005 reporting service

Hi all,

I am developing reports using sql2005 report service. I can export reports in excel and pdf format, but can't export to csv and xml correctly.

The exported csv and xml files only contain some thing like the textbox,..., but no report content are there.

Anybody can help? thanks in advance.

BTW, all reports are matrix, is martrix can cause some issues?

Hi,

For most items on your report, you can define how it needs to be rendered to XML. For example the xml output for an item in a matrix can be set as follow:

select the item in the matrix|||

Thanks, Greert.

Your reply is really helpful. Now I know how to export report in xml format. But, how about CSV? I still can't export report to csv.

Thanks again

|||

Hi,

The same goes for CSV. For example if you set the Output of a column to No, you will see that the column is not included in the CSV file.

Greetz,

Geert

Geert Verhoeven
Consultant @. Ausy Belgium

My Personal Blog

|||Hi Geert,

Thanks a lot.

When I set th output of a column to yes, it works. Before, the the output of column was set to Auto.

Can't connection to SQL 2000 on Windows 2003 from web application running on windows x

I'm developing a web application that is running locally on my Windows XP PC
. It connects to remote database server which sits on a Windows 2003 server.
When i try to open the connection, i recieve an error, "SQL Server does not
exist or access denied". I
know for fact this connection string works, because I can use the same conne
ction string in a console application, and retrieve data. So far I have esta
blished the following:
-- I can connect to the DB via all client applications (query analyzer, .net
console appliation etc.), except from .net web application.
-- Other developers running windows 2003 and II6 can connect to DB using the
same configuration.
-- Developers, like myself, running on XP and IIS 5.1 can NOT connect.
-- from the .net web application I can connect to SQL servers that reside on
Windows 2000 server.
thanksThanks for posting what you've tried:
This helps enormously. <g>
-- I can connect to the DB via all client applications (query analyzer,
.net console appliation etc.), except from .net web application.
-- Other developers running windows 2003 and II6 can connect to DB using
the same configuration.
-- Developers, like myself, running on XP and IIS 5.1 can NOT connect.
-- from the .net web application I can connect to SQL servers that reside
on Windows 2000 serv
So, what's missing here is what security context or that your web
application is using and what security mode
IIS is in.
Are you running the IIS site in Annony, Basic or Windows Auth ?
Are you attempting to connect to SQL from IIS using an account with
username & password or
with a Trusted Connection?
Does the .NET app attempt to Impersonate?
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||Kevin,
thank you for the reply. The settings on the IIS and the web application are
fairly generic, I believe I'm using all the default values for configuratio
n.

>Are you running the IIS site in Annony, Basic or Windows Auth ?
Annonymous access is enable on the IIS.

>Are you attempting to connect to SQL from IIS using an account with
username & password or with a Trusted Connection?
I'm using an SQL account with username and password to connect to the DB

>Does the .NET app attempt to Impersonate?
there is no impersonation involved.
-- Kevin McDonnell [MSFT] wrote: --
Thanks for posting what you've tried:
This helps enormously. <g>
-- I can connect to the DB via all client applications (query analyzer,
.net console appliation etc.), except from .net web application.
-- Other developers running windows 2003 and II6 can connect to DB using
the same configuration.
-- Developers, like myself, running on XP and IIS 5.1 can NOT connect.
-- from the .net web application I can connect to SQL servers that reside
on Windows 2000 serv
So, what's missing here is what security context or that your web
application is using and what security mode
IIS is in.
Are you running the IIS site in Annony, Basic or Windows Auth ?
Are you attempting to connect to SQL from IIS using an account with
username & password or
with a Trusted Connection?
Does the .NET app attempt to Impersonate?
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||it turns out, to resolve the issue, we just needed to install sp3 a couple o
f times on the SQL server.|||Hi,
I'm having the same problem. And these are mine settings:
Q: Are you running the IIS site in Annony, Basic or Windows Auth ?
A: I'm using FORMS-authentification (web.config)
Q: Are you attempting to connect to SQL from IIS using an account with usern
ame & password or with a Trusted Connection?
A: I want to connect throug username and password
Q: Does the .NET app attempt to Impersonate?
A: As far as i know i don't.
I hope u can explain me the problem.
Thanx Bram
Posted using Wimdows.net NntpNews Component -
Post Made from http://www.SqlJunkies.com/newsgroups Our newsgroup engine sup
ports Post Alerts, Ratings, and Searching.

Cant connect to SQL server 2000 instance from domain machines

Hi
We currently have installed sql2005 (installed first as default
instance) and sql 2000 with a named instance. When developing sites
and using connection strings, we can access the sql2000 db fine by
using SERVERNAME\INSTANCENAME.
However, if we try to connect via enterprise manager from any other
machine on the domain, we cannot seem to use SERVERNAME\INSTANCENAME
and the instance name alone wont work either.
How do we get round this as at present, we are having to log into the
database server to make any changes etc!!!
Novice here so excuse me if I have missed anything obvious!
Cheers
RajThe easiest workaround would be to connect to the instance using its IP
address followed by a comma and then the port number. You should not use just
hte instance name alone. The SQL Server instance name is not a newtwork name
and won't get resolved to an IP/port number.
Can you connect to the default instance (SQL2005) from a machine where you
can't connect to the SQL2000 instance using ServerName\Instance?
Linchi
"karwalr@.hotmail.com" wrote:
> Hi
> We currently have installed sql2005 (installed first as default
> instance) and sql 2000 with a named instance. When developing sites
> and using connection strings, we can access the sql2000 db fine by
> using SERVERNAME\INSTANCENAME.
> However, if we try to connect via enterprise manager from any other
> machine on the domain, we cannot seem to use SERVERNAME\INSTANCENAME
> and the instance name alone wont work either.
> How do we get round this as at present, we are having to log into the
> database server to make any changes etc!!!
> Novice here so excuse me if I have missed anything obvious!
> Cheers
> Raj
>|||Managed to sort it. I set it up on my client machine Client Network
Alias to map to the server and the port as suggested. Found the
documentation at Microsoft..
http://support.microsoft.com/kb/265808/en-us
Many thanks!

Cant connect to SQL server 2000 instance from domain machines

Hi
We currently have installed sql2005 (installed first as default
instance) and sql 2000 with a named instance. When developing sites
and using connection strings, we can access the sql2000 db fine by
using SERVERNAME\INSTANCENAME.
However, if we try to connect via enterprise manager from any other
machine on the domain, we cannot seem to use SERVERNAME\INSTANCENAME
and the instance name alone wont work either.
How do we get round this as at present, we are having to log into the
database server to make any changes etc!!!
Novice here so excuse me if I have missed anything obvious!
Cheers
RajThe easiest workaround would be to connect to the instance using its IP
address followed by a comma and then the port number. You should not use jus
t
hte instance name alone. The SQL Server instance name is not a newtwork name
and won't get resolved to an IP/port number.
Can you connect to the default instance (SQL2005) from a machine where you
can't connect to the SQL2000 instance using ServerName\Instance?
Linchi
"karwalr@.hotmail.com" wrote:

> Hi
> We currently have installed sql2005 (installed first as default
> instance) and sql 2000 with a named instance. When developing sites
> and using connection strings, we can access the sql2000 db fine by
> using SERVERNAME\INSTANCENAME.
> However, if we try to connect via enterprise manager from any other
> machine on the domain, we cannot seem to use SERVERNAME\INSTANCENAME
> and the instance name alone wont work either.
> How do we get round this as at present, we are having to log into the
> database server to make any changes etc!!!
> Novice here so excuse me if I have missed anything obvious!
> Cheers
> Raj
>|||Managed to sort it. I set it up on my client machine Client Network
Alias to map to the server and the port as suggested. Found the
documentation at Microsoft..
http://support.microsoft.com/kb/265808/en-us
Many thanks!

Cant connect to membership provider db

I've started developing an ASP.net 2.0 app with VWD Express.

The default membership provider db of SQL Server 5005 Express is not installed on my host servers. So my workaround has been to use a Full blown SQL Server 2005 DB as a custom membership provider declared in web.config.

This works fine on the production server. However, when i try to login from my development app I get Exception # 40 can't connect to SQL server membership provider.. Moreover, my app configuration confirms there is problems connecting to this server in my development environment.

How can I solve this and bring my development app up & running again?

many thanks

If you have access to your Production SQL Server from your development environment, the problem is probably due to your connection string.

For my development, I use SQL Express on my local development box and SQL Server for production. There are two things that you have to do. Keeps separate scripts for changes to the database (from development to production). In addition, a separate web.config for production and development to hold your connection strings.

Cant connect to database

I am developing my first website for my boss. I am trying to connect to an access database which I have created a DSN for on the server. I am using the following code sample...

//Connection String 1

string dsn_name ="access_WALLINVEN.dsn";

string sDSNDir = Server.MapPath("_dsn");

string connectstr = ("Data Source="

+ (sDSNDir + ("\\" + dsn_name)));

//Connection String 2

string connectstr ="Data Source=/jwallpaint/_dsn/access_WALLINVEN.dsn;Uid=jwallpaint;Pwd=J2512wall;";

string commandString ="Select * from Inventory";

//Pass strings to sqlDataAdapter constructor

SqlDataAdapter dataAdapter =newSqlDataAdapter(commandString, connectstr);

//Create a dataset

DataSet dataSet =newDataSet();

//fill the dataset object

dataAdapter.Fill(dataSet,"Inventory");

//Get the table from the dataset

DataTable dataTable = dataSet.Tables["Inventory"];

//Bind to the gridview

GridView1.DataSource = dataTable;

GridView1.DataBind();

For Connection String 1 I get the error of...

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)

For Connection String 2 I get the error of...

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)

I am not sure which connection string to use either...

It is strange to me that I get this error talking about SQL Server when I am trying to reach my Access database.....Any Help?? Thanks...

Connection string forFile DSN:

"FILEDSN=c:\myData.dsn;Uid=myUsername;Pwd=;"

Checkhttp://www.connectionstrings.com/ for more connection strings.

Cant connect to any database not owned by servername\ASPNET

I'm developing an intranet application and am using the Express versions of VWD and SQL Server 2005 for initial development before obtaining full licensed versions.

Database connections work fine when testing from within VWD but when testing from browser, unless the database owner is the IIS servername\ASPNET, there are various errors depending on the specific connection settings, i.e.

Login failed for user ''. The user is not associated with a trusted SQL Server connection.-

Receive this error when a GridView is connected to a remote SSE db.

--

SELECT permission denied on object 'Table_1', database 'TEST', schema 'dbo'.

Receive this error when GridView is connected to local SSE db not owned by servername\ASPNET.

--

Failed to generate a user instance of SQL Server due to a failure in starting the process for the user instance. The connection will be closed.

This happens when using any control that is connected to SSE db created in VWD and stored in App_Data folder (owner is the user logon name)

--

Any help or ideas would be appreciated. I want to have all local data stored in App_Data folder.

Thank you.

You need to set SQL Server to use both Windows and SQL Server, that is covered below. Post again if you still need help.

http://msdn2.microsoft.com/en-us/library/ms188670.aspx