I am proud to announce the availability of the following positions for talented candidates, if you feel that you are qualified to fulfill these positions, please feel free to submit your resume and we will be contacting you immediately. I would kindly ask only “ready” people to send their resumes, honestly we cannot look into resumes without having enough qualifications, we are looking for candidates to start working on projects from day five, the first 4 days will be an orientation to get introduced to our standards and how we do business.
This morning I worked with one of the customers on configuring the database backups, and stuck with an issue that after finalizing the Maintenance Plan the job been generating an error, getting into the job history I have seen the below dumb message: Unable to start execution of step 1 (reason: line(1): Syntax error) Luckily I found the below articles about this subject and it helped: http://social.msdn.microsoft.com/Forums/sqlserver/en-US/dc52e0d9-af14-46b9-9904-29b9afa798cd/syntax-error-executing-maintenance-plan-job?forum=sqldatabaseengine http://www.sqlserver-expert.com/2011/08/unable-to-start-execution-of-step-1.html I found few difficulties while looking into the “package” mentioned in the resolution and therefore I though I would share a screenshot, adding a slash “” to the beginning of the text worked like a charm: Regards, — Mohammad R. Daoud MVP – MCT MCP, MCBMSP, MCTS, MCBMSS +962 – 79 – 999 65 85 firstname.lastname@example.org http://www.di.jo
I got a very interesting case few months back, one of my customers implemented the Management Reporter and tried to implement their existing reports, it went well but for the reports that uses the Analytical Accounting Budgets that has filters over specific dimensions, budget amounts were not pulled at all. At that time I tried very hard to resolve the issue with no luck, and therefore I had to install the FRx and work out the reports there till getting this resolved by Microsoft
Part 3 – Resolving Microsoft Dynamics GP 2013 Web Client Functional Issues Last week, Part 2 of this series dealt with resolving Web Client implementation issues. The key to remember is any exception condition prior to the Microsoft Dynamics GP login window is treated as an implementation issue and as noted back in Part 2, there are two major processes – steps, if you will – in compiling information that will lead to resolving Web Client exceptions. Just like with the implementation issues, you must compile information related to all application exceptions