te')); return $arr; } /* 遍历用户所有主题 * @param $uid 用户ID * @param int $page 页数 * @param int $pagesize 每页记录条数 * @param bool $desc 排序方式 TRUE降序 FALSE升序 * @param string $key 返回的数组用那一列的值作为 key * @param array $col 查询哪些列 */ function thread_tid_find_by_uid($uid, $page = 1, $pagesize = 1000, $desc = TRUE, $key = 'tid', $col = array()) { if (empty($uid)) return array(); $orderby = TRUE == $desc ? -1 : 1; $arr = thread_tid__find($cond = array('uid' => $uid), array('tid' => $orderby), $page, $pagesize, $key, $col); return $arr; } // 遍历栏目下tid 支持数组 $fid = array(1,2,3) function thread_tid_find_by_fid($fid, $page = 1, $pagesize = 1000, $desc = TRUE) { if (empty($fid)) return array(); $orderby = TRUE == $desc ? -1 : 1; $arr = thread_tid__find($cond = array('fid' => $fid), array('tid' => $orderby), $page, $pagesize, 'tid', array('tid', 'verify_date')); return $arr; } function thread_tid_delete($tid) { if (empty($tid)) return FALSE; $r = thread_tid__delete(array('tid' => $tid)); return $r; } function thread_tid_count() { $n = thread_tid__count(); return $n; } // 统计用户主题数 大数量下严谨使用非主键统计 function thread_uid_count($uid) { $n = thread_tid__count(array('uid' => $uid)); return $n; } // 统计栏目主题数 大数量下严谨使用非主键统计 function thread_fid_count($fid) { $n = thread_tid__count(array('fid' => $fid)); return $n; } ?>SSIS 2022 Excel Connection Manager cannot map columns - Stack Overflow

科技改变生活-雨落星辰 - 所有的伟大,都源于一个勇敢的开始

    最新消息：雨落星辰是一个专注网站SEO优化、网站SEO诊断、搜索引擎研究、网络营销推广、网站策划运营及站长类的自媒体原创博客
    你的位置： 首页>programmer>SSIS 2022 Excel Connection Manager cannot map columns - Stack Overflow

    SSIS 2022 Excel Connection Manager cannot map columns - Stack Overflow

    programmeradmin4浏览0评论

    On our dev environment we have MS Office 365 32-bit version on Windows 11 64-bit and Visual Studio 2022 with SSDT.

    The issue we are experiencing is in SSIS when creating Excel Destination in order to write data into an excel file. When trying to map the columns from source to Excel Destination we get an error message below: "The requested ole db provider microsoft.ace.oledb.12.0 is not registered if the 64 bit driver is not installed, run the package in 32-bit mode. error code: 0x00000000"

    I know Visual Studio 2022 is 64-bit and the debug option Run64BitRuntime is greyed out and it is set to True.

    The database server, where the SSIS package has to run on (as SSIS package file through SQL Server job), the Office and the Excel app in 64-bit with Microsoft Access Database Engine installed. Not sure if that is 64 or 32 bit version.

    Do you know, if we need 32-bit or 64-bit version Microsoft Access Database Engine on dev machine? And how about on Database Server, where package is run?

    We probably need to install 32-bit version Microsoft Access Database Engine 2016, as we have Office 365 32-bit version on our dev machines. Right? If we install 32-bit Microsoft Access Database Engine 2016 on our dev machine, will this solve the issue with error above? And can we run the package as 64 bit on database server?

    Thanks in advance for your help.

    Kind Regards

    On our dev environment we have MS Office 365 32-bit version on Windows 11 64-bit and Visual Studio 2022 with SSDT.

    The issue we are experiencing is in SSIS when creating Excel Destination in order to write data into an excel file. When trying to map the columns from source to Excel Destination we get an error message below: "The requested ole db provider microsoft.ace.oledb.12.0 is not registered if the 64 bit driver is not installed, run the package in 32-bit mode. error code: 0x00000000"

    I know Visual Studio 2022 is 64-bit and the debug option Run64BitRuntime is greyed out and it is set to True.

    The database server, where the SSIS package has to run on (as SSIS package file through SQL Server job), the Office and the Excel app in 64-bit with Microsoft Access Database Engine installed. Not sure if that is 64 or 32 bit version.

    Do you know, if we need 32-bit or 64-bit version Microsoft Access Database Engine on dev machine? And how about on Database Server, where package is run?

    We probably need to install 32-bit version Microsoft Access Database Engine 2016, as we have Office 365 32-bit version on our dev machines. Right? If we install 32-bit Microsoft Access Database Engine 2016 on our dev machine, will this solve the issue with error above? And can we run the package as 64 bit on database server?

    Thanks in advance for your help.

    Kind Regards

    • excel
    • ssis
    • office365
    • visual-studio-2022
    • access-database-engine
    Share Improve this question asked Feb 18 at 4:17 ausmodausmod 715 bronze badges 1
    • Another observation I had recently is that I in SSMS Import and Export Wizard I have Microsoft Excel in the drop down list for the Data Source or Destination. But, in Visual Studio SSIS the Microsoft Excel is missing in the drop down list for the SSIS Import and Export Wizard! And I assume, SSMS is 32 bit application. – ausmod Commented 2 days ago
    Add a comment  | 

    1 Answer 1

    Reset to default 1

    It sounds like you're dealing with a common issue when working with SSIS and Excel files, especially when there's a mix of 32-bit and 64-bit components. Let me break this down for you:

    1. Since you have Office 365 32-bit installed on your dev machine, you’ll need the 32-bit version of the Microsoft Access Database Engine. This is because SSIS needs to match the bitness of the Office installation to interact with Excel files properly.
    2. Installing the 32-bit Access Database Engine should resolve the error you're seeing during column mapping in Visual Studio.
    3. On the database server where the SSIS package will run, if the Office installation is 64-bit, you’ll need the 64-bit version of the Microsoft Access Database Engine. This ensures compatibility when the package is executed via SQL Server Agent.
    4. If the server has a 64-bit Office installation, the package should run in 64-bit mode without issues.
    5. Dev Machine: Install the 32-bit Access Database Engine to match your 32-bit Office installation.
    6. Database Server: Install the 64-bit Access Database Engine if the the server has a 64-bit Office installation.
    7. Package Execution: Ensure the Run64BitRuntime setting is correctly configured for development and deployment. On the server, it should be set to True if running in 64-bit mode.
    8. If you’re developing in Visual Studio 2022 (64-bit) but need to debug in 32-bit mode, you might need to adjust your project settings or use a 32-bit version of Visual Studio for debugging purposes.
    9. Double-check the bitness of the Access Database Engine installed on both the dev machine and the server to avoid mismatches.

    与本文相关的文章

    发布评论

    评论列表(0)

    1. 暂无评论