Sunday, June 19, 2011

Migrating Email into Google from existing server

I was testing the migration of email being hosted on Yahoo Business to Google Apps Business. Google has tool in the Account options listed as 'Get mail from other accounts:'. You can use this tool to migrate emails from the existing inbox into the new gmail inbox.

However, in my migration the email addresses were the same name because I wanted to use the same domain and user name and only switch who hosted it. Google gave me an error because I was trying to use the same email address.

For example you are trying to move 'junk@junk.com' on yahoo to 'junk@junk.com' now hosted on gmail. For me, I received an error trying to do this. So to get around this error, type that you are migrating 'junk1@junk.com' then proceed to give it the correct Login credentials for the account. That should work! It did for me.

Actually, I am not really sure why this error happens, it may be totally legit. Maybe Gmail just wants the stuff coming in to be uniquely name or just that account move uniquely named. I have no idea and there was not info in the error message....

Hope that helps!

Monday, June 13, 2011

VS 2010 Report runs locally, but not on server

Last week, I attempted to work with the VS 2010 reporting component. It took a bit of time to figure out setting up a data source...getting a decent layout, etc. All I really needed was a basic report that allowed the user the option of exporting the data to Excel. The VS built-in tool did everything I needed.

Once I got it running on my local server, I moved it up to the production server that was provided by a third party vendor. However, once I moved out there, I received the error: 'Local report processing requires FullTrust Code Access Security permissions, which is unavailable to the calling code. Grant the application FullTrust permissions or use ServerReport to execute the report remotely.'

After modifying various reporting options inside the reporting component and then in the code-behind, nothing seemed to work. Until I found a post that mentioned the web.config settings. And that resolved it. Make sure you have moved all of the related reporting web.config items (I did not have everything initially...) then try adding the following tag in the <system.web> section:

<trust level="Full" />

This change did it for me. Hope that helps!