MSFTDPProdSamples Work Item Rss Feed

Created Issue: DateTimeOleDB: An unhandled win32 exception occurred in datetimeoledb.exe. [10680]

libinzhao — Thu, 24 Sep 2009 03:03:33 GMT

Environment:
======================
1.　Windows 2003 ENU x86
2.　Katmai 10.0.1600.22
3.   Sample 90908

Repro Steps:
======================
1.   Build the DateTimeOleDB sample successfully.
2.   Run the script successfully “…\Engine\Data Access\oledb\DateTimeOleDB\Scripts\setup.sql”.
3.   Locate to "...\Engine\Data Access\oledb\DateTimeOleDB\cpp\Debug".
4.   Double click “datetimeoledb.exe”.

Expectations:
======================
The datetimeoledb.exe should run properly without any exception.

Actual Results:
======================
An unhandled win32 exception occurred in datetimeoledb.exe.
Please see the attached file "datetimeoledbError.jpg" about the details.

Commented Issue: DateTime_ODBC: There is a ODBC error when run the DateTime_ODBC.exe on x86 platform.

libinzhao — Fri, 28 Aug 2009 05:32:16 GMT

Environment:
======================
1.　Windows XP SP3 CHS x86
2.　Katmai 10.0.1600.22
3.    Sample 90810
4.　VS 2005
5.    Create ODBC data source called DateTime by readme

Repro Steps:
======================
1.   Build the DateTime_ODBC sample successfully.
2.   Run the script successfully “…\Engine\Data Access\odbc\DateTime_ODBC\scripts\ setup.sql”.
3.   Locate to "...\Engine\Data Access\odbc\DateTime_ODBC\cpp\Debug".
4.   Double click “DateTime_ODBC.exe”.

Expectations:
======================
The DateTime_ODBC.exe should run properly without any exception.

Actual Results:
======================
There is a ODBC error when run the DateTime_ODBC.exe:
Error: SQLSTATE=22003, Native error=0, msg=[Microsoft][SQL Server Native Client 10.0]Numeric value out of range.

Please see the attached files:
1.      Windows XP SP3 CHS x86: DateTime_ODBC_error.jpg
2.      AMD64 with the default configuration (Win32): AMD64_win32_error.jpg

Comments:
======================
This issue repro on AMD64 when building with the default configuration (Win32), but this sample works well when building with the configuration (X64).
Comments:

There is the description "To build and run this sample as a 32-bit application on a 64-bit operating system, you must create the ODBC data source with the ODBC Administrator in %windir%\SysWOW64\odbcad32.exe. " in this sample readme on codeplex "http://msftdpprodsamples.codeplex.com/Wiki/View.aspx?title=SS2008%21Readme_ODBC%20Date%20Time&referringTitle=Home".

Commented Issue: DateTime_ODBC: There is a ODBC error when run the DateTime_ODBC.exe on x86 platform.

mor_kab — Thu, 27 Aug 2009 17:36:31 GMT

Created Issue: DateTime_ODBC: There is a ODBC error when run the DateTime_ODBC.exe on x86 platform.

libinzhao — Tue, 18 Aug 2009 03:07:14 GMT

Closed Issue: odbc_spatial: The Banned API "wsprintf" is used in this sample.

leilu — Tue, 28 Jul 2009 07:10:09 GMT

Environment:
======================
Sample 81021
Whidbey 8.0.50727.42

Repro Steps:
======================
1. Open sample odbc_spatial.sln to check the Banned APIs
2. Check the 124 line of the file odbc_spatial.cpp.

Expectations:
======================
The Banned APIs should not be used in sample code.

Actual Results:
======================
The Banned API "wsprintf" is used in line 124 of odbc_spatial.cpp.

Commnets:
======================
For Scecuriy Note about "wsprintf", please refer the following webpage:
http://msdn2.microsoft.com/en-us/library/ms647550.aspx
Comments: Verified on Sample Build 90727

Commented Issue: odbc_spatial: The Banned API "wsprintf" is used in this sample.

libinzhao — Tue, 28 Apr 2009 07:04:19 GMT

Closed Issue: ODBC_largeUDT: The setup.sql is executed with error ”Type 'LargeStringUDT' in assembly 'LargeStringUDT' is not public”.

cmslydia — Thu, 12 Mar 2009 05:55:59 GMT

Environment:
====================
1. Win2k3 x86 ENT ENU SP2.
2. VS2005
3. Katmai Samples 090228

Steps:
====================
1.       Open and build the solution “..\Engine\Data Access\odbc\ODBC_largeUDT\cpp\ODBC_largeUDT.sln" via vs2005.
2.       Enable the CLR of Katmai.
3.       Double click to setup.sql from “..\Samples\Engine\Data Access\odbc\ODBC_largeUDT\scripts”.
4.       Click Connect button to connect server.
5.       Execute the setup.sql script.

Expectation:
===================
The script should be execute successfully without error.

Actual Results:
===================
The script is executed failed with error:
Msg 6576, Level 16, State 3, Line 2
Type 'LargeStringUDT' in assembly 'LargeStringUDT' is not public.
Msg 6597, Level 16, State 1, Line 2
CREATE TYPE failed.
Msg 2715, Level 16, State 7, Line 2
Column, parameter, or variable #2: Cannot find data type LargeStringUDT.
Msg 243, Level 16, State 1, Line 2
Type LargeStringUDT is not a defined system type.
Msg 208, Level 16, State 1, Line 2
                Invalid object name 'dbo.LargeStringUDTs'.

Comments:
====================
If define the class LargeStringUDT of LargeStringUDT project as a public class, the sample can work well.

Closed Issue: Oledb_largeUDT: The setup.sql is executed with error "Type 'LargeStringUDT' in assembly 'LargeStringUDT' is not public".

libinzhao — Mon, 09 Mar 2009 07:51:20 GMT

Environment:
====================
1. Win2k3 x86 ENT ENU SP2.
2. VS2005
3. Katmai Samples 090228

Steps:
====================
1.       Open and build the solution “..\Engine\Data Access\oledb\Oledb_largeUDT\cpp\Oledb_largeUDT.sln" via vs2005.
2.       Enable the CLR of Katmai.
3.       Double click to setup.sql from “..\Samples\Engine\Data Access\Oledb\Oledb_largeUDT\scripts”.
4.       Click Connect button to connect server.
5.       Execute the setup.sql script.

Expectation:
===================
The script should be execute successfully without error.

Actual Results:
===================
The script is executed failed with error:
Msg 6576, Level 16, State 3, Line 2
Type 'LargeStringUDT' in assembly 'LargeStringUDT' is not public.
Msg 6597, Level 16, State 1, Line 2
CREATE TYPE failed.
Msg 2715, Level 16, State 7, Line 2
Column, parameter, or variable #2: Cannot find data type LargeStringUDT.
Msg 243, Level 16, State 1, Line 2
Type LargeStringUDT is not a defined system type.
Msg 208, Level 16, State 1, Line 2
            Invalid object name 'dbo.LargeStringUDTs'.

Comments:
====================
If define the class LargeStringUDT of LargeStringUDT project as a public class, the sample can work well.

Created Issue: Add Readme_Integrated Kerberos Authentication (ODBC) to wiki.

ReedMe — Sat, 07 Mar 2009 01:10:10 GMT

Katmai_Trunk\odbc\ODBC_SPN\ReadMe.htm

Created Issue: Add Send and Receive Data Incrementally with FILESTREAM (ODBC) to wiki.

ReedMe — Sat, 07 Mar 2009 01:04:34 GMT

Katmai_Trunk\odbc\ODBC_filestream\readme.htm

Created Issue: Add Mirroring Failover (ODBC) readme to wiki.

ReedMe — Sat, 07 Mar 2009 01:02:55 GMT

Katmai_Trunk\odbc\MirroringFailover\readme.htm

Commented Issue: Oledb_largeUDT: The setup.sql is executed with error "Type 'LargeStringUDT' in assembly 'LargeStringUDT' is not public".

leilu — Fri, 06 Mar 2009 02:16:58 GMT

Environment:
====================
1. Win2k3 x86 ENT ENU SP2.
2. VS2005
3. Katmai Samples 090228

Steps:
====================
1.       Open and build the solution “..\Engine\Data Access\oledb\Oledb_largeUDT\cpp\Oledb_largeUDT.sln" via vs2005.
2.       Enable the CLR of Katmai.
3.       Double click to setup.sql from “..\Samples\Engine\Data Access\Oledb\Oledb_largeUDT\scripts”.
4.       Click Connect button to connect server.
5.       Execute the setup.sql script.

Expectation:
===================
The script should be execute successfully without error.

Actual Results:
===================
The script is executed failed with error:
Msg 6576, Level 16, State 3, Line 2
Type 'LargeStringUDT' in assembly 'LargeStringUDT' is not public.
Msg 6597, Level 16, State 1, Line 2
CREATE TYPE failed.
Msg 2715, Level 16, State 7, Line 2
Column, parameter, or variable #2: Cannot find data type LargeStringUDT.
Msg 243, Level 16, State 1, Line 2
Type LargeStringUDT is not a defined system type.
Msg 208, Level 16, State 1, Line 2
            Invalid object name 'dbo.LargeStringUDTs'.

Comments:
====================
If define the class LargeStringUDT of LargeStringUDT project as a public class, the sample can work well.
Comments: oledb\Oledb_largeUDT\cpp\LargeStringUDT\LargeStringUDT.cs
Modify Line==>32
class LargeStringUDT : INullable, IBinarySerialize {
public class LargeStringUDT : INullable, IBinarySerialize {

Commented Issue: ODBC_largeUDT: The setup.sql is executed with error ”Type 'LargeStringUDT' in assembly 'LargeStringUDT' is not public”.

leilu — Fri, 06 Mar 2009 02:16:42 GMT

Created Issue: ODBC_largeUDT: The setup.sql is executed with error ”Type 'LargeStringUDT' in assembly 'LargeStringUDT' is not public”.

cmslydia — Mon, 02 Mar 2009 09:45:42 GMT

Created Issue: Oledb_largeUDT: The setup.sql is executed with error "Type 'LargeStringUDT' in assembly 'LargeStringUDT' is not public".

libinzhao — Mon, 02 Mar 2009 09:00:03 GMT

Environment:
====================
1. Win2k3 x86 ENT ENU SP2.
2. VS2005
3. Katmai Samples 090228

Steps:
====================
1.       Open and build the solution “..\Engine\Data Access\oledb\Oledb_largeUDT\cpp\Oledb_largeUDT.sln" via vs2005.
2.       Enable the CLR of Katmai.
3.       Double click to setup.sql from “..\Samples\Engine\Data Access\Oledb\Oledb_largeUDT\scripts”.
4.       Click Connect button to connect server.
5.       Execute the setup.sql script.

Expectation:
===================
The script should be execute successfully without error.

Actual Results:
===================
The script is executed failed with error:
Msg 6576, Level 16, State 3, Line 2
Type 'LargeStringUDT' in assembly 'LargeStringUDT' is not public.
Msg 6597, Level 16, State 1, Line 2
CREATE TYPE failed.
Msg 2715, Level 16, State 7, Line 2
Column, parameter, or variable #2: Cannot find data type LargeStringUDT.
Msg 243, Level 16, State 1, Line 2
Type LargeStringUDT is not a defined system type.
Msg 208, Level 16, State 1, Line 2
            Invalid object name 'dbo.LargeStringUDTs'.

Comments:
====================
If define the class LargeStringUDT of LargeStringUDT project as a public class, the sample can work well.

Created Issue: odbc_spatial: The Banned API "wsprintf" is used in this sample.

cmslydia — Mon, 19 Jan 2009 04:26:21 GMT

Created Issue: BulkCopyNativeMode: Run BulkCopyNativeMode.exe and then “bcp_exec(hdbc1) Failed” was displayed in SDK command prompt on Russian OS.

leilu — Thu, 25 Dec 2008 09:02:48 GMT

Environment:
======================
1.　Win2K3 ENT SP1 Russian.
2.　Whidbey 50727.42.
3. Yukon RTM 9.00.1399.06.25.
4. Sample MSI 60611.
Steps:
===================
1. Compile BulkCopyNativeMode.sln successfully.
2. Run BulkCopyNativeMode.exe in SDK.
Expectation:
===================
“Number of rows bulk copied out = 104” should be displayed in SDK command prompt.
Actual Results:
===================
“bcp_exec(hdbc1) Failed” was displayed in SDK command prompt.
Comment:
====================
1. The bug only depends on Russian.
2. In BulkCopyNativeMode.cpp file, after running the following code “retcode = bcp_exec(hdbc1, &cRows)” in Line 101, the value of the retcode equals zero.

Created Issue: CTP6: MirroringFailover: There are warnings in Code Analysis results.

leilu — Thu, 25 Dec 2008 09:02:48 GMT

This is a defect of sample code , it repron on bothKatmai SxS 10.0.1003.6 and Yukon SP2 09.00.3039.00.

Dup bug: 211254.
Environment:
======================
1.　Windows2003 ENT ENU
2.　Katmai DEV ENU 10.0.1003.6
3. Katmai integrated sample
4.　Whidbey 8.0.50727.42

Repro Steps:
======================
1.Open the solution file "...\\Microsoft SQL Server\100\Samples\Engine\Data Access\odbc\MirroringFailover\MirroringFailover\MirroringFailover.sln" in Whidbey
2.Select and right click on the MirrofingFailover project to open the Properties. In Code Analysis tab, check "Enable Code Analysis (defines CODE_ANALYSIS constant)"
3.Execute code analysis from the menu: Build -> Run Code Analysis on MirrofingFailover
4.Check the analysis results.
5.Run Code Analysis on DataAccessLayer and check the results.

Expectations:
======================
There should be 0 Errors, 0 Warnings.

Actual Results:
======================
There are 72 Warnings for Project MirrofingFailover.
There are 28 Warnings for Project DataAccessLayer.
See the attached file for the warning details.