Showing posts with label environment. Show all posts
Showing posts with label environment. Show all posts

Wednesday, March 21, 2012

Error creating new SSIS project

When I start a new project the BI environment cannot open the DTSX package and I get only one tab with the message:

"microsoft visual studio is unable to load this document. Object reference not set to an instance of an object".

I tried uninstall and install of BI Development Studio as well as a repair install of Visual Studio 2005. None of which helped. Please help me to get this fixed.

Kind regards,

Neeva

Just to let you know, this problem seemed to have disappeared when I had to install SQL Server Express for a completely unrelated reason. I still don't understand it, but oh well..

Wednesday, March 7, 2012

Error connecting to datasource using bulk load

I am trying to use xml bulk load in a .net environment using vb.net.
The first issue I ran into was not being able to do a bulk load in a
multi-threaded environment. So I now have initiated a new thread prior
to trying to execute the bulk load. I am consistenly getting an unable
to connect to data source error. Does anyone have any ideas as to what
I may be doing incorrectly? The connection string is the same one I
use in other places without any issues.
Private Sub BulkLoadXML()
Dim bulkload As New Thread(New ThreadStart(AddressOf
ExecuteBulkCall))
bulkload.ApartmentState = ApartmentState.STA
bulkload.Start()
bulkload.Join()
End Sub
Private Sub ExecuteBulkCall()
Dim _bulkInstance As New SQLXMLBulkLoad3Class
_bulkInstance.ConnectionString = _strConn
_bulkInstance.ErrorLogFile = "c:\temp\xmlerror.log"
_bulkInstance.KeepIdentity = False
_bulkInstance.Execute("c:\SampleSchema.xsd",
"c:\SampleXMLData.xml")
End Sub
franksag
Posted via http://www.codecomments.com
What does the connection string look like? When you say it worked in other
places - what places are those?
Andrew Conrad
Microsoft Corp

Error connecting to datasource using bulk load

I am trying to use xml bulk load in a .net environment using vb.net. The fi
rst issue I ran into was not being able to do a bulk load in a multi-threade
d environment. So I now have initiated a new thread prior to trying to exec
ute the bulk load. I am consistenly getting an unable to connect to data so
urce error. Does anyone have any ideas as to what I may be doing incorrectly
? The connection string is the same one I use in other places without any i
ssues.
Private Sub BulkLoadXML()
Dim bulkload As New Thread(New ThreadStart(AddressOf ExecuteBulkCall
))
bulkload.ApartmentState = ApartmentState.STA
bulkload.Start()
bulkload.Join()
End Sub
Private Sub ExecuteBulkCall()
Dim _bulkInstance As New SQLXMLBulkLoad3Class
_bulkInstance.ConnectionString = _strConn
_bulkInstance.ErrorLogFile = "c:\temp\xmlerror.log"
_bulkInstance.KeepIdentity = False
_bulkInstance.Execute("c:\SampleSchema.xsd", "c:\SampleXMLData.xml")
End SubWhat does the connection string look like? When you say it worked in other
places - what places are those?
Andrew Conrad
Microsoft Corp|||thanks for getting back to me. I am able to connect to the database elsewhe
re in the application to call stored procedures and retrieve the data to dis
play. This is the only place within the application that I am unable to conn
ect. I suspect it has to do with the fact that I am calling within a single
thread. Here is the connect string:
"Data Source=(local);Initial Catalog=IOC;User ID=sg2user;password=sg2user"|||Try setting the Provider=sqloledb value in the connection string. Here's an
example from our docs of Bulkload in .NET:
[STAThread]
static void Main(string[] args)
{
try
{
SQLXMLBULKLOADLib.SQLXMLBulkLoad3Class objBL = new
SQLXMLBULKLOADLib.SQLXMLBulkLoad3Class();
objBL.ConnectionString =
" Provider=sqloledb;server=server;database
=databaseName;integrated
security=SSPI";
objBL.ErrorLogFile = "error.xml";
objBL.KeepIdentity = false;
objBL.Execute ("schema.xml","data.xml");
}
catch(Exception e)
{
Console.WriteLine(e.ToString());
}
}
"franksag" <franksag.1llvtp@.mail.codecomments.com> wrote in message
news:franksag.1llvtp@.mail.codecomments.com...
> thanks for getting back to me. I am able to connect to the database
> elsewhere in the application to call stored procedures and retrieve the
> data to display. This is the only place within the application that I am
> unable to connect. I suspect it has to do with the fact that I am
> calling within a single thread. Here is the connect string:
> "Data Source=(local);Initial Catalog=IOC;User
> ID=sg2user;password=sg2user"
>
> --
> franksag
> ---
> Posted via http://www.codecomments.com
> ---
>

error connecting to datasource

environment:
Win 2000
SqlServer2000
ReportServices
Reports and ReportServer virtual directories set to Windows authentication
-- Sample reports installed without any problems thru the sql script
-- Reports and Reportserver pages accessible without any problems
VS .NET 2003
Using VS .NET 2003,
I have created a Report Project
Shared Data Source:
name mysqlodbc
ODBC
dsn=mysqlodbc;database=myski;Driver={MySQL ODBC 3.51 Driver}
I have created a report3.rdl using the mysqlodbc data source.
In the design view of the report, the preview of the report works fine.
When I try to run the report I get the following error:
An error has occurred during report processing. (rsProcessingAborted) Get Online Help
Cannot create a connection to data source 'mysqlodbc'. (rsErrorOpeningConnection) Get Online Help
ERROR [IM002] [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified
Please help.It looks like the mysqlodbc ODBC data source is not defined on the report
server machine. Check that
'mysqlodbc' is defined as a system-level DSN on the server.
--
Albert Yen
SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"jerry" <jerry@.discussions.microsoft.com> wrote in message
news:34955583-B44A-4115-AACC-D7EB2A732CF2@.microsoft.com...
> environment:
> Win 2000
> SqlServer2000
> ReportServices
> Reports and ReportServer virtual directories set to Windows authentication
> -- Sample reports installed without any problems thru the sql script
> -- Reports and Reportserver pages accessible without any problems
> VS .NET 2003
> Using VS .NET 2003,
> I have created a Report Project
> Shared Data Source:
> name mysqlodbc
> ODBC
> dsn=mysqlodbc;database=myski;Driver={MySQL ODBC 3.51 Driver}
> I have created a report3.rdl using the mysqlodbc data source.
> In the design view of the report, the preview of the report works fine.
> When I try to run the report I get the following error:
> An error has occurred during report processing. (rsProcessingAborted) Get
Online Help
> Cannot create a connection to data source 'mysqlodbc'.
(rsErrorOpeningConnection) Get Online Help
> ERROR [IM002] [Microsoft][ODBC Driver Manager] Data source name not found
and no default driver specified
> Please help.
>
>

Friday, February 17, 2012

Error after migrating package from development to staging

I've migrated a package that has worked in our development environment. In both environments (dev & staging) I am in the BUILTIN/Administrators local group which is in the sysadmin server role.

In our staging environment, I execute DTEXEC command from the command line and get the following results.

D:\Reporting>"D:\Program Files\Microsoft SQL Server\90DTS\Binn\DTEXEC.EXE" /SQL "\MSDB\ProcessReportingDatabase" /SERVER USFKL16DB1CI01 /MAXCONCURRENT " -1 " /
CHECKPOINTING OFF /REPORTING V /SET "\Package.Variables[User::RunID].Value";65 /
SET "Package.Connections[RSAnalytics].InitialCatalog";"VR New Test 1 Dec28-FndPrj 1 Dec28"
Microsoft (R) SQL Server Execute Package Utility
Version 9.00.1399.06 for 32-bit
Copyright (C) Microsoft Corp 1984-2005. All rights reserved.

Started: 1:46:43 PM
Could not load package "\MSDB\ProcessReportingDatabase" because of error 0xC0014062.
Description: The LoadFromSQLServer method has encountered OLE DB error code 0x80004005 (Login timeout expired). The SQL statement that was issued has failed.
Source:
Started: 1:46:43 PM
Finished: 1:47:02 PM
Elapsed: 18.797 seconds

In addition to my login, all logins that access this package are in the sysadmin role; and I have gone back and included these logins in msdb's dts_operator role. Has anyone seen this before?

Thanks - Dave

I received the same error. In my case, I was using an environment variable to indirectly point to a configuration file that would update connection strings in my connection managers. It worked fine during development, but when moved to production, that's when the error occurred. After some trial and error, I found that if I removed the indirect configuration and allowed the connection managers to use the default connections I setup, it worked properly. That doesn't explain why it worked in development but not in staging. I have a hunch that the difference is in development the config file was locally on my drive (a C:\... path), but when moved to staging, it was changed to a UNC path on another machine. There is no security on the path or file on the other machine that would block the user (the share is wide open to everyone on the domain for testing purposes), so it might just be the fact that it's a UNC path. I'll have to test it out on Monday. Hope that helps.

Update: I ended up having enough time to try a few things. I tried a UNC path pointing back to my pc using the PC name (not just 127.0.0.1) and it worked ok that way. So it appears it's not necessarily that it's a UNC path. Whenever I attempt to access the remote path from Explorer I'm able to view the config file. I guess I'll start looking into the Component Service configuration on Monday. Although I think it would be easier to try to rethink of how to manage my configuration files so that I can keep them on the local machine.