Patrick.O.Ige

Good SSRS Expression  tip and tricks here
Enjoy

 

I just came across this  article and i taught its a good resource for BI Developers and other Analysts.
Hope it helps

 

 

When working with Microsoft Chart Control.
You sometime get error:
1)Error executing child request for ChartImg.axd
or
2)No http handler was found for request type 'POST' and Chart control

For error 2 you just need to add

<add path="ChartImg.axd" verb="GET,HEAD,POST" type="System.Web.UI.DataVisualization.Charting.ChartHttpHandler, System.Web.DataVisualization, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" validate="false" />

to the handler in your web.config

Solution to error 1:
It could also be  a permission problem with the image not found error.
Set the "Allow modify" permissions on your image folder (per default it is "C:\TempImageFiles" for the account under which your website is running.

Another solution i found out is you will have to set your website to application pool to use "Classic Asp.net" - This is for IIS 7.0

Hope it helps

I have a WSS v3 server with SP1 and i was looking at upgrading the search to MS search express 2008.
So i taught let me upgrade it to SP2.
Donwloaded the trouble and then installed it and it went like a breeze.
Everything went ok only i didn't test whether the search was working(MY FAULT -trusted MS)

After a while i got an email from a user saying search isn't working.And i taught i'll just restart the search service and it will be fine.But that didn't do the trick

Look a the ULS logs and Event Viewer and found lots of troubles liek below:):


The start address <sts3://myserver/contentdbid={6a68a5ab-2b97-419f-9e88-57875d494f39}> cannot be crawled.
Context: Application 'Search index file on the search server', Catalog 'Search'
Details:
    The object was not found.   (0x80041201)

After doing some research i found its a common error with different solutions but nothing specific.

Funny enough the search was working before installing SP2
So the error didn't make sense to me at first.

See similar errors here

Later i came across :
Method 1 :Disabling the loopBack check
Method 2 : Specify Hostnames
And you will have to do this in the registry  See how to do it here

But tried all that but still no LUCK

So i taught maybe i should look at my default content access accts and the search acct. But they all have access to the database.

Also did a fullcrawl from the command line but nothing.

Later started looking  at the AAM(Alternate Access Mapping) maybe somethings had changed but all remained the same.
I later found Ivans post here about  AAM's and i must say its a MUST READ.
But after going through that i didn't find anything that could solve my problem.

I also came across this post by MVPs and one person reckons you might have to re-install  WSS  

I now taught of looking at site collections and subsites to make sure all the access is OK  etc
After i checked the root site http://myserver:PORTNUMBER and bingo i got a http 404 error which means the site wasn't exisitng thats why it couldn't start the crawl at the root address.

So i wenu to the Sharepoint Central Admin > App Management > Create Site Collection and created a blank team site on the root site.

And bingo it worked like a charm

Hope this helps.

Just to let everyone know that
Sharepoint 2010 and Office 2010 is on the way

Sure many sharepoint Admin/ Developers/Architects must have come across this issue when trying to  uninstall and re- install Sharepoint 2007.
I have uninstalled sharepoint instance before just by going to the Add Remove programs and it was a breeze.
But on my Dev server when i tried the same but nothing basically happened. The status bar did show as if it was uninstalled but when i go back and check nothing was removed :(

I later found this which did help :www.howtonetworking.com/msapps/wss14.htm

Which stated different ways to uninstall it....
But after taking all the steps posted on that site above you have to remember to do one thing  STEP 7 in METHOD 2.
I actually did it but after running the sharepoint config wizard i get the error:

The language is not supported on the server

When i looked the the registry i couldn't find the entry so i added it manually and after that the error dissapeared.

But as the wizard was running to configure the Sharepoint_Config database another error popped up :(

MSSQLSERVER login failed for user 'MACHINE or DOMAIN\user'. [CLIENT: <local machine>]

This error is very common as i found scenarios were it wasnt only related to  Sharepoint but to other products like SQL Reporting services etc...

The main problem is that when you remove a DB or put it Offline that error basically starts every minute.
This happens because Sql Agent is responsible to 

Solution(not related to Sharepoint):
For those of you that have installed an ASP.net application or state server in SQL Server, you will have to use the aspnet_regsql tool to remove it.  Manually deleting the databases or taking them offline will produce these errors.

Here is one of them that doesn't relate to sharepoint and you can read more  here


Post and Solution related to  Sharepoint: here
Solution:
You need to go into sql server management studio and disable the job called SharedServices_DB_job_deleteExpiredSessions

Also see this post here

Hope this helps

 

I was trying to export data from a txt/csv file to sql server table.
After setting up the package and executed it .It worked if the sql server destination is on the same server were i ran the package from.

But when i tried  to export the data to a different server i get the error:-

[SQL Server Destination [2625]] Error: SSIS Error Code DTS_E_OLEDBERROR.  An OLE DB error has occurred. Error code: 0x80040E14. An OLE DB record is available.  Source: "Microsoft SQL Native Client"  Hresult: 0x80040E14  Description: "Could not bulk load because SSIS file mapping object 'Global\DTSQLIMPORT              ' could not be opened. Operating system error code 2(error not found). Make sure you are accessing a local server via Windows security.".

After doing some search i found this great article.
Which stated that  SQL Server Destination that cannot access a remote box because BULK INSERT will not be able to access the memory space of a remote machine.
So the way to go is to use OLEDB Destination.

One more thing though is you could setill get error after switching to OLE DB Desitnation and you might need to re map your columns to get it to work :( especially if it was set as SQL server Destination.

Tip: Make sure you use SQL SERVER Authentication when using the remote option

Hope that saves your time.

I solved a problem identical to the description of this problem with SQL SERVER and you can see my post here;
and I’ll share the solution for oracle below.

After you have configured the Oracle data source (and worked your way through the errors) and the data source appears in the library - the problem cannot be solved with the configuration tools in SPD.

 Go to the ‘_catalogs/fpdatasources’ folder in the folder list panel of SPD.  Find the XML file that corresponds to the data source in error as it appears in the data source library.

 Double-click on the XML file to open it up in SPD.  The find the connection string attibute.

Simplify the connection string to just: Data Source, User ID and password.  (E.G. “Data Source=XXX;User ID=XXX;password=XXX”
~ Replace XXX with your parameters.)
Set the attribute ProviderName=”System.Data.OracleClient”
If you don’t have an Oracle provider for the SPD that works, I used _designer:Provider=”MSDAORA” and it worked form me.
 
Save the file and close it.

Test the data source in an existing data view or create a new data view.

I hope this solution the works for you.

Good Luck!

 

Procedure or function has too many arguments specified?

When i use a stored proc and don't name it the same params as the column names i get this error.

My solution was to only make sure your stored proc runs in Query Analyzer and make sure if your column name is e.g lastname then param name must be @lastname.

If i use a different param name to the column name and i look at my sql profile i see this:

exec pr_updategetLastMonth @doc = NULL, @do = NULL, @ipa = NULL, @cdate = NULL, @title = N'N79', @DisplayOrder = N'187', @CreationDate = N'5/04/2009 5:06:33 PM', @Document = N'Nokia6260Slide.pdf', @IsPersonal = 1, @sid = 249

 Its basically adding the params twice like above(AS YOU CAN SEE above @doc is the same as @Document and @do the same as @DisplayOrder etc..

Anyone with more updates on this...

Using VS.NET 2005 i was on a project and tried using the TABS in AjaxControl kit
I was sure the version was 1.0.61025.0 but anytime i compile the project i get the error :

The type 'System.Web.UI.ScriptManager' exists in both 'c:\Windows\assembly\GAC_MSIL\System.Web.Extensions\3.5.0.0__31bf3856ad364e35\System.Web.Extensions.dll' and 'c:\Windows\assembly\GAC_MSIL\System.Web.Extensions\1.0.61025.0__31bf3856ad364e35\System.Web.Extensions.dll'   

I did all i knew to add the right TAGS in web.config but with no luck. Funny enough i could get the page to load on my local server but not on production when i deploy it.
I later created another project using VS.NET 2008 with the same setup and looking at the web.config noticed there was other tags that was included that wasn't in the previous project e.g

<runtime>
        <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
            <dependentAssembly>
                <assemblyIdentity name="System.Web.Extensions" publicKeyToken="31bf3856ad364e35"/>
                <bindingRedirect oldVersion="1.0.0.0-1.1.0.0" newVersion="3.5.0.0"/>
            </dependentAssembly>
            <dependentAssembly>
                <assemblyIdentity name="System.Web.Extensions.Design" publicKeyToken="31bf3856ad364e35"/>
                <bindingRedirect oldVersion="1.0.0.0-1.1.0.0" newVersion="3.5.0.0"/>
            </dependentAssembly>
        </assemblyBinding>
    </runtime>

The Solution:
After i added these tags above  to the web.config before the end tag </configuration>
It worked like a charm

Enjoy and save your time

To resolve this issue, you must change your development machine .net security configuration since you are accessing items across the network.
In the event that you need this ability at runtime, you must change the trust level in your config file to full.

However, since this is only in development, I can change my local PC's security by going to Start > Control Panel > Administrative Tools > Microsoft .NET Framework 2.0 Configuration.

After it fully loads (sometimes takes a bit), fully expand My Computer in the navigation tree and click Runtime Security Policy. In the right hand pane, choose Adjust Zone Security.

Leave the default option (Make changes to this computer) and hit next. Choose Local Intranet and change the trust level to Full Trust.
Then choose next and then finish. Restart Visual Studio 2005 and you should be all set.

Hope that helps

Some useful SSIS stuff:-

Enjoy

I have a SSIS package that loads data from a Sharepoint List using s Sharepoint List Source component.
When i run the package from V.S NET it works well and the data destination is to a sql table.

But when i create a job for it and schedule it i get error:
Failed to open package file "Package.dtsx" due to error 0x80070005 "Access is denied."

I spent time looking at the history of the job and all i could see is that the job failed saying  it was was invoked by me but i noticed its been executed by another USER :(

After pulling out my hair and making sure i granted the acct running Sql server agent admin access but still didn't work.
I later came across PROXIES you can find them under the Sql Server Agent Folder

There s also a a Proxy tutorial here.

After i configured the proxy and used it to run the job as specified in the articles above. The job worked like a charm:)
** Remember you have to create credentials first before you see them when creating a job.To do that just go to your root folder in SQL SERVER Management Studio and right click > Security > New > Credentials.

Hope that helps and keep integrating

I decided to install sql server 2008 and all went well suprisingly
But after trying to connect to Reporting Services 2008 and tried running Reporting Services Configuration Manager
I get error :"No report servers were found. Details: Invalid namespace"
Below is a solution i was from one of the MSDN posts:

Steps to modify the ReportingServices.MOF file to fix this issue:

 

1.       Locate the existing MOF file (example: %ProgamFiles%\Microsoft SQL Server\MSRS10.SQL2008\Reporting Services\ReportServer\bin\reportingservices.mof would be the default location for a Reporting Services instance named SQL2008).

2.       Copy this reportingservices.mof to reportingservicesalt.mof (or some other unique name).

3.       Notepad reportingservicealt.mof

4.       Choose edit->replace…

5.       In the dialog, in the Find What: text box enter the modified instance name (for an RS instance named SQL2008, the modified instance name is RS_SQL2008), in the Replace with: text box enter the instance name unmodified (so for an RS instance named SQL2008, just enter SQL2008).

6.       Press the Replace All button.

7.       Save and close notepad.

8.       From a command window at the same location as the results of step 1, type MOFCOMP REPORTINSERVICESALT.MOF (or whatever the name from step 2 was).

 

Now the configuration tool should work with the following exception, if the RS instance name contains an underscore (_), a dollar sign ($) or a hash (#), then step 8 will fail and the user will need to re-install the Reporting Services instance with a name that does not include any of these three characters.

There is  also a detailed solution here and it works.
Enjoy

Hi,

I was gettng this error when trying to call the Sharepoint's webservice from my asp.net page.

The resolution for this is putting the following code in the web.conig.

i.e. enable impersonation in your web.config and deny anonymous access in IIS

<identity impersonate=”true”/>

Hope this helps