Showing posts with label visual. Show all posts
Showing posts with label visual. Show all posts

Monday, March 26, 2012

Error when opening Designer

When I try to open the designer (with exiting, e.g. tutorial or new project/package) I get the following error 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.

After closing the project I have the following application event log error:

Faulting application devenv.exe, version 8.0.50727.42, stamp 4333e699, faulting module unknown, version 0.0.0.0, stamp 00000000, debug? 0, fault address 0x014fb87c.

I had the same problem. Any ideas anyone?|||I found the answer. Reformat and reinstall everything. As far as I can tell that is the only solution.|||

Did you find a solution to this? I am experiencing the same problem and hoping that a reformat and reload is not the only path.

Thanks

Richard

Error when opening Designer

When I try to open the designer (with exiting, e.g. tutorial or new project/package) I get the following error 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.

After closing the project I have the following application event log error:

Faulting application devenv.exe, version 8.0.50727.42, stamp 4333e699, faulting module unknown, version 0.0.0.0, stamp 00000000, debug? 0, fault address 0x014fb87c.

I had the same problem. Any ideas anyone?|||I found the answer. Reformat and reinstall everything. As far as I can tell that is the only solution.|||

Did you find a solution to this? I am experiencing the same problem and hoping that a reformat and reload is not the only path.

Thanks

Richard

sql

Thursday, March 22, 2012

Error when i try to Deploy my reports to Reporting services - PLEASE HELP i'm also NEW at t

Hi

I'm running a SQL 2000 DB with reporting Services 2005 and Visual Studio 2005, I can connect and browse to Reporting Services through any management console and even to my site through //ServerName/Reports but when i try to deploy any of my reports to the Reporting Services through my VS2005 solution i get this error

A connection could not be made to the report server http://Forge/Reports.

Additional Information:

The Attempt to connect to the report server failed. Check your connection information and that the report server is a compatible version. (Microsoft.ReportingServices.Designer)

The status of all of my things in Reporting Services Configuration is Green and i can see my site in the IIS, i can also browse my site, it just doesn't want2 deploy.

Please HELP!!!

I suspect the problem lies here:

>I'm running a SQL 2000 DB with reporting Services 2005 and Visual Studio 2005

and, considering the error:

>that the report server is a compatible version

I am thinking there is a problem with your deploying RS 2005 reports to a 2000 RS database. I wasn't aware you could deploy 2005 reports to a 2000 RS database. Maybe you can do it if you don't convert (existing 2000) reports, I am not sure; but I doubt you'll be able to deploy them if you have converted them from 2000 to 2005. I especially think and new reports will bomb out since they would be native 2005.

There are threads in this forum that talk about this subject.

|||Try deploying to http://forge/reportserver instead.|||wow. good eye!|||

Thanks for th information but it still gives me the same error, but don't worry too much about it, i'm just going to reinstall SQL 2000 RS with Visual Studio 2003. apparently there is some incompatibility issue between .Net Framework 2.0 and 1.1 that prevent my solutions from working properly, so until i figure out the exact problem and link the Frameworks manually in my solution i doubt that it will work.

Thanks a lot for your effort guys!

|||

Hi

I traced down my problem, but i'll post my solution here just incase some else might battle with the same problem.

When i installed the RS i changed the Virtual Directory Name to Forge too, so when i deployed them i had to deploy them to Forge/Forge instead of Forge/ReportServer which it suppose to be by default. ->PC Name / ReportServer Virtual Directory<--

Error when i try to Deploy my reports to Reporting services - PLEASE HELP i'm also NEW at t

Hi

I'm running a SQL 2000 DB with reporting Services 2005 and Visual Studio 2005, I can connect and browse to Reporting Services through any management console and even to my site through //ServerName/Reports but when i try to deploy any of my reports to the Reporting Services through my VS2005 solution i get this error

A connection could not be made to the report server http://Forge/Reports.

Additional Information:

The Attempt to connect to the report server failed. Check your connection information and that the report server is a compatible version. (Microsoft.ReportingServices.Designer)

The status of all of my things in Reporting Services Configuration is Green and i can see my site in the IIS, i can also browse my site, it just doesn't want2 deploy.

Please HELP!!!

I suspect the problem lies here:

>I'm running a SQL 2000 DB with reporting Services 2005 and Visual Studio 2005

and, considering the error:

>that the report server is a compatible version

I am thinking there is a problem with your deploying RS 2005 reports to a 2000 RS database. I wasn't aware you could deploy 2005 reports to a 2000 RS database. Maybe you can do it if you don't convert (existing 2000) reports, I am not sure; but I doubt you'll be able to deploy them if you have converted them from 2000 to 2005. I especially think and new reports will bomb out since they would be native 2005.

There are threads in this forum that talk about this subject.

|||Try deploying to http://forge/reportserver instead.|||wow. good eye!|||

Thanks for th information but it still gives me the same error, but don't worry too much about it, i'm just going to reinstall SQL 2000 RS with Visual Studio 2003. apparently there is some incompatibility issue between .Net Framework 2.0 and 1.1 that prevent my solutions from working properly, so until i figure out the exact problem and link the Frameworks manually in my solution i doubt that it will work.

Thanks a lot for your effort guys!

|||

Hi

I traced down my problem, but i'll post my solution here just incase some else might battle with the same problem.

When i installed the RS i changed the Virtual Directory Name to Forge too, so when i deployed them i had to deploy them to Forge/Forge instead of Forge/ReportServer which it suppose to be by default. ->PC Name / ReportServer Virtual Directory<--

Error when i try to Deploy my reports to Reporting services - PLEASE HELP i'm also NEW at t

Hi

I'm running a SQL 2000 DB with reporting Services 2005 and Visual Studio 2005, I can connect and browse to Reporting Services through any management console and even to my site through //ServerName/Reports but when i try to deploy any of my reports to the Reporting Services through my VS2005 solution i get this error

A connection could not be made to the report server http://Forge/Reports.

Additional Information:

The Attempt to connect to the report server failed. Check your connection information and that the report server is a compatible version. (Microsoft.ReportingServices.Designer)

The status of all of my things in Reporting Services Configuration is Green and i can see my site in the IIS, i can also browse my site, it just doesn't want2 deploy.

Please HELP!!!

I suspect the problem lies here:

>I'm running a SQL 2000 DB with reporting Services 2005 and Visual Studio 2005

and, considering the error:

>that the report server is a compatible version

I am thinking there is a problem with your deploying RS 2005 reports to a 2000 RS database. I wasn't aware you could deploy 2005 reports to a 2000 RS database. Maybe you can do it if you don't convert (existing 2000) reports, I am not sure; but I doubt you'll be able to deploy them if you have converted them from 2000 to 2005. I especially think and new reports will bomb out since they would be native 2005.

There are threads in this forum that talk about this subject.

|||Try deploying to http://forge/reportserver instead.|||wow. good eye!|||

Thanks for th information but it still gives me the same error, but don't worry too much about it, i'm just going to reinstall SQL 2000 RS with Visual Studio 2003. apparently there is some incompatibility issue between .Net Framework 2.0 and 1.1 that prevent my solutions from working properly, so until i figure out the exact problem and link the Frameworks manually in my solution i doubt that it will work.

Thanks a lot for your effort guys!

|||

Hi

I traced down my problem, but i'll post my solution here just incase some else might battle with the same problem.

When i installed the RS i changed the Virtual Directory Name to Forge too, so when i deployed them i had to deploy them to Forge/Forge instead of Forge/ReportServer which it suppose to be by default. ->PC Name / ReportServer Virtual Directory<--

Friday, February 24, 2012

Error trying to deploy Report

I have a report which works perfectly well within Visual Studio in design. However as soon as I try to deploy this to the Report Server it throws the following error:

w3wp!library!6!02/12/2007-16:29:17:: i INFO: Call to CreateReport( 'Defects by Application (Inactive and Active by Severity) Chart', '/AET Deployment', def)
w3wp!library!6!02/12/2007-16:29:17:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException: An internal error occurred on the report server. See the error log for more details., ;
Info: Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException: An internal error occurred on the report server. See the error log for more details. > System.Data.SqlClient.SqlException: String or binary data would be truncated.
The statement has been terminated.
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result)
at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe)
at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
at Microsoft.ReportingServices.Library.InstrumentedSqlCommand.ExecuteNonQuery()
at Microsoft.ReportingServices.Library.DBInterface.CreateObject(Guid id, String shortName, String fullPath, String parentPath, Guid parentId, ItemType objectType, Byte[] objectContent, Guid intermediateSnapshotID, Guid link, String linkPath, ItemProperties objectProperties, String parameters, Byte[] createdBySid, String createdByName, DateTime creationDate, String mimeType)
at Microsoft.ReportingServices.Library.DBInterface.CreateObject(Guid id, String shortName, String fullPath, String parentPath, Guid parentId, ItemType objectType, Byte[] objectContent, Guid intermediateSnapshotID, Guid link, String linkPath, ItemProperties objectProperties, String parameters, String createdBy, DateTime creationDate, String mimeType)
at Microsoft.ReportingServices.Library.CatalogItemCreator.CreateItem()
at Microsoft.ReportingServices.Library.CreateReportAction._CreateReport(String report, String parent, Boolean overwrite, Byte[] definition, Property[] properties)
at Microsoft.ReportingServices.Library.CreateReportAction.CreateReport(Guid batchId, String report, String parent, Boolean overwrite, Byte[] definition, Property[] properties)
End of inner exception stack trace

I cannot identify any issues in the report definition which may indicate where data truncation may occur.

Any help appreciated.

Exception error relates to some problem with the tools, you might try to deploying the report from another machine where BIDS is installed with this project, also confirm the service pack of SQL & RS used here.|||

Using RS 2005 SP1 with SQL 2000 SP3

We have tried deploying this report from a number of locations - from BIDS, from Visual Studio, from RS itself - all fail. We have been able to deploy other reports but cannot see what is causing this deployment to fail ... especially as it runs without issues in preview.

|||

Looks like we have found the issue.

I had been looking at the parameters that were being passed from the Report back to the stored procedures and had verified all of those were OK. However one of the stored procs was returning a dataset with a tinyint which was then being used as an int within other parameters. Not sure how going from tinyint to int can ever result in truncation but when we set the type to int in the stored procedure it deployed OK.

Sunday, February 19, 2012

Error tmp file is too large

I am getting the follwoing error when running my package.

An OLE DB record is available. Source: "Microsoft OLE DB Provider for Visual FoxPro" Hresult: 0x80004005 Description: "File c:\docume~1\sortiz\locals~1\temp\00003589001o.tmp is too large.".

I use a select statement to join to large foxpro tables. The data contains over a million records.

Any help is greatly appreciated.

Thanks

Try loading the fox pro data into a SQL Server table first, and then do your join there.

Wednesday, February 15, 2012

Error running schedule job

I have this SSIS Package that it works when I run it on development on Visual Studio. But when I imported it and schedule the job, it gives me the following error:

Executed as user: MAINOFFICE\ASPNET. ... 9.00.3042.00 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 2:38:39 PM Error: 2007-11-05 14:38:41.02 Code: 0xC0202009 Source: Export_WHSCANP Connection manager "10.5.1.10.DRDB400.aspnet1" Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005. An OLE DB record is available. Source: "IBMDA400 Session" Hresult: 0x80004005 Description: "CWBSY0002 - Password for user ASPNET on server 10.5.1.10 is not correct ". End Error Error: 2007-11-05 14:38:41.04 Code: 0xC020801C Source: Data Flow Task OLE DB Destination [801] Description: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "10.5.1.10.DRDB400.aspnet1" failed with error code 0xC0202009. There may be error messages posted before this with more information on why the AcquireConnec... The package execution fa... The step failed.

This is trying to get a table from the SQL server and copy it to an IBM AS400 server. Any ideas?

Thanks,

Erick

Is the connection information the same in the new environment as it was in development?

|||

It is, I didnt change anything I just uploaded the working SSIS Package to the integration services and call it from a job schedule. The job runs in the integration services, but the schedules fails.

|||

I found a very helpfull article on this problemhttp://www.cubido.at/Blog/tabid/176/EntryID/71/Default.aspx