I have Upgrade my report file Crystal Report 8.5 to ver.-9.00. Report files are intragated with vb6(No external .rpt file). From many reports i upgrade 18 report file. When i run the project 18 times reminder me For "Crystal Decision Registration Wizard".Till i don not close project Every thing OK. If i close the project and reopen then again 18 times reminder me For "Crystal Decision Registration Wizard".
I have Upgrade my report file Crystal Report 8.5 to ver.-9.00. Report files are intragated with vb6(No external .rpt file). From many reports i upgrade 30 report file. When i run the project 30 times reminder me For "Crystal Decision Registration Wizard".Till i don not close project Every thing OK. If i close the project and reopen then again 18 times reminder me For "Crystal Decision Registration Wizard".
Simple,
first create an exe file with Visual Basic, write form load event just end
private sub form_load()
end
end sub
yes..your exe just start and end. Then compile it and rename it regwiz.exe
then, search regwiz.exe in your local drive C (before search, change the directory setting->view, show hidden files and folder... because sometimes if any file located in a directory which is hidden, windows can not find it).
Then replace your new regwiz.exe with the old one.
Crystal already will open 18 times but it will not wait your attention :) do not delete... I tried it will create
Related
I am new to this field and have no idea how this works. We have BusinessObjects installed on one of our windows servers. We can access the reports after hitting the URL. Now I am trying to make some changes on the reports, I can open this report from Crystal Report > Open > Enterprise > local
I checked Web Content under BO installation path, FileStore but I am not able to find out what is the location of this Enterprise. Can someone tell where we can find these reports on our windows server?
By default, the filestore (FRS) is located in:
C:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\FileStore
However, it is very rare that you'd need to access files in the FRS directly. If you do, you'll need to know the exact folder path and file name. In BI launchpad, open up the report's properties, and the path will be displayed as "File Name". This is the logical path relative to the FRS parent.
Once you have made your changes to the report you need to save it back to the BusinessObjects platform. If you are using Crystal Reports for Enterprise here is a video on how to do that. If you are using Crystal Reports 201x check out this video.
I have developed an add-in (xlam) for Excel 2013 (some users have 2010) that contains half a dozen macros.
I used to load it from UNC path on the server and that worked great, but every time I need to update it, all the users have to quit excel because it's locked. There are now too many users in multiple buildings, so this is approach is no longer viable. I need to find a way to deploy new version of the macro-enabled workbook and the add-in, so that it works on local PC's.
We use Microsoft SCCM at work, so I figured, no problems, I'll just deploy the add-in to the users' local add-in directory (%APPDATA%/Microst/Addins). This works fine. The problem is when I send them an updated version of the macro enabled worksheet that uses the add-in (which changes fairly frequently), %appdata% has been expanded to my user name and of course the path to the add-in is not valid on someone else's machine.
I figured, no problems, I'll make a common dir on everyone's machine (C:\Program Files\CompanyName\Addins) and install the add-in there, so that the path is valid on all machines. I open my workbook, load the add-in and test it. Works great.
I have a DisplayVersions macro that shows the correct version and the path I just loaded the addin from (C:\Program Files\CompanyName\Addins) as the Addin path.
I save the worksheet, quit Excel. Next time I open it, it's trying to load it from my %appdata%/Microsoft/Addins directory and of course it doesn't exist there. It never asked me if I wanted to copy it there.
This is driving me mad. There HAS to be a way to deploy an add-in and a worksheet, so it will work from all local PC's
Anyone got any suggestions
Regards
Mark
I'm using MS Business Intelligence Development Studio.
This morning, when I open one of my dtsx files, BIDS just sits there, stuck validating one of the tasks in the particular dtsx file that I'm trying to open.
Are there things that I can do to fix this problem?
Has anyone encountered this before?
David
I would set the DelayValidation property on the package and control flow tasks to True. So that the package doesn't validate all the tasks every time I open it. It will speed up the process of opening the packages but the package will validate any changes in the connections or schema only during run time. If you click on the task that has a connection or schema, it will still validate even if you have DelayValidation set to true.
As the other responders suggest, you want to select Work Offline from the SSIS menu, then you want to open your SSIS project.
However, when you open Business Intelligence Developer Studio, there may not be an SSIS menu. If this happens, create a throw-away SSIS project (File | New | Project | Integration Services Project). Once the throw-away SSIS project is open, there will be an SSIS menu, from which you must select 'Work Offline'.
Next, from the Solution Explorer, right click on SSIS Packages, and select Add Existing Package. Specify File System in the Package location control, the specify the file path to the DTSX file in the Package path control.
At this point, you can open your intended SSIS package without the excruciating delay.
My manager asked me to update the .rdl file from prod to dev. But before doing that I have to keep that old report as it is and have to create a duplicate report on same server and that too be I am working on browser.
I have downloaded the the .rdl file and renamed the report as *_old also. But I am not able to understand how to create another same report with same datasources and everything.
I can see an option update next to edit button. I am assuming that if I get a duplicate report on the same server I can update the .rdl file with that update button.
Please help me with this problem.
- Download the report RDL file from the report manager.
- Rename the rdl file eg. MyReport1_old.rdl
- Upload the report rdl file from the report manager.
Now you will have the original report (MyReport1) and the copy of it(MyReport1_old).
We're about to start development of a number of reports using Jasper Server Reports version 3.7.0 CE.
Does anyone have any recommendations as to how best to manage version control with this development, given that the structure of the report units is managed in the database and through either iReport or the web front end?
In fact you can import/export to a directory structure using the js-import/js-export scripts, but then you can't edit these files directly with iReport.
Does anyone have any pointers?
This is problematic. I have established a subversion repository to allow standard reports delivery to be versioned but it is a real pain because jasper does not make this even a little bit easy.
I created a maven project with an assembly descriptor so that "src/main/xml/resources/Reports,adhoc,Domains, etc" can be packaged up in a zip that is pushed to our maven repository.
The biggest problem is that you can't just develop adhoc and input controls merely by modifying XML files. The developer has to import what is in source control into a working jasper server, modify the reports or add new ones (after making sure that his organization and datasources are configured) and once he's satisfied that the report(s) works, export the resources to a directory or zip file, manually modify all references in the exported files from datasources and organization specific resource locations back to "generic" before checking in his changes.
When importing into jasper, the same process has to be done in reverse. The generic paths and organization values have to be converted to the developer's organization so they can be easily imported/updated and he can prove out that the full "round trip" works properly before checking in.
To make the export/subversion checkin easier, I created an ant build file which lives in the maven project's root dir. The build prompts (or will read a properties file) to determine the exported zip location, the organization id of the exported tree. It then opens exported zip file from jasper, explodes it, performs text replacements on the files, resets the "createdDate" and "updatedDate" elements to something standard (so that the developer does not end up checking in files that haven't actually changed since jasper does not preserve the date values), and then copy the files into the subversion tree.
For the import process (from the subversion tree into jasper) we have a script that takes as input the organization id and then modifies the versioned xml files to the appropriate values so that the entire tree can be easily imported/updated into their organization.
The reason this level of complexity is required is to allow us to create the same standard reports in a multi-tenant environment, plus jasper's notion of deploying reports is absolutely bizarre. I'm not sure it would be possible to make this process more difficult if you were intending to do so.
If I was in your position I would have established this kind of process:
end of development session: export all reports to a directory structure in a project under version control
commit the project
before next development session: synchronize the project with svn repository
import directory structure to Jasper Server Reports
continue development
Not sure if someone found posted the solution.
This is what I have done for existing reports.
export reports from jasper server
modify file names from .data to .jrmxl
modify subreport calling to add extension (like in A.jrxml should have subreport name as B.jrxml
modify add .jrmxl to datafile,label and name in report unit xml files.
If you are creating new report on jasper server, it simple
give .jrxml to name and label while adding jrxml file. thats it.
Now you can work same files in local and import same to jasper server.