Showing posts with label connected. Show all posts
Showing posts with label connected. Show all posts

Thursday, March 22, 2012

Error 8114 Date data

I am trying to pull over data in for a specified date from an ODBC connected
AS/400 table, and I get the following error.
Server: Msg 8114, Level 16, State 8, Line 1
Error converting data type DBTYPE_DBTIMESTAMP to datetime.
Here's an example of what the field looks like in the AS/400 table:
1999-08-24 00:00:00.000
I thought that I could just as "where date = '2005-07-01 00:00:00.00'" but
it doesn't work.
Any thoughts'
Thanks in advance.This could be the limitation of the provider you use. Try a different or
newer provider.
Adrian
"aschossler" <aschossler@.discussions.microsoft.com> wrote in message
news:6C6CD9AF-F37E-459E-9A42-64CE221D2E94@.microsoft.com...
>I am trying to pull over data in for a specified date from an ODBC
>connected
> AS/400 table, and I get the following error.
> Server: Msg 8114, Level 16, State 8, Line 1
> Error converting data type DBTYPE_DBTIMESTAMP to datetime.
> Here's an example of what the field looks like in the AS/400 table:
> 1999-08-24 00:00:00.000
> I thought that I could just as "where date = '2005-07-01 00:00:00.00'"
> but
> it doesn't work.
> Any thoughts'
> Thanks in advance.

Friday, March 9, 2012

Error 500, Maximum concurrent users have reached

We are running three web sites in a clustered environment
WLBS. The web servers are connected to a Database Server
running MS SQL server enterprise edition licensed as per
CPU license. The Windows 2000 Advanced Server Licensing
mode on all the servers is per SEAT license.

Our customers are accessing our web servers and after some
time getting error 500, Maximum concurrent users have
reached.

We have been told by our software provider that the
connection problem lies with the ADO components which
communicating with the SQL server.

We have been turning round and round, without any luck.

Your help will be highly appreciated.

Thanks and best regards

Dave

Learning is a Never Ending process

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!Dave Kissoondoyal (network@.bowmans.intnet.mu) writes:
> We are running three web sites in a clustered environment
> WLBS. The web servers are connected to a Database Server
> running MS SQL server enterprise edition licensed as per
> CPU license. The Windows 2000 Advanced Server Licensing
> mode on all the servers is per SEAT license.
> Our customers are accessing our web servers and after some
> time getting error 500, Maximum concurrent users have
> reached.
> We have been told by our software provider that the
> connection problem lies with the ADO components which
> communicating with the SQL server.

A message that starts with a three-digit number with a leading 5
looks like a response code from a protocol that sits on top of
TCP/IP. That is, I would assume that this message comes from the
web server and not SQL Server.

Whether the web server reacts this way due to some error code
from SQL Server, I don't know. But it seems that you will have
to investigate the web server first.

--
Erland Sommarskog, SQL Server MVP, sommar@.algonet.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp

Sunday, February 26, 2012

error 3073 problem

Hi I have a problem with inserting new data for a newly connected database. What i do is i have a current connection open and running. When the user picks another database source from an OpenFileDialog, I create a temporary variable to test the database connection (from the openfiledialog) and if it can connect then i close the previous connected database and connect to the new database. I close the previous database and set the new database into one and the same variable.

The problem is when i connect to the new database, and am going to insert some new values to a certain table. It shows the error something like:

error 3073. An updatable query is necessary.

I have checked the data source of the database and it contains the path where the new connection is. The sql query is also valid because i have checked it in the ms access query builder. The permission is also valid since it is in write permission.

Hope anyone has an idea for my problem. Thanks in advance!

Please post the query.

SQL Server and Access have syntax differences in updating.

For example:

Access

--

Update table1 t1, table2 t2

SET t1.ID = t2.ID

...this will not work in SQL

SQL Server

--

Update t1

SET t1.ID = t2.ID

FROM Table1 t1

LEFT JOIN Table2 t2 on t1.ID = t2.ID

So testing the query in Access might fail in SQL Server.

Adamus

|||Here is the sample sql:

INSERT INTO [table name](ID, DIVISION, USER_NAME, EXEC_TIME, [CONTENTS]) VALUES (1, 'Division', 'user', '2005/05/19 10:45:01', 'Comments.');

After I call the OleDbCommand to ExecuteNonQuery, this error occurs. I am using MS Access by the way. Thanks!
|||Could you please the code part which is relevant (including initialization for the command) ?

Jens K. Suessmeyer.

http://www.sqlserver2005.de

|||

Technically this is not a SQL Server issue (since you're using Access), but please post the full ADO coding.

Adamus

|||Sorry for the confusion I was also hoping someone in this forum could also help me in my problem. I was thinking that this error is not dependent on what type database you use. But thanks still for the effort. This is another thread I created that has the necessary codes involved.

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

Please feel free to take a look. If you are going to reply kindly reply to this thread (SQL Server) instead so the threads will be more organized (opinions of the people in a particular expertise) and i won't get more confused Smile Thanks a lot!