Feeds:
Posts
Comments

Archive for August, 2009

You can find the solution in this blog: http://www.tek-tips.com/viewthread.cfm?qid=1506766&page=6
 
— Returns current Date/time
Select GetDate()

— Returns float representation
Select Convert(Float, GetDate())

— Removes fractional component
Select Floor(Convert(Float, GetDate()))

— Convert back to DateTime, no time component
Select Convert(DateTime, Floor(Convert(Float, GetDate())))

Read Full Post »

I restored one of the databases and when trying to run one of the MDX reports, I get the following error about trustworthy assembly. To resolve this, run the following on the database you have just restored.
 
TRUSTWORTHY is required to be ON for the RunMDX stored procedure to function.
 

ALTER

DATABASE [database_name] SET TRUSTWORTHY ON

Read Full Post »

I converted reports from 2005 to 2008. When opening one of the report data sources, it threw the following error:
 
When creating new datasources using the same name throws an error stating
"Specify a valid name, The name cannot contain spaces, and it must begin with a letter followed by letters, numbers, or the underscore character (_).
 
Apparently spaces are not allowed in SSRS 2008. Any data source name that contains spaces migrated from SSRS 2005 needs renaming.  Solution: remove spaces from the data source name.
 
This has been confirmed as a bug by Microsoft – "We have fixed this issue for the next release but unfortunately there is no easy work around for the current release other than renaming the datasources and updating reports."
 

Read Full Post »

Open the SSRS 2005 report solution in the Visual Studio/BIDS 2008. If it throws the following error, close the solution then run the command "devenv.exe /ResetSkipPkgs". Open the solution again and it would have been converted to 2008.
 
"report project cannot be opened because its project type is not supported by this version of the application visual"

Read Full Post »

I had a problem with the execution of a package in SSIS and the following error was thrown and the package stopped at the OLEDB source.
 

SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER.  The AcquireConnection method call to the connection manager "OLEDB Source" failed with error code 0xC0202009.  There may be error messages posted before this with more information on why the AcquireConnection method call failed.

By looking at the above errors, I concluded that there are 2 places need checking:
1) Global package configuration
2) Config.[SSIS Configuration] table
 
Both Global package configuration and Config.[SSIS Configuration] table showed the following connection string for the OLEDB source:
          Data Source=localhost;User ID=test;Initial Catalog=AdventureWorks;Provider=SQLNCLI.1;
Notice that the password has not been included in the connection string. For very odd unknown reasons, the password has been opted out as this is the first time it happened. Once the password is included in the connection string, the package executes successfully.
Data Source=localhost;User ID=test;Password=test;Initial Catalog=AdventureWorks;Provider=SQLNCLI.1;
Other web blogs suggest checking the ProtectionLevel setting, which I did but it did not help resolving the above error.

Read Full Post »

 I was getting the above error whilst trying to print a web report from report manager.

 
I did a quick research and found out that Internet Explorer requires modification to allow AcitveX control in order for the print function on web reports to work.
 
The following is extracted from http://forums.asp.net/t/1292337.aspx. Both solutions work in my case, however, I didn’t have to do steps 3, 4, 5, 6 and 7.

SQL Server Reporting Services uses an ActiveX Print control to control the print functions in Windows Internet Explorer, this problem may occur if the ActiveX components are not installed. As you mentioned that you met the error message even you have installed that components, I just want to make sure if you have installed the ActiveX components in the right way. Try to check the following setps:

1. Start Windows Internet Explorer.
2. On the Tools menu, click Internet Options.
3. On the Security tab, click Local Intranet, and then click Sites
4. Click Advanced.
5. Type the URL for the computer that is running Microsoft Dynamics CRM server in the Add this website to the zone box, and then click Add.
6. Type the URL for the computer that is running Microsoft SQL Server Reporting Services in the Add this website to the zone box, and then click Add.
7. Click Close to close the Local Intranet dialog box, and then click OK.
8. On the Security tab, click Custom Level.
9. Click Enable for each component that is listed under ActiveX controls and plugins.
10. Click OK to close the Internet Options dialog box.
11. Exit Windows Internet Explorer, and then start Microsoft Dynamics CRM 3.0.
12. Try printing the report.

If you continue to experience the problem that is described in the "Symptoms" section, manually install the ActiveX components. To do this, follow these steps:

a.  Locate the Report Server\bin folder.

Notes

• If you run Microsoft SQL Server 2000 Reporting Services, the folder is located in the following location:
C:\Program Files\Microsoft SQL Server\MSSQL\Reporting Services\ReportServer\bin
• If you run Microsoft SQL Server 2005 Reporting Services, the folder is located in the following location:
C:\Program Files\Microsoft SQL Server\MSSQL.4\Reporting Services\ReportServer\bin

 
b.  Right-click the RSClientPrint.cab file, and then click Extract. Extract the file to the folder in step 12a.
c.  Right-click the RSClientPrint.inf file that you extracted in step 12b, and then click Install.
d.  Try to print the report.

Read Full Post »

 Answer: Right click on the OLE DB source then choose "Advanced Editor". In the Advanced Editor window, choose the last tab, i.e. "Input and Output Properties", then choose "OLE DB Source Output" on the left. Look for IsSorted under Common Properties on the right. Set this to True then go to Output columns and remember to set the SortKey Position to either positive value or negative value but not 0 before the output of the OLE DB source can be fed into  "Merge Join" transform.

Read Full Post »

Older Posts »

%d bloggers like this: