CR2010 for vs2010 Runtime to deploy on client available or not ???

OK we have converted our solution to VS2010 and it uses CR2010 for VS2010. The converted solution seems to work even displaying reports.
I am trying to understand, do we have a runtime to install for delpoyement on client computers RIGTH NOW or we dont ?
If we do not, we should have been advised of this before waiting for the launch of VS2010 and then for SAP BusinessObjects to release the current BETA.
This is really not funny at all. To my knowledge, it is the first time we are stuck waiting for CR and holding our usage of the latest dev environment from MS because of this.
We have been using CR for decades without questions, today, we are planning meetings to discuss the complete removal of CR reports from our solutions. A real bummer!
A fast reply from SAP would be appreciated with an date of availabilty for the deployement runtime solution.
Thanks.

Hello,
I have been following the posts and I have a few questions that I am still not clear on. I have read the white paper at the following link: [white paper|http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d085f103-ff2d-2d10-2f9e-ffb14d10ef33?quicklink=index&overridelayout=true].
Here are the conditions.
1. I have changed the configuration file for a WinForms application as instructed but I can still not get the application to work with .NET 4.0.
2. If I compile the application under .NET 3.5 the application works. Under .NET 4.0 an exception is thrown when ReportDocument.SetDataSource() is called. The error message states "Unknown Query Engine Error".
3. The version of Crystal Reports being used is Crystal Reports Basic for Visual Studio 2008. Service Pack 1.
Here are my questions
1. Is this the correct thread to ask this question or should it be moved somewhere else?
2. Is Crystal Reports Basic for Visual Studio 2008 supported with .NET 4.0 (WinForms and Web App)?
3. If it is supported are there instructions on how to get it to work?
4. The white paper gave a work around but I got the impression that the white paper was only for a development/test environment but not production. Is that true?
Thanks,
Tim

Similar Messages

Is Crystal Report for VS2010 runtime redistributable package required?

Is Crystal Report for VS2010 runtime redistributable package required when develop reports using WPF window/XBAP technology?
Is it required to install this runtime package (.MSI/.MSM) into the client machine?
If .msm is to be used, then how to setup and deploye msm package into VS2010?
Environment:
VS 2010
CR for VS2010
Please reply friendz.
Thanks & Regards,
Mani G.S.

Hello Mani
Yes, the runtime is required on all computers that the app will run on. See the wiki [Deploying Crystal Reports for Visual Studio 2010 runtime|http://wiki.sdn.sap.com/wiki/x/ZwdeDw]. Also, consult your CRVS2010 developer help file:
http://help.sap.com/businessobject/product_guides/sapCRVS2010/en/crnet_api_2010_en.zip
Ludek
Follow us on Twitter http://twitter.com/SAPCRNetSup
Got Enhancement ideas? Try the [SAP Idea Place|https://ideas.sap.com/community/products_and_solutions/crystalreports]

Using Crystal Report for VS2010 with target Framework 4 Client Profile

I´m need know if is possible use the Crystal Reports for VS 2010 with the framework 4 client Profile. Exists some posibility?
I need use the WPF Crystal Report Viewer, and the export/print mechanism.
Regards

Hi Null,
No it is not, CR requires the full client in all framework versions.
Thank you
Don

CR for VS2010 - font when printing (what you see is not what you get)

If anyone can help resolve this issue, I would be very grateful!
We use VS 2010 with the production Crystal Reports for VS 2010. I deployed a web site to production on a Win 2008 r2 server with IIS 7.
When the user runs a report (we have it set to be pdf), the font used by the report displays properly. When printing, it prints with a different font. The correct font is Old English. I believe it is printing in arial.
I installed the font on the server. I gave rights to the fonts directory for the web site. I ran the redistributable. I'm not sure what else to try.

Yes, I do mean client-side.
Also, the crystal report viewer control print mode set to pdf instead of Active X.
We had issues with users being able to install the Active X viewer.
The font has been installed on the client.
When you stated "Print Control is via binary page descriptors, where the font composition is turned to printable images on the client-side" --- Does that mean that certain fonts or even font types may not work?
Thank you for your help.

SCCM 2012 agent Deployed on clients SCEP in not update and shown inactive on cosole

Dear there are no of system in this state. SCCM client installed but SCEP is also installed but not getting update.
durranifaisal

OK, a couple of things for you. First off, if a client had not sent in Heartbeat DDR, then the console would not reflect "Yes" in the "Client" column. Yours does, so you have had at least one Heartbeat DDR received and processed by the client. If you want
to see when it was, you can view the Properties for that client, and in the Properties dialog, look at the AgentTime attribute. Very likely (always has been in my experience) it will be the very last time listed (you likely will have three or four 'agents'
that have discovered this client, and thus reported time.
The "Client Activity" column can be updated when you Refresh Client Status (on the Client Status node in the Monitoring workspace). It will happen automatically, but you can force it with this action.
Lastly, none of this has anything to do with the fact that the Endpoint Protection menu option is unavailable. I don't even have it enabled in my test site (the current snapshot that I'm testing on), and the menu item still appears. My guess there is that
you are logged on with a user that does not have rights to that action. So more likely a security issue rather than clients not reporting properly.
Wally Mead

WSUS lists app. 178 missing updates for the Windows 8/8.1 clients, but the clients report that no updates are necessary

We are operating a small network consisting of a SBS 2011 and a few clients, most of which operate WXP and W7. Some time ago we converted the first client to W8 and noticed, that WSUS reported a big number of missing updates (all being language packs and
language interface packs), which the client never pulls, as from its perspective everything is in best order. When searching for updates over the internet the client again does not detect anything missing.
We first thought of an issue with this single W8 client, as neither the WXP nor the W7 machines show the same phenomenon, but recently we introduced the first two W8.1 clients, and interestingly we saw the same problem. The question now is, why
does WSUS believe that these updates were necessary whilst the clients themselves are convinced that everything is fine? And who is right, WSUS or W8/8.1? (I tend to believe the clients, though.)
Best regards, Dietmar.

why does WSUS believe that these updates were necessary whilst the clients themselves are convinced that everything is fine?
Because you're misinterpreting the meaning of the state "Needed"...
which is discussed elsewhere in this forum ad naseum.
And you're making the mistake of trying to compare information with WU with information from WSUS. The two are not comparable.
Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
SolarWinds Head Geek
Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
http://www.solarwinds.com/gotmicrosoft
The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

Crystal Report for VS2010 show Login when deployed

I am having a problem with my Windows Form project in VS2010 regarding
the SAP Crystal Reports for VS2010.
When I deploy my project on client's PC it shows a login dialog box.
The client's PC is in XP.
I already installed the correct runtime in their PC.
When the login dialog box appear and the cancel button is clicked,
the Report shows correctly.
But our client did not want to always see the login dialog box.
I already try to fix it like this:
u2022 Add connection and login info in the codes (CrystalDecisions.Shared.ConnectionInfo)
u2022 Verify and reconnect the database
u2022 reinstall the runtime of Crystal Report(CRRuntime_32bit_13_0_1.msi)
But nothing works.
I am using an XML schema to display the report, I do not directly connect
to a database. Like this:
CrystalReport.SetDataSource(DataSet);
The framework I use is C#.Net 3.5.
My project is in Windows Form.
My Crystal Report for VS2010 version is 13.0.1
Please help me.
Thanks in advance.

Moved to .NET SDK forum.
Can you clarify? What data source are you using? Direct connection to the DB or Dataset?
It's prompting because what ever source you are using doesn't have the proper connection method being used or the log on info is incorrect.
Don

Crystal Reports for VS2010 Prerequisites for ClickOnce Deployment

I keep getting this Error when publishing my application with clickonce even though I have Crystal Reports for VS2010 installed: I want the prerequisites to be downloaded from the same location as my app. Publishing fails with the following error.
The install location for prerequisites has not been set to 'component vendor's web site' and the file 'Crystal Reports for .NET Framework 4.0\CRRuntime_32bit_13_0.msi' in item 'SAP Crystal Reports Runtime Engine for .NET Framework 4.0' can not be located on disk.

See KB [1534388 - CRVS2010 - Creating Click Once deployment|http://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes_boj/sdn_oss_boj_bi/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/scn_bosap/notes%7B6163636573733d36393736354636443646363436353344333933393338323636393736354637333631373036453646373436353733354636453735364436323635373233443330333033303331333533333334333333383338%7D.do].
I think typing "clickonce crvs2010" in the search box at the top right corner of this web page will also bring up the KB (just an FYI).
Ludek
Follow us on Twitter http://twitter.com/SAPCRNetSup
Got Enhancement ideas? Try the [SAP Idea Place|https://ideas.sap.com/community/products_and_solutions/crystalreports]

CR runtime for VS2010 (v13) not generating report

I installed Crystal Reports Runtime for VS2010 version 13 on Win2003 Server 64 bit (for intranet website that is used to execute reports). The web site is executed under Integrated security. The user account and the network service account have write and modify access to the designated temp folder on the web server. But for some reason when I execute the report, "Database Logon Failed" error is getting generated. Crystal Reports 10.5 runtime under same settings worked fine, but when I installed CR13 runtime and changed Web.config to point to CR13 version, it is generating this error. The correct version 13 is getting picked up as I checked the ReportDocument object's Class Version after the ReportDocument.Load() is executed, and it points to version 13. It is generating this error when executing " ReportDocument.ExportToDisk". Does any account other than the user account (logged in NT account) and service account require permissions to temp folder. Does any other folder require permissions? What is new in version 13 regarding the temp folder that CR uses to generate the report? The temp folder that is used in our intranet web site to generate CRs is a special folder (not C:\Win\Temp but another designated folder) that has the user account & Network service account have write and modify access. Has anything regarding the temp folder that CRs uses changed between CR10.5 and CR13. The web site, Crystal Reports(.rpt) and SQL server (Network is set up for Kerberos Authentication) are all set up for integrated security, and this set up worked with CR10.5 runtime, but does not work with CR13 runtime.
Error Details:
Server Error in '/' Application.
Database logon failed.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.Runtime.InteropServices.COMException: Database logon failed.

I have the same issue as you. I have converted my reports from CR10 to CR13. I can execute them locally (I'm in "Administrator Group"), but when I deploy the reports to my DEV environment I have this error :
CrystalDecisions.CrystalReports.Engine.LogOnException: Echec de la connexion à la base de données. ---> System.Runtime.InteropServices.COMException (0x8004100F): Echec de la connexion à la base de données.
   à CrystalDecisions.ReportAppServer.Controllers.ReportSourceClass.Export(ExportOptions pExportOptions, RequestContext pRequestContext)
   à CrystalDecisions.ReportSource.EromReportSourceBase.ExportToStream(ExportRequestContext reqContext)
   --- Fin de la trace de la pile d'exception interne ---
   à CrystalDecisions.ReportAppServer.ConvertDotNetToErom.ThrowDotNetException(Exception e)
   à CrystalDecisions.ReportSource.EromReportSourceBase.ExportToStream(ExportRequestContext reqContext)
   à CrystalDecisions.CrystalReports.Engine.FormatEngine.ExportToStream(ExportRequestContext reqContext)
   à CrystalDecisions.CrystalReports.Engine.FormatEngine.Export(ExportRequestContext reqContext)
   à CrystalDecisions.CrystalReports.Engine.FormatEngine.Export()
   à CrystalDecisions.CrystalReports.Engine.ReportDocument.Export()
   à
I don't understand how it could be a database connection problem, because the report crash on CrystalDecisions.CrystalReports.Engine.ReportDocument.Export() call and, at this point, data are loaded into the dataset from my Data Tier (which did not fired an exception).

Problem releasing webservice for runtime in non-modifiable client

Hi
I created a webservice definition ( virtual interface & all dependent objects ) in a development client ( client- A ) of a ECC5.0 instance.
Now, we have another client ( client-B ) in the same server that we want to release the webservice for SOAP runtime. ( reason is that the webservice is not available at runtime in this client-B client )
This client-B has status - non-modifiable and hence cannot use WSCONFIG --> create option to release it for runtime.
How do we release this webservice definition to client - B . I tried a SCC1 transaction on client-B pointing to the transport that contains the WS definition in client-A. I got dictionary errors indicating that the WS definition objects are all client independent.
Is there something I am missing ? Any thoughts/similar experiences shared is appreciated.

Good to hear it worked out for you. But like I already said, I haven't experienced anything like this, but for similar problems this is exactly what we did to solve it. But you're probably right, that this is no long term solution. There should be another way of doing this, but no experience in that field expertise.

CR for VS2010 deployment - crtslv.dll failed to register

I'm still having problems with packaging up the CR for VS2010 library with our applications installation.
I'm using InstallShield 2011 for the installation setup.
I've included the CRRuntime_13_0.msm file. (That is the only MSM file I included, are the others needed also?)
I've included the Microsoft Visual C++ 2005 SP1 Redistributable Package (x86 and the x64 versions.)
I have tried to do a test install on both a 64bit and a 32bit Windows 7 computer and it keeps giving me the crtslv.dll failed to register error on both computers.
Error 1904.Module C:\Program Files\SAP BusinessObjects\Crystal Reports for .NET Framework 4.0\Common\SAP BusinessObjects Enterprise XI 4.0\win32_x86\crtslv.dll failed to register. HRESULT -2147010895. Contact your support personnel.
I thought it might just be due to the 32 bit MSM causing the problem on the 64bit computer, but I can't even get it to install on a 32bit computer. (On the 32bit computer install, I even removed the x64 bit version of the MS C++ 2005 Redistributable from the installation setup just to make sure it wasn't causing a problem).
I have even tried having my Install Shield setup 'Chain' the CRRuntime_32bit_13_0.msi file to my main installation (not using the Merge module). Even when that runs, it produces the same crtslv.dll failed to register again.
BUT, if I run the CRRuntime_32bit_13_0.msi manually on the computer it installs correctly. (I even tried using the same /qf parameters that InstallShield is using on it and it also worked OK that way.) So I can't figure out how to get it to run in conjunction with my InstallShield installation.
Can anyone give me any suggestions?
Mike...

I finally got past this issue and got things to install, with a few hackish work-arounds.
First the CR13 msm redistributable appears to requre the 32 bit version of "Microsoft Visual C++ 2005 Service Pack 1 Redistributable Package ATL Security" that you'll read about in every post. On 64 bit machines I found that even when it was installed,I would still get a crtslv.dll failed to register message, followed several other dlls not registering. Once I installed the 32 bit version on the 64 bit OS, the crystal 13 redistibutable installed fine everytime. I did this on several 64 bit VMs all running Server 2003,XP, and Windows 7. It ran fine every time.
The problem you'll face is how do you install the 32 bit version of this ATL security pack on a 64 bit machine. You may be able to download and run the 32 bit version from Microsoft's site with the link Ludek has posted. That wouldn't work for me because I had to distribute it with my software so I used the prerequisite available for InstallShield. The prereq however is designed to only run on 32 bit machines, so I edited it in InstallShield and modifed the conditions to allow it to run on both 32 & 64 bit operating systems.
The next problem encountered is that this 32 bit prereq getting installed on a 64 bit machine will result in an error being returned that the installation appears to have failed. Well it is a 32 bit installation not intended for a 64 bit OS and we're not supposed to do that. I did say hackish work-around. The 32 & 64 bit files are installed to different directories and the 64 bit version does not get overwritten. If you check the event viewer you'll see a message logged in that the installation of the ATL prereq completed sucessfully. So I modified the behavior of the prereq in InstallShield to "continue the setup if the condition still indicates it is required after completion". Now it runs without error and everything for Crystal installs sucessfully.
The final problem was also with the pre-requisite. The code determines if it is already installed by looking for the file:
[WindowsFolder]\WinSxS\x86_Microsoft.VC80.ATL_1fc8b3b9a1e18e3b_8.0.50727.4053_x-ww_473666fd\ATL80.dll
I found on some machines it was previousy installed to:
[WindowsFolder]\WinSxS\x86_microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.4053_none_d1c738ec43578ea1\
This results in the prereq being required every time because the file it's checkig for is not found. Furthermore, it fails every time, most likely because it's alreday installed and not supposed to be installed again. So once again, I modified the prereq conditios in InstallShield and made it look for the file in both locations to determine if it was installed.
I haven't seen any problems since with either the Crystal runtime or the ATL update. Happy day.
The part I stll don't understand is that SAP says they can't distribute the ATL update in their MSM because of licensing issues, but we can sell our software and distribute it freely. Microsoft even create the prereq so that we could distribute it freely. So why can't SAP distribute the required files for their runtime? A lot of people on these threads have wasted a lot of time and money on this issue. Ludek provides great support but maybe this issue needs to be investigated further by development.

Crystal Report prompts for username / pwd when deployed to Bus Obj Server

Hi All,
I'm relatively new to Crystal Reports development. My day job is test analyst. I'm reasonably technically proficient.
PROBLEM
I have created a number of Crytsal Reports which have now been deployed to an Enterprise Business Objects Report Server. The Server is Business Objects Server XI release 2.
When I run the report in Crystal Reports Desiger 2008 it does not prompt me to enter the database credentials except if I have modified the SQL command or some other report detail. Most times I run the report, no database username / pwd is required because I already set this up in the datasource config.
I' connecting to an Oracle database using ODBC (RDO) connection type. I cannot get the ODBC (RDO) connection type working from my PC using Crystal Reports Designer 2008, because I don't have ODBC configured for my datasource. Instead, Im using the native Oracle Server driver to connect to my datasource.
An existing user in the client organisation configured my report to use the ODBC (RDO) conneciton type for me because the Business Objects Server in the client organisation does not (currently) support the native Oracle driver. Other reports this user has created and deployed using the ODBC conenction type run successfully without prompting user to enter the database connection credentials.
NOTE:
This report users an SQL Command (new to Crystal 2008 I beleive?). The command is reqiured for this report due to the complexity of the underlying SQL query.
Does anybody know why the report keeps prompting me to enter the database credentials at runtime? Obviously for security reasons I don't want report users to have to enter the database schema name and password in order to run the report.

Hi,
You need to uncheck "Propmt the user for database logon when viewing". You will find this when you deploy the report on the BOE XI R2.
The deployment step main heading is
Specify Databse Crendentials.
Hope this helps,
Thanks
-Azhar

For Your Consideration: Ultimate Lync 2010 client install with SCCM 2007

While the subject of my post may be very presumptuous, I submit the following for your consideration to answer the often-asked question about how to deploy Lync 2010 client with SCCM.
Background:
I cannot understand why Microsoft made the Lync install so darned confusing, complex, and convoluted.
After our Lync 2010 FE server was up and running and all users migrated off our OCS server to the Lync environment, I spent about a month and a half trying to figure out how to:
1. Uninstall the OCS 2007 R2 client
2. Install all prerequisites for the Lync client
3. Install Lync on all user workstations silently.
While researching this, the simple answer I kept seeing given to this question was, "just use the .exe with the right switches according to the TechNet article here: http://technet.microsoft.com/en-us/library/gg425733.aspx". Well, my response is, I
tried that and while the program installed itself correctly pushed through SCCM, because I was doing it using an administrative account (i.e. the SYSTEM account) due to our users not having admin rights, when the install was done, Lync would automatically
start up, but in the SYSTEM context so that the user couldn't see it was running, they go to run it and it won't run for them. I was unable to find any switch or option to prevent the automatic launch. I suppose the simple solution to that would
be to have the user reboot, but that's unnecessarily disruptive and was contrary to the desire to make this a silent install.
The next simplest answer I saw was, "extract the MSI and use that with the right switches". Problem with that is that the MSI by itself doesn't remove the OCS client or install the prerequisites, and also either requires a registry change to even allow
the MSI to be used or a hacked MSI that bypasses the registry key check. I tried to put a package together to uninstall OCS, install the prereqs, and use a hacked MSI, but I never could get the MSI hacked properly. The other problem I ran into
was detecting if the OCS client was running in a predictable way so I could terminate it, properly uninstall it, and then do the rest of the installations. It was this problem that ultimately led me to the solution that I'm about to detail and that has
worked marvellously for us.
Solution:
As I said before, when I first looked at this problem, I started by building a typical software deployment package (Computer Management -> Software Distribution -> Packages) and then created the programs to do the install. My first attempt was
just with the .exe file provided as-is by Microsoft using the switches they document in the link above for IT-Managed Installation of Lync, and...well, the end result wasn't quite as desirable as hoped. So, my next attempt was to extract all the prerequisite
files and the Lync install MSI (both for x86 and x64), attempt to hack it to get around the "UseMSIForLyncInstallation" registry key, and make the command-lines to terminate OCS and uninstall it.
In the past when I had an install to do with SCCM that also required uninstalling an older version of a given application, I typically used the program-chaining technique. That's where you have, for example, 3 or more programs that run in a package
in a sequence and you have Program 3 be set to run after Program 2 does and then set Program 2 to run after Program 1 so you get the desired sequence of Programs 1-2-3 running in that order. So, I created programs to 1) kill Communicator.exe 2) uninstall
Communicator 2007 R2 by doing an "msiexec /uninstall {GUID}" 3) install Silverlight 4) install Visual C++ x86 5) optionally install Visual C++ x64, and then 6) install the Lync x86 or x64 client. That final step was always the point of failure because
I couldn't get the hacked MSI for the Lync Client install to work. I also realized that if Communicator wasn't running when the deployment started, that step would fail and cause the whole process to bail out with an error. That's one of the downsides
of program-chaining, if one step fails, SCCM completely bails on the deployment. This is what also led me to the key to my solution: TASK SEQUENCES.
I'm not sure how many people out there look in the "Operating System Deployment" area of SCCM 2007 where Task Sequences normally live, but I also wonder how many people realize that Task Sequences can be used for more than just Operating System deployments.
One of the biggest advantages of a task sequence is you can set a step to ignore an error condition, such as if you try to terminate a process that isn't running. Another advantage is that task sequences have some very good built-in conditionals that
you can apply to steps, for example, having the sequence skip a step if a certain application (or specific version of an application) is not installed on the machine. Both of those advantages factor highly into my solution.
OK, for those who already think this is "TL;DR", here's the step-by-step of how to do this:
First, you need to extract all the files from the LyncSetup.exe for your needed architectures. We have a mix of Windows XP and Windows 7 64-bit, so my solution here will take both possibilities into account. To extract the files, just start up
the .exe like you're going to install it, but then when the first dialog comes up, navigate to "%programfiles%\OCSetup" and copy everything there to a new location. The main files you need are: Silverlight.exe, vcredist.exe (the x64 LyncSetup.exe includes
both x86 and x64 Visual C++ runtimes, you need them both, just rename them to differentiate), and Lync.msi (this also comes in an x86 and x64 flavor, so if you have a mix of architectures in your environment, get both and either put them into their own directories
or rename them to reflect the architecture).
For my setup, I extracted the files for the x86 and x64 clients and just dumped them each into directories named after the architectures.
Next, move these files into a directory to your SCCM file server, whatever it might be that you deploy from, in our case, it was just another volume on our central site server. Go to the SCCM console into Computer Management -> Software Distribution
-> Packages and then create a new package, call it something meaningful, and then point to the directory on your SCCM file server for the source files.
Now you need to create 3 to 5 programs inside the package:
1. Name: Silverlight
   Command Line: x86\Silverlight.exe /q     (remember, inside my main Lync install folder on my distribution point, I have an x86 directory for the files from the x86 installer and an x64 folder for the files from the x64 installer.
The fact is the Silverlight installer is the same in both, so you only need one of them.)
   On the Environment tab: Program can run whether or not a user is logged in, runs with administrative rights, Runs with UNC name
   On the Advanced tab: Suppress program notifications
   All other options leave default.
2. Name: Visual C++ x86
    Command Line: x86\vcredist_x86.exe /q
   On the Requirements tab: Click the radio button next to "This program can run only on specified client platforms:" and then check off the desired x86 clients.
   Environment and Advanced tabs: same as Silverlight
   (If you have only x64 clients in your environment, change all x86 references to x64. If you have a mixed environment, create another program identical to this one, replacing references to x86 with x64.)
3. Name: Lync x86
    Command Line: msiexec /qn /i x86\Lync.msi OCSETUPDIR="C:\Program Files\Microsoft Lync" (The OCSETUPDIR fixes the issue with the Lync client wanting to "reinstall" itself every time it starts up)
    Requirements, Environment, and Advanced tabs: Same as with Visual C++ and Silverlight
    (Same deal as above if you have all x64 clients or a mix, either change this program to reflect or make a second program if necessary)
Now you need to make the Task Sequence. Go to Computer Management -> Operating System Deployment -> Task Sequences. Under the Actions pane, click New -> Task Sequence. In the Create a New Task Sequence dialog, choose "create a
new custom task sequence", Next, enter a meaningful name for the task sequence like "Install Microsoft Lync", Next, Next, Close.
The task sequence will have up to 12 steps in it. I'll break the steps down into 3 phases, the prereqs phase, uninstall OCS phase, and then Lync install phase.
Prereqs Phase:
These are the easiest of the steps to do. Highlight the task sequence and then in the Actions pane, click Edit.
1. Click Add -> General -> Install Software. Name: "Install Microsoft Silverlight". Select "Install a single application", browse to the Lync package created earlier and then select the Silverlight program.
2. Add -> General -> Install Software. Name: "Install Microsoft Visual C++ 2008 x86". Install Single Application, browse to the Lync package, select the Visual C++ x86 package.
As before, if you're an all-x64 environment, replace the x86 references with x64. If you have a mixed environment, repeat step 2, replacing x86 with x64.
3. Add -> General -> Run Command Line. Name: "Enable Lync Installation". This step gets around the UseMSIForLyncInstallation registry requirement. The Lync client MSI simply looks for the presence of this key when it runs, so
we'll inject it into the registry now and it doesn't require a reboot or anything. It just has to be there before the client MSI starts.
Command Line: reg add "hklm\Software\Policies\Microsoft\Communicator" /v UseMSIForLyncInstallation /t REG_DWORD /d 1 /f
Uninstall OCS Phase:
This part consists of up to 6 Run Command Line steps. (Add -> General -> Run Command Line)
4. Name: "Terminate Communicator". Command Line: "taskkill /f /im communicator.exe". On the Options page, check the box next to "Continue on error". This will terminate the Communicator process if it's running, and if it's not, it'll
ignore the error.
5. Name: "Terminate Outlook". Command Line: "taskkill /f /im OUTLOOK.exe". Check the "Continue on error" on the Options page here too. Communicator 2007 hooks into Outlook, so if you don't kill Outlook, it might prompt for a reboot
because components are in use.
(NOTE: If necessary, you could also add another step that terminates Internet Explorer because Communicator does hook into IE and without killing IE, it might require a restart after uninstalling Communicator in the next steps. I didn't run into
this in my environment, though. Just repeat step 5, but replace OUTLOOK.EXE with IEXPLORE.EXE)
6. Name: "Uninstall Microsoft Office Communicator 2007". Command Line: "msiexec.exe /qn /uninstall {E5BA0430-919F-46DD-B656-0796F8A5ADFF} /norestart" On the Options page: Add Condition -> Installed Software -> Browse to the
Office Communicator 2007 non-R2 MSI -> select "Match this specific product (Product Code and Upgrade Code)".
7. Name: "Uninstall Microsoft Office Communicator 2007 R2". Command Line: "msiexec.exe /qn /uninstall {0D1CBBB9-F4A8-45B6-95E7-202BA61D7AF4} /norestart". On the Options page: Add Condition -> Installed Software ->
Browse to the Office Communicator 2007 R2 MSI -> select "Match any version of this product (Upgrade Code Only)".
SIDEBAR
OK, I need to stop here and explain steps 6 and 7 in more detail because it was a gotcha that bit me after I'd already started deploying Lync with this task sequence. I found out after I'd been deploying for a while that a tech in one of our remote
offices was reinstalling machines and putting the Communicator 2007 non-R2 client on instead of the R2 client, and my task sequence was expecting R2, mostly because I thought we didn't have any non-R2 clients out there. So, at first I just had our Help
Desk people do those installs manually, but later on decided to add support for this possibility into my task sequence. Now, when you normally uninstall something with msiexec, you would use the Product Code GUID in the command, as you see in steps 6
and 7. All applications have a Product Code that's unique to a specific version of an application, but applications also have an Upgrade Code GUID that is unique for an application but common across versions. This is part of how Windows knows that
Application X version 1.2 is an upgrade to Application X version 1.1, i.e. Application X would have a common Upgrade Code, but the Product Code would differ between versions 1.1 and 1.2.
The complication comes in that Communicator 2007 and Communicator 2007 R2 have a common Upgrade Code, but different Product Codes and the "MSIEXEC /uninstall" command uses the Product Code, not the Upgrade Code. This means that if I didn't have step
6 to catch the non-R2 clients, step 7 would be fine for the R2 clients, but fail on non-R2 clients because the Product Code in the MSIEXEC command would be wrong. Luckily, we only had one version of the non-R2 client to deal with versus 4 or 5 versions
of the R2 client. So, I put the command to remove Communicator 2007 non-R2 first and checked for that specific product and version on the machine. If it was present, it uninstalled it and then skipped over the R2 step. If non-R2 was not present,
it skipped that step and instead uninstalled any version of the R2 client. It's important that steps 6 and 7 are in the order they are because if you swap them, then you'd have the same outcome as if step 6 wasn't there. What if neither is on the
machine? Well the collection this was targeted to included only machines with any version of Communicator 2007 installed, so this was not a problem. It was assumed that the machines had some version of Communicator on them.
8. Name: "Uninstall Conferencing Add-In for Outlook". Command Line: "msiexec.exe /qn /uninstall {730000A1-6206-4597-966F-953827FC40F7} /norestart". Check the "Continue on error" on the Options Page and then Add Condition ->
Installed Software -> Browse to the MSI for this optional component and set it to match any version of the product. If you don't use this in your environment, you can omit this step.
9. Name: "Uninstall Live Meeting 2007". Command Line: "msiexec.exe /qn /uninstall {69CEBEF8-52AA-4436-A3C9-684AF57B0307} /norestart". Check the "Continue on error" on the Options Page and then Add Condition -> Installed Software
-> Browse to the MSI for this optional component and set it to match any version of the product. If you don't use this in your environment, you can omit this step.
Install Lync phase:
Now, finally the main event, and it's pretty simple:
10. Click Add -> General -> Install Software. Name: "Install Microsoft Lync 2010 x86". Select "Install a single application", browse to the Lync package created earlier and then select the "Lync x86" program. As before, if you
only have x64 in your environment, replace the x86 with x64, or if you have a mixed environment, copy this step, replacing x86 references with x64.
And the task sequence is done! The final thing you need to do now is highlight the task, click Advertise in the Actions pane, and deploy it to a collection like you would with any other software distribution advertisement. Go get a beer!
Some final notes to keep in mind:
1. You can't make a task sequence totally silent...easily. Users will get balloon notifications that an application is available to install. The notifications cannot be suppressed through the GUI. I've found scripts that supposedly
hack the advertisement to make it be silent, but neither of them worked for me. It was OK, though because in the end we wanted users, especially laptop users, to be able to pick a convenient time to do the upgrade. The task sequence will appear
in the "Add/Remove Programs" or "Programs and Features" Control Panel. You can still do mandatory assignments to force the install to happen, you just can't make it totally silent. On the plus side, the user shouldn't have to reboot at any point
during or after the install!
2. In the advertisement setup, you can optionally show the task sequence progress. I've configured the individual installs in this process to be silent, however, I did show the user the task sequence progress. This means instead of seeing
5 or 6 Installer windows pop up and go away, the user will have a single progress bar with the name of the step that is executing.
3. One step that I didn't consider when I actually did this was starting the Lync client as the user when the install was complete. The user either had to start the client manually or just let it start on its own at the next logon. However,
while I was writing this, I realized that I could possibly start the client after installing by making another Program in the Lync Package with a command line that was along the lines of "%programfiles%\Microsoft Lync\communicator.exe" and then in the Environment
tab, set it to "Run with user's rights" "only when a user is logged on".
4. My first revision of this task sequence has the Prereqs phase happening after the OCS uninstall phase, but I kept running into problems where the Silverlight installer would throw some bizarre error that it couldn't open a window or something wacky
and it would fail. Problem was, I couldn't re-run the task sequence because now it would fail because OCS had been uninstalled, so that's why the Prereqs happen first. It ran much more reliably this way.
5. For some reason that baffles me, when I'd check the logs on the Site Server to monitor the deployment, I'd frequently see situations where the task sequence would start on a given machine, complete successfully, almost immediately start again, and
then fail. I'm not sure what is causing that, but I suspect either users are going to Add/Remove Programs and double-clicking the Add button to start the install instead of just single-clicking it, or the notification that they have software to install
doesn't go away immediately or Lync doesn't start up right after the install, so they think the first time it didn't take and try it a second time.
I hope this helps some of you SCCM and Lync admins out there!

On Step 8 I found multiple product codes for the Conferencing Add-In for Outlook. Here's a list of the ones I found in the machines on my network:
{987CAEDE-EB67-4D5A-B0C0-AE0640A17B5F}
{2BB9B2F5-79E7-4220-B903-22E849100547}
{13BEAC7C-69C1-4A9E-89A3-D5F311DE2B69}
{C5586971-E3A9-432A-93B7-D1D0EF076764}
I'm sure there's others one, just be mindful that this add-in will have numerous product codes.

VS 2010 app looking for CR Runtime v 11.5.3700

Someone at my company developed a piece of simple C# console app code (below) to create .rpt files in a folder to be emailed later.
They did this work on a machine with Visual Studio 2010 and Crystal Reports v 11.5. The created application will be installed on our client's Windows Server 2008 R2 machine.
ReportDocument doc = new ReportDocument();
doc.Load(DOC_PATH);
CrystalReportExtensions.ApplyCredentialsFromConnectionString(doc, Con);
CrystalReportExtensions.ApplyCustomParameter(doc, string.Format("[Table Name].DOC_ID={0}", DOC_ID));
doc.ExportToDisk(CrystalDecisions.Shared.ExportFormatType.PortableDocFormat, EXPORT_FILE);
When I run the application on the Windows 2008 R2 Server, it doesn't work because it cannot find the correct version of the Crystal Reports Engine, so it throws that error. In fact, when I look under C:\Windows\Assembly on the server, I see that it does not have any version of Crystal assemblies installed.
So, I tried to find the correct runtime to install so that the application could create the .rpt files and everything would work, but I cannot find the correct version. I have found 10.2, 10.5, 13.0, and many other things that wouldn't even begin to install. The phone support for Crystal is not equipped to handle these types of questions. They can only provide general knowledge and links to downloads for runtimes, which are often incorrect or not useful.
What do I need to do to get this to work?
1. Is there indeed a CR runtime for v 11.5.3700?
2. If not, then what can I do to install another runtime and reset the VS references to that version?

The use of the version 11.5 runtime with VS 2013 is NOT supported. Here's what needs to happen:
1. The developer needs to download the latest version of the Crystal for VS install executable here: http://scn.sap.com/docs/DOC-7824. You'll also need one of the runtime installs from this page for the machine where the application will be deployed.
2. The application needs to be set to reference the version 13.x Crystal assemblies instead of the 11.5.x version. Then it needs to be recompiled.
3. The appropriate version of one of the Crystal for VS runtime installs needs to be installed on the machine where the application will run.
-Dell

Hyperlinks in CR Viewer for VS2010 drop parameters

Related to post in Beta forum [Re: CRVS2010 Beta - Hyperlink translator dropping parm|Re: CRVS2010 Beta - Hyperlink translator dropping parm]
Reports containing hyperlinks with query parameters e.g. 'http://www.test.com/page.aspx?id=366363' drop parameters on transfer from report e.g. above link would transfer to 'http://www.test.com/page.aspx?id'
I believe this is because hyperlinks are rendered as javascript which is executed on click, and the function contains "functionName('url=[url of hyperlink]')". Any occurrences of '=' in a hyperlink break the syntax of this javascript function call.
This was assumed fixed in the RTM version, but it is still present.
Having convinced my manager to port our applications to CR for VS2010 this is and incredibly frustrating bug to discover too late. I'd hate to have to roll back to a previous version. If this has indeed been fixed, please advise as to the version of CR we should install, including runtime for deployment.

On [this|CRVS2010 Beta - Hyperlink translator dropping parm; thread, tracking number ADAPT01481748 is quoted for this issue.
In a post from Oct 21, 2010 at the above thread, I posted the following:
1) The issue has been reported.
2) I can not guarantee that it will be fixed.
3) If it is fixed today, I would not be able to give you the fix in any case.
4) If it is fixed, the fix will be in the RTM product, or possibly a subsequent Service pack.
5) If I get an update from PM, I will copy it here.
6) If the product releases before an update from PM, we can look and see if the issue is resolved before you make any future investments.
A possible work-around is given by Roger Adams in the same thread, post dated Oct 27, 2010:
"A possible workaround is if you can convert the querystring into a routed URL. "
All I can give you at this point is that R&D is aware of the issue. Service Pack 1 is scheduled to be released end of February 2011. No guarantees that a resolution to the issue will be included in SP1. I will check with Program Management and see if it is on their list. However note that even if it is on the list, it may not make it inot SP1.
Ludek

CR2010 for vs2010 Runtime to deploy on client available or not ???

Similar Messages

Maybe you are looking for