无法在Windows 10 Pro上将SSIS包部署到SQL Server 2016 Express [英] Can't deploy SSIS package to SQL Server 2016 Express on Windows 10 Pro

查看:298
本文介绍了无法在Windows 10 Pro上将SSIS包部署到SQL Server 2016 Express的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我在将Windows 10 Home计算机上开发的SSIS包部署到Windows 10 Pro计算机上的SQL Server 2016 Express实例时遇到困难.

I'm having difficulty deploying an SSIS package developed on my Windows 10 Home machine to the SQL Server 2016 Express instance on my Windows 10 Pro machine.

我的家庭网络设置中有两台计算机,一台Windows 10 Home机器正在执行VB.NET和SSIS软件包开发,一台Windows 10 Pro机器正在运行Microsoft SQL Server 2016 Express.

I have two computers in my home network setup, a Windows 10 Home machine where I'm doing VB.NET and SSIS package development and a Windows 10 Pro machine where I'm running Microsoft SQL Server 2016 Express.

在运行程序包部署向导时,选择目标服务器名称后,我遇到了Kerberos错误目标主体名称不正确.无法生成SSPI上下文".

In running the package deployment wizard, after selecting the destination server name I'm running into the Kerberos error "The target principal name is incorrect. Cannot generate SSPI context".

在运行SQL Server 2016 Express的Windows 10 Pro计算机上下载并运行Kerberos连接疑难解答,并得到错误

Downloaded and ran the Kerberos Connectivity Troubleshooter on the Windows 10 Pro machine running SQL Server 2016 Express and got the error

无法从系统访问用户主体信息

Unable to access User Principal information from the System

当尝试连接到该计算机上的本地SQL实例时.

when trying to connect to the local SQL instance on that machine.

在疑难解答程序的日志文件中,我得到了一些更具体的信息,但是我的在线研究陷入了僵局:

In the log file for the troubleshooter I get some more specific information but I'm running into a dead end with my online research:

2017/3/26下午6:55:50信息:连接到WMI,\ root \ cimv2
2017/3/26下午6:55:52错误:访问用户主体信息失败System.ArgumentException:提供的上下文类型与联系的服务器不匹配.服务器类型为ApplicationDirectory.

3/26/2017 6:55:50 PM Info: Connect to WMI, \root\cimv2
3/26/2017 6:55:52 PM Error: Access of User Principal information failed System.ArgumentException: The supplied context type does not match the server contacted. The server type is ApplicationDirectory.

在System.DirectoryServices.AccountManagement.PrincipalContext.DoServerVerifyAndPropRetrieval()
在System.DirectoryServices.AccountManagement.PrincipalContext..ctor中(ContextType contextType,字符串名称,字符串容器,ContextOptions选项,字符串userName,字符串密码)
在System.DirectoryServices.AccountManagement.PrincipalContext..ctor(ContextType contextType,字符串名称)
在KerberosCM.WMIHelper.TryGetUser(SystemInfo mi,UserPrincipal& user)

at System.DirectoryServices.AccountManagement.PrincipalContext.DoServerVerifyAndPropRetrieval()
at System.DirectoryServices.AccountManagement.PrincipalContext..ctor(ContextType contextType, String name, String container, ContextOptions options, String userName, String password)
at System.DirectoryServices.AccountManagement.PrincipalContext..ctor(ContextType contextType, String name)
at KerberosCM.WMIHelper.TryGetUser(SystemInfo mi, UserPrincipal& user)

下一步我需要检查或配置什么?

What do I need to check or configure next?

推荐答案

SQL Server Express没有SSIS服务器组件.

SQL Server Express does not have an SSIS server component.

请注意,Express没有"SSIS设计器和运行时"

Note here that Express does not have "SSIS Designer and runtime" https://docs.microsoft.com/en-us/sql/integration-services/integration-services-features-supported-by-the-editions-of-sql-server.

开发版是免费的,具有此功能,但您不允许将其用于生产目的.

The Developer edition, which is free, does have this but you aren't allowed to use it for production purposes.

此外,我认为这些版本的Windows也都不支持Kerberos.

Further to that, I don't think those editions of windows support Kerberos either.

这篇关于无法在Windows 10 Pro上将SSIS包部署到SQL Server 2016 Express的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆