Error accessing report: installation

Showing posts with label installation. Show all posts

Tuesday, March 27, 2012

Error encountered UNC path error during remote installation

Good day good people of the forum while carrying out a remote installation i encountered an UNC path error can anyone be of help giving me a comprehensive answer to the problem. am stuck i cant move ahead from that part of the installation

Hi Yudee, can you send us the error message? Are you getting it in a log? If so, which log?

Thanks,
Samuel Lester (MSFT)

sql

Monday, March 26, 2012

error during quiet installation of June CTP.

I am trying quiet installation of June CTP with the .ini file .

The installation is failing with Last Action :Install Finalize:
The sql server service failed to start.
Error number:29523
--
My ini file settings were as folllows
[snip]
SQLBROWSERACCOUNT= "NT AUTHORITY\LOCAL SERVICE"
SQLBROWSERPASSWORD=

SQLACCOUNT="NT AUTHORITY\LOCAL SERVICE"
SQLPASSWORD=

AGTACCOUNT="NT AUTHORITY\LOCAL SERVICE"
AGTPASSWORD=

ASACCOUNT=
ASPASSWORD=

RSACCOUNT=
RSPASSWORD=
[snip]
-
As mentioned in one of the mails in the group i changed the three accounts to
"NT AUTHORITY\LOCAL SYSTEM".

Now i get new errors as follows
Last Action : Validate_ServiceAccounts
Error String : SQL Server Setup was unable to validate the account or accounts you provided. To continue, verify that the user name, password, and domain name are correct, or provide another user account for SQL Server service login.
The logon account cannot be validated for the service SQL Browser.
Error Number : 29609
--

One observation is that the installation goes fine with <domain\user> and providing the password . But in my case i will have to ship the ini file with the product and dont the the settings on the customer system.
So i cannot use domain user.

Try removing the unused parameters (e.g. SQLBROWSERPASSWORD=, ASACCOUNT=, etc). When using a built-in account the password parameter is not necessary. Also, if you're installing on a localized OS (e.g. German or French) you need to pass the localized version of the built-in account. For example, Local System on a German OS is: NT-AUTORIT?T\SYSTEM

You can find the complete list in the setup help file, setupsql9.chm, under the topic Setting Up Windows Service Accounts.

If you still get errors please post your entire .ini file here.

Dan|||

Hello Dan,

Thanks for your reply.

I have made changes as per your suggestions , but still getting the validation error.

Last Action : Validate_ServiceAccounts
Error String : SQL Server Setup was unable to validate the account or accounts you provided. To continue, verify that the user name, password, and domain name are correct, or provide another user account for SQL Server service login.
The logon account cannot be validated for the service SQL Browser.
Error Number : 29609

Here is the test.ini file.

-
[Options]
;--
; If USERNAME or COMPANYNAME are not specified, the default operating system username and company name values for the server are used.
; Note: If names contain spaces, surround the names with quotes.

USERNAME=test
COMPANYNAME=test
;--
; Usage: PIDKEY=ABCDE12345FGHIJ67890KLMNO (This is not an actual key value.)

; NOTE: For the SQL Server 2005 CTP releases, the following PIDKEY command is not required
; because the PIDKEY parameter for the MSI file is preset. However, the final released version
; of SQL Server 2005 will require the PIDKEY parameter.
; NOTE: PIDKEY is not required for SQL Server Express Edition.
; NOTE: Do not include "-" in the PIDKEY.

;PIDKEY=
;--
; INSTALLSQLDIR specifies the location for the instance specific binary files.
; Default location is: %ProgramFiles%\Microsoft SQL Server\
; To use the default path, do not specify the following parameter.

; NOTE: INSTALLSQLDIR is REQUIRED for clustered installations and must point to a local
; drive for which the drive letter exists on all nodes in the cluster definition.
; NOTE: If there is a space in a specified path, surround the path with quotes
; and end every path with a '\'.

INSTALLSQLDIR="C:\Program Files\Microsoft SQL Server\"
;--
; INSTALLSQLSHAREDDIR specifies a custom location for Integration Services
; Notification Services, Client Components, SQL Server Books Online and Samples.
; To use the default path, do not specify the following parameter. Default path is %ProgramFiles%\Microsoft SQL Server\

; If Tools components are already installed on the computer, this parameter is ignored.
; NOTE: If there is a space in a specified path, surround the path with quotes
; and end every path with a '\'.

; The installation paths will be:
;<InstallDir>\90\DTS
;<InstallDir>\90\Notification
;<InstallDir>\90\Tools

INSTALLSQLSHAREDDIR=
;--
; INSTALLSQLDATADIR specifies the location for the SQL Server data files.
; Default: INSTALLSQLDIR\Data\
; To use the default path, do not specify the following parameter.

; NOTE: INSTALLSQLDATADIR is REQUIRED for clustered installations and must point to a
; shared drive which is a member of the cluster group specified for installation.
; NOTE: If there is a space in a specified path, surround the path with quotes
; and end every path with a '\'.

INSTALLSQLDATADIR=
;--
; INSTALLASDATADIR specifies the location for the Analysis Server Data Files.
; Default: INSTALLSQLDIR\Data\
; If Analysis Server is already installed on the computer, this parameter is ignored.
; To use the default path, do not specify the following parameter.

; NOTE: Do not use with a SQL Server Express installation.
; NOTE: If there is a space in a specified path, surround the path with quotes
; and end every path with a '\'.

INSTALLASDATADIR=
;--
; ADDLOCAL specifies which components to install. If ADDLOCAL is not
; specified, setup will fail.
; See SQL Server Books Online for more information on this topic.

ADDLOCAL=SQL_Engine,SQL_Data_Files,SQL_Replication,SQL_FullText,Client_Components,Connectivity,SQL_Tools90,SQL_Profiler90,SQLXML,SQL_Documentation,SQL_BooksOnline,SQL_SQLServerBooksOnline

INSTANCENAME=MSSQLSERVER
;--
; The UPGRADE property specifies which product to upgrade.
; The allowed values are SQL_Engine, RS_Server and AS_Server.
; If the UPGRADE option is specified, the INSTANCENAME parameter
; is REQUIRED to define which instance to upgrade.

;--
; The services for SQL Server and Analysis Server are set auto start. To use the *ACCOUNT settings
; make sure to specify the DOMAIN, e.g. SQLACCOUNT=DOMAINNAME\ACCOUNT
; NOTE: When installing SQL_Engine 3 accounts are REQUIRED: SQLACCOUNT, AGTACCOUNT and SQLBROWSERACCOUNT.
; SQLACCOUNT Examples:
; SQLACCOUNT=<domain\user>
; SQLACCOUNT="NT AUTHORITY\SYSTEM"
; SQLACCOUNT="NT AUTHORITY\NETWORK SERVICE"
; SQLACCOUNT="NT AUTHORITY\LOCAL SERVICE"

;Note that if SQLBrowser is already installed, SQLBROWSERACCOUNT and SQLBROWSERPASSWORD are ignored.
SQLBROWSERACCOUNT= "NT AUTHORITY\LOCAL SYSTEM"
;SQLBROWSERPASSWORD=

SQLACCOUNT="NT AUTHORITY\LOCAL SYSTEM"
;SQLPASSWORD=

AGTACCOUNT="NT AUTHORITY\LOCAL SYSTEM"
;AGTPASSWORD=

;ASACCOUNT=
;ASPASSWORD=

;RSACCOUNT=
;RSPASSWORD=
;--
; To use the *AUTOSTART features, specify 1 to start automatically or 0 to start manually.
; NOTE: If you decide to start SQL Agent automatically, then SQL is also started automatically.
; If *AUTOSTART is not specified on the command line, startup is set to manual.

SQLBROWSERAUTOSTART=1
SQLAUTOSTART=1
AGTAUTOSTART=1
ASAUTOSTART=0
RSAUTOSTART=0
;--
; To use Mixed mode authentication, use SECURITYMODE=SQL.
; If SECURITYMODE=SQL is not specified, then Windows Authentication only will be used by default.
; If you use SQL Authentication, you are REQUIRED to provide a strong system administrator (SA) password.
; If you use Windows Authentication, the SA account will be disabled.
; To set SA password specify SAPWD.

SECURITYMODE=SQL
SAPWD=Ericsson
;--
; SQLCOLLATION specifies the collation for Database Services.
; ASCOLLATION specifies the collation for Analysis Server.
; See SQL Server Books Online for more information on collation options.

SQLCOLLATION=SQL_Latin1_General_Cp1_CS_AS
ASCOLLATION=SQL_Latin1_General_Cp1_CS_AS
;--

I am not able to figure out what is wrong with this file.
However as specified in the setupsql9.chm file i am successfully installing from
command line using

Start /wait <DVD Drive>\setup.exe /qn INSTANCENAME=<InstanceName> ADDLOCAL=SQL_Engine,SQL_Replication SAPWD=<StrongPassword>

Here nothing is specified about the service accounts . It seems specifying them
i am gettting into trouble.

Regards
Ray

|||

I have tried removing all the accounts related information from the inin file . Then installation fails with

Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_DNASERVER3_SQL.log
Last Action : SetUnattendedSvcAccountProp
Error String : SQL Server Setup has determined that the following account properties are not specified: 'SQLBROWSERACCOUNT, AGTACCOUNT, SQLACCOUNT' . The properties specify the startup account for the services that are installed. To proceed, refer to the template.ini and set the properties to valid account names. If you are specifying a windows user account, you must also specify the password for the account.
Error Number : 28006

Ray

|||

Well the ini file should be like this ..
[snip]
SQLACCOUNT="NT AUTHORITY\SYSTEM"
;SQLPASSWORD=

AGTACCOUNT="NT AUTHORITY\SYSTEM"
;AGTPASSWORD=

SQLBROWSERACCOUNT= "NT AUTHORITY\SYSTEM"
;SQLBROWSERPASSWORD=

;ASACCOUNT=
;ASPASSWORD=

;RSACCOUNT=
;RSPASSWORD=
[snip]

I had put "NT AUTHORITY\LOCAL SYSTEM" instead.. A very painful oversight.

However there is a new problem . On 2003 server installation goes on just fine
but on 2000 server it fails with ->[Microsoft][SQL Native Client]Encryption not supported on the client. Refer to the blah blah blah.

On 2003 i have cryptography sercices running ...
Has neone faced this problem before

|||

Well the ini file should be like this ..
[snip]
SQLACCOUNT="NT AUTHORITY\SYSTEM"
;SQLPASSWORD=

AGTACCOUNT="NT AUTHORITY\SYSTEM"
;AGTPASSWORD=

SQLBROWSERACCOUNT= "NT AUTHORITY\SYSTEM"
;SQLBROWSERPASSWORD=

;ASACCOUNT=
;ASPASSWORD=

;RSACCOUNT=
;RSPASSWORD=
[snip]

I had put "NT AUTHORITY\LOCAL SYSTEM" instead.. A very painful oversight.

On 2003 i have cryptography sercices running ...
Has neone faced this problem before?

Ray

error during installing SP3

Hi
I've got following error during installing SP3
by running this file Sql2kasp3.exe after successfully
installation sql 2ksp3.exe,
(SQL server 2000,server station)
"an error occurred during move data process : -145"
Thanks for any reply
--
Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/Are you running analysis services?
--
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
"RM" <m_r1824@.yahoo.co.uk> wrote in message
news:opr1kakxwshqligo@.msnews.microsoft.com...
> Hi
> I've got following error during installing SP3
> by running this file Sql2kasp3.exe after successfully
> installation sql 2ksp3.exe,
> (SQL server 2000,server station)
> "an error occurred during move data process : -145"
> Thanks for any reply
> --
> Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/sql

Error during installation process

Microsoft SQL Server 2005 Setup
-

The setup failed to get IID_IIMSAdminBase object. The error code is -2147467262.

Hi there,

I have checked every possible site for this error but unable to find any solution. I received the above alert message during the installation of SQL2k5, Reporting Services. I am using window xp with sp2.

When click OK to alert box then it rollback all installed components of Reporting Services.

Please help.

Cheers,

Zafar.

I believe you have a typo on the error message you have listed. I believe it actually states that it can not find the IIS Imsadminbase. This is the metabase (http://msdn2.microsoft.com/en-us/library/ms525941.aspx). I would remove IIS and then add it back and try the SSRS installation again.

Larry

error during installation of sql server 2005

I have sql server 2000 installed on my PC. Now it is giving following error during installation of sql server 2005.

"The procedure entry point _vswprintf_c_l could not be located in the dynamic link
library MSVCR80.dll."

What can be wrong?I would suggest posting this to SQL Server Setup & Upgrade forum for faster response.

Thanks,
-Vineet Rao

Error during installation of reporting services

Hi,
I've stuck with an error message and I can't sort it out. I am trying to
install a standard reporting service on a server separated from database
server.
Web server (report services): no domain
Databasebase server: a member of a domain.
I can install RS with domain authentication mode but I can't with SQL
authentication such as sa.
Errror message:
login failed for user '(null)'. reason: not associated with a trusted sql
server connection.
Anyone have an workaround for this error?
ThanksI found that using setup /i command lines and I did without any problem.
"Oliver" <dummy@.hotmail.com> wrote in message
news:eRbesy9EFHA.1936@.TK2MSFTNGP14.phx.gbl...
> Hi,
> I've stuck with an error message and I can't sort it out. I am trying to
> install a standard reporting service on a server separated from database
> server.
> Web server (report services): no domain
> Databasebase server: a member of a domain.
> I can install RS with domain authentication mode but I can't with SQL
> authentication such as sa.
> Errror message:
> login failed for user '(null)'. reason: not associated with a trusted sql
> server connection.
> Anyone have an workaround for this error?
> Thanks
>|||Running setup with the /i command line did not have any impact on this issue
for me.
"Oliver" wrote:
> I found that using setup /i command lines and I did without any problem.
> "Oliver" <dummy@.hotmail.com> wrote in message
> news:eRbesy9EFHA.1936@.TK2MSFTNGP14.phx.gbl...
> > Hi,
> >
> > I've stuck with an error message and I can't sort it out. I am trying to
> > install a standard reporting service on a server separated from database
> > server.
> > Web server (report services): no domain
> > Databasebase server: a member of a domain.
> >
> > I can install RS with domain authentication mode but I can't with SQL
> > authentication such as sa.
> >
> > Errror message:
> > login failed for user '(null)'. reason: not associated with a trusted sql
> > server connection.
> >
> > Anyone have an workaround for this error?
> >
> > Thanks
> >
> >
>
>

Error during installation

I was installing SQL Server 2005 Standard Edition on Windows 2000 server. During the prerequisites installation .NET 2.0 installed sucessfully but unable to install Microsoft SQL Native Client and produce an error.

Error occurred during installation:

Error 1619 installing Microsoft SQL Native Client. See log file for more detailed information. This installation package could not be opened. Varify that the package exists and that you can access it, or contact the application vendor to valify that this is a valid Windows Installer package.

Log File Errors:

=== Verbose logging started: 7/24/200616:04:11Build type: SHIP UNICODE 3.01.4000.2435Calling process: C:\WINNT\system32\msiexec.exe ===

MSI (c) (04:98) [16:04:11:359]: Resetting cached policy values

MSI (c) (04:98) [16:04:11:359]: Machine policy value 'Debug' is 0

MSI (c) (04:98) [16:04:11:359]: ******* RunEngine:

******* Product: F:\MS SQL Server 2005\Disk 1\setup\sqlncli.msi

******* Action:

******* CommandLine: **********

MSI (c) (04:98) [16:04:11:359]: Client-side and UI is none or basic: Running entire install on the server.

MSI (c) (04:98) [16:04:11:359]: Grabbed execution mutex.

MSI (c) (04:98) [16:04:11:437]: Cloaking enabled.

MSI (c) (04:98) [16:04:11:437]: Attempting to enable all disabled priveleges before calling Install on Server

MSI (c) (04:98) [16:04:11:468]: Incrementing counter to disable shutdown. Counter after increment: 0

MSI (s) (D0:C0) [16:04:11:515]: Grabbed execution mutex.

MSI (s) (D0:C8) [16:04:11:515]: Resetting cached policy values

MSI (s) (D0:C8) [16:04:11:515]: Machine policy value 'Debug' is 0

MSI (s) (D0:C8) [16:04:11:515]: ******* RunEngine:

******* Product: F:\MS SQL Server 2005\Disk 1\setup\sqlncli.msi

******* Action:

******* CommandLine: **********

MSI (s) (D0:C8) [16:04:11:531]: Note: 1: 2203 2: F:\MS SQL Server 2005\Disk 1\setup\sqlncli.msi 3: -2147287037

MSI (s) (D0:C8) [16:04:11:531]: MainEngineThread is returning 3

MSI (c) (04:98) [16:04:11:531]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.Counter after decrement: -1

MSI (c) (04:98) [16:04:11:531]: MainEngineThread is returning 3

=== Verbose logging stopped: 7/24/200616:04:11 ===

Any ideas. Please help....

Thanks.

Zafar.

Zafar, if you're attempting to install SQL Server 2005 onto Windows Server 2000 via a network share it will not work. You either have to put the CD/DVD directly into the server's reader drive or copy the files from the network share to the local hard drive of the server to perform the installation.sql

error during install SP3

quote:

> Hi
> I've SQL server 2000 on server station and wanted
> to install SP3,at first installation of sql2ksp3.exe
> was completed successfully,and following error appearred
> on running sql2kasp3.exe:
> "An error occurred during move data process : -145"
> why ?
> what's wrong?
> any help would be greatly appreciated.
> --
> --
> Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/

|||no ,I didn't install completely
an error casued to exit it,
On Sun, 11 Jan 2004 12:07:47 +0000 (UTC), John Bell
<jbellnewsposts@.hotmail.com> wrote:

quote:

> Hi
> Sql2kasp3.exe Updates Analysis Services is this actually installed?
> John
> "RM" <m_r1824@.yahoo.co.uk> wrote in message
> news:opr1linpoqhqligo@.msnews.microsoft.com...
>

Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/|||Hi
Sql2kasp3.exe will update your existing install of Analysis services,
you need Analysis services to already be installed and working before
applying this patch.
John
RM <m_r1824@.yahoo.co.uk> wrote in message news:<opr1nbozoghqligo@.msnews.microsoft.com>...[QUOTE][c
olor=darkred]
> no ,I didn't install completely
> an error casued to exit it,
> On Sun, 11 Jan 2004 12:07:47 +0000 (UTC), John Bell
> <jbellnewsposts@.hotmail.com> wrote:
>

error during install SP3

Hi
I've SQL server 2000 on server station and wanted
to install SP3,at first installation of sql2ksp3.exe
was completed successfully,and following error appearred
on running sql2kasp3.exe:
"An error occurred during move data process : -145"
why ?
what's wrong?
any help would be greatly appreciated.
--
--
Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/Hi
Sql2kasp3.exe Updates Analysis Services is this actually installed?
John
"RM" <m_r1824@.yahoo.co.uk> wrote in message
news:opr1linpoqhqligo@.msnews.microsoft.com...
> Hi
> I've SQL server 2000 on server station and wanted
> to install SP3,at first installation of sql2ksp3.exe
> was completed successfully,and following error appearred
> on running sql2kasp3.exe:
> "An error occurred during move data process : -145"
> why ?
> what's wrong?
> any help would be greatly appreciated.
> --
> --
> Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/|||no ,I didn't install completely
an error casued to exit it,
On Sun, 11 Jan 2004 12:07:47 +0000 (UTC), John Bell
<jbellnewsposts@.hotmail.com> wrote:
> Hi
> Sql2kasp3.exe Updates Analysis Services is this actually installed?
> John
> "RM" <m_r1824@.yahoo.co.uk> wrote in message
> news:opr1linpoqhqligo@.msnews.microsoft.com...
>> Hi
>> I've SQL server 2000 on server station and wanted
>> to install SP3,at first installation of sql2ksp3.exe
>> was completed successfully,and following error appearred
>> on running sql2kasp3.exe:
>> "An error occurred during move data process : -145"
>> why ?
>> what's wrong?
>> any help would be greatly appreciated.
>> --
>> --
>> Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/
>
Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/|||Hi
Sql2kasp3.exe will update your existing install of Analysis services,
you need Analysis services to already be installed and working before
applying this patch.
John
RM <m_r1824@.yahoo.co.uk> wrote in message news:<opr1nbozoghqligo@.msnews.microsoft.com>...
> no ,I didn't install completely
> an error casued to exit it,
> On Sun, 11 Jan 2004 12:07:47 +0000 (UTC), John Bell
> <jbellnewsposts@.hotmail.com> wrote:
> > Hi
> >
> > Sql2kasp3.exe Updates Analysis Services is this actually installed?
> >
> > John
> >
> > "RM" <m_r1824@.yahoo.co.uk> wrote in message
> > news:opr1linpoqhqligo@.msnews.microsoft.com...
> >> Hi
> >>
> >> I've SQL server 2000 on server station and wanted
> >> to install SP3,at first installation of sql2ksp3.exe
> >> was completed successfully,and following error appearred
> >> on running sql2kasp3.exe:
> >>
> >> "An error occurred during move data process : -145"
> >>
> >> why ?
> >> what's wrong?
> >> any help would be greatly appreciated.
> >>
> >> --
> >>
> >> --
> >> Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/
> >
> >

Thursday, March 22, 2012

Error deploying SSIS package to SQL Server

I am getting strange error on deploying ssis package to SQL Server.

TITLE: Package Installation Wizard
-

Could not save the package "C:\Documents and Settings\Administrator\My Documents\Visual Studio 2005\Projects\Integration Services Project1\Integration Services Project1\bin\Deployment\DataTrans.dtsx" to SQL Server "(local)".

-
ADDITIONAL INFORMATION:

The SaveToSQLServer method has encountered OLE DB error code 0x80004005 ([DBNETLIB][ConnectionOpen (PreLoginHandshake()).]Encryption not supported on SQL Server.). The SQL statement that was issued has failed.

-
BUTTONS:

OK
-

=====================================================
=============================================

=============================================

-
Program Location:

at Microsoft.SqlServer.Dts.Runtime.Application.SaveToSqlServer(Package package, IDTSEvents events, String serverName, String serverUserName, String serverPassword)
at Microsoft.SqlServer.Dts.Deployment.DtsInstaller.SavePackageToSqlServer(WizardInputs wizardInputs, String packagePassword, Boolean bUseSeverEncryption, String serverName, String userName, String password, String packageFilePath, List`1 configFileNames)
at Microsoft.SqlServer.Dts.Deployment.DtsInstaller.InstallPackagesToSqlServer(WizardInputs wizardInputs)

=============================================

-
Program Location:

at Microsoft.SqlServer.Dts.Runtime.Wrapper.ApplicationClass.SaveToSQLServer(IDTSPackage90 Package, IDTSEvents90 pEvents, String ServerName, String ServerUserName, String ServerPassword)
at Microsoft.SqlServer.Dts.Runtime.Application.SaveToSqlServer(Package package, IDTSEvents events, String serverName, String serverUserName, String serverPassword)

Ashwani Sharma has the following solution:

As you may know, the SSIS runtime forces use of encryption when loading or saving packages from/to SQL Server. As part of that, certificates have to be present and validated by the transport layer. If certificates are not properly setup, users get errors during deployment to SQL Server that say something like this:

The SaveToSQLServer method has encountered OLE DB error code 0x80004005 ([DBNETLIB][ConnectionOpen (PreLoginHandshake()).]Encryption not supported on SQL Server.). The SQL statement that was issued has failed.

In the current CTP builds, if you get this error message, you'll need to get a provisioned certificate and install it. A couple of links that describe this well are http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q276553 and http://support.microsoft.com/kb/318605.

We've been working with several customers in the past who ran into this issue and we weren't able to figure out what was going on due to the infrastructure used here in Redmond. Thanks for your patience, guys!

Hopefully we'll take care of this during setup so that those of you who did run into this issue don't anymore.

|||

Hi all,

I'm having the same issue in the Release version of developer edition SQL 2005. Now, the only caveat is that I also have SQL Express installed from visual studion 2005, which was installed first. Would this have any affect on me deploying SSIS Packages to my machine?

|||

I am also receiving this error:

===================================

Save to SQL Server failed.

No description found (SQL Server Import and Export Wizard)

===================================

No description found

Program Location:

I am running the Release version of Dev SQL Server 2005.

Any Ideas?

|||

Hi,

I would recommend to open a new thread since this "old" one is based on a CTP and so your problem might not get the attention it deservs...

|||Yes, I have an idea! I just resolved this problem, and hopefully it will work for you as well.

Found an answer for a very similar error burried in a comment here: Oren Ellenbogen

Basically, this is a symptom of your MSXML registration being corrupted. Reregister MSXML by running these two commands:

regsvr32.exe msxml3.dll

regsvr32.exe msxml6.dll

I wasn't sure if the issue would be on the client or the server, as both of them would probably need to have MSXML working nicely. So I ran those two commands in both places, and then was (HAPPILY!) able to deploy my SSIS packages in comfort.

There are curse words involved, but I wrote about it in my blog. So I could put in images & the answer outside of a long, old thread on MSDN.|||

Kapil Aggarwal wrote:
Ashwani Sharma has the following solution:
As you may know, the SSIS runtime forces use of encryption when loading or saving packages from/to SQL Server. As part of that, certificates have to be present and validated by the transport layer. If certificates are not properly setup, users get errors during deployment to SQL Server that say something like this:
The SaveToSQLServer method has encountered OLE DB error code 0x80004005 ([DBNETLIB][ConnectionOpen (PreLoginHandshake()).]Encryption not supported on SQL Server.). The SQL statement that was issued has failed.
In the current CTP builds, if you get this error message, you'll need to get a provisioned certificate and install it.

is it absolutely necessary to get a provisioned certificate if the package is saved to sql server 2005? sql server 2005 provides a CREATE CERTIFICATE statment which creates and installs a certificate.

also, is configuring encryption on sql server 2005 different from previous versions of sql server?

|||

Hi,

The user who is trying to save the SSIS package in SQL Server MSDB database should be the member of all "dts" related roles like dtsadmin in msdb database.

Please try it will work.

Thanks,

Arijit

Error deploying SSIS package to SQL Server

I am getting strange error on deploying ssis package to SQL Server.

TITLE: Package Installation Wizard
-

-
ADDITIONAL INFORMATION:

-
BUTTONS:

OK
-

=====================================================
=============================================

=============================================

-
Program Location:

=============================================

-
Program Location:

Ashwani Sharma has the following solution:

Hopefully we'll take care of this during setup so that those of you who did run into this issue don't anymore.

|||

Hi all,

|||

I am also receiving this error:

===================================

Save to SQL Server failed.

No description found (SQL Server Import and Export Wizard)

===================================

No description found

Program Location:

I am running the Release version of Dev SQL Server 2005.

Any Ideas?

|||

Hi,

I would recommend to open a new thread since this "old" one is based on a CTP and so your problem might not get the attention it deservs...

|||Yes, I have an idea! I just resolved this problem, and hopefully it will work for you as well.

Found an answer for a very similar error burried in a comment here: Oren Ellenbogen

Basically, this is a symptom of your MSXML registration being corrupted. Reregister MSXML by running these two commands:

regsvr32.exe msxml3.dll

regsvr32.exe msxml6.dll

There are curse words involved, but I wrote about it in my blog. So I could put in images & the answer outside of a long, old thread on MSDN.|||

Kapil Aggarwal wrote:
Ashwani Sharma has the following solution:
As you may know, the SSIS runtime forces use of encryption when loading or saving packages from/to SQL Server. As part of that, certificates have to be present and validated by the transport layer. If certificates are not properly setup, users get errors during deployment to SQL Server that say something like this:
The SaveToSQLServer method has encountered OLE DB error code 0x80004005 ([DBNETLIB][ConnectionOpen (PreLoginHandshake()).]Encryption not supported on SQL Server.). The SQL statement that was issued has failed.
In the current CTP builds, if you get this error message, you'll need to get a provisioned certificate and install it.

also, is configuring encryption on sql server 2005 different from previous versions of sql server?

|||

Hi,

The user who is trying to save the SSIS package in SQL Server MSDB database should be the member of all "dts" related roles like dtsadmin in msdb database.

Please try it will work.

Thanks,

Arijit

Error deploying SSIS package to SQL Server

I am getting strange error on deploying ssis package to SQL Server.

TITLE: Package Installation Wizard
-

-
ADDITIONAL INFORMATION:

-
BUTTONS:

OK
-

=====================================================
=============================================

=============================================

-
Program Location:

=============================================

-
Program Location:

Ashwani Sharma has the following solution:

Hopefully we'll take care of this during setup so that those of you who did run into this issue don't anymore.

|||

Hi all,

|||

I am also receiving this error:

===================================

Save to SQL Server failed.

No description found (SQL Server Import and Export Wizard)

===================================

No description found

Program Location:

I am running the Release version of Dev SQL Server 2005.

Any Ideas?

|||

Hi,

I would recommend to open a new thread since this "old" one is based on a CTP and so your problem might not get the attention it deservs...

|||Yes, I have an idea! I just resolved this problem, and hopefully it will work for you as well.

Found an answer for a very similar error burried in a comment here: Oren Ellenbogen

Basically, this is a symptom of your MSXML registration being corrupted. Reregister MSXML by running these two commands:

regsvr32.exe msxml3.dll

regsvr32.exe msxml6.dll

There are curse words involved, but I wrote about it in my blog. So I could put in images & the answer outside of a long, old thread on MSDN.|||

Kapil Aggarwal wrote:
Ashwani Sharma has the following solution:
As you may know, the SSIS runtime forces use of encryption when loading or saving packages from/to SQL Server. As part of that, certificates have to be present and validated by the transport layer. If certificates are not properly setup, users get errors during deployment to SQL Server that say something like this:
The SaveToSQLServer method has encountered OLE DB error code 0x80004005 ([DBNETLIB][ConnectionOpen (PreLoginHandshake()).]Encryption not supported on SQL Server.). The SQL statement that was issued has failed.
In the current CTP builds, if you get this error message, you'll need to get a provisioned certificate and install it.

also, is configuring encryption on sql server 2005 different from previous versions of sql server?

|||

Hi,

The user who is trying to save the SSIS package in SQL Server MSDB database should be the member of all "dts" related roles like dtsadmin in msdb database.

Please try it will work.

Thanks,

Arijit

Error deploying SSIS package to SQL Server

I am getting strange error on deploying ssis package to SQL Server.

TITLE: Package Installation Wizard
-

-
ADDITIONAL INFORMATION:

-
BUTTONS:

OK
-

=====================================================
=============================================

=============================================

-
Program Location:

=============================================

-
Program Location:

Ashwani Sharma has the following solution:

Hopefully we'll take care of this during setup so that those of you who did run into this issue don't anymore.

|||

Hi all,

|||

I am also receiving this error:

===================================

Save to SQL Server failed.

No description found (SQL Server Import and Export Wizard)

===================================

No description found

Program Location:

I am running the Release version of Dev SQL Server 2005.

Any Ideas?

|||

Hi,

I would recommend to open a new thread since this "old" one is based on a CTP and so your problem might not get the attention it deservs...

|||Yes, I have an idea! I just resolved this problem, and hopefully it will work for you as well.

Found an answer for a very similar error burried in a comment here: Oren Ellenbogen

Basically, this is a symptom of your MSXML registration being corrupted. Reregister MSXML by running these two commands:

regsvr32.exe msxml3.dll
regsvr32.exe msxml6.dll

I wasn't sure if the issue would be on the client or the server, as both of them would probably need to have MSXML working nicely. So I ran those two commands in both places, and then was (HAPPILY!) able to deploy my SSIS packages in comfort.

There are curse words involved, but I wrote about it in my blog. So I could put in images & the answer outside of a long, old thread on MSDN.
|||

Kapil Aggarwal wrote:
Ashwani Sharma has the following solution:

As you may know, the SSIS runtime forces use of encryption when loading or saving packages from/to SQL Server. As part of that, certificates have to be present and validated by the transport layer. If certificates are not properly setup, users get errors during deployment to SQL Server that say something like this:

The SaveToSQLServer method has encountered OLE DB error code 0x80004005 ([DBNETLIB][ConnectionOpen (PreLoginHandshake()).]Encryption not supported on SQL Server.). The SQL statement that was issued has failed.

In the current CTP builds, if you get this error message, you'll need to get a provisioned certificate and install it.

also, is configuring encryption on sql server 2005 different from previous versions of sql server?

|||

Hi,

The user who is trying to save the SSIS package in SQL Server MSDB database should be the member of all "dts" related roles like dtsadmin in msdb database.

Please try it will work.

Thanks,

Arijit

Error deploying SSIS package to SQL Server

I am getting strange error on deploying ssis package to SQL Server.

TITLE: Package Installation Wizard
-

-
ADDITIONAL INFORMATION:

-
BUTTONS:

OK
-

=====================================================
=============================================

=============================================

-
Program Location:

=============================================

-
Program Location:

Ashwani Sharma has the following solution:

Hopefully we'll take care of this during setup so that those of you who did run into this issue don't anymore.

|||

Hi all,

|||

I am also receiving this error:

===================================

Save to SQL Server failed.

No description found (SQL Server Import and Export Wizard)

===================================

No description found

Program Location:

I am running the Release version of Dev SQL Server 2005.

Any Ideas?

|||

Hi,

I would recommend to open a new thread since this "old" one is based on a CTP and so your problem might not get the attention it deservs...

|||Yes, I have an idea! I just resolved this problem, and hopefully it will work for you as well.

Found an answer for a very similar error burried in a comment here: Oren Ellenbogen

Basically, this is a symptom of your MSXML registration being corrupted. Reregister MSXML by running these two commands:

There are curse words involved, but I wrote about it in my blog. So I could put in images & the answer outside of a long, old thread on MSDN.
|||

Kapil Aggarwal wrote:
Ashwani Sharma has the following solution:

As you may know, the SSIS runtime forces use of encryption when loading or saving packages from/to SQL Server. As part of that, certificates have to be present and validated by the transport layer. If certificates are not properly setup, users get errors during deployment to SQL Server that say something like this:

The SaveToSQLServer method has encountered OLE DB error code 0x80004005 ([DBNETLIB][ConnectionOpen (PreLoginHandshake()).]Encryption not supported on SQL Server.). The SQL statement that was issued has failed.

In the current CTP builds, if you get this error message, you'll need to get a provisioned certificate and install it.

also, is configuring encryption on sql server 2005 different from previous versions of sql server?

|||

Hi,

The user who is trying to save the SSIS package in SQL Server MSDB database should be the member of all "dts" related roles like dtsadmin in msdb database.

Please try it will work.

Thanks,

Arijit

sql

Wednesday, March 21, 2012

Error Data bases not compatible, Installation Reporting services

Hi,
I install Report services (standard, developer, enterprise edition) on sql
server 2000 personal edition, and windows 2003 server enterprise, during the
installation, when creating the data base sends the following message of
error "This version of the data base of the Reporting services is not
compatible with the version of SQL server 2000"
all the scene this in Spanish language.
I do not understand because, help me please.
excuse I do not speak ingles, thanksYou are posting the same problem multiple times. The answer will be the
same. Personal edition will not work. See my other post which has links to
the MS website that documents this.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Arturo Alegria Palacios" <Arturo Alegria
Palacios@.discussions.microsoft.com> wrote in message
news:89C41CA4-B525-49B2-980D-BB39CDE4E018@.microsoft.com...
> Hi,
> I install Report services (standard, developer, enterprise edition) on sql
> server 2000 personal edition, and windows 2003 server enterprise, during
> the
> installation, when creating the data base sends the following message of
> error "This version of the data base of the Reporting services is not
> compatible with the version of SQL server 2000"
> all the scene this in Spanish language.
> I do not understand because, help me please.
> excuse I do not speak ingles, thanks|||Thanks bruce, I am going to verify the documentation of website, will verify
the scene where this executing itself now
"Bruce L-C [MVP]" wrote:
> You are posting the same problem multiple times. The answer will be the
> same. Personal edition will not work. See my other post which has links to
> the MS website that documents this.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Arturo Alegria Palacios" <Arturo Alegria
> Palacios@.discussions.microsoft.com> wrote in message
> news:89C41CA4-B525-49B2-980D-BB39CDE4E018@.microsoft.com...
> > Hi,
> > I install Report services (standard, developer, enterprise edition) on sql
> > server 2000 personal edition, and windows 2003 server enterprise, during
> > the
> > installation, when creating the data base sends the following message of
> > error "This version of the data base of the Reporting services is not
> > compatible with the version of SQL server 2000"
> >
> > all the scene this in Spanish language.
> >
> > I do not understand because, help me please.
> >
> > excuse I do not speak ingles, thanks
>
>

Error creating new SSIS project

In my local client installation of the BI tools, I get the following error when simply creating an SSIS project and the default empty Package tries to display on the screen.

Index (zero based) must be greater than or equal to zero and less than the size of the argument list.

I can use the Reporting Services designer with no problems, and I can use SSIS from the client tools on the server. It is just on my local PC that I get this error. I have completely uninstalled all the tools and reinstalled with no luck.

PLEASE HELP!

If anyone can help, please reply. I am unable to use SSIS AT ALL right now because a new package will only display this error message. And this is the purchased version, not the evaluation copy.

Here is the full message

Microsoft Visual Studio is unable to load this document:
Index (zero based) must be greater than or equal to zero and less than the size of the argument list.

|||

I know it looks like I'm being a pest by bumping my post again, but I am not able to use SSIS at all on my PC. I HAVE TO get this resolved.

I am on Windows XP Pro fully patched and updated. I had SQL Express on my PC before and have since uninstalled it to see if that would help.

PLEASE HELP!!!

error creating mdf - Connection to SQL server files (*.mdf) require SQL express 2005 to...

Connection to SQL server files (*.mdf) require SQL express 2005 to function properly. please verify the installation of the component or download fromhttp://go.microsoft.com/fwlink/?linkid=49251

I AM GOING TO RIP MY HAIR OUT WITH THIS PROBLEM. I have reinstalled both sql server express 2005 and VWD about 5 times with the same problem. please, please, please someone throw me a bone here and help me resolve this problem.

When I create a new EMPTY website and I rightclick on my website in the solution explorer and choose add item, I chooe SQL Database, I give it a name 'database.mdf' and click add. I get the following message:

you are attempting to add a database to an asp.net application. for a database to be gfenerally consumable in your site, it should be placed inside the 'app_data' folder. would you like to place the database inside the 'app_data' folder? I click YES (I know this message is normal)

then I get the following message:

Connection to SQL server files (*.mdf) require SQL express 2005 to function properly. please verify the installation of the component or download fromhttp://go.microsoft.com/fwlink/?linkid=49251

I can add anything else but this damn mdf file.

thanks for all your help in advance.

FYI to anyone who has had this problem and cannot find a resolution. I have found the solution in a another forum:

From:Brian Piesik -view profileDate:Mon, Feb 13 2006 3:20 pmEmail:Brian Piesik <bpie...@.community.nospam>Groups:microsoft.public.dotnet.framework.windowsforms

Not yet rated

Rating: show options

Thanks Jeffrey, the problem turned out to be a problem in Visual Studio
with an incorrect setting.

What I did was go into Tools, Options, Database Tools, Data Connections.

UnderSQLServer Instance Name (blank for default) i had the following
in there: MyComputerName\SQLEXPRESS

I changed it to the following: SQLEXPRESS

I also tested it just leaving it blank and working too.

Of course I would love to say a favorite end user quote "I never changed
it", but I'm too geeky to know that.

Happy Coding!

Brian Piesik

|||

Thanksbigdbingo, for this valuable post

Error Creating Maintenance Plan

I have a new installation of SQL 2005 x64 SP 1 Standard Edition installed on
Windows 2003 x64 SP 1 Standard Edition. I installed using unattended
install. In the ini file for unattended install I specified ADDLOCAL and
amoung other features I specified SQL_Tools90, which according to the
template.ini in the install file will install management tools. And I
thought they were installed because I can use SQLWB, Performacne tools,
configuration tools, etc. But when I tried to create a maintenance plan I
got the error below. So I ran an additional install manually and indicated
to install management tools. But the installer told me they were already
installed.
Also, I don't know if it makes a difference but I installed using the MSDN
iso image.
///////////////////////////////////////////////////////////////////////
Error Message:
The action you attempted to perform on a remote instance of SQL Server has
failed because the action requires a SQL Server component that is not
installed on the remote computer. To proceed, install SQL Server 2005
Management Tools on the remote computer, and then try again. For more
information, see "How to: Install SQL Server 2005 (Setup)" in SQL Server
2005 Books Online, or find the article on MSDN at
http://go.microsoft.com/fwlink/?LinkID=57083 . (ObjectExplorer)
For help, click: http://go.microsoft.com/fwlink/?LinkID=57083
///////////////////////////////////////////////////////////////////////
Please help!I found the solution - SSIS wasn't installed. We aren't using it at all so I
didn't install it. Apparently it's needed.
For due credit, this is where I found the problem:
http://sqljunkies.com/Forums/ShowPost.aspx?PostID=9920
Mark|||The issue is fixed in SP1. SSIS doesn't have to be installed
if you are on SP1. Refer to the maintenance plans section in
the following:
A list of the new features and improvements that are
included in SQL Server 2005 Service Pack 1
http://support.microsoft.com/?id=916940
-Sue
On Fri, 11 Aug 2006 16:13:52 -0600, "Mark Miller"
<mark_n_0-s*p..am@.maxpreps.com> wrote:

>I found the solution - SSIS wasn't installed. We aren't using it at all so
I
>didn't install it. Apparently it's needed.
>For due credit, this is where I found the problem:
>http://sqljunkies.com/Forums/ShowPost.aspx?PostID=9920
>Mark
>|||Thanks. You are right, however, the information on that page is wrong.
I ran SELECT @.@.VERSION and it returns "Microsoft SQL Server 2005 -
9.00.2047.00 (x64) Apr 14 2006 01:11:53"
Which matches the version number reported for SP 1 here:
http://www.microsoft.com/downloads/...&displaylang=en
The only thing that doesn't match up is the file size (the SP 1 install I
used is 311,007 KB) and the date 4/14 when the date in the link above is
4/18. I think I downloaded the SP from msdn. Could they be different?
I'm going to download the one from the link above and verify.
Mark|||I checked and according to the file properties in windows explorer, the two
files (the one I downloaded from MSDN and the one from
http://www.microsoft.com/downloads/...&displaylang=en )
are the exact same size, version number, and build date. So it appears that
Microsoft did NOT fix the bug in SP 1.
However, I would like to thank Sue for her response. It wasn't her fault the
documentation was incorrect.
Mark

Error Creating Maintenance Plan

I have a new installation of SQL 2005 x64 SP 1 Standard Edition installed on
Windows 2003 x64 SP 1 Standard Edition. I installed using unattended
install. In the ini file for unattended install I specified ADDLOCAL and
amoung other features I specified SQL_Tools90, which according to the
template.ini in the install file will install management tools. And I
thought they were installed because I can use SQLWB, Performacne tools,
configuration tools, etc. But when I tried to create a maintenance plan I
got the error below. So I ran an additional install manually and indicated
to install management tools. But the installer told me they were already
installed.
Also, I don't know if it makes a difference but I installed using the MSDN
iso image.
///////////////////////////////////////////////////////////////////////
Error Message:
The action you attempted to perform on a remote instance of SQL Server has
failed because the action requires a SQL Server component that is not
installed on the remote computer. To proceed, install SQL Server 2005
Management Tools on the remote computer, and then try again. For more
information, see "How to: Install SQL Server 2005 (Setup)" in SQL Server
2005 Books Online, or find the article on MSDN at
http://go.microsoft.com/fwlink/?LinkID=57083 . (ObjectExplorer)
For help, click: http://go.microsoft.com/fwlink/?LinkID=57083
///////////////////////////////////////////////////////////////////////
Please help!I found the solution - SSIS wasn't installed. We aren't using it at all so I
didn't install it. Apparently it's needed.
For due credit, this is where I found the problem:
http://sqljunkies.com/Forums/ShowPost.aspx?PostID=9920
Mark|||The issue is fixed in SP1. SSIS doesn't have to be installed
if you are on SP1. Refer to the maintenance plans section in
the following:
A list of the new features and improvements that are
included in SQL Server 2005 Service Pack 1
http://support.microsoft.com/?id=916940
-Sue
On Fri, 11 Aug 2006 16:13:52 -0600, "Mark Miller"
<mark_n_0-s*p..am@.maxpreps.com> wrote:
>I found the solution - SSIS wasn't installed. We aren't using it at all so I
>didn't install it. Apparently it's needed.
>For due credit, this is where I found the problem:
>http://sqljunkies.com/Forums/ShowPost.aspx?PostID=9920
>Mark
>|||Thanks. You are right, however, the information on that page is wrong.
I ran SELECT @.@.VERSION and it returns "Microsoft SQL Server 2005 -
9.00.2047.00 (x64) Apr 14 2006 01:11:53"
Which matches the version number reported for SP 1 here:
http://www.microsoft.com/downloads/details.aspx?familyid=CB6C71EA-D649-47FF-9176-E7CAC58FD4BC&displaylang=en
The only thing that doesn't match up is the file size (the SP 1 install I
used is 311,007 KB) and the date 4/14 when the date in the link above is
4/18. I think I downloaded the SP from msdn. Could they be different?
I'm going to download the one from the link above and verify.
Mark|||I checked and according to the file properties in windows explorer, the two
files (the one I downloaded from MSDN and the one from
http://www.microsoft.com/downloads/details.aspx?familyid=CB6C71EA-D649-47FF-9176-E7CAC58FD4BC&displaylang=en )
are the exact same size, version number, and build date. So it appears that
Microsoft did NOT fix the bug in SP 1.
However, I would like to thank Sue for her response. It wasn't her fault the
documentation was incorrect.
Mark

Sunday, February 26, 2012

error code sql server

Good morning
MOM server 2005 prompt this message during the installation
Failed to setup database security.
Error code: -2147217900 (user, group, or role 'SC DW DTS'
already exist in the current database)
what can i do in this casehttp://groups.google.co.uk/group/microsoft.public.mom/browse_thread/thread/9
fc353baf7bde8b8/45c77c865aeb54a8?lnk=st&q=user%2C+group%2C+or+role+'SC+DW+DT
S'+already+exists&rnum=1&hl=en#45c77c865aeb54a8
"Djeff" <e.djeff@.free.fr> wrote in message
news:mn.b33c7d5c80e5082d.46131@.free.fr...
> Good morning
> MOM server 2005 prompt this message during the installation
> Failed to setup database security.
> Error code: -2147217900 (user, group, or role 'SC DW DTS'
> already exist in the current database)
> what can i do in this case
>

Tuesday, March 27, 2012

Error encountered UNC path error during remote installation

Monday, March 26, 2012

error during quiet installation of June CTP.

error during installing SP3

Error during installation process

error during installation of sql server 2005

Error during installation of reporting services

Error during installation

error during install SP3

error during install SP3

Thursday, March 22, 2012

Error deploying SSIS package to SQL Server

Error deploying SSIS package to SQL Server

Error deploying SSIS package to SQL Server

Error deploying SSIS package to SQL Server

Error deploying SSIS package to SQL Server

Wednesday, March 21, 2012

Error Data bases not compatible, Installation Reporting services

Error creating new SSIS project

error creating mdf - Connection to SQL server files (*.mdf) require SQL express 2005 to...

Error Creating Maintenance Plan

Error Creating Maintenance Plan

Sunday, February 26, 2012

error code sql server

Error accessing report

Blog Archive

About Me