Microsoft SQL Server 2008 R2 — & GT; SQL SERVER Business Intelligence Development Studio
Using the EXCEL data source or target reported the following error
Start the SSIS Package “package.dTSx”.
message: 0x4004300A, located in data flow task, ssis. Pipeline: validation phase is beginning.
error: 0xC00F9304, located in the Package, connection manager “Excel connection manager 1” : SSIS error code DTS_E_OLEDB_EXCEL_NOT_SUPPORTED: because there is no OLEDB access interface available, Excel connection manager is not supported in the 64-bit version of SSIS.
error: 0 xc020801c, located in the data flow task, Excel source [89] : SSIS DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER error code. The AcquireConnection method call to connection manager “Excel Connection Manager 1” failed with error code 0xC00F9304. An error message may have been sent prior to this, providing detailed information about why the AcquireConnection method call failed.
error: 0xC0047017, located in data flow task, ssis. Pipeline: component “Excel source” (89) fails validation, returns error code 0xC020801C.
error: 0xC004700C, on data flow task, ssis. Pipeline: one or more components fail validation.
error: 0xC0024107, error occurs during data flow task: task validation.
SSIS Package “package.dtsx” completed: failed.
Solution: Select the item, right-click the properties shown in the figure, and change Run64BitRuntime to FALSE
[Excel Destination [31]] Error: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager “Excel Connection Manager” failed with error code 0xC00F9304. There may be error messages posted before this with more information on why the AcquireConnection method call failed.
Error: SSIS Error Code DTS_E_OLEDB_EXCEL_NOT_SUPPORTED: The Excel Connection Manager is not supported in the 64-bit version of SSIS, as no OLE DB provider is available.

 

Reproduced in: https://www.cnblogs.com/qiangshu/p/5238161.html

如果您在项目的错误日志中收到此错误，这里是它的描述和解决方案。
先决条件:应用程序必须具有基于实现的表单身份验证方法的自定义登录功能。此外，必须使用用于角色、用户和成员的内置功能。
问题:可见的问题是用户无法登录到应用程序，在事件查看器中出现以下错误(Start ->控制面板→管理工具→事件查看器):
事件查看器中的错误:
事件代码:4006
事件消息:成员证书验证失败。
事件时间:28/08/2006 12:30:12
事件时间(UTC): 28/08/2006 09:30:12
事件ID: 04b22a752da345baabe19236fb25675f
事件序列:2
事件发生:1
事件详细代码:0
事件详细代码:0
事件详细代码:0
事件发生:1
事件详细代码:0
事件详细代码:0
这里是解决方案:“aspnet_Applications”数据库表中的“ApplicationName”值和web中所有提供者的“ApplicationName”属性值。配置(成员资格提供程序、角色提供程序、配置文件提供程序等)必须具有相同的值。

转载于:https://www.cnblogs.com/dimg/archive/2008/12/03/1346373.html

After connecting to the SqlServer database with pymssql, when inserting a block of data containing the time field into the database, the Conversion error is reported as follows:
‘Conversion failed when converting date and/or time from character string. Db-lib error message 241,
Process:
1, directly in the database to execute the insert statement

INSERT INTO [dbo].[ClustedResult]([outputScript],[classId],[startTime],[endTime]) VALUES(0x76A914E67550CD61C6D89DF67F4D5F8E0B4AD30013C65888AC,'493886f0-7387-11e7-ab02-047d7ba2a507','2017-07-28 19:24:14.431000','2017-07-28 19:24:14.431000')

An error was also reported, indicating that string and date conversion failed.
2, view the data type
of each field in the table: [startTime],[endTime] data type of two fields is datetime
There are 6 data types of sqlserver 2008 representing time on the Internet.
time, date, smalldatetime, datetime, datetime2, datetimeoffset;
Datetime
date and time section, can represent date range from January 1, 1753 AD 00:00:00 000 to December 31, 9999 23:59:59.997, accurate to 3.33 ms, it requires 8 bytes of storage space. The DateTime field type corresponds to the time format of YYyy-Mm-DD HH: MM: Ss.FFF, three F’s, accurate to 1 ms (ms), example 2014-12-03 17:06:15.433
Smalldatetime
date and time data from January 1, 1900 to June 6, 2079 are accurate to minutes. Smalldatetime values of 29.998 seconds or less are rounded down to the closest minute, and SmallDatetime values of 29.999 seconds or more are rounded up to the closest minute. 4 bytes of storage space is required.
Date
SQL Server 2008 newly introduced data type. It represents a date, without a time component, and can represent dates ranging from January 1, A.D., to December 31, 9999. Only three bytes of storage is required.
DateTime2
DateTime2 field type corresponding to the time format is yyyy-mm-dd HH: MM :ss.fffffff, 7 f, accurate to 0.1 microsecond (s), example 2014-12-03 17:23:19.2880929.
The data is read in the same format regardless of whether your field is datetime or SmallDatetime (e.g. 1900-01-01). A datetime doesn’t show its milliseconds, but it does show up in milliseconds during time comparisons, making the time periods not equal.
If it’s SQL Server 2005, use Smalldatetime to get half of the data, even if it doesn’t look any different when queried.
if you are SQL Server 2008, please use date. Although 3 bytes is not much different from 4 bytes, it has greatly improved in design and logical clarity.
If the SQL date function is used for assignment, the DateTime field type is GETDATE() and the DateTime2 field type is SYSDATETIME().
There’s a very detailed reference: http://www.csdn.net/article/1970-01-01/282777

http://blog.csdn.net/justdb/article/details/7575021
3. After a series of knowledge catch up with, look at the characteristics of time types in python

begin = datetime.datetime.now()
print type(begin)
print str(begin)

#运行结果：
<type 'datetime.datetime'>
2017-07-28 19:24:14.431000

4. The reason is that python and sqlserver have different time types: format. Offer two solutions:
Solution 1: Unify the Python Datetime format with the database format.
timeStamp = STR (datetime. Datetime. Now ())[0:-3] scheme 2: modify the database data type to a wider range of datetime2

today, there was a student installing SQL 2012 and using administrator to log in the system for installation, and setup account privileges Failed unexpectedly, saying that he had no authority.

so I create a new user on Windows, join the administrators group, and use that user to install.

someone else gave an Oracle file, the result was found when importing the problem, the error was reported as follows:

IMP-00010: not a valid export file, header failed verification

after searching on the Internet, I found that it was caused by the version database problem. I opened the DMP file with UE editor and saw the first line as follows:

the figure above indicates that the database version is: Oracle12c version

use SQL:select * from v$version to query the current database version

we modified the TEXPORT:V12.02 of the DMP file to V11.02 and imported it again to solve the problem perfectly.

reproduced in: https://www.cnblogs.com/OliverQin/p/9565569.html

this period of time customer mail system upgrade, basically the same as before, CAS+HUB NLB, DAG database,

try creating a new mailbox. Error reporting

Load balancing failed to find a valid mailbox database.”

but if you choose a specific database it’s ok,

after the search reasons are as follows:

1) select update RU6

for exchange sp1

2) check to see if the database has dismount

3) mail database server not installed, but I think this should appear this error 🙂

reproduced in: https://blog.51cto.com/4763146/987147

alter table stu add foreign key(cno) references user(id);

Failed to add the foreign key constraint. Missing index for constraint ‘stu_ibfk_1’ in the referenced table ‘user’

solution:

as the foreign key, user table id must be a unique value, so the constraint unique, or primary key must be added;