cannot P/Invoke SQLCEME30.DLL when debugging Pocket PC 2003 SE Emulator

I'm trying to debug an assembly with System.Data.SqlServerCe - and when I deploy to a IPAQ 2210 - I get no errors! Alas, when I try to debug using the Pocket PC 2003 SE Emulator - I get the "cannot P/Invoke SQLCEME30.DLL" exception.

Can anyone offer directions?

best regards,
Walther

wDiechmann wrote:

I'm trying to debug an assembly with System.Data.SqlServerCe - and when I deploy to a IPAQ 2210 - I get no errors! Alas, when I try to debug using the Pocket PC 2003 SE Emulator - I get the "cannot P/Invoke SQLCEME30.DLL" exception.

Can anyone offer directions?

best regards,
Walther

I tried with a SmallTestProject having nothing except statements to create new "test.sdf" and my take on this is: you cannot debug solutions for smart devices aka Pocket PC 2003 in VS2005, if you want to use the emulator!

Please someone prove me wrong!

a nice weekend from sunny Denmark,
Walther|||

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=604751&SiteID=1

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=438553&SiteID=1

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=220816&SiteID=1

|||So are you meant to install the SQLMobile CAB file on the emulator? How will it know that you unstalled the CAB file the last time you loaded up the emulator?

I don't undertstand this.|||

I'm not sure what exactly you do not understand.

You copy the CAB, you click on it - it's now installed. If you save emulator state, it would remain installed. If you don't save the emulator's state - it's all gone on restart, repeat the installation every time emulator is started (or save state).

|||Ahh, right, get you now :)

I didn't know the Emulator state saved things like that (installation of things) :)

I'm guessing that each device model/version has its own emulator state?|||Ilya Tumanov,

I'm afraid I do not see where you're taking me on this!

I debug my apps perfectly allright on the device - but I'm not able to debug apps using the emulator (where no device is involved - just my desktop)

The links you threw my way all talk about copying CABs to the device - but I'm not debugging on the device. I'm debugging on the emulator!?

Sorry if my english is not fluently enough to present my case properly :(

best regards,
Walther|||OK, Walther, judging by what Ilya as stated, you need to install the SQL CAB's onto the Emulator.

To do this, in VS 2005 go to 'Tools'->'Device Emulator Manager', then in the available Emulators select the Emulator you need then go to 'Actions'->'Connect' (wait for Green tick next to Emulator). Then in the Emulator Window go to 'File'->'Configure', then under the 'General' tab in the 'Shared Folder', click the '...' button. Locate to the Bin/debug directory of your application, and ok that. In this directory you should have placed your SQL CAB files.

Now in the Emulator, click 'Start'->'Programs'->'File Explorer'->'My Device'->'Storage Card' - in here should be your CAB files, click on them to install them. Remember to save the Emulator state.

Ilya, is this the correct way of doing it, or is there an easier way?

Thanks
|||

Normally VS 2005 would install NETCF and SQL Mobile automatically as soon as you hit F5. If for some reason that does not work, then installation via mapped folder should work.

As device vs. emulator, there's no difference in this case. You see, emulator is a device, only simulated. You can even Active Sync it if you want in copy files via AS just like you would do with physical device.

cannot P/Invoke SQLCEME30.DLL when debugging Pocket PC 2003 SE Emulator

I'm trying to debug an assembly with System.Data.SqlServerCe - and when I deploy to a IPAQ 2210 - I get no errors! Alas, when I try to debug using the Pocket PC 2003 SE Emulator - I get the "cannot P/Invoke SQLCEME30.DLL" exception.

Can anyone offer directions?

best regards,
Walther

wDiechmann wrote:

I'm trying to debug an assembly with System.Data.SqlServerCe - and when I deploy to a IPAQ 2210 - I get no errors! Alas, when I try to debug using the Pocket PC 2003 SE Emulator - I get the "cannot P/Invoke SQLCEME30.DLL" exception.

Can anyone offer directions?

best regards,
Walther

I tried with a SmallTestProject havingnothing except statements to create new "test.sdf" and my take on this is: you cannot debug solutions for smart devices aka Pocket PC 2003 in VS2005, if you want to use the emulator!

Please someone prove me wrong!

a nice weekend from sunny Denmark,
Walther
|||

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=604751&SiteID=1

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=438553&SiteID=1

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=220816&SiteID=1

|||So are you meant to install the SQLMobile CAB file on the emulator? How will it know that you unstalled the CAB file the last time you loaded up the emulator?

I don't undertstand this.|||

I'm not sure what exactly you do not understand.

You copy the CAB, you click on it - it's now installed. If you save emulator state, it would remain installed. If you don't save the emulator's state - it's all gone on restart, repeat the installation every time emulator is started (or save state).

|||Ahh, right, get you now :)

I didn't know the Emulator state saved things like that (installation of things) :)

I'm guessing that each device model/version has its own emulator state?|||Ilya Tumanov,

I'm afraid I do not see where you're taking me on this!

I debug my apps perfectly allright on the device - but I'm not able to debug apps using the emulator (where no device is involved - just my desktop)

The links you threw my way all talk about copying CABs to the device - but I'm not debugging on the device. I'm debugging on the emulator!?

Sorry if my english is not fluently enough to present my case properly :(

best regards,
Walther
|||OK, Walther, judging by whatIlya as stated, you need to install the SQL CAB's onto the Emulator.

To do this, in VS 2005 go to 'Tools'->'Device Emulator Manager', then in the available Emulators select the Emulator you need then go to 'Actions'->'Connect' (wait for Green tick next to Emulator). Then in the Emulator Window go to 'File'->'Configure', then under the 'General' tab in the 'Shared Folder', click the '...' button. Locate to the Bin/debug directory of your application, and ok that. In this directory you should have placed your SQL CAB files.

Now in the Emulator, click 'Start'->'Programs'->'File Explorer'->'My Device'->'Storage Card' - in here should be your CAB files, click on them to install them. Remember to save the Emulator state.

Ilya, is this the correct way of doing it, or is there an easier way?

Thanks
|||

Normally VS 2005 would install NETCF and SQL Mobile automatically as soon as you hit F5. If for some reason that does not work, then installation via mapped folder should work.

As device vs. emulator, there's no difference in this case. You see, emulator is a device, only simulated. You can even Active Sync it if you want in copy files via AS just like you would do with physical device.

Cannot open a connection

I am using reporing services in my c# web application. When I debug my web
application, the reporting section show me the following error: "The report
server cannot open a connection to the report server database. A connection
to the database is required for all requests and processing.
(rsReportServerDatabaseUnavailable) SQL Server does not exist or access
denied". Then it show me the following warning: "An unhandled exception of
type
'Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerDatabaseUnavailableException' occurred in microsoft.reportingservices.diagnostics.dll
Additional information: The report server cannot open a connection to the
report server database. A connection to the database is required for all
requests and processing."
Any ideas?
Thanks in advance.First thing is to make sure the report works outside of your application.
Have you tried the report from Report Manager, does it work from there?
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"mlugoc" <mlugoc@.discussions.microsoft.com> wrote in message
news:A33D1D4C-7E66-4A8F-93F3-06293284BFD6@.microsoft.com...
>I am using reporing services in my c# web application. When I debug my web
> application, the reporting section show me the following error: "The
> report
> server cannot open a connection to the report server database. A
> connection
> to the database is required for all requests and processing.
> (rsReportServerDatabaseUnavailable) SQL Server does not exist or access
> denied". Then it show me the following warning: "An unhandled exception
> of
> type
> 'Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerDatabaseUnavailableException'
> occurred in microsoft.reportingservices.diagnostics.dll
> Additional information: The report server cannot open a connection to the
> report server database. A connection to the database is required for all
> requests and processing."
> Any ideas?
> Thanks in advance.
>|||Yes, I used Report Manager to test my report and it works great.
"Bruce L-C [MVP]" wrote:
> First thing is to make sure the report works outside of your application.
> Have you tried the report from Report Manager, does it work from there?
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "mlugoc" <mlugoc@.discussions.microsoft.com> wrote in message
> news:A33D1D4C-7E66-4A8F-93F3-06293284BFD6@.microsoft.com...
> >I am using reporing services in my c# web application. When I debug my web
> > application, the reporting section show me the following error: "The
> > report
> > server cannot open a connection to the report server database. A
> > connection
> > to the database is required for all requests and processing.
> > (rsReportServerDatabaseUnavailable) SQL Server does not exist or access
> > denied". Then it show me the following warning: "An unhandled exception
> > of
> > type
> > 'Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerDatabaseUnavailableException'
> > occurred in microsoft.reportingservices.diagnostics.dll
> >
> > Additional information: The report server cannot open a connection to the
> > report server database. A connection to the database is required for all
> > requests and processing."
> >
> > Any ideas?
> > Thanks in advance.
> >
> >
>
>