Datatype problem: development vs production servers

This is driving me nuts: On my development machine the code runs finebut generates an error on the production server. Both are running SQLServer 2000 and ASP.NET 1.1

The datatype of the field in question isdatetime.
The webform has a calendar for a user to select and automaticallyinsert the date into the textbox. The update command in the webform is:
cmdInsert.Parameters.Add("@.citation_date", CDate(txtDate.Text))

This works without a hitch on my development system, but on the production server it generates the following error:
Cast from string "19-12-1997" to type 'Date' is not valid.

WHY?
It has to do with the locale information (country, language, etc.) for the computer. Check to make sure the server is set to whatever you're using on your local development PC. I'm not familiar with setting/changing these since I only use U.S. format and English.|||

jcasp wrote:

It has to do with the locale information (country,language, etc.) for the computer. Check to make sure the serveris set to whatever you're using on your local development PC. I'mnot familiar with setting/changing these since I only use U.S. formatand English.

You are right. I'm inputting U.S format of date for the time being until I've figured a way around it. Thanks!|||Use YYYY-MM-DD format, then it doesn't matter what culture you are in.

datasource connection error

have developed a report on a test windows server machine in SSRS 2005 which
I can access from i./e. http://localhost/reports
DataSourcce is accessed using a sql login
My colleague on his machine can not access. His error is:
An error has occurred during report processing. (rsProcessingAborted)
Cannot create a connection to data source 'MarketAnalytics'.
(rsErrorOpeningConnection)
For more information about this error navigate to the report server on the
local server machine, or enable remote errorsCheck the SRS error logs they should have a better error for you. They can be
found in: C:\Program Files\Microsoft SQL Server\MSSQL.#\Reporting
Services\LogFiles.
--
SQL Server Developer Support Engineer
"arkiboys2" wrote:
> have developed a report on a test windows server machine in SSRS 2005 which
> I can access from i./e. http://localhost/reports
> DataSourcce is accessed using a sql login
> My colleague on his machine can not access. His error is:
> An error has occurred during report processing. (rsProcessingAborted)
> Cannot create a connection to data source 'MarketAnalytics'.
> (rsErrorOpeningConnection)
> For more information about this error navigate to the report server on the
> local server machine, or enable remote errors
>

Databases folder empty in Enterprise Manager

Hi all,
I have installed MSDE 2000 SP3a on a workstation, as well as SQL Server
client tools on the same machine. When I open Enterprise Manager, the
Databases folder is empty. Even the master database plus other default
databases (msdb, ...) are not shown. I have made sure the "show system
databases and objects" setting is checked. This happens whether I
connect to the MSDE server using the sa account or Windows
authentication. Also the Query Analyzer utility doesn't work as well.
It opens, but the command window has no place to type SQL commands, and
the Object Browser doesn't show any databases.
I also have a number of old databases (.mdf and .ldf files) that I want
to attach to this instance. These databases have been originally
copied from another machine, and have been working on this machine with
a previous installation of SQL Server Personal Edition. When I open
the attach databases window in Enterprise Manager, and select a mdf
file, and click OK, at first nothing happens (no feedback, and the
dialog even doesn't go away) but clicking OK a second time gives an
error message stating that a database with the same name already exists
(and yet the dialog remains open.) Any further actions will take
Enterprise Manager down by a crash.
Then I tried connecting to MSDE using osql.exe, and a "USE master;
SELECT * FROM sysdatabases;" shows the attached db as well, and I can
even switch to that db and select/insert/update/delete data in it. And
using the sp_attach_db stored procedure in osql.exe works without any
errors. But still none of the databases listed in sysdatabases is
shown in Enterprise Manager.
I could go on working in osql.exe but I'm not very knowledgable in
working with MSDE using SQL commands, and I'd rather do the same in
Enterprise Manager. I have the exact same setup on other workstations
and they work beautifully. Upgrding MSDE to SP4 and client tools to
SP3 didn't solve anything as well.
Can someone help me there please?
Thanks!
Ehsan
The MSDE edition of SQL Server was developed to answer the needs of some
people who don't want to spend money on buying SQL Server. MSDE is available
to anyone but has some restrictions, some of them are:
- 2 GB maximum capacity
- Doesn't work with Graphic Administration Tools like Enterprise Manager.
The administration must be made by code (T-SQL).
I don't know the kind of needs you have but try to build an Access project
and link the database tables to it. You can build views directly and have
access to table objects.
"ehsan.akhgari@.gmail.com" wrote:

> Hi all,
> I have installed MSDE 2000 SP3a on a workstation, as well as SQL Server
> client tools on the same machine. When I open Enterprise Manager, the
> Databases folder is empty. Even the master database plus other default
> databases (msdb, ...) are not shown. I have made sure the "show system
> databases and objects" setting is checked. This happens whether I
> connect to the MSDE server using the sa account or Windows
> authentication. Also the Query Analyzer utility doesn't work as well.
> It opens, but the command window has no place to type SQL commands, and
> the Object Browser doesn't show any databases.
> I also have a number of old databases (.mdf and .ldf files) that I want
> to attach to this instance. These databases have been originally
> copied from another machine, and have been working on this machine with
> a previous installation of SQL Server Personal Edition. When I open
> the attach databases window in Enterprise Manager, and select a mdf
> file, and click OK, at first nothing happens (no feedback, and the
> dialog even doesn't go away) but clicking OK a second time gives an
> error message stating that a database with the same name already exists
> (and yet the dialog remains open.) Any further actions will take
> Enterprise Manager down by a crash.
> Then I tried connecting to MSDE using osql.exe, and a "USE master;
> SELECT * FROM sysdatabases;" shows the attached db as well, and I can
> even switch to that db and select/insert/update/delete data in it. And
> using the sp_attach_db stored procedure in osql.exe works without any
> errors. But still none of the databases listed in sysdatabases is
> shown in Enterprise Manager.
> I could go on working in osql.exe but I'm not very knowledgable in
> working with MSDE using SQL commands, and I'd rather do the same in
> Enterprise Manager. I have the exact same setup on other workstations
> and they work beautifully. Upgrding MSDE to SP4 and client tools to
> SP3 didn't solve anything as well.
> Can someone help me there please?
> Thanks!
> Ehsan
>
|||Thanks for your reply,
I did not know about this restriction for MSDE. That explains
everything now.
Ehsan

Databases folder empty in Enterprise Manager

Hi all,
I have installed MSDE 2000 SP3a on a workstation, as well as SQL Server
client tools on the same machine. When I open Enterprise Manager, the
Databases folder is empty. Even the master database plus other default
databases (msdb, ...) are not shown. I have made sure the "show system
databases and objects" setting is checked. This happens whether I
connect to the MSDE server using the sa account or Windows
authentication. Also the Query Analyzer utility doesn't work as well.
It opens, but the command window has no place to type SQL commands, and
the Object Browser doesn't show any databases.
I also have a number of old databases (.mdf and .ldf files) that I want
to attach to this instance. These databases have been originally
copied from another machine, and have been working on this machine with
a previous installation of SQL Server Personal Edition. When I open
the attach databases window in Enterprise Manager, and select a mdf
file, and click OK, at first nothing happens (no feedback, and the
dialog even doesn't go away) but clicking OK a second time gives an
error message stating that a database with the same name already exists
(and yet the dialog remains open.) Any further actions will take
Enterprise Manager down by a crash.
Then I tried connecting to MSDE using osql.exe, and a "USE master;
SELECT * FROM sysdatabases;" shows the attached db as well, and I can
even switch to that db and select/insert/update/delete data in it. And
using the sp_attach_db stored procedure in osql.exe works without any
errors. But still none of the databases listed in sysdatabases is
shown in Enterprise Manager.
I could go on working in osql.exe but I'm not very knowledgable in
working with MSDE using SQL commands, and I'd rather do the same in
Enterprise Manager. I have the exact same setup on other workstations
and they work beautifully. Upgrding MSDE to SP4 and client tools to
SP3 didn't solve anything as well.
Can someone help me there please?
Thanks!
EhsanThe MSDE edition of SQL Server was developed to answer the needs of some
people who don't want to spend money on buying SQL Server. MSDE is available
to anyone but has some restrictions, some of them are:
- 2 GB maximum capacity
- Doesn't work with Graphic Administration Tools like Enterprise Manager.
The administration must be made by code (T-SQL).
I don't know the kind of needs you have but try to build an Access project
and link the database tables to it. You can build views directly and have
access to table objects.
"ehsan.akhgari@.gmail.com" wrote:
> Hi all,
> I have installed MSDE 2000 SP3a on a workstation, as well as SQL Server
> client tools on the same machine. When I open Enterprise Manager, the
> Databases folder is empty. Even the master database plus other default
> databases (msdb, ...) are not shown. I have made sure the "show system
> databases and objects" setting is checked. This happens whether I
> connect to the MSDE server using the sa account or Windows
> authentication. Also the Query Analyzer utility doesn't work as well.
> It opens, but the command window has no place to type SQL commands, and
> the Object Browser doesn't show any databases.
> I also have a number of old databases (.mdf and .ldf files) that I want
> to attach to this instance. These databases have been originally
> copied from another machine, and have been working on this machine with
> a previous installation of SQL Server Personal Edition. When I open
> the attach databases window in Enterprise Manager, and select a mdf
> file, and click OK, at first nothing happens (no feedback, and the
> dialog even doesn't go away) but clicking OK a second time gives an
> error message stating that a database with the same name already exists
> (and yet the dialog remains open.) Any further actions will take
> Enterprise Manager down by a crash.
> Then I tried connecting to MSDE using osql.exe, and a "USE master;
> SELECT * FROM sysdatabases;" shows the attached db as well, and I can
> even switch to that db and select/insert/update/delete data in it. And
> using the sp_attach_db stored procedure in osql.exe works without any
> errors. But still none of the databases listed in sysdatabases is
> shown in Enterprise Manager.
> I could go on working in osql.exe but I'm not very knowledgable in
> working with MSDE using SQL commands, and I'd rather do the same in
> Enterprise Manager. I have the exact same setup on other workstations
> and they work beautifully. Upgrding MSDE to SP4 and client tools to
> SP3 didn't solve anything as well.
> Can someone help me there please?
> Thanks!
> Ehsan
>|||Thanks for your reply,
I did not know about this restriction for MSDE. That explains
everything now.
Ehsan

Databases folder empty in Enterprise Manager

Hi all,
I have installed MSDE 2000 SP3a on a workstation, as well as SQL Server
client tools on the same machine. When I open Enterprise Manager, the
Databases folder is empty. Even the master database plus other default
databases (msdb, ...) are not shown. I have made sure the "show system
databases and objects" setting is checked. This happens whether I
connect to the MSDE server using the sa account or Windows
authentication. Also the Query Analyzer utility doesn't work as well.
It opens, but the command window has no place to type SQL commands, and
the Object Browser doesn't show any databases.
I also have a number of old databases (.mdf and .ldf files) that I want
to attach to this instance. These databases have been originally
copied from another machine, and have been working on this machine with
a previous installation of SQL Server Personal Edition. When I open
the attach databases window in Enterprise Manager, and select a mdf
file, and click OK, at first nothing happens (no feedback, and the
dialog even doesn't go away) but clicking OK a second time gives an
error message stating that a database with the same name already exists
(and yet the dialog remains open.) Any further actions will take
Enterprise Manager down by a crash.
Then I tried connecting to MSDE using osql.exe, and a "USE master;
SELECT * FROM sysdatabases;" shows the attached db as well, and I can
even switch to that db and select/insert/update/delete data in it. And
using the sp_attach_db stored procedure in osql.exe works without any
errors. But still none of the databases listed in sysdatabases is
shown in Enterprise Manager.
I could go on working in osql.exe but I'm not very knowledgable in
working with MSDE using SQL commands, and I'd rather do the same in
Enterprise Manager. I have the exact same setup on other workstations
and they work beautifully. Upgrding MSDE to SP4 and client tools to
SP3 didn't solve anything as well.
Can someone help me there please?
Thanks!
EhsanThe MSDE edition of SQL Server was developed to answer the needs of some
people who don't want to spend money on buying SQL Server. MSDE is available
to anyone but has some restrictions, some of them are:
- 2 GB maximum capacity
- Doesn't work with Graphic Administration Tools like Enterprise Manager.
The administration must be made by code (T-SQL).
I don't know the kind of needs you have but try to build an Access project
and link the database tables to it. You can build views directly and have
access to table objects.
"ehsan.akhgari@.gmail.com" wrote:

> Hi all,
> I have installed MSDE 2000 SP3a on a workstation, as well as SQL Server
> client tools on the same machine. When I open Enterprise Manager, the
> Databases folder is empty. Even the master database plus other default
> databases (msdb, ...) are not shown. I have made sure the "show system
> databases and objects" setting is checked. This happens whether I
> connect to the MSDE server using the sa account or Windows
> authentication. Also the Query Analyzer utility doesn't work as well.
> It opens, but the command window has no place to type SQL commands, and
> the Object Browser doesn't show any databases.
> I also have a number of old databases (.mdf and .ldf files) that I want
> to attach to this instance. These databases have been originally
> copied from another machine, and have been working on this machine with
> a previous installation of SQL Server Personal Edition. When I open
> the attach databases window in Enterprise Manager, and select a mdf
> file, and click OK, at first nothing happens (no feedback, and the
> dialog even doesn't go away) but clicking OK a second time gives an
> error message stating that a database with the same name already exists
> (and yet the dialog remains open.) Any further actions will take
> Enterprise Manager down by a crash.
> Then I tried connecting to MSDE using osql.exe, and a "USE master;
> SELECT * FROM sysdatabases;" shows the attached db as well, and I can
> even switch to that db and select/insert/update/delete data in it. And
> using the sp_attach_db stored procedure in osql.exe works without any
> errors. But still none of the databases listed in sysdatabases is
> shown in Enterprise Manager.
> I could go on working in osql.exe but I'm not very knowledgable in
> working with MSDE using SQL commands, and I'd rather do the same in
> Enterprise Manager. I have the exact same setup on other workstations
> and they work beautifully. Upgrding MSDE to SP4 and client tools to
> SP3 didn't solve anything as well.
> Can someone help me there please?
> Thanks!
> Ehsan
>|||Thanks for your reply,
I did not know about this restriction for MSDE. That explains
everything now.
Ehsan

Database Users Appear to be Corrupt

We had a hardware error on our production machine and had to replace it with
our backup machine. Both machines are running SQL Server 2000 on Windows
2000. I used the SQL Server database backup file from production to restore
the backup server.
I know about the sid's being out of sync between the logins and the database
users. I used our standard procedures to re-align them but must have done
something wrong. Now when I run sp_change_users_login 'Report', the list is
empty. I can see the users listed under the database using the enterprise
manager and the users can access the database but I fear that some table
somewhere pertaining to users is corrupted.You should be ok. The Report option of
sp_change_users_login only lists logins that are out of
sync. If you don't get any back from
sp_change_users_login 'Report', then they should all be in
sync.
This is taken directly from BOL pertaining to the Report
option:
"Lists the users, and their corresponding security
identifiers (SID), that are in the current database, not
linked to any login."
>--Original Message--
>We had a hardware error on our production machine and had
to replace it with
>our backup machine. Both machines are running SQL Server
2000 on Windows
>2000. I used the SQL Server database backup file from
production to restore
>the backup server.
>I know about the sid's being out of sync between the
logins and the database
>users. I used our standard procedures to re-align them
but must have done
>something wrong. Now when I run
sp_change_users_login 'Report', the list is
>empty. I can see the users listed under the database
using the enterprise
>manager and the users can access the database but I fear
that some table
>somewhere pertaining to users is corrupted.
>
>.
>|||Hi Robert,
Thank you for using MSDN Newsgroup! It's my pleasure to assist you with your issue.
As Van has pointed out, no report from sp_change_ueses_login means no sync problem of
the corresponding SID and everything seems fine on your side.
It is also recommended you try Database Consistency Checker (DBCC) statements after you
backup and restore your database.
You can use DBCC CHECKDB to check the allocation and structural integrity of the whole
database, or use DBCC CHECKALLOC / DBCC CHECKTABLE to check the individual objects
(including some suspicious tables).
For more information, please refer to Books Online on the topic "DBCC CHECKDB" and
"DBCC CHECKTABLE".
Robert, does this answer your question? If there is anything more we can do to assist you,
please feel free to post it in the group
Best regards,
Billy Yao
Microsoft Online Support
----
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only. Thanks.