Thursday, March 29, 2012
error loading the report in the designer
I'm working on rs2005, and i cannot load any server report in the
designer.
i get the following error:
"One or more errors encountered while loading the designer. The errors
are listed below.
Exception has been thrown by the target of an invocation "
I can load local reports, and i can load the server reports on other
computers.
It just suddenly stopped working in my laptop, and no reinstallation
helps (at least not the visual studio, framework, or the report server)
Does anyone hav an idea?
Thanks,
EyalWell, i found the solution eventually,
After getting a message "font verdana does not support style regular"
while trying to load a winforms into the designer, i deleted all my
fonts from my computer, and copied them from another computer.
both the winform problem and the reporting services problem has gone
forever.
it seems that a corrupted font has crashed the visual studio designer.
Eyal
Eyal =EB=FA=E1:
> Hi all,
> I'm working on rs2005, and i cannot load any server report in the
> designer.
> i get the following error:
> "One or more errors encountered while loading the designer. The errors
> are listed below.
> Exception has been thrown by the target of an invocation "
> I can load local reports, and i can load the server reports on other
> computers.
> It just suddenly stopped working in my laptop, and no reinstallation
> helps (at least not the visual studio, framework, or the report server)
> > Does anyone hav an idea?
> Thanks,
> Eyal
Monday, March 19, 2012
Error in SELECT clause: expression near '='.
studio 2005. i get the error that it doesnt understand this. However
the sql is just fine is there a way to make this work in visual studio?
i did set the prefix for the parameters so it does understands the @. in
other types of query.
DECLARE @.TEMP t_timestamp
this block in the designer:
SELECT @.TEMP=rprl_timestamp
FROM rap_rol
WHERE rol_id = 10Jeroen a crit :
> When I use a construction like this in the sql designer of visual
> studio 2005. i get the error that it doesnt understand this. However
> the sql is just fine is there a way to make this work in visual studio?
> i did set the prefix for the parameters so it does understands the @. in
> other types of query.
> DECLARE @.TEMP t_timestamp
^^^^^^^^^^^
what is this type '? t_timestamp ?
Do you use a CLR UDT ?
> this block in the designer:
> SELECT @.TEMP=rprl_timestamp
> FROM rap_rol
> WHERE rol_id = 10
>
Frdric BROUARD, MVP SQL Server, expert bases de donnes et langage SQL
Le site sur le langage SQL et les SGBDR : http://sqlpro.developpez.com
Audit, conseil, expertise, formation, modlisation, tuning, optimisation
********************* http://www.datasapiens.com ***********************|||its just a user defined datatype
it does not matter what type for my question. but in this case its a
datetime.
the problem is in the line SELECT @.TEMP=rprl_timestamp
where the @.temp is filled with the value of rprl_timestamp. its perfect
sql but the designer doesnt understand it.
Friday, February 17, 2012
Error immediately on creating new Integration Services project in VS2005
error immediately after creating the project. The error is in the
designer and it displays a red X, saying "Microsoft Visual Studio is
unable to load this document: Object reference not set to an instance
of an object". Clicking on the error in the error window just opens up
the xml file which contains the following:
<?xml version="1.0"?><DTS:Executable xmlnsTS="www.microsoft.com/
SqlServer/Dts" DTS:ExecutableType="MSDTS.Package.1"><DTSroperty
DTS:Name="PackageFormatVersion">2</DTSroperty><DTS
roperty
DTS:Name="VersionComments"></DTSroperty><DTS
roperty
DTS:Name="CreatorName">BNHO1\mbell</DTSroperty><DTS
roperty
DTS:Name="CreatorComputerName">BT4WKS1361</DTSroperty><DTS
roperty
DTS:Name="CreationDate" DTSataType="7">8/14/2007 12:22:35 PM</
DTSroperty><DTS
roperty DTS:Name="PackageType">5</
DTSroperty><DTS
roperty DTS:Name="ProtectionLevel">1</
DTSroperty><DTS
roperty DTS:Name="MaxConcurrentExecutables">-1</
DTSroperty><DTS
roperty DTS:Name="PackagePriorityClass">0</
DTSroperty><DTS
roperty DTS:Name="VersionMajor">1</
DTSroperty><DTS
roperty DTS:Name="VersionMinor">0</
DTSroperty><DTS
roperty DTS:Name="VersionBuild">0</
DTSroperty><DTS
roperty
DTS:Name="VersionGUID">{834A3ADF-377D-4F01-88DC-1E0B5424B918}</
DTSroperty><DTS
roperty DTS:Name="EnableConfig">0</
DTSroperty><DTS
roperty DTS:Name="CheckpointFileName"></
DTSroperty><DTS
roperty DTS:Name="SaveCheckpoints">0</
DTSroperty><DTS
roperty DTS:Name="CheckpointUsage">0</
DTSroperty><DTS
roperty DTS:Name="SuppressConfigurationWarnings">0</
DTSroperty><DTS
roperty DTS:Name="ForceExecValue">0</
DTSroperty><DTS
roperty DTS:Name="ExecValue" DTS
ataType="3">0</
DTSroperty><DTS
roperty DTS:Name="ForceExecutionResult">-1</
DTSroperty><DTS
roperty DTS:Name="Disabled">0</
DTSroperty><DTS
roperty DTS:Name="FailPackageOnFailure">0</
DTSroperty><DTS
roperty DTS:Name="FailParentOnFailure">0</
DTSroperty><DTS
roperty DTS:Name="MaxErrorCount">1</
DTSroperty><DTS
roperty DTS:Name="ISOLevel">1048576</
DTSroperty><DTS
roperty DTS:Name="LocaleID">4105</
DTSroperty><DTS
roperty DTS:Name="TransactionOption">1</
DTSroperty><DTS
roperty DTS:Name="DelayValidation">0</DTS
roperty>
<DTS:LoggingOptions><DTSroperty DTS:Name="LoggingMode">0</
DTSroperty><DTS
roperty DTS:Name="FilterKind">1</
DTSroperty><DTS
roperty DTS:Name="EventFilter" DTS
ataType="8"></
DTSroperty></DTS:LoggingOptions><DTS
roperty
DTS:Name="ObjectName">Package</DTSroperty><DTS
roperty
DTS:Name="DTSID">{433D7504-1A63-4960-86EB-8501C7A77A37}</
DTSroperty><DTS
roperty DTS:Name="Description"></
DTSroperty><DTS
roperty DTS:Name="CreationName">MSDTS.Package.1</
DTSroperty><DTS
roperty DTS:Name="DisableEventHandlers">0</
DTSroperty></DTS:Executable>
I have VS2005 SP1, running WindowsXP SP2. Integration Services is
running on my machine, but I would think that this shouldn't matter
anyway as the error is happening before I have even indicated and data
source to use. If I take this xml file with the error and copy it to another new SSIS project on another machine, it works fine. Reinstalling VS2005 had no effect. I am now reinstalling SQL Server 2005 SP2 to see what effect that may have.
Any ideas?
Thanks,MarcusTry searching, but in the mean time:
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1627891&SiteID=1|||Thanks for the link. I have seen that one, and I tried re-registering the xml dlls, but that didn't do anything. Hopefully after my reinstall of Sql Server things will be better.
Marcus
|||
Well that was disappointing. After the SQL Server reinstall and adding SP2 there is no change with my problem. >>HEAVY SIGH!<<. I think it is time to call MS...unless any other ideas?!?!?!?
Marcus
|||Anybody?
M.